There is also a setting for Session Quota. This sets a limit on the amount of data that can be sent in a single backup session. Any data that is remaining to be backed up will be backed up during the next backup session, and subsequent backup sessions if necessary.

It is our opinion that business clients need to know that backups will happen regardless of any contingency, including breaking their quota. Most service providers have stairstepped contracts that call for a user to simply pay more for more storage space when he breaks his quota - similar to the way cellphone contracts are handled.

Refusing to accept a backup for any reason other than nonpayment, including quotas, is simply bad business practice. Above everything else, clients need to be able to rely on their backups.

Instead of halting backups, increase fees according to a schedule spelled out in the service contract.

See also: Why does it take so long to do a backup?

There is a separate function that you can set which will change this "soft" quota to a "hard" quota, which will prevent further backups when an account reaches its quota.

However, we get requests for recommendations from some clients who want to operate their own SMTP server.

We recommend the Advanced Email Redirector from mailutilities.com which can be found at the following link.

http://mailutilities.com/adr/

2. Auto-Select INCLUDES and EXCLUDES

3. Folder/File Selection with only Auto-Select EXCLUDES

Folder/File selection method one involves simply Green-Checking files and folders, and excluding files and folders within that selection. Method 1 is good for backing up specific files and folders quickly

Method 2, Auto-Select INCLUDES and EXCLUDES, is the most thorough method but takes the longest, and can potentially generate huge backups. This is fine if that's what you want, but it's also easy to pick up a lot of relatively unnecesary files.

Method 3 is a combination of method 2 and method 1.

Methods 1 and 3 are pre-optimized before being fed into the scanning process, scanning root and sublevel folders separately to improve the speed of the process.

INTERACTIVE SELECTIONS

While selecting files, you can use the right-click menus to easily modify your selections based on the files you see, for example, you can right-click on ABC.ZIP and select the Auto-Select exclusion of all ZIP files. You will immediately see any other ZIP files receive a Red X.

USER-TYPES Trump FILE-TYPES

Auto-select offers two method of defining filters. The File Types are taken from the list of filetypes maintained by windows, and can vary based on applications installed and user modification, so cannot always be depended on from one computer to another.

User-Types are your user-defined collection of file types, by extension. User-Types take precedence over File-Types, and both can contain a list of file extensions. Normally, a Red-X TRUMPS a Green Check except with User-Types, where a Green-Checked usertype can reverse a Red-X in a File-Type for the same extension.

Example File Name without original name: 200302131250.16B69FD90000000004200000285.001

Example file name including original file name: Employee.doc_200306011117.79292AB50000000670720000001.007

Employee.doc Original Name 

_ Separator
20030601 Date (6/1/2003)
1117 Time (11:17 AM)
. (dot)
79292AB5 Unique Checksum
000000067072 Original File Size
0000001 File Sequence Number
. (dot)
007 Backup Set Code

If you want to see entire filenames, set Storename Characters to something large, like 128 or 256.

When RBS publishes an upgrade, we publish for both the Server and the Endpoints (clients). When you are notified by email or by a popup on your RBS Server, download the update and apply it to your RBS Server. This will update both your RBS Server and the unbranded core Endpoint software files.

Build an endpoint installer with the new version, and test it. When you are ready to deploy to your end users, select Setup->Endpoint Upgrades (or Client Upgrades) in your Server's Web Console. Set "Enable Automatic Software updates" to TRUE and click the "Upgrade Clients" button.

Overall "normal" business data compresses to about 50-60%. Some files compress to 90%.

We are not going to turn off your software after you buy it. The evaluation version has a time limit, but there is no such limit on the live package. As part of your Maintenance Subscription we offer a Server Locator service which works as long as your Maintenance Subscription is in force. You are not required to maintain that subscription, however, and your software will continue to operate without it, only without the added services we offer, such as the Server Locator service. Your software will work without the Server Locator service.

This calculation considers only data transmission time in an optimally-configured system. Time for the Client software to prepare a backup by doing its compression and encryption is not a part of this calculation, and can be effected greatly by constraints outside the control of the software.

Transmission speeds can vary widely from this calculation depending on outside factors like the configuration of the software, routers, firewalls, anti-virus software, ports, and CPU speeds.

This calculation is for optimal connections. It is not intended for use as a benchmark or acceptance test for the software. This calculation is based on the way RBackup Remote Backup software transmits and verifies files, NOT on any theoretically "perfect" file transmission formula. Our software adds overhead for authentication which is often very difficult to predict, as it is based on the current health and speed of the network connection between the Client and the Server, as well as the type of data and number of files in a backup set, and the speed of the processors in the Client and the Server.

Your transmission speed will vary. Use this only to estimate.

If your backups seem to be taking too long, please read this article: BACKUPS TAKE A REALLY LONG TIME.

Here is the Calculator: http://remote-backup.com/calculators/

RBackup's Backup Exclusions list contains a list of items that will be excluded from backups, and they will also be excluded from the file selection menus. By default, the recycle bin is included in the list.

You can edit the exclusion list in the Web Console, Remote Manage Endpoint.

You can also set defaults for your installers in Customize Endpoint Installers -> Backup Sets.

Endpoint software sends backups first-in-first-out, only one at a time. If you have more than one backup set scheduled for the same time, or if they overlap, subsequent backups will wait until the first ones complete.

With RBackup version 11.11 the Account Group is no longer a part of the login sequence, so Endpoints can be switched from group to group at the server.

Then load up a number of endpoints on your RBS Server. Give them login names and passwords at random, or in some order that you can use to tell which computer store signed up the endpoint. Something like this, maybe:

Joe's Computer Store is Account 000002. Assign the endpoints of Joe's Computer Store names like "024ART8B11" where the 02 at the beginning is always the account number. 02 = Joe's Computer Store, account number 000002

Make an installer for Joe to use when installing clients on new computers.

You can give Joe the list of names and passwords you have assigned to him so he can tell his customers. The first time the new computer is started, the user will be prompted to enter that data to activate his RBS account.

Joe becomes an Agent of yours, and you pay him for every new client he signs up. When new customers use your service, you will know which agent sent them by looking at your reports or at the name on the active account.

If you want to give your Agents more control over their endpoints you can purchase the  Multitennancy addon for your Server. This gives each Agent the ability to manage his own endpoints online, with full branding and other features.

With your VPN you have internal static IP addresses at both ends - the Server and the Endpoint, so just program the server's private IP for the Endpoint to access through the VPN.

The IP address of your endpoint computer doesn't matter. It can be static or dynamic.

