<![CDATA[Remote Backup Systems]]> <![CDATA[CRC errors or invalid signature in installers]]> Problem: The Online Installer (or any of the RBS files) shows CRC errors or Invalid Signature.

Solution: All RBS downloads and installers are digitally signed and encapsulated to prevent tampering.

If anything happens to any of the files in the installers to alter them from the originals that were certified at RBS before distribution, errors and warnings will happen during use.

The two most common causes for this are files that are corrupted or changed somehow during uploading or downloading, and viruses that can attach to the files at any time after they are downloaded from RBS. All files that leave RBS are certified virus-free and are digitally signed to prevent tampering.

Viruses can damage the installer files at any point after they leave RBS. The fix for this is to find and fix the virus, then obtain an original certified copy of the affected installer and replace the damaged one.

The fix for download errors is to download the installar again.

If these errors are reported when customers try to download endpoint software from your server, you can suspect viruses on your web site, viruses on the web server, or on the customer's computer.

It is also possible, but not very common, that something about the web server or the equipment between it and the computer attempting the installation is damaging the Online Installer files. This can theoretically be caused by a bad connection, or something else that is causing the files to fail to properly download.

To determine if the problem is on the computer attempting to use the Online Installer, try downloading a known good RBS Endpoint software. If the installation works, the problem is NOT your computer. If the installation fails, the problem IS your computer.

 

]]> <![CDATA[Error 10048 port currently in use]]> This is reported on RBS Servers, usually during installation, when there is already another server running on the same computer and using the RBS Server's port number.

If the RBS Server attempts to use port 21, and your computer already runs an FTP server, this error may happen.

If your computer is already running an RBS Server as a Service, and you try to run another instanace of the RBS Server as an application, this error may happen.

This problem is basically a Port Conflict, and is easy to fix.

Find out which other Servers are running on your computer and either stop them or change the port number of your RBS Server to a different port. The default port number for RBS Servers is 2774.

You can also change your server's port number on the Properties screen of RBS Manager. Doing so will require manually logging in and changing each Endpoint's port number in the endpoints admin interface.

 

]]> <![CDATA[File not found error 48]]> File not found error 48

Endpoint will not install because of a missing file.

There are two possible causes for this failure.

This error message shows up when Windows fails to properly install a file on the Endpoint computer. This is caused sometimes by incorrect file permissions.

]]> <![CDATA[How many installations of the RBS client software do I need?]]>

Question: Would I become the Server and ALL my endpoints would have an RBS Endpoint installed on their PC's including the server(s)? Would each of my clients have their own copy of the RBS endpoint software for each PC in their network? For instance, a customer with a Server and 10 workstations would have about 11 separate copies of the RBS endpoint software?

Answer: Yes, you can do it this way. One RBS Server can service a lot of endpoints. When we say "endpoint" we mean one installation of our endpoint software. When we say Customer or Client we mean a company or individual who is your customer and who may have multiple endpoints.

If your customer has his PCs networked, you can put a single copy of our endpoint software on the computer that has access to all the others through shared drives. Or, you can put a copy of the endpoint software on each workstation. That's up to you, depending on the network topography.

In your example, I'd suggest using 11 endpoints - one for the Server and 10 for the workstations. If the server has access to the workstation's drives through shares, you can put one endpoint on the Server and back up all 11 workstations with it. There are a number of ways to do it.

You need only one RBS Server, and you need a endpoint for each of the Clients' computers. You can use the single RBS Server to back up hundreds or thousands of endpoints and many different Customers.

We sell the software in packages that each include one Server and multiple endpoints.

 

]]> <![CDATA[Installation tips for the RBS Server]]> Most RBS Server installations are easy, and much easier by following instructions. When you run the Server's installation file it displays some help files that should be read completely. Follow the links in the files and read the docs that display. I know it's boring and you want to get on with using the software, but the documentation is critical.

The system installs the Server and a plain vanilla endpoint installer which you must then customize before you can make your endpoint installers. Almost all installation problems happen when the documentation isn't read and followed. Being a serious Internet server complicated by the included endpoint installer that is built into it, its installation isn't quite intuitive.

Reading the documentation is critically important to understand how it all works and to be comfortable with it in the long run. We've found that the people who have the most trouble with installations are usually the smartest ones, who know the most about Internet hosting etc., and rush through the docs because they assume this Server is just like all the others. Doing that leaves gaps in your knowledge of the system as a whole and can make for some frustration now and later.

There's a really good searchable Knowledge Library on our web site.

After you have your Server installed and your endpoint installation customized, test your server with our Online Server Tester BEFORE you try to install your first endpoint. Make sure your Server is functioning as it should be before working with the endpoint.

 

]]> <![CDATA[Manually deleting RBackup software]]>