If you were using public IP addresses (not a VPN) the IP address of your Server computer wouldn't matter either, as long as you use a Dynamic DNS service like our built-in Server Locator, which is part of your Maintenance Subscription. Your endpoint computer needs to know how to reach your Server computer, and it can find it at its IP address (if the Server has a static IP) or at its Host Name (if you're using a Dynamic DNS service or our Server Locator.)

For security, the endpoint ALWAYS initiates the connection. It can do this on a schedule that you predetermine, or it can be launched manually

You can launch your RBS session manually by remote by using Terminal Services or pcAnywhere, or some other remote control software to log into your endpoint computer and run the backup. Most people don't do that, rather, they just set up a schedule for the endpoint to use.

The loss of an encryption key can be an emotionally-charged situation. The customer's hard drive may have crashed, or the computer has been stolen. Perhaps the customer has phoned you and is strongly demanding that you restore his data. He may consider it your sole responsibility to restore his data and may be blaming you for not being able to do so because he lost his encryption key. In a worst case, perhaps it WAS your responsibility to maintain your customer's encryption key.

Both you and your customer know his files are safely stored on your RBS Server, and it can be upsetting to know that they cannot be restored because the Encryption Key has been lost. Often the customer's business is adversely affected and the longer his files are lost the more upset he becomes.

RBackup is so secure that it is impossible for a Service Provider to recover files if a customer forgets his encryption key. (But there is hope. Please read on.) For this reason, we strongly recommend that your customers make a Key Disk during installation of their software, and that they record their encryption key on paper and keep it in a safe place. When the software is installed it prompts the user to make and store the Key File and to print the Key Report that it displays, and keep it in a safe place.

If you have the Key Report printed or the latest Key File you can recover the encryption key. If your customer does not remember his encryption key, and does not have the Key Report or the Key File, there is an alternative which can be used in emergencies.

RBackup is the only online backup software that has a built-in Key Escrow system. It can be activated or deactivated by the Service Provider. It is ON by default. This exclusive, highly secure triple-key cryptographic key recovery module allows RBS (and nobody else) to restore a client’s hopelessly lost encryption key. Only RBS can do it, and only with approval from the customer, and only if your customer has not changed his Encryption Key without rebuilding his Key Escrow file. (The software prompts for rebuilding this file whenever the key is changed.)

Recovering Encryption Keys is NOT covered under any RBS Maintenance Subscription. RBS offers no guarantee that we will be successful in recovering an Encryption Key. Some Encryption Keys cannot be restored, even if Key Escrow is turned ON.

To perform a key recovery operation we need some files from your client’s latest backup from your Server, a key file generated by your Server, and legal documents signed by your client and yourself authorizing us to recover the key.

The process requires the consent of your Client and yourself, and can only be done if the Service Provider has turned on the Key Escrow feature.

Recovering encryption keys represents a significant legal liability for RBS, and a significant amount of time. Our insurance carrier requires that we don’t make the process easy or cheap, and that we follow the proper Best Practices guidelines.

There is a fee to have RBS recover a lost encryption key, which will be refunded if we are unable to recover the key. Since it is usually the customer’s responsibility to safeguard his Encryption Key, most Service Providers charge the customer for our fee.

To start the process of recovering an encryption key, fill out and return the TWO (2) forms below, and click here to pay the key escrow fee.

The Key Recovery process can take from fifteen minutes to twenty four hours, depending on the complexity of the key. Our process for recovering it involves applying our key and the Service Provider’s Key in a brute force attack on the triple-cryptographically locked escrow files in an attempt to discover the missing third part of the algorithm.

RBS alone cannot recover an encryption key without the consent of the client and the service provider.

Instead, we highly recommend that your client makes a Key Disk during installation of his software (which the software will ask him to do) and also print the Key Form, for which the software will prompt. This avoids the trouble and expense of using Key Escrow.

If you need to initiate a Key Recovery, following are the forms and instructions.

Please fill out the two forms at the link on the bottom of this form and fax them back to us. Instructions are at the top of each form. After we receive your forms we will contact you to arrange payment for this service.  We are usually able to recover a lost encryption key within a few hours of receiving your forms and payment.

You will be asked to email us some files from your RBS Server.

Because of the high security of the encryption process our success rate recovering encryption keys when all the files we need are available is about 75%.

We WILL NOT be able to recover an encryption key if you have turned OFF the Key Escrow feature of your RBS Software. This feature is ON by default. We will not be able to recover an encryption key if we do not have access to  all the files we need from your RBS Server or if those files are corrupted.

-------------------------------------------------------------------------

FORM 1

Authorization to Recover Encryption Key

To be filled out by the RBS Provider

Fax to +1 901-495-2389

RBS Service Provider Company Name: ____________________________________________

Address _____________________________________________________________________

 _____________________________________________________________________

Telephone ______________________ Email _______________________________

Responsible Individual: _________________________________________________________

Customer: ___________________________________________________________________

I hereby certify that it I provide Remote Backup Services to the Customer named above; that the Customer has lost his Encryption Key; that the Customer has authorized me to recover it for him.

I certify that the individual requesting this Key Recovery is known to me as the true and honest representative of the Customer and that he is authorized to have full access to the Customers' data, in raw form, as well as his Encryption Key.

I know that during the Key Recovery process Remote Backup Systems (RBS) will have access to this Encryption Key; that RBS will have access to, and may view and transmit, the Customer's raw data.

I hereby authorize RBS full access the Customer's account and any files it needs from the Customer's file set and the RBS Application Folder on my RBS Server.

To the maximum extent permitted by applicable law, in no event shall Remote Backup Systems or its suppliers, employees, assigns or representatives be liable for any damages whatsoever (including without limitation, direct or indirect damages for personal injury, loss of business profits, business interruptions, loss of business information or any other pecuniary loss) arising out of this procedure, even if Remote Backup Systems has been advised of the possibility of such damages. In any case, Remote Backup Systems' and its suppliers', employees', assigns', and representatives' entire liability under any provision of this agreement shall be limited to the amount actually paid by you for this procedure. 

While RBS uses every effort to perform this procedure as quickly as possible, we do not guarantee that we can do it within any specific time period. We will work as fast as we can, but the procedure sometimes takes longer than expected. Successful completion depends strongly on the level and speed of cooperation of the Remote Backup Service Provider and the Customer, and in cases where the procedure relies on the Internet, successful completion depends on the availability of Network resources and the integrity and availability of the Remote Backup Service Provider's equipment and Internet connection.

I realize that RBS warrants only that it will attempt to recover the Encryption Key, Key Disk or Escrow File and to deliver it to the Customer or the RBS Provider. RBS does not guarantee that it will recover the Encryption Key or the Customer's data - such is the responsibility of the RBS Provider and Customer together or separately using the Encryption Key, Key Disk or Escrow File provided by RBS.

__________________________________________   ________________________ 

RBS Provider, Authorized Individual                   Date

------------------------------------------------------------------------

FORM 2

Authorization to Recover Encryption Key

To be filled out by the End User

Fax to +1 901-495-2389

Customer's Name: _____________________________________________________________

Address _____________________________________________________________________

_____________________________________________________________________

Telephone ______________________  Email _______________________________

Responsible Individual __________________________________________________________

Remote Backup Service Provider _________________________________________________

I hereby certify that it I use the Remote Backup Services provided by Remote Backup Service Provider above; that I have lost my Encryption Key; that I have authorized the Remote Backup Service Provider named above to recover it for me.

I certify that I am the true and honest representative of the Customer and that I am authorized to have full access to the Customers' data, in raw form, as well as the Encryption Key.

I know that during the Key Recovery process Remote Backup Systems (RBS) will have access to this Encryption Key; that RBS will have access to, and may view and transmit, the Customer's raw data. 

I hereby authorize RBS full access the Customer's account and any files it needs from the Customer's file set and the RBS Application Folder on the RBS Server.

To the maximum extent permitted by applicable law, in no event shall Remote Backup Systems or its suppliers, employees, assigns or representatives be liable for any damages whatsoever (including without limitation, direct or indirect damages for personal injury, loss of business profits, business interruptions, loss of business information or any other pecuniary loss) arising out of this procedure, even if Remote Backup Systems has been advised of the possibility of such damages. In any case, Remote Backup Systems' and its suppliers', employees', assigns', and representatives' entire liability under any provision of this agreement shall be limited to the amount actually paid by you for this procedure.

While RBS uses every effort to perform this procedure as quickly as possible, we do not guarantee that we can do it within any specific time period. We will work as fast as we can, but the procedure sometimes takes longer than expected. Successful completion depends strongly on the level and speed of cooperation of the Remote Backup Service Provider and the Customer, and in cases where the procedure relies on the Internet, successful completion depends on the availability of Network resources and the integrity and availability of the Remote Backup Service Provider's equipment and Internet connection.

I realize that RBS warrants only that it will attempt to recover the Encryption Key, Key Disk or Escrow File and to deliver it to the Customer or the RBS Provider. RBS does not guarantee that it will recover the Encryption Key or the Customer's data - such is the responsibility of the RBS Provider and Customer together or separately using the Encryption Key, Key Disk or Escrow File provided by RBS.

________________________________________   ________________________

End User, Authorized Individual             Date

In the above examples, 76543210 is your serial number (do not use this example) and ddns.rbsnet.net is RBS' DNS server.

So, for your Endpoints to connect to your Server, they will connect to your Host Name rather than your IP address. This way, they can always find you even if your IP address changes.

The Server Locator is a service offered as part of your Maintenance Subscription (Support/Upgrade Subscription) It works only when your subscription is current.

# Anti-Virus Software Some anti-virus software examines all files uploaded or downloaded. This can take a long time, and will slow down transfers at either the Client side or the Server side, or both. Try temporarily disabling your anti-virus software to see if that speeds things up.

# Internet Speed Of course if the Internet is slow, your backups will be slow. The total throughput is limited by the slowest speed between your Client and your Server. Typically download speeds are much higher than upload speeds. So, the Server’s download speed is typically several times faster than Client’s upload speed. For example, the backup from a Client with an upload speed of 256K to a Server with a download speed of 2.0 MBPS (2000K) will go at 256K, and NOT 2.0 MBPS. Remember that “average” inexpensive broadband connections have a high download speed and a slow upload speed.

# Improperly Configured Firewalls Firewalls are designed to stop traffic, and they do it very well. Make sure your firewall isn’t too strict.

# Too many files selected. Try using multiple Backup Sets with smaller numbers of files in each. Try being more selective in the files you back up. NEVER back up entire hard drive. No technology on this planet can back up an unreasonable number of files over the Internet.

# Files are too big. It takes 2.77 hours to transmit a single gigabyte (1000 Megabytes) over a fast T1 Internet connection running at 1.53 MBPS. It takes much longer with slower Internet connections. That’s just how long it takes, and nothing can speed it up. Some files are just not good candidates for Remote Backup simply because they are too big.

# The computer running the RBS Client doesn’t have enough resources. Before RBS can transmit a file to the Server, it has to compress and encrypt that file. This process requires CPU time, disk space, RAM, and swap file space - the more, the faster this process will go. If you are trying to back up a 10 gigabyte file from a Pentium 2 computer with 32 meg of RAM and a slow hard drive, it will take a long time.

# Not enough bandwidth. The typical DSL Internet connection is 256K upstream. At that speed it takes over 16 hours to transmit a single gigabyte. Reduce the size of the backup or increase the Internet bandwidth. If you think your backup is too slow, verify the UPSTREAM speed from the Client. There’s where the bottleneck usually is. Typical Internet connections have a much lower UPLINK (upload) speed than their DOWNLINK (download) speed. ISPs often advertise the DOWNLINK speed and downplay the slower uplink speed. You can test your uplink speed at dslreports.com

# FULL backup mode is improperly used. It isn’t necessary to back up some files. Don’t back up operating system files, swap files, or anything else that you can either rebuild or reload from a distribution CD. Don’t back up an entire hard drive by selecting the root of the drive.

See also: Why does it take so long to do a backup?

If RBackup needs a Windows component, it will download it and install it free of charge.

Other companies require you to purchase a Windows Server operating system and other software to support the core features of their product. For example, one company's software requires a Windows Server operating system with one Microsoft CAL per customer, as well as Microsoft Access for printing reports. RBackup has its reporting functions built-in, and does not require an expensive Server operating system.

This is an Internet server. It also contains an endpoint software installer which has to be burned with your particular server information. It's a serious piece of commercial software that, by design and necessity, requires a little more to install it than, for example, a computer game. If we made the installation simpler it would compromise your security and that of your clients. You only have to install the Server and customize the endpoint installer once. We think it's worth the 30 minutes it might take to do it.

Of course we have installed dozens of them, but most of us at RBS can install a complete system in about 10 minutes.

rbstest@test.com;rbstest@rbsc.com

You can also change location of Temp Folder if you need to, on the endpoint. This is under Options: Preferences: double click on the padlock icon, enter the override password (the default is Admin) - go to to Backup tab: Temp Folder to change the location.

This procedure can be followed if you have trouble setting up the endpoint in Services mode with access the mapped/network drives.

Running Remote Backup using Windows Task Scheduler: To run the client using Windows Scheduler, you need to first remove the shortcuts to Remote Backup software from the start menu list - so it does not launch automatically on startup. You will be relying on the windows scheduler to launch the rbClient.exe program (which is the client interface application, and main program that runs the backup), instead of Remote Backup’s scheduler (rbackup.exe) which runs in the system tray. To run a backup, there are command lines options that you need to include for rbClient.exe that launches the backup of a particular set.