Sometimes the RBackup software fails to uninstall properly while testing it. This problem happens after many installs and uninstalls, and can also happen when an install or uninstall is accidentally aborted before it completes. These instructions are for manually deleting the RBackup software.

IMPORTANT (before uninstalling anything):

Always SAVE a copy of the rbs.mdb file which is the Server catalog file to another location before Uninstalling the software. This file contains all the endpoint accounts info and backup transactions. Most Critical file for the RBS server.

For existing endpoints, similarly the catalog file is thebackup.mdb file that needs to be copied to another location before uninstalling the endpoints.

After reinstalling, the catalogue file needs to be copied back to the original location and restart the applications. (Both server and endpoint)

* The above need not be applied if you're starting from scratch.

Steps for completely removing the RBS Server:

1. Uninstall RBS Server from Add/Remove Programs.

2. Delete the folder C: \Program Files\RBS Server (or C:\Program Files (x86)\RBS Server)

3. Delete C:\Program Files\InstallShield Installation Information\{948CE7CB-9D25-11D4-9C95-000039A6B115} folder. (HIDDEN Folder) (If you cannot find this folder, proceed to the next step)

4. Delete Registry Branch: HKEY_LOCAL_MACHINE\SOFTWARE\Quantum Tech, Inc.

Steps for complete uninstall of endpoint:

1. Uninstall the endpoint (Remote Backup) by going into Control panel->Add/Remove Programs.

2. Delete the C:\Program Files\Remote Backup folder (or C:\Program Files (x86)\Remote Backup)

3. Delete C:\Program Files\InstallShield Installation Information\{f0674b40-d8c3-11d3-8c61-00104b1f6cf0} folder. Or make a search for it, and delete it. (HIDDEN folder) (If you cannot find this folder, proceed to the next step)

4. Delete Registry Branch: HKEY_LOCAL_MACHINE\SOFTWARE\Quantum Tech, Inc.\Remote Backup.

 

]]> <![CDATA[Your evaluation version is hard to install. Whats up?]]> RBS will be happy to install and configure and test your evaluation software for you. We do this free of charge for all evaluations and live software.

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.

 

]]> <![CDATA[Procedure to migrate/move an existing Endpoint installation to an...]]> To reinstall or move an existing Endpoint to another machine (NOT THE RBS SERVER)

There are two ways you can do this.

1) This is probably the easiest way. First stop the existing Endpoint application on the original machine.

2) Copy the contents of the BitBackup Reference Folder to the new computer into the same path as before. (if it exists)

3) Install the Endpoint software on the new machine, making sure to use all the same temp path locations and BitBackup reference paths.

** DO NOT select NEW REGISTRATION and proceed to register this Endpoint as a new user/ ALSO NEVER re-register with same username/password.

After installing the Endpoint software on the new machine, when prompted for NEW REGISTRATION or DISASTER RECOVERY - simply Close (Exit) the Endpoint application. Copy over the catalog file (backup.mdb) file from the original Endpoint (under C:\Program Files (x86)\Remote Backup) to the new machine replacing the fresh catalog.

Restart the Endpoint application.

You can now continue to run backups from this machine.

Uninstall the Remote Backup application from the old machine using Add/Remove Programs.

If Reinstalling on the same machine:

First save a copy of the backup.mdb file to an alternate location.

Save a copy of the BitBackup Reference Path files.

 

Uninstall and reinstall the Endpoint software.

After reinstall, when prompted for NEW REGISTRATION or DISASTER RECOVERY, close the Endpoint and copy back the saved backup.mdb file in \program files\remote backup folder.

Copy the contents of the BitBackup Reference Path.

Restart the client.

2) Instead of copying over the catalog file (backup.mdb) from the old to new machine - you can alternatively do a DISASTER RECOVERY after installing a fresh Endpoint on the new system.

You can perform the DR operation using the original Endpoint's Key Disk/File or Key information.

* NEVER REINSTALL AN EXISTING ENDPPOINT AND SELECT NEW REGISTRATION - ALWAYS CHOOSE ONE OF THE ABOVE TWO METHODS TO MOVE THE CATALOG OR RETRIEVE THE ORIGINAL CATALOG FILE ACROSS TO THE NEW INSTALLATION.

 

]]> <![CDATA[Moving RBS Server installation through imaging or virtual or clou...]]>
It is not recommended to use an image backup or cloned instance of the RBS Server on another system. This is mainly because of the Licensing system that RBS uses.

Each RBS Server license is bound to specific system parameters for protection. To move an existing RBS Server instance to another system or hardware, you will have to follow the steps outlined in the article below:

http://help.remote-backup.com/index.php?_m=knowledgebase&_a=printable&kbarticleid=257

Note: The RBS Server license does not rely on the MAC Address alone. So, changes to the MAC Address on an existing system should not be a cause for concern.