Note: Following this method, you will not longer see any system tray icons - since rbackup.exe will no longer be running. You can add the User account under which the scheduled task will run. Make sure this user account has access/correct permissions to the mapped drives (if mapped drives are included in the backup).

This method of using the windows scheduled tasks is a workaround, if the SYSTEM account cannot access mapped/network drives. (that is, when the RBackup endpoint software cannot access mapped drives when installed as a service) Follow these instructions to create a Scheduled Task for Remote Backup:

1. Click on Windows Start, Select Settings -> Control Panel. Open Scheduled Tasks Folder.

2. Double Click on ‘Add Scheduled Task’, Click Next.

3. This Screen should show you list of almost all the programs installed in your machine. Look for the rbClient.exe, if its not there click on Brow se and select rbClient.exe from the client installation directory(by default, its C:\Program Files\Remote Backup). Selecting the exe file automatically takes you to the next screen which shows schedule options.

4. Select Daily, Weekly or Monthly according to your preferences, click next.

5. Select Start Time, Start Date for this scheduled Task. Click Next.

6. Enter a valid windows username and password for this scheduled task to run. The Client software when launched on schedule runs under this user account’s credentials, so make sure this account has permission to access all the necessary files and folders. Click Next.

7. Click Finish. We have set up the Task Scheduler to launch the Client Software on Schedule, now we have modify the task properties to automatically start the backup for a Backupset.

8. Right Click on the Created Task(it should be named as rbclient, unless you changed the Task Name) and Select Properties.

9. In the Task Tab, the Run option would point to the absolute path of the rbclient.exe. Add the word “Run” and the backupset name to the end of the path. For example if the backupset name is ‘ default ‘ and the installtion path is C:\Program Files\Remote Backup, the Run option should be “C:\Program Files\Remote Backup\rbclient.exe run default

10. Click Apply, the Task Scheduler might ask for the windows username and password again, please enter them and click OK.

Keywords: service mode windows service UNC path 

RBackup contains MANY advanced features to help you select only the files that really need to be backed up. Learn how to use them. Select only the directories containing files that need to be backed up (like My Documents). Use AutoSelect to select files from particular applications. Be reasonable with your file selections.

It takes a while to back up Exchange the right way.

Big Exchange databases, or those with lots of email accounts, may take a long time to prepare for backup. The more email accounts; the bigger the Exchange database; the more complicated the Exchange environment, the longer it will take to complete a backup.

Be aware that a huge Exchange database may take a few days to complete its first backup. Subsequent backups will be much faster. RBackup backs up and restores Exchange while it is in use. So there’s no need to shut down Exchange to back it up or to restore it.

Other software can complete an Exchange database faster than ours. However, they are not doing as thorough a job as we do, and do not save Exchange data in a format that can be easily and quickly restored.

There are many clients using RBackup to store millions of files, and massive Exchange databases with hundreds of mailboxes.

Interference from Other Programs

A running backup session can be slowed down or stopped completely by other programs. For example, if a computer is set to automatically install operating system updates, it may reboot itself automatically. This can interrupt a backup session.

Antivirus and anti-spyware software that updates itself automatically can stop a backup session, and keep it from running the next night, too. For example, if a new virus definition or a new Internet rule is applied through an automatic update, it might interpret RBackup’s Internet activity as spyware, and stop it, presenting a message to the user that he never sees. This can happen night after night if there’s nobody to view the message and allow RBackup to run. Of course RBS can tell you how to solve the problem.

Computers must be turned ON to be backed up.

This may seem obvious. However, RBS has had a number of bitter complaints about our software not working, which have been traced to the fact that the computer simply was not turned on at the time the backup was scheduled to run.

This is especially true of laptop computers, which can run out of batteries, or which the user may simply turn off, forgetting that a backup is scheduled to run. It can also be true of desktop computers and even servers if they shut down because of a glitch in electricity.

Conclusion

Please remember that backups are run at night when nobody is there to watch them. If, while evaluating RBackup, you sit for hours watching a big backup run, you might think there’s something wrong with the software. There isn’t. It’s just doing the job it was programmed to do.

There are MANY ways to optimize RBackup for specific platforms and applications. Please contact RBS for help.

While we will attempt to help you resolve issues unrelated to our software, Remote Backup Systems is not responsible for problems caused by external events, other software, hardware, or by bandwidth constraints. The caveats in this article define your rights under our Software License Agreement concerning the proper use of our software.

See also: Why does it take so long to do a backup?

pre-{backupset name}.bat
post-{backupset name}.bat

For example, if the backup set name is "Blank" then, create batch files and name them as: "pre-Blank.bat" and "post-Blank.bat"

Then, these batch files are only executed if the backup set "Blank" runs.

Causes: There are several, all caused by issues unrelated to the RBS software itself. This is a general warning caused by 1) a temporary loss of network connectivity; 2) misconfigured Server-side router or firewall; 3) bad Network Interface Card; 4) Server Monitoring service

Solution: First make sure that your RBS Server tests fine using the Online Server Tester: http://remote-backup.com/support/testrbs.htm

If the above test fails, it is most likely that your RBS Server's router or firewall isn't properly configured. Recheck your server settings and router/firewall settings.

This issue is caused when the endpoint or the Server attempts to open a connection, and the connection never completes. If an endpoint opens the connection, but sends no message, the port eventually gives up and issues an error 10053. This can be caused by several reasons:

1. Some third party Server Monitors can cause this warning, because they connect to test the Server, but the port resets because no data are transferred. The Server Monitor provided by RBS does not cause this issue.

2. Command Port (usually 2774, but can be configured for any port) of the RBS Server is improperly routed through the router serving the RBS Server. For example: If the server's internal IP address is 10.0.0.2, the port forwarding rule for command port should be routed to 10.0.0.2 address. Make sure the right ports are open on your server-side router.

The ports required on the server are below:

Command port of RBS Server: Can be cofigured for any port. The default is 2774, but common alternatives are 80, 21, or 443, as long as they do not conflict with another service also using the same port.

Data Ports: Can be configured for any port range. The default is 29001-29100. Older versions of RBS Server defaulted to 1024-2048. This range should match the Data Port range defined for the Server. Assign 2-5 ports per simultaneous user expected to connect to the RBS Server. Fewer ports produce slower transfer speeds. Do not assign ports below 1024.

Web Console Port: Port 80 is used by default for the web console. If you want to make this tool available outside your network, open port 80.

Full Image Backup Port: Port 2773 is used to send full image backups to the RBS Server. It should be open inbound.

Server Sync Port: Port 2772 is used to syncronize banks of RBS Servers. They communicate with one another in this port. Open 2772 if you need this service.

This error has also been attributed to the following:

* A hiccup in the network.

* A bad network interface card (NIC) on server.

* Faulty routers.

* Other applications or hardware interfering with connections.

Note: This article only concerns DIALUP Internet connections.

Error 11001 sometimes happens when you have incorrect settings that affect how the RBS endpoint software dials an ISP.

Start the RBS Client software. Click OPTIONS > PREFERENCES > CONNECTION tab.

If you want your Client to dial the ISP to establish an Internet connection, select the ÔÇ£ISPÔÇØ option under ÔÇ£Connection Type.ÔÇØ

Then, in the "Connection to ISP" area select Default to have the RBS endpoint use this computer's default ISP connection. Of course, there must be a default connection and it must work properly.

OR

You can select from the ISP connections already set up for this computer by using the pull-down menu.

Double-click the little padlock icon.

Enter the default password: Admin (This is case-sensitive.) You will have an opportunity to change the default password when you install your live system, so your clients will not have access to this screen.

Highlight the field Backup Server URL which probably has the following text in it right now: enter your server host name

Enter the IP address of your RBS Server.

If you are installing a test endpoint on the same computer as your test Server, the IP address will always be 127.0.0.1

If you are installing a test endpoint on another computer in the same network as your test server, enter private IP address (local IP) of the RBS Server computer.

If you are installing a test endpoint on another computer across the Internet, enter the Public IP address of your RBS Server. If you don't know your Public IP address you can use a browser on your RBS Server computer to pick the following link. Your IP address will be displayed near the top of the screen:

http://remote-backup.com/support/

Then

# click the Apply button
# answer NO to the question about making an updated recovery diskette
# Answer OK to the Preferences Saved information screen
# Click Test Connection to test your connection.

The second most common problem with the Evaluation Version is an apparent lock-up of the endpoint while attempting to make a connection to the Server. The endpoint isn't really locked up, it is just cycling for a few seconds while it tries different methods to get through your router or your firewall. This problem is very easily solved by using our Server Locator Service which comes with the live software.

Whatever the trouble, if you can't solve it quickly using these instructions and others in the Knowledge Library, PLEASE contact us at Remote Backup Systems. We will be more than happy to walk you through it, and we promise to be nicer in person than we are in print.

RBackup has several ways to provide mirroring and failover for RBS Servers. This is just one way.

To setup RBS Server (backup server) for Load Balancing and Failover capabilities:

Software Requirements:

1) RBS Server with SQL Back-end (SQL Backend for the RBS Server is available as a plug-in). Have the back-end installed on a separate server or on the Primary server system.

2) Install another RBS Server (you will need to purchase a license for each additional server instance*) on a secondary machine which will serve as your auto-failover server. This server can reside on the same network or offsite location.

Setup:

Configure both the Primary and Secondary servers to look at the same SQL backend, and data drives. (Secondary server will need to map drives to the data drives). This way, both servers will have the same user accounts, and have access to the same data drives.

Configure Rbackup Endpoint with two IP addresses or DNS addresses separated by semicolon (;). Example, Backup Server URL on the Endpoint should be:

backupserver1.domain.com;backupserver2.domain.com

This way the Endpoint knows to failover to the secondary server (or 3rd or 4th server) automatically, if it cannot make a connection to the primary.

You can also have two Internet connections (one ISP servicing primary and another connection for secondary server). This way, if one ISP goes down, you are still backing up.

Automatic Load Balancing - Servers can be set to forward Endpoint sessions to other Servers after they reach a predetermined point of loading.

You can set the 'ThresholdConnections' (Registry key setting under HKEY_LOCAL_MACHINE\SOFTWARE\Quantum Tech, Inc.\RBSServer\Settings branch. A value of 0, means unlimited) to a number which will be equivalent to the maximum number of Endpoint you want backing up on an individual server. Additional Endpoint connections when the Threshold is reached will be served by your secondary server, thus obtaining a load-balancing environment.

You can also have many RBS Servers (as mentioned above) forming a cluster of servers leading to increased scalability and performance.

If you want a technician to install/configure the setup for you, RBS can do it for a small fee*.

* - contact Sales for current pricing

Creating Backup Sets:

Identifying Data for Backup

Data can be categorized into three tiers: critical (integral to ongoing operations), important (valuable but not mission critical) or archival (required but not typically retrieved).

Let's take an example of Joe's Exchange Server. In this case Exchange Server data, System state and Active Directory can be categorized as being critical data, which should be backed up every day.

The same server might host other applications and data which might be critical as well for the customer's ongoing operations. Typically, 70% of data on a server never changes or changes very rarely. There could be lots of old files that are not being used, and might never change, but the user wants them backed up.

If you (as a provider) have a hands on relationship with the customer, the decision on what is critical data (or important or archival data) should be decided by talking to the customer and deciding what applications his business relies on and what data usually changes.

Backup Sets

When you have categorized data, create separate backup sets based on rules:

Create one backup set for critical data. Schedule it for Daily or Monday-to-Friday. Set the start time an hour after close of business, and an attempt window of 6-8 hours.

For Important data, create a separate backup set and set the schedule for once a week or during weekend.

For archival data, create another backup set and set the schedule for once or twice a month.

Depending on what changes daily and what changes rarely, you can split your data into multiple backup sets thus making the backup process less resource-intensive and time-consuming.

Scheduler

Recommended: Use the Windows Task Scheduler option in the Scheduler Interface. Either select "Use System Account" or enter the Administrator's (or logged in user's) username and password. The Endpoint automatically creates Windows Scheduled Jobs/Tasks for you.

Backup Type 