Using an image or cloning the system to another system, will lead to licensing issues. You will need to contact RBS Tech Support and have to perform some manual steps to get the server running again.

]]> <![CDATA[How To Use Security Certificates - SSL and Code Signing]]> What are Security Certificates and how can I use them? Do I need them? Where can I buy them?

There are two kinds of Security Certificates that can be used by RBackup and its web-based PlugIns.

SSL Certificate – used to secure data in transit over the web when using a web browser. An SSL certificate is installed on the Web Server, and changes the HTTP:// protocol to HTTPS:// which indicates a secure connection. This also activates a graphic (usually a padlock) on the browser.

SSL Certificates are typically used on websites that accept personal information like passwords and credit card numbers. The certificate encrypts the data sent to the website, making sure that it cannot be intercepted and compromised along the Internet.

The RBackup RBS Server does not require an SSL certificate.

The Web Manager PlugIn and the E-Commerce PlugIn will operate without an SSL certificate, but we strongly advise you use one, especially with the E-Commerce PlugIn, which accepts credit cards and personally identifiable information.

Code Signing Certificate – used to secure files that can be downloaded over the Internet. The Certificate guarantees that the file has not been changed since it was signed. The RBS Server and the Web Manager PlugIn can use a Code Signing Certificate to secure your Endpoint installers if one is available. They will also operate without one.

Files that are downloaded over the Internet (like your Endpoint installer) are usually checked for viruses and other threats by the browser used to download them. Code signed files contain a special signature that tells browsers that the file has not been modified since it was signed. If a the file becomes infected with a virus after it has been signed, the browser will know about it and will notify the end user with a warning.

One advantage of Code Signing your Endpoint installers is that the browser will recognize the certificate, and will present the end user with fewer (and less dramatic) messages during download. The browser will trust the Endpoint installer because it is code signed.

Endpoint installers are code signed using your Code Signing Certificate at the time they are built by the RBS Server or the Web Manager PlugIn.

Please be aware that some of the RBackup Endpoint files are already signed with a Code Signing certificate belonging to RBS. If you re-sign them with your own, our certificate will be replaced with yours, which is a good thing.

Where can I buy Security Certificates?

Both the SSL Certificate and the Code Signing Certificate can be bought from Certificate Authorities like GoDaddy, Verisign, and others. Any type of SSL certificate will work, so buy an inexpensive one. They are available for about $29/year.

The Code Signing Certificate must support Microsoft Authenticode. Inexpensive Code Signing Certificates cost about $179 per year.

The Certification Process

Various Certification Authorities have different procedures for assigning Security Certificates. They will need to verify that you are who you say you are, and that your website is a valid one. They might need to verify your address and telephone number.

The process can take several days to complete, and can require you to submit proof by way of Fax.

How do I install Security Certificates?

See the instructions provided by your Certificate Authority. Installing your certificates is not a part of the installation services provided by RBS.


]]> <![CDATA[How do I change the company information displayed on installation...]]> Question:

I want to remove Remote Backup Systems' name from the Client software. Windows displays Remote Backup Systems on installation in Windows 7.

Answer:

The information displayed on installation of the Endpoint software by Window's User Account Control (UAC) comes from the Versign Class 3 Code Signing Certificate that RBS used to sign the .EXE files.

We code-sign the files so Windows won't complain about installing them, and to ensure that the files contain no viruses and they have not been modified since we produced them. It is an important security measure required by many companies and modern Windows operating systems.

If you try to install an unsigned dll or exe file, Windows (particularly win7 and beyond) complains bitterly, and its UAC, depending on how it is set, can refuse to install it at all. Also some antivirus software will delete unsigned files, if the UAC allows them to be installed at all.

Files that are downloaded over the Internet (like your Endpoint installer) are usually checked for viruses and other threats by the browser used to download them. Code signed files contain a special signature that tells browsers that the file has not been modified since it was signed. If the file becomes infected with a virus after it has been signed, the browser will know about it and will notify the end user with a warning.

One advantage of Code Signing your Endpoint installers is that the browser will recognize the certificate, and will present the end user with fewer (and less dramatic) messages during download. The browser will trust the Endpoint installer because it is code signed.

Our software fully supports using your own certificate and if you do, your own info will be there instead. Full instructions are in the Server's documentation. You can purchase a certificate at the link below.

http://www.symantec.com/theme.jsp?themeid=verisign-code-signing

We do not have a procedure for generating a non-signed installer. You might be able to find a way to "unsign" it or remove the code signing signature by doing a web search.

 

]]> <![CDATA[How to Upgrade the Server and Endpoints]]> Follow the instructions below to upgrade RBS Server and Endpoints.

1) Go to website, http://portal.remote-backup.com

2) Enter your email address, serial number, and password. (The first password is the serial number.)