BitBackup - (Please Read: http://www.remote-backup.com/whitepapers/bitbackup.pdf) This method backs up only the changes to files that happened between backups. Use this backup method only for huge files that change just a little every day, like CAD drawings, Outlook PST files, and Quickbooks files.

Because this backup method requires a lot of local disk space for caching files, it should not be used for average every day files like MS Office files.

Typically, the bitbackup local cache requires one-and-half times the disk space as the original data size. So, if the total data comes to 10 GB, make sure you have at least 15 GB of free space for the local cache.

Bitbackup is suitable only for huge files, like databases, PST files, etc which are not practical to be backed up at the file-level on a daily basis. BitBackup by default does a full backup the first time. There is no need to do a first Full backup and then switch to BitBackup.

Recommendations

For Exchange Server data (Mailboxes): Use Incremental Backup. (Use the built-in Exchange Backup Agent to backup all the Mailboxes. Read the Endpoint's Help/Manual for more information. The agent does a full backup the first time it runs, and then backs up only new exchange emails (or tasks, contacts, etc) . There is no need to do a first full and then switch to Incremental. Just start out with Incremental backup for Exchange.)

For SQL Server (databases): Use the built-in SQL Backup Agent to backup all SQL databases. If the endpoint computer has more than than one instance of SQL Server installed, you can backup the second instance as well by creating a new backup set for the second instance.

In the case of Joe's Exchange Server (the example cited earlier), we recommend creating two backup sets:

First backup set: Include Exchange (all mailboxes), System State and Active Directory. Incremental backup type, scheduled for Daily backups.

Important Note: For a complete DR solution for Exchange Server, you should also backup System State and Active Directory.

Second (and maybe a third) backup set: For all other data files, documents, etc. Backup Type: Bitbackup or Incremental. Schedule based on importance of data.

Data Retention

Based on your Service Level Agreement (SLA) or payment plan for the customer, correctly set these options before running the first backup. There is a lot of difference in time taken for backup/sync (especially for sync routines) in setting a retention period of 365 days vs. 30 days.

More info on these settings can be found in the Endpoint's documentation and Help File.

Recommended:

"Keep Latest Version of All Files Online" should be turned ON.

Set the "Purge Files Older Than" option to x days. Commonly this option is set to 30 or 60 days. (In some cases, 365 days or longer)

File Selection Method

There are 3 File Selection Methods - Archive Bit, Modified Date/Time, and Fast Pick. The Selection Method ONLY applies to normal files. The backup agents (Exchange, SQL, Active Directory, System State and SharePoint) do not depend on the File Selection Method.

Unless the end user has another form of backup (like Tape Backups, etc) always use Archive Bit.

IMPORTANT: The first backup using Archive Bit will back up all files, similar to a FULL backup. Tnereafter the Endpoint will switch to Incremental automatically.

Choose Modified Date/Time, if the number of files in the backup set is less than 10,000. The first backup using Modified Date/Time will back up all files, and then switch automatically to Incremental.

NOTE: This method is slower than Archive Bit and Fast Pick. The Scanning time increases with this method, sometimes dramatically.

Choose Fast Pick, if the number of files is greater than 10,000. The first backup using Fast Pick method will back up all files, and then automatically switch to Incremental.

Endpoint Checklist:

Temp Path Location

By default, the Endpoint uses the C:\Temp\Rbackup\ directory as its Temporary Folder. The Endpoint temporarily uses this location to compress and encrypt files. If there is not enough free space on C:\ drive, you should redirect the Temp Path Location to a bigger drive.

BitBackup Reference Path (or Local Data Store) 

If you are using BitBackup as your backup type, assign the BitBackup Reference Path to a drive that has plenty of space. The requirement is one-and-half times the original data size.

Test Connection

After registering the Endpoint, run a Test Connection from the Endpoint software. If the Test Connection passes successfully, the Endpoint is ready to do backups. If the Test Connection fails, usually the Connection parameters are set incorrectly. (Check the following: Username (logon name), Password, Account Group, Backup Server IP/URL, and Port number)

Personal Firewalls

If there is a software firewall installed, make sure that rbackup.exe and rbClient.exe are not blocked as that can prevent backups from occurring.

Schedules

Make sure your schedules are set correctly. If you have multiple backup sets, it is recommended you stagger the start times so they don't overlap. If they do happen to overlap, RBackup will run them one at a time, queuing subsequent backup sets to start as soon as earlier ones are finished.

First Backup (Copy-To-Disk):

If the first backup is too big to back up online in a reasonable amount of time it is recommended to use the "Copy-To-Disk" backup option for the first backup. 

For this procedure, take an external USB device to your client's site. Connect the drive and open the Endpoint software. Create your backup set and select files for backup.

Then, go to Run > Copy to Disk. The software will ask you to confirm a location for the backup. Select your external USB device. The backup will run just as it would over the internet, except it's going to your local disk, so the transfer times are much shorter. When the backup is complete, take the drive to the Server machine.

Open the RBS Manager utility. Select the Accounts button. Right click on the account you want to import, and select the Import option.

http://aws.amazon.com/ebs/

http://www.cloudiquity.com/2009/03/differences-between-s3-and-ebs/

In terms of performance, S3 has a higher latency than EC2 and also has higher variation in latency. S3 write latency can also be higher than read latency . EBS on the other hand has lower latency with less variation. For file listing, S3 is slow and search is by prefix only whereas EBS has fast directory listing and searching. S3 is performance optimized by using multiple buckets. The write performance is optimized by writing keys in sorted order . EBS single volume performance is similar to a disk drive with writeback caching.

We have heard similar complaints from other customers when using a third party utilities to store data in the cloud. The third party software lacks IO speed and produces many errors. This is why our software uses EBS instead of S3. If you are determined to use S3, you might try looking for another S3 utility.

http://www.remote-backup.com/pages/rbackupv11x#tabs3277

2) Inside the Temp folder, create 2 folders called log and temp. (Example: E:\OracleBackup\Temp\log and E:\OracleBackup\Temp\temp)

3) Extract and copy the attached file rman_incremental.bat to the Remote Backup (or Endpoint's application folder) folder.

4) If you are going to create a separate backup set for Oracle, create a pre-rbs.bat file with the name pre-[backupsetname].bat inside the Remote Backup (or application) folder. Or just edit the existing pre-rbs.bat file.

5) Include the command inside the pre-rbs.bat file: 

rman_incremental.bat sys password SUMMIT DB E:\Oraclebackup\%d_%p_%s_%t.bkp

(in the above command: replace the"sys" with Username, password with the password for Oracle and E:\Oraclebackup with the actual path where you have created the folder in step 1)

6) In Remote Backup Endpoint, select the backup set and include the folder E:\OracleBackup for backup.

When the backup runs, the Endpoint will execute the pre-rbs.bat (or pre-[backupsetname].bat) file and create a backup of Oracle DB in the folder E:\Oraclebackup folder that you specify.

The Endpoint then compresses, encrypts and transfers the file to the offsite backup server.

NOTE: After the first backup you have to edit the rman_incremental.bat file. Search for LEVEL 0 DATABASE in the batch file, and replace it with LEVEL 1 DATABASE. This will then do incremental backups of oracle.

Create a batch file called "rman_incremental.bat" containing the following code:


if (%1)==() goto USAGE
if (%2)==() goto USAGE
if (%3)==() goto USAGE

set ORALOG=E:\Oraclebackup\Temp\log
set ORATMP=E:\Oraclebackup\Temp\temp

if (%ORALOG%)==() goto ENV_VARIABLES
if (%ORATMP%)==() goto ENV_VARIABLES

set FILENAME=rman_backup_hot_full
set DB_USERNAME=%1%
set DB_PASSWORD=%2%
set TNS_ALIAS=%3%
set DB_BACK=%4%
set CMDFILE=%ORATMP%\%FILENAME%_%TNS_ALIAS%.rcv
set LOGFILE=%ORALOG%\%FILENAME%_%TNS_ALIAS%.log

del /q %CMDFILE%
del /q %LOGFILE%


REM +--------------------------------------------------------------------------+
REM | WRITE RMAN COMMAND SCRIPT. |
REM +--------------------------------------------------------------------------+

echo backup INCREMENTAL LEVEL 0 DATABASE plus archivelog format "%DB_BACK%" delete input; > %CMDFILE%
REM echo crosscheck backup of database; >> %CMDFILE%
REM echo crosscheck backup of controlfile; >> %CMDFILE%
REM echo crosscheck archivelog all; >> %CMDFILE%

echo delete noprompt force obsolete;>> %CMDFILE%
REM echo delete force noprompt expired backup of database; >> %CMDFILE%
REM echo delete force noprompt expired backup of controlfile; >> %CMDFILE%
REM echo delete force noprompt expired archivelog all; >> %CMDFILE%

echo exit; >> %CMDFILE%


rman target %DB_USERNAME%/%DB_PASSWORD%@%TNS_ALIAS% nocatalog cmdfile=%CMDFILE% msglog %LOGFILE%

findstr /i "error" %LOGFILE%
if errorlevel 0 if not errorlevel 1 echo WARNING %FILENAME% %TNS_ALIAS% %COMPUTERNAME% %DATE% %TIME% %LOGFILE%

echo ...
echo END OF FILE REPORT
echo Filename : %FILENAME%
echo Database : %TNS_ALIAS%
echo Hostname : %COMPUTERNAME%
echo Date : %DATE%
echo Time : %TIME%
echo RMAN Log File : %LOGFILE%

goto END

:USAGE
echo Usage: rman_backup_hot_full.bat DBA_USERNAME DBA_PASSWORD TNS_ALIAS
echo DBA_USERNAME = Oracle DBA Username - (Requires SYSDBA Role)
echo DBA_PASSWORD = Oracle DBA Password
echo TNS_ALIAS = Connect String to connect to the database (ex. ORCL)
goto END

:ENV_VARIABLES
echo ERROR: You must set the following environment variables before
echo running this script:
echo ORALOG = Directory used to write logfile to
echo ORATMP = Directory used to write temporary files to
goto END

:END
@echo on

With Exchange 2010 and newer you can restore to PST files.

HKEY_LOCAL_MACHINE\SOFTWARE\Quantum Tech, Inc.\Remote Backup\Settings: "ServerOS" - REG_SZ - "True"

If there is no registry key, close the Endpoint application and create a new registry key (String value) in the above branch, and called in 'ServerOS'. Set the value to True.

Restart the Endpoint application, and test.

3) IF the DLL in step 1 is present, and the registry key is set correctly, the system is most likely missing a VC++ DLL. Download the Microsoft Visual C++ redistributable from the link below, and install this on the server. After installation, restart the Endpoint application.

MS VC++ Redistributable Download:

http://www.microsoft.com/downloads/en/confirmation.aspx?FamilyID=BD2A6171-E2D6-4230-B809-9A8D7548C1B6

WSCK: ERROR 11004 - Valid name, no data record of requested type...

followed by a SendEmailNotification message including the SMTP server's name.

Winsock Errors are Microsoft Windows Sockets (TCP) errors, not RBS software errors, and are not directly related to RBS software.

This specific Winsock error implies some types of Names Resolution issues within the network environment. RBS software does not directly perform any type of Name Resolution, it simply asks the Operating System to perform all Name Resolution, and this error is being returned by the Operating System to the software. Therefore, if the SMTP Server Name is being entered by its Host Name or FQDN (fully qualified domain name), try using the IP address instead. This may resolve the issue.

Also make sure the SMTP server name is spelled correctly.

Sometimes an end user wants his data backed up to two locations, one on the RBS Server, and another to a geographically distant location. This article discusses two ways to do this on a customer-by-customer basis.

1  Use the RBackup Endpoint's built-in Local Mirror feature.

This solution has the advantage of making the restore from the alternate location completely automatic, while using the end user's bandwidth rather than the Servers bandwidth to support the second backup site.

The RBackup Endpoint has a built in feature that can automatically maintain a mirror of everything it stores on the RBS Server. Typically this mirror is written to a hard drive in the local network environment, either a shared network drive or a USB drive, or a NAS device.

This feature is useful for backup redundancy and also to dramatically speed up restores. During a restore the RBackup software will check the local mirror location first to see if the files to be restored are there. If they are, RBackup gets them from the local mirror at full local network speed.

Solution number one is to move the mirror location out of the local network into a remote location and map it as a drive letter through a VPN. The RBackup software will see the mapped drive letter as a local drive, and when it writes the mirror backup, it actually goes through the VPN to the remote location.

2  Use a folder sync utility to synchronize the end users folder on the RBS Server with a remote location.

This method has the advantage of being able to mirror more than one (or all) users' data without requiring a VPN.

Every user on an RBS Server has his own folder under which all his data are stored. You can mirror any single user's folder (or all users' folders) to another data center, providing a geographically distant backup site for your own RBackup server.

This is a typical folder structure for an RBS Server. It starts with a drive letter (in this case C:,) and then a folder name (in this case \RBS) and then below \RBS there are a number of system folders (.sync, Reg$In, Reg$Out) and some log files.

The other folders are for user data, and are named the same as the usernames. In the example below, DEMO is a user account, so is Rob.

Mirroring user data to a remote location is simple. Just install a computer at another location, or bring up an instance on a cloud service like Amazons EC2 service. Then install your favorite folder synchronization software and set it up to synchronize one or more users folders.

Use one of the search engines to find synchronization software by entering a query like: download folder sync software

Example: For one set of Endpoints you can group them under one Account group and have the notifications configured to send email to end users (i.e. User Email). Then, you may have another account group for Endpoint's were you don't want to send emails to, but only have them sent to you or Account Administrators. You can use the setup process below to achieve this.

The implementation for this override is a manual procedure. Please follow each step correctly to avoid failures.

Here are the steps to configure notifications for individual Account Groups:\

1.Stop and close the RBS Manager and RBS Server. If the RBS Server is running as a service, stop the service from the Services Panel.

2.Create a new registry key under the branch shown, as follows:

HKEY_LOCAL_MACHINE\SOFTWARE\Quantum Tech, Inc.\RBSServer\Enotify:

UseAccount REG_SZ True

The UseAccount key turns ON the feature to use custom EmailSettings.ini and custom templates for all notifications defined for each account group.

3.There is no User interface to edit/maintain these custom templates currently. You have edit/add/maintain the EmailSettings.ini and the template files manually.