3) Select the Software Updates menu and follow instructions.

To upgrade RBS Server::

NOTE:: Upgrading RBS Server will reset the client customization to DEFAULT. Please take a backup of RBS Server folder.

1) Close the RBS Server completely and go to the Task Manager- ->Processes, kill the RBSMgr.exe and RBS.exe if running.

If RBS server is running as a service then go to the command prompt
For 32- Bit Operating System: C:\Program Files \RBS Server and type in RBS /u

For 64- Bit Operating System: C:\Program Files (x86)\RBS Server and type in RBS /u

This will remove RBS server from service mode.

2) Run the upgrade installer. Reboot the system when prompted.

NOTE:: Right click on the installer and run as administrator

3) Start RBS Server. The upgrade process is complete.

 

MANUALLY UPGRADING THE ENDPOINTS

On the Endpoint computers, close the Endpoint software. Check Task Manager. Kill rbclient.exe and rbackup.exe if running.

Run the new Endpoint EXE file you created.

Reboot if prompted to do so.


AUTOMATICALLY UPGRADING ENDPOINTS

The RBS Web Console (Web Manager) can automatically distbute Endpoint upgrades. See the documentation for instructions.

You can use the RBSUpdate utility to automatically upgrade your Endpoints, if you have installed and configured it. Instructions are in the RBS Serer's Help File.

]]> <![CDATA[Fatal Error - Server will not run. Contact technical support.]]> This error is caused when the RBS Server has been moved to a different computer or VM without first uninstalling it from the previous computer or VM, or when something major has changed on the server's or the VM's hardware - like its CPU serial number, or hard drive, etc.

The RBS Server "thinks" it has been stolen and moved, so it has stopped running to prevent a security breach.

Built into the RBS Server software is a security feature that is designed to help protect your Endpoints' backup data from being hijacked. The feature prevents a second RBS Server from starting if it is installed with a serial number that is already active on another system. This eliminates security risks associated with IP spoofing and serial number theft.

Installing the RBS Server software registers its serial number to a specific computer or VM, preventing the use of the same serial number on another computer. Uninstalling the RBS Server software de-registers its serial number so it can then be installed on a different computer. If you can't (or don't want) to uninstall the software, you can use this form to move its serial number. 

If you have recently moved your RBS Server to another computer or VM without following this procedure, you can manually move your RBS Server's license at the following link. [move server license here]

]]> <![CDATA[Installation Worksheet and Checklist]]> For a complete error-free installation of RBackup, use the same Installation Worksheet and Checklist used by RBS Engineers.

[Download the PDF Here]

]]> <![CDATA[Web Manager Localization]]> Steps below to Convert the Default Language in Web Manager

1. Login to Web Manager as Administrator.

2. Go to Setup-->Web Manager Setup

3. Select the Default setting from Dropdown box

4. Click on Update button.

Changes will be applied after logging out and Logging back in to Web manager.

Please check the attached document(Web Manager Localization.pdf) to Add New Language in Web Manager.

NOTE: It is also possible to Localize the Client side Simple Interface. Please contact Tech support for details.

]]> <![CDATA[Pre-requisites for installing RBackup]]> List of prerequisites for installing RBackup:
 
(*) The prerequisites for installing the RBS Server are: Your target computer must be running a Windows operating system with a web browser and be able to browse the Internet.
 
(*) Our installer will install Windows Internet Information Server (IIS) to run your Server's Web Console - the portal that you log into to manage your Server and your Endpoints. It will use port 80 by default. If you already have a web server on port 80, please tell us now so we can make plans to work around it.
 
(*) Your firewall and router must be configured as follows:
 
Ports 80, 2772, 2773, and 2774 mapped to your Server, TCP inbound unsolicited traffic
Ports 29001 through 29100 mapped to your Server, TCP inbound solicited traffic
 
(*)  Typically, turn OFF the Windows firewall. At least allow the above ports through it.
 
E-Commerce Only:
 
(*) SSL Certificate installed (if desired)
 
(*) Credit Card Merchant Account Activated, if you will accept credit cards
 
(*) Payment Gateway configured and set up (authorize.net or Payflow Pro), if you will accept credit cards
 
(*) PayPal Business Account set up for Express Checkout, if you will use PayPal
 
The RBS Server comes by default with a built-in database that is adequate for up to 50 endpoints. If you want to service more endpoints, we recommend you install MS SQL Server.
 
(*) SQL Server 2005 or Higher
(*) SQL Management Studio
 
When you are ready with the above pre-requisites,  please initiate a live chat session via our website below:
 
http://help.remote-backup.com (OR) http://remote-backup.com
 
We do installations on the following schedule:
 
9:00 AM to 4:00 PM  US CST
9:00 AM to 10:00 PM GMT (Monday to Friday)

 

]]>