4.When UseAccount key is True, the Email Notifications program looks for the templates under the folder structure: Application folder (i.e. C:\Program Files\RBS Server\Enotify\AccountGroup).

Example: For House Account (000001), the EmailSettings.ini and Template Files (SuccessTemplate.ini, FailedTemplate.ini, etc) should be under C:\Program Files\RBS Server\Enotify\000001\ folder.

For Account group (000004), the EmailSettings.ini and Template files (SuccessTemplate.ini, FailedTemplate.ini, etc) should go under C:\Program Files\RBS Server\Enotify\000004\ folder.

Manually create the folder structure (as above) for every Account Group defined on your server.

5.Restart the RBS Server and Manager.

6.From Tools: Email Notifications, edit the settings for the first account group. Save your changes and close the Email Notifications. Now, copy the EmailSettings.ini and the Template files from C:\Program Files\RBS Server\ folder to the corresponding Enotify template folder (as defined in step 4).

7.Re-open the Email Notifications program and change the settings for the second account group. Save, and copy the template files to the corresponding Enotify template folder (as defined in step 4 for this account group). And, so on.

NOTE: You have to define Enotify template folders for every Account Group you have defined on the server.

Client not opening

Close the RBS Endpoint completly. Go to Task Manager- ->Processes,

Stop rbclient.exe and rbackup.exe if running.

Try opening the Endpoint by running rbclient.exe in the folder C:\Program Files (x86)\Remote Backup\ 

Please add both rbclient.exe and rbackup.exe to the DEP exception list.

To get to these settings:

1. Right-click on "My Computer" and select the Properties page.

2. On the Properties page, select the "Advanced" tab, and click on the "Settings" button in the "Performance" section.

3. On the Performance Options page, select the "Data Execution Prevention" tab.

4. Select "Turn on DEP for all programs and services except those I select".

5. Use the "Add" button on this page to add rbclient.exe and rbackup.exe to the "opt out" list. Make sure they are enabled and checked.

6. Click "OK" on each of the pages when finished and reboot the system.

Start RBS Endpoint software.

1.) DES is the old US Federal Standard. "8.2 Compatible" is the legacy RBackup (pre-1995) version, and "8.3 Standard" is the legacy RBackup (pre-1998) version.

2.) TDES is a much more secure form of DES

3.) Blowfish is probably the most secure of all. It uses a key length that is variable from four bits to 448 bits. This is the fastest encryption method, and the default for RBackup.

4.) AES is the US Federal Standard for military and diplomatic data. RBackup supports three levels of AES from 128 bits to 256 bits. 256 bit AES is very secure, but it is a bit slow due to complex encryption process.

RBackup can automatically generate "statistically perfect" encryption keys - the most secure keys. If you want the very highest security, do not pick your own key. Allow RBackup to generate it for you. For maximunm level of security and uniformity of status Rbackup uses Key-Based Encryption Algorithms

The way RBackup generates a key depends on which encryption standard you have chosen.

Our encryption support includes the ability to generate a key that, due to its structure, provides stronger encryption of your files. All methods except Blowfish have a mandated key length. The system will ask for a key length if Blowfish is used.

1.) Install the Endpoint either on the RBS Server Machine or on a PC locally connected to the RBS Server (Same LAN where the RBS Server is located).

2.) Close RBS Endpoint. Kill rbclient.exe and rbackup.exe via task manager.

3.) Replace the attached backup.mdb file to this new Endpoint's Remote backup folder.

4.) Restart the Endpoint and change the backup server URL on client as follows. 

If the Endpoint is going to be installed on the RBS Server Machine itself the Backup server URL is 127.0.0.1

If the Endpoint is going to be installed on the Local LAN/PC that is on the same network the Backup Server URL should be the Local IP/Internal IP address of the RBS Server Machine. (192.x.x.x or 10.x.x.x)

To change the Backup Server URL:

On the RBS Endpoint software, go to Options>Preferences and then double-click the padlock icon and enter the password ("Admin" with a capital "A" by default). Now, you should be able to see the username, pass, port, URL, etc.

Change the Backup Server URL. Click on Apply and Okay.

5.) Restart the Endpoint and do the restore.

This error might be caused because you are using the old key file. 

Go to this user data folder on the RBS Server machine, do a search for a file named 'escrow'.

Arrange the files with modified date/time. Find out the latest escrow file, if you have more than one file.

Compare the date/time of the latest escrow file with that of the key disk which you have and tried for disaster recovery. If they do not match, then that indicates that a new key is being generated on the client side which led to this new escrow file on the server.

As a Work Around:

Install the Endpoint either on the RBS Server Machine itself or on a PC locally connected to the RBS Server (Same LAN where the RBS Server is located) and Perform the Disaster Recovery procedure. You will need to Redirect the restores to a removable drive so you can ship the original data back to the client.

1. Create a new Endpoint installer with the Account Settings the same as the Endpoint, but change the Backup Server URL Address as below.

If the Endpoint is going to be installed on the RBS Server Machine itself, set the Backup Server URL to 127.0.0.1

If the Endpoint is going to be installed on a computer that is on the same local network as the RBS Server, the Backup Server URL should be the Local IP/Internal IP address of the RBS Server Machine. (192.x.x.x or 10.x.x.x)

2. Install the Endpoint using the New Endpoint Installer that you have created and perform the Disaster Recovery using the client Key Disk that you have.

Also See: What if a client forgets his encryption key? How does the Key Escrow process work?

There are three ways to perform a Disaster Recovery in case of hard drive failure or system crash:

1) Restore from the .VHD file maintained during a Full Image Backup. You can also directly mount the VHD file.

2) Using the Encryption Key Disk/File:

First install a fresh Endpoint on the new system. When prompted for 'New Registration' or 'Disaster Recovery' Select Disaster Recovery.

The Endpoint will ask you if you have the Key Disk. If you have the Key disk/file with you select Yes, and the Endpoint will ask you for the location of the Key Disk/File.

After reading the file the Endpoint will contact the server and retrieve the last known catalog file from the server. Upon successfully recovering the catalog it will ask you to restart the Endpoint application. Restart the Endpoint and you will see all the files to restore in the Restore window.

2) With the hard copy or the Printout of the encryption key info:

After installing an Endpoint, and selecting Disaster Recovery Option: Say 'No' to when prompted for 'Do you have the Encryption Key Disk?'

The Endpoint will present you a new form where in you can manually enter the Username, password, encryption method and key information. BE CAREFUL. You must enter all the information exactly as it appears on the printout. Don't confuse zero with "O" (a capital letter O)

After entering the details the Endpoint will start the DR process, restoring the latest catalog from the server. Files available for restore will show up in the Restore window.