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 

Some of our component files have been digitally signed with our Class 3 Code Signing Certificate, for security reasons, and to make sure viruses can't attach to the software you deploy. The name of our holding company is displayed in the certificate. If you want to replace that with your own name you can buy your own Code Signing Certificate, and your RBS Server will use it to re-sign all of your components.

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.

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.

When you select the entire drive (E:\ drive) for backup - by default, it also selects all hidden and system/OS files/folders which cannot be viewed normally through explorer. That is why you backed up so many.

To view all the selections made by the client, first close the endpoint application. Then bring up Windows Explorer and go to Tools: Folder Options, View:

Check "Show Hidden Files and Folders" and uncheck "Hide Protected Operating system files". Now, start the endpoint software. You will see the \SYSTEM\ folder and files that were selected.

The right way to make file selections:

Instead of selecting the whole drive and excluding everything else, it is better to directly include the file/folders you want backed up. For examnple, if you want to include C:\test\test.bak file and C:\backup folder, then from the endpoint interface, browse to the file and folder and INCLUDE them with green checksmarks. You dont have to EXCLUDE anything else. Now, when you run a backup you will see that it only scans and picks what you have selected.

* Change the Explorer Folder Options back to default after making the changes.

You can change the port number if you like. Some people use port 443 or 80, as long as they don't conflict with any other service. RBackup's own Web Console uses port 80.

Pick Options:Preferences.

Pick the Connection tab.

Double click the padlock icon.

Enter the password. The default is "admin".

Select the Backup tab.

Select the Create Support Pack button.

The software will create a Support Pack and display a message telling you where it is on the drive. You can then email the Support Pack to Tech Support.

As an alternative you can select Help->About and then click the Send Diagnostics button. This will send a support pack directly to RBS Support.

Pick Options:Preferences.

Pick the Connection tab.

Double click the padlock icon.

Enter the password. The default is "admin".

Select the Backup tab.

Select the Create Key Disk button.

This article describes making changes to the registry. If you are uncomfortable doing that, please don't do it.

After you have already installed the endpoint software

Use this procedure if you have already installed the Client software and want to change the way it works.

1. Start REGEDIT to edit the registry.

2. Drill down to HKEY_LOCAL_MACHINE / Software / Quantum Tech, Inc. / Remote Backup / Settings

3. Find the registry key OverrideAS If it isn't there, add it as type String.

4. Change the value of OverrideAS to True (with a capital T)

5. Quit Registry Editor.

6. Checkmark the folder(s) you want to back up with a green checkmark.

7. Turn on AutoSelect

8. Edit the AutoSelect Filter (User Defined Types) to add the file types you want to exclude from the backup, and exclude them with a red X.

9. Clear all file selections in the File Types tab by highlighting all of them and selecting the Clear button.

If you have NOT installed the Client Software, and you want to edit your Client installer so it installs this by default

1) From the RBS Server's Web Console, select Setup: Customize Endpoint Installer

2) Select the 'Backup Sets' tab and the Auto Select Filter subtab.

3)  In the sub-tab called 'Auto Select Filter' change the option 'Override AutoSelect?' to Yes.

3) Exclude the file extensions that you want excluded using the filter options in this tab.

4) Apply, and Save your settings. Build new client installer(s).

Command line to run copy to disk

rbclient.exe /Run$$[ Backupset name]$$ "copy to disk location"

keywords: embed add backup functionality

Quit REGEDIT

Reboot the computer.

The first full backup is usually large. With RBackup you can use a portable hard drive to do that backup, then take it to the Server and import it. Subsequent backups are all done online, and are incremental - so another full backup is not needed.

Another way to do an onsite full backup is to use RBackup's Full Image Backup. This backs up entire drives (logical or physical) locally to Hyper-V files (VHD) that can be directly mounted with any hypervisor, booted, or restored to bare metal.

With RBackup the first backup of any new backup set is Full. Thereafter, RBackup automatically switches to the Backup Method you have chosen, which is usually Incremental.

You can do the first full backup using a portable hard drive. In the RBackup Endpoint software, select the Backup Set you want to run, and then select Run -> Copy to Disk.

RBackup will ask you for the location of your hard drive, and then it will run the backup. As it does, it prepares the Server to receive the backups, and it sends the actual backup files to the USB drive.

When the backup is finished, take the USB drive to the Server.

Open the RBS Manager console application. Click the Accounts button.

Right-click the account you want to import, and select Import Data from the menu.

The data will then be imported into the Server, and it will be available for restores online.

If you used the Full Image Backup feature, then your backup is stored in a standard Hyper-V file with the extension VHD. You can use this file to burn the backup image to a new hard drive, or you can mount it immedately with any hypervisor. You can also boot it. It is a fully bootable, complete image of the hard drive.

Check under Control Panel: Admin Tools: Services, and make sure that the service 'ExchangeBackupService' is running. If the service is stopped, start the service and restart the client software.

Solution 2:

Error: -2146233077 Failed to write to an IPC Port: The pipe is being closed on frmBackupSet.ExchangeProcess

In 64 bit OS, if you see an IPC port error like above then try the following steps:

- Close the client application, and the system tray application. Make sure rbclient.exe and rbackup.exe processes are not running (in task manager).
- Go to the Services Panel, stop ÔÇ£ExchangeBackupAgentÔÇØ service.
- Go to the client installation folder (usually, C:\Program Files (x86)\Remote Backup) and create a text file and name it as "ExchangeService.ini" (if there is not one already).
- Open the file using Notepad and enter the following two lines of text (below) and save it.

Channel=ipc
Port=59000

* NOTE: Channel and Port are case sensitive, not values.
- Start the ÔÇ£ExchangeBackupAgentÔÇØ Service from services panel.

By default the Channel Port would be 9999 as you can see in the 'ExchangeAgent.log' in the client application/installation folder. If you still see the IPC port error, then change the Channel to 'tcp' and increase the port number (max value: 65535) and retry the above steps.

The above steps can also be applied when you get errors like "Error 0 connecting to exchange" while connecting to the exchange plugin and/or when expanding the mailboxes.

After restarting the service, you can go to ExchangeAgent.log to see if the values are applied properly.

If you still have issues, please contact Technical Support and provide the logs.

If you are using the Advanced Interface: Select the menu option "Run" > "Copy to Disk".

If you are using the Simple/Standard Interface: Select the Backup Set option, and choose your backup set from the drop down. Then, select the option 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 will send backups to your local disk, and the transfer times are much quicker.

When the backup is complete, take the drive to the Server and import it with the RBS Manager.

Push the Accounts button, right-click on the account you want to import, and pick the Import choice.

1) If the Modified Date/Time of the file is greater than the threshold date/time, OR
2) If the Creation Date/Time of the file is greater than the threshold date/time.

Note: All date/time comparisons are done in UTC.

Since there are no database lookups in the scanning process, the time taken to scan thousands of files is greatly reduced.

This method of selection is useful when you are backing up a file sever (for example) that has thousands of files that need to be scanned, or in cases where archive bit cannot be used for file selection (like a Samba/Linux box).

The first backup using this File Selection method, will select ALL files for backup.

If you make changes to File Selection, i.e. include a new file or folder to backup after the initial backup, you have to make sure to Set the Modified Date for these new inclusions. Otherwise these files will not be selected for backup. For this reason, there is a right click menu option called "Set Modified Date/Time" that you can use to set/change the modified date/time stamp of these new inclusions. Further, when you add a new file/folder to the inclusion list after the first full, the software itself will prompt you to change the Modified Date/Time (if the Fast Pick method is being used for the backup set).

Use the built-in SQL Backup Agent to backup all SQL databases. If you have more than one instance of SQL Server installed on a system, backup the second instance as by creating a new backup set for the second instance.

The built-in SQL backup agent always does a full backup of the database by running SQL built-in queries. Then, the Endpoint does a bitbackup against this backup file, thus transfering only the changed bits to the backup server.

Refer to the Endpoint's manual (section: SQL Server) for more information on SQL Server.

1) Open Command prompt.
2) Browse to location of InstallUtil.exe which can found under C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727, folder.
3) Run the command>
InstallUtil "C:\Program Files\Remote Backup\ExchangeBackupService.exe"
This will install the service.
4) Start the service "Exchange Backup Agent" from the Services Panel.
5) Restart the client software, and try reconnecting to Exchange.


Reference: http://msdn.microsoft.com/en-us/library/aa984379(VS.71).aspx

http://support.microsoft.com/kb/249694

1.Perform disaster recovery of the Remote Backup software with your username, password and the encryption key or the key file.
2.Install Active Directory. It is required that you use the same domain name and the DNS Server settings.
3.Restore System State. Restart the computer for the changes to take effect.
4.Restart the computer in Directory Services Repair Mode. Now restore Active Directory.

Additional Resources:

Restoring Active Directory on a computer with different hardware configuration:

http://support.microsoft.com/kb/263532

Exchange Backup was not running while temp path was on a NAS drive. Normal backups were working fine.

Cause :

In Windows XP, Windows Server 2003, and earlier versions of Windows, all services run in Session 0 along with applications. According to Microsoft, this situation poses a security risk. That is why in Windows Vista, Windows Server 2008, and later versions of Windows, the operating system isolates services in Session 0 and runs applications in other sessions, so services are protected from attacks that originate in application code.

The RBS Endpoint exchange service is designed to read the permissions from the services panel. Since the service was not running in session 0 (zero) session, it was not able to resolve the permissions to this mapped drive (K:), where K:\ drive was the temp path location assigned for the RBackup Client.

Resolution :

Follow the steps below -

1) Create a new mapped drive letter (M:). The reason for creating this was because actual R: drive was under another share(\\machine3\D$\ExchangeBackup). Need not do it if there is no nesting.

2) Create a new file name called "Exchangeincremental.ini" in Remote Backup folder with the commands to read the permissions of this mapped drive.

Insert the following parameters in this INI file (case sensitive). Example below:

UNC=\\machine3\D$\ExchangeBackup
DRIVE=R
USER=$DomainName$\Administrator (check the root node under 'Active Directory system and users'.)
PASS=password

3) Restart the Endpoint.

To get to the Account Group: double-click on where it says "Backup Server URL" (* the label to the left, and not the text). That should show the Account Group.

Enter the new account group. Note that the leading zeros are significant, so enter them. For example, account group number one (1) is 000001

Click Apply

Browse to the registry branch:

HKEY_LOCAL_MACHINE\SOFTWARE\Quantum Tech, Inc.\Remote Backup\plugins\Exchange Server(VSS)

- Select the branch 'Exchange Server(VSS)' and then select 'Edit' menu and select 'New -> String Value'

Name the new registry key as "WriterAvailable" and set the value to True.

- Restart the Endlpoint software (or service).

VSS open files Backup failed. Error: The maximum number of volumes has already been added to the shadow copy set. in BCVssOpenFilesProcess

The Error is thrown by VSS (Volume Shadow Copy Service). This error is caused due to the following reasons:

- Not enough disk space available to create a shadow copy of the files. Make sure you have enough free space (Temp Path location for the Endpoint).

If you do not have enough free space, redirect the Temp Path location on the Endpoint to a bigger drive, or free some space by deleting Temporary files and running Disk Cleanup. You can also create more free disk space by deleting all restore points except the latest:

http://support.microsoft.com/kb/555367

- Some other software may also be trying to access the shadow volume for that drive, e.g. disk defragmenters, other backup software. If you have other software installed that maybe be using VSS, reschedule the backup to a different time.

It will log exceptions in the backup log for files that failed to backup that exceed this quota as 'EXCP: xxxxx file was skipped. File exceeds SessionQuota.'

To increase or change the Session Quota on the Endpoint software, follow the steps below:

From the Server:

• Log into the Server's Web Console as Admin.
• Select Endpoints -> Manage Endpoints
• Select the Remote Management icon for the Endpoint you want to edit.
• Select the Backup Schedule subtab.
• Scroll down to the Purge/Retention and Advanced Properties section, and edit the Session Quota.

At the Endpoint Simple/Standard Interface:

- Select 'Backup Set' and click on Edit Existing Backup Set. Click on Next till you reach the scheduling options (step 3 of 3)
- Click on 'Advanced' button, and enter Admin override password (default admin password is Admin)
- Select the tab 'Schedule Options' and change the setting 'Session Quota'. Click on Ok to save changes.

AT the Endpoint Advanced Interface:

- Select 'Options' - Preferences from the client menu.
- Double click on the lock and enter the Admin override password.
- Click on 'OK' to close the Preferenecs window, and come back to the main interface.
- From the Schedule menu, choose 'Backup Schedule'.
- In the schedule inteface, at the bottom you will find Properties. Change the Session Quota value here and click on Apply/Save.

Note: There is an automatic Image Converter on the Partner's Portal that can do this conversion for you. Log into the Partner's Portal, select the Graphics Conversion Utility and follow instructions.

The images required are 4 icon files (.ICO) and 2 bitmap files (.BMP). Image files must be rendered EXACTLY according to these specifications and file types. The software will not run otherwise.

rbabout.bmp (The About screen)

Width       - 304 pixels
Height      - 144 pixels
HResol      - 72 dpi
VResol      - 72 dpi
Bitdepth    - 32
Frame Count - 1
Bits Per Pixel - 24
Size-128KB

rbicon1.ico (16 pixel desktop icon)

Width       - 16 pixels
Height      - 16 pixels
HResol      - 96 dpi
VResol      - 96 dpi
Bitdepth    - 32
Frame Count - 1
Bits Per Pixel - 24
Size-1.37Kb

rbicon3.ico (Progress icon)

Width       - 16 pixels
Height      - 16 pixels
HResol      - 96 dpi
VResol      - 96 dpi
Bitdepth    - 32
Frame Count - 1
Bits Per Pixel - 24
Size-1014 bytes

rbicon4.ico (Progress icon)

Width       - 16 pixels
Height      - 16 pixels
HResol      - 96 dpi
VResol      - 96 dpi
Bitdepth    - 32
Frame Count - 1
Bits Per Pixel - 24
Size-1014 bytes

RBicon.ico (32 pixel Desktop icon)

Width       - 32 pixels
Height      - 32 pixels
HResol      - 96 dpi
VResol      - 96 dpi
Bitdepth    - 32
Frame Count - 1
Bits Per Pixel - 24
Size-3.18KB

rbu3216.ico (The in-EXE icon)

Width       - 16 pixels
Height      - 16 pixels
HResol      - 96 dpi
VResol      - 96 dpi
Bitdepth    - 32
Frame Count - 1
Bits Per Pixel - 24
Size-3.18KB

redx3216.ico (The red X)

Width       - 16 pixels
Height      - 16 pixels
HResol      - 96 dpi
VResol      - 96 dpi
Bitdepth    - 32
Frame Count - 1
Bits Per Pixel - 24
Size-3.55KB

rbsplash.bmp (The splash screen)

Width       - 478 pixels
Height      - 201 pixels
HResol      - 72 dpi
VResol      - 72 dpi
Bitdepth    - 32
Frame Count - 1
Bits Per Pixel - 24
Size-281KB

For more information, contact Technical Support.

]]> Eliminating VSS Error 8194 from Event Log:

When you start the Remote Backup program you may experience multiple instances of VSS Error 8194 in the Application event log. These errors DO NOT generally impact the ability of the program to perform online backups, but often raise questions from system administrators or managed service providers due the error status indicated. This tech note explains how to make the adjustments required to eliminate these messages from occurring in the Application event log.

The 8194 events are typically generated by the following services: System Writer (Cryptographic) service, NPS VSS Writer service, TS Gateway Writer service and (Windows) SP Search VSS Writer service. There may be others. The error is similar to the following taken from an SBS 2008 R2 system:

----------------------------------------------
Log Name: Application
Source: VSS
Date: 7/20/2011 11:16:01 PM
Event ID: 8194
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: MYSERVER.mydomain.local
Description:
Volume Shadow Copy Service error: Unexpected error querying for the IVssWriterCallback interface. hr = 0x80070005. This is often caused by incorrect security settings in either the writer or requestor process.

Operation:
Gathering Writer Data

Context:
Writer Class Id: {57af97e4-4a76-4ace-a756-d11e8f0294c7}
Writer Name: SPSearch VSS Writer
Writer Instance ID: {5c70a0f1-d237-4ae5-b9c3-a2bfce0f6517}

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

Error code 8194 is an "Accessed Denied" error caused by the inability of one or more VSS system writers to communicate with the Remote Backup VSS requestor process via the "COM" calls exposed in the IVssWriterCallback interface (Microsoft programming interface to the Volume Shadow Service).

This is not a functional error in the Remote Backup program, but rather a security issue caused by select VSS writer(s) running as a service under the "Network Service" (or "Local Service") account(s) and not the Local System or Administrator account. By default, in order for a Windows service to perform a COM activation it must be running as Local System or as a member of the Administrators group.

In general, Remote Backup is not used to backup the files managed by these VSS system writers - so the errors have no impact on the success of the backup. However, Managed Service providers are typically concerned by these recurring error messages and often question whether the backups are actually running properly - since the event is listed as a serious error.

There are two ways to clear the problem.

The first is to locate the VSS writers (Start | Run | services.msc) that are erring out and change the account they are running under from Network Service to Local System. Then, restart the service process (or reboot the computer) and the VSS Writer will run with max privileges - thereby eliminating the IVssWriter callback errors.

The possible security issue with this method is that the service will be running with a higher level of access than Microsoft intended. Should the VSS Writer process be "hacked", this could be a security weakness. But, if you're not overly concerned about that, repeat this process for each VSS Writer that generates an 8194 error and you should not experience any more error events in normal operation.

The second (preferred) way to work around the issue is to make an adjustment to the default COM service activation permissions - allowing Network Service (and possibly Local Service) user account(s) to activate the IVssWriter callback interface. This method has the benefit of permanently fixing the issue in one place and allowing the VSS Writer service(s) to run at the privilege level that Microsoft intended. Any COM object accessed (by a process running as Network Service) still has the ability to enforce security restrictions it so chooses.

Make this fix by doing the follow: Start | Run | dcomcnfg. This brings up the Component Services application.

On the left pane navigate to Component Services | Computer | MyComputer.

Right click on MyComputer and select properties.

Select the COM Security tab and select the Edit Default button under Access Permissions.

Use the Add... button to add the "Network Service" account to the permission list.

Verify that ONLY the Local Access box is checked and click OK.

Close Component Services.

A reboot is then required to make the requested changes to COM Security.

Remote Backup uses Windows Volume Shadow Copy Service (VSS) to backup Exchange 2003, 2007 and 2010. Snapshots of the Exchange files are taken to ensure the consistency of the backup data. Once the snapshot is complete, Exchange database and log files are checked for integrity. If the integrity check fails, an exception is written to the backup log file.

Remote Backup supports full and differential backups for Exchange Server Database level backup. The first backup is always a full backup (irrespective of the backup type selected, preferred is Incremental), which will backup the database and the log files. When the full backup finishes successfully the transaction log files are flushed.

Successive backups are differential (irrespective of the backup type selected), and back up only the transaction log files. After every differential backup a check is performed to confirm that the Exchange server can be rebuilt using the last differential and the dependent full backup. If this check fails, a full backup is forced.

Differential backups of Exchange grow in size as you do daily backups. You can set either of the following options (registry key option) for Exchange backup to roll-over and do another full:

HKEY_LOCAL_MACHINE\SOFTWARE\Quantum Tech, Inc.\Remote Backup\Plugins\Exchange Server(VSS)

KeyName: DiffMaxCount
KeyType: REG_SZ
KeyValue: Number representing the "Number of differential" backups before forcing a full (Example: 30 - So, after first full backup, the client performs 30 differentials before forcing another full.)

KeyName: DiffPerct
KeyType: REG_SZ
KeyValue: Number representing the percentage size of the differential backups compared to the full that has to be reached or exceeded to force a full backup. (Example: 75 - meaning if the differential reaches 75% of the size of the full, a full backup is performed.)

SQL Backup Threshold Options:

Remote Backup supports differential backup. The first backup will always be a full backup of the data (regardless the backup type selected - preferred is "Incremental") and successive backups will be differential (regardless the backup type selected). After every differential backup a check is performed to confirm that the SQL database can be restored using the last differential and the full backup. If the check fails, a full backup is forced.

Differential backups keep growing in size. You can set either of the two options below to force another full:

HKEY_LOCAL_MACHINE\SOFTWARE\Quantum Tech, Inc.\Remote Backup\Plugins\SQL Server

KeyName: DiffMaxCount
KeyType: REG_SZ
KeyValue: Number representing the "Number of differential" backups before forcing a full (Example: 30 - So, after first full backup, the client performs 30 differentials before forcing another full.)

KeyName: DiffPerct
KeyType: REG_SZ
KeyValue: Number representing the percentage size of the differential backups compared to the full that has to be reached or exceeded to force a full backup. (Example: 75 - meaning if the differential reaches 75% of the size of the full, a full backup is performed.)

Step 1: Is it the same machine, with a new hard drive?  If yes, proceed to Step 2, if not proceed to Step 8.

Step 2: Make sure the Operating System and other software (third party software) are installed as per the last system build (i.e. as per the day before system crash). Installing all the third party software or at least most of them will ensure proper operations after the System State restore.

Make sure Active directory is installed and configured with same 'Domain Name' as before.

Step 3: Install the RBackup Endpoint software (in Application mode) and make sure it’s the same version as before system crash. That is, if the old machine had version 11.11 try to install the same version instead of latest version. Installing the same version will make sure the registry settings do not change after the System State restore.

If you don’t have the previous version, you can still install the latest version (Follow procedure in Step 7).

Step 4: Start the RBackup Endpoint and select Disaster recovery. Provide the latest key file or type in the Key details. (Make sure you use the latest key file information). Once the Distaster Recovery is complete, restart the client application.

Step 5: (System State Restore) From RBackup restore interface, restore the most recent version of System State (Preferably the last backup). System State can ONLY be restored to original location.  On successful restore, reboot the machine.

Step 6: (Login to Directory Services Restore Mode) Reboot the machine and login to Directory Services Restore Mode (DSRM): To reboot into DSRM mode, reboot your PC, and press [F8] during the startup sequence. You'll see the following options: -

-Safe Mode
-VGA Mode
-Last Known Good
-Directory Services Restore
Select Directory Services Restore Mode.  DSRM mode looks like Safe Mode with Networking enabled. (Active Directory services will be stopped) 

Step 7 (Active Directory Restore): If you have installed the latest version of the Endpoint to restore System State, then the RBackup Endpoint should have restored all the old registry settings, which includes the previous version of RBackup Endpoint’s registry settings (as in the original machine). Therefore the newer version of the Endpoint may sometimes fail to open with error messages (like 'Active X' errors, 'Automation' errors or 'Block variable not set' errors). 

Close the Endpoint application (also from system tray) and take a backup of the "backup.mdb" file. This file resides under the application folder (usually, C:\Program Files\Remote Backup). After making a copy of the backup.mdb file, uninstall the Endpoint application. Reinstall the latest version again. When prompted for New Registration or Disaster Recovery, close the Endpoint application and copy back the backup.mdb that you saved earlier into the application folder. Restart the Endpoint application.

From the RBackup Restore interface, restore the most recent version of Active Directory (preferably from the last backup). Active Directory can ONLY be restored to the original location.  On successful restore you will get a message saying “Reboot machine in normal mode”. Reboot the machine in Normal mode and check the Active Directory settings.

Step 8: Active Directory restore to a different machine - http://support.microsoft.com/kb/263532 (How to perform a disaster recovery restoration of Active Directory on a computer with a different hardware configuration).

Error in backup log: 'Failure to backup open file'

The problem is the inability of the Endpoint module to load its VSS libraries due to missing/redirected Visual C++ runtime library routines. This is sometimes caused by the installation/uninstallation of Visual Studio development platform or other corruption.

The fix is to reinstall the 2008 SP1 Visual C++ Runtime Library routines as listed below: (pick your machine architecture and install 1 only)

http://www.microsoft.com/download/en/details.aspx?id=5582
Microsoft Visual C++ 2008 SP1 Redistributable Package. (x86)

http://www.microsoft.com/download/en/details.aspx?id=2092
Microsoft Visual C++ 2008 SP1 Redistributable Package. (64-bit)

Reboot not required.

Sometimes someone other than the Online Backup Service Provider works on an end user's computer and finds the RBackup Endpoint software running, and has questions about it.

Remote Backup Systems cannot support the end users of our customers. So, you have to find out who the Service Provider is and ask him to support you. If the software has not been branded, you have to dig through the registry to find the server's serial number.

Use Regedit (AT YOUR OWN RISK!) to get the value of the key:

HKLM\Software\Quantum Tech, Inc.\Remote Backup\Serial

If the value is there, write it down and contact Remote Backup Systems. We can look up the serial number and tell you who the Service Provider is. If the value is NOT there, the software is too old and we will not be able to find the Service Provider.

Follow the steps given below on this Endpoint.

1. On RBS Client, go to Schedule--Backup Schedule.

2. Click on Apply and close.

Repeat the above two steps for all the available backup sets.

This will reinitialize the backup sets and force the client to send session info file to RBS Server.

Run a schedule backup and check now.

Go to Setup -> Test Server

If online Server test is successful, run a Test Connection from any Endpoint  (Run -> Test Connection)

Also try to telnet from the Endpoint machine to RBS Server, if there is a Telnet client on the Endpoint.

Follow the steps given below

IMPORTANT: If this is an existing Endpoint, take a copy of the backup.mdb file from the Remote Backup folder (usually c:\program files\remote backup\) before following the steps given below.

Now follow the steps below to uninstall the client manually:

Steps for complete uninstall of Endpoint: (Skip the steps which are not applicable in your case and perform the next step)

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

2. Delete the folder C:\Program Files\Remote Backup\

3. Delete the folder C:\Program Files\Common Files\

4. Go to the folder C:\Program Files\Install Shield Installation Information\

Delete the folder: f0674b40-d8c3-11d3-8c61-00104b1f6cf0

...or search for it and delete it. (This may be a HIDDEN folder)

5. Go to Start->Run. Type in regedit

Go to HKEY_Local Machine->Software->

Delete the whole 'Quantum Tech, inc' branch.

6. Open a command window. Type set

Look for the path for the temp directory. Go to that directory and delete everything in it.

7. Delete the folder \common files\installshiled\engine\6\

Also try the following steps before reinstalling:

1. Open RegEdit.

2. Navigate to HKEY_CLASSES_ROOT

3. Press "r", that should jump you to the vicinity of "rbClient.Connector

rbClient.Connector

rbClient.IrbStatus

rbControl.CRBCommand

There may be a few others. Any other entries here that start with rbclient, rbackup or rbcontrol. should be deleted.

Restart the machine, reinstall the Endpoint using the default Endpoint installer. Reboot the system when prompted.

Replace the saved backup.mdb which was copied from the Remote backup folder, overwriting the empty file that was most recently installed.

To run a copy-to-disk please follow the steps:

1.) Make sure the Attempt Window on the Schedule -> Backup Schedule window is set to "Unlimited".

2.) Make sure the schedule is set to "On Demand" for all the available backup sets (Including the current backupset).

3.) Close the Rbackup Endpoint completely. Kill rbackup.exe and rbclient.exe via Task Manager (If running).

4.) Now go to Start -> Run and type 'regedit'. This will open the registry editor window. On the registry editor window, navigate to the path below:

HKEY_LOCAL_MACHINE\SOFTWARE\Quantum Tech, Inc.\Remote Backup\Settings:

For 64-bit machine

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Quantum Tech, Inc.\Remote Backup\Settings:

On the right pane create a new String value as below:

"SetWindow" - REG_SZ - "False"

5.) Now Start the Endpoint and start the Copy to Disk backup.

Incremental backup will scan for files' archive flags and backup the files which have been changed since last backup. The operating system automatically sets the Archive Flag on each file that is edited. Incremental always backs up full files. That is why incremental backup is recommended for small size files.

Bitbackup on the other hand will backup only changes. Here is an example.

Lets say there is a 1 GB file. If you backup this file using the Incremental backup type, the first backup will be a FULL backup and then if this file is ever changed (for example, 100MB is added, so now the size is 1.1 GB), the next incremental backup will backup this 1.1 GB file.

If you backup this file using BitBackup, the first backup will be a FULL backup and the next backup only the 100 MB that has been added.

So, BitBackup will not do a backup of entire 1.1 GB. This is the reason BitBackup is recommended for very large files that change only a little - like CAD drawings.

The BitBackup process takes more time than Incremental backup because it has to scan entire files and extract changes while comparing previous versions. It is NOT a good idea to use BitBackup for all files because of the slower speed and because it requires sometimes a lot of temporary space on the Endpoint computer.

Do not use BitBackup on medical radiographs, movies, pictures, sound files, or other large files that NEVER change.

The Endpoint-side disk space needed for Incremental is only temporary, just enough to store the backup files that have been prepared for backup but not sent to the Server yet. The files are deleted from the local drive after they have been verified on the Server. The number of files queued up locally is 100 by default. This can be adjusted, and the location of the temporary file path can also be set to another drive if needed.

BitBackup uses permanent space on the Endpoint to store its reference files. This is called the BitBackup Ref Path. It needs about one and a half times the size of all the files included in a BitBackup backup set. Because this can be such a large amount of space, we recommend against using BitBackup except on specific file sets containing large files that change just a little.

The scheduler interface includes options to set up scheduled jobs to run via the Windows Task Scheduler instead of RBackup's built in scheduler. Advanced options for Windows Task Scheduled jobs include Power Management Options: 1) Don't start the task when running on batteries 2) Stop the task if battery mode begins, and 3) Wake computer to run backups.

From the Endpoint interface go to Schedule -> Backup Schedule

Use Task Scheduler – Select this checkbox to use the Windows Task Scheduler to launch this backup set instead of using RBackup’s built-in scheduler. Some applications have the potential to interfere with RBackup’s built-in scheduler, especially when RBackup is running in Service Mode. It is generally considered more reliable for wide-scale distributions to use the Windows Task Scheduler.

If you want to manually create a scheduled task to run Rbackup, follow these instructions:

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 a list of almost all the programs installed in your machine. Look for the rbClient.exe, if it is not there, browse and select rbClient.exe from the client installation directory (by deafult, its C:\Program Files\Remote Backup). Selecting the exe file automatically takes you to the next screen which shows schedule options.

4. Select the options according to your preferences, click next.

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

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

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 should 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.

IMPORTANT : Make sure that the Endpoint interface is closed during scheduled time.

1.) Close the Rbackup Endpoint completely. Stop rbackup.exe and rbclient.exe via task manager (If running).

Open the Registry Editor (regedit.exe) and browse to the following registry branch: 

For 32 Bit:

HKEY_LOCAL_MACHINE\SOFTWARE\Quantum Tech, Inc.\Remote Backup\Plugins\Exchange Server(VSS):

For 64 Bit:

 HKEY_LOCAL_MACHINE\SOFTWARE\wow6432\Quantum Tech, Inc.\Remote Backup\Plugins\Exchange Server(VSS):

KeyName: EseutilPath

KeyValue: (path of the Eseutil program, usually this location is the Exchange 'Install Dir'\Bin folder)

Make sure the value of the key "EseutilPath" points to the location of Eseutil.exe.

First run the DOS Command: vssadmin list writers

Run the DOS command: net stop vss

This should stop the volume shadow copy service. Make sure the status shows as manual.

Check for errors.

Restart RBackup Endpoint and start a backup with Backup Now.

1. Open Registry Editor (regedit.exe) and navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Quantum Tech, Inc.\Remote Backup\Plugins\Exchange Server and look for the ExcludeItems key.

 2. You can exclude multiple items by separating them by a colon.

Example 1: If you want to exclude any mailbox folder, use MBX/mailboxname/foldername. For example, to exclude the Administrator's Inbox, this would be "MBX/Administrator/Inbox"

Example 2: For Public folders, use public folders/foldername. For example, to exclude Internet Newsgroups, use "public folders/Internet Newsgroups"

Example 3: For excluding multiple items the value of the key should be like below:

MBX/Administrator/Calender:MBX/User1/Calender:public folders/My Public Calender/Calender

The above string in the ExcludeItems registry key would exclude Administrator's Calender, User1's calender and a "Calender" folder item in public folders/My Public Calender.

If stopped or set as manual, change it to Automatic.

Now start the Endpoint and try to connect to the Exchange server.

Method 1 - Can be used to grant Administrator full access so new users added later can also be accessed by the Rbackup Endpoint.

Method 2 - If you do not want Administrator to give full permissions, then create a default user, and give that full permissions.

Method 1:

1. Follow these steps to give the administrator account full access to all the mailboxes (Information Store)

The Administrators group should have the Allow option set and Deny option not set for Send As and Receive As Permission.

i. Open the Exchange System Manager.

ii. Expand the Organization

iii. Next expand the Administrative Groups container

iv. Expand <administrative group name>, Servers container, <server name>, the Storage Group and <storage group name>

a. Right click on the store containing the mailboxes you want to grant access to, and choose properties

b. Click on the security tab and choose the Administrators group from the list. If the Administrators group is not already there, click on Add and add it.

c. Scroll down the list of permissions and check Allow for the Send As and Receive As permission and then click OK. Make sure Deny Permissions are not set for them.

Restart the Rbackup Endpoint Software.

If you still cannot access the mailbox, restart all Exchange services from the Services Panel or reboot the machine and try it again from the Rbackup Endpoint software.

Method 2:

Follow these steps to create a new user and give him access to all the mailboxes (Information Store) 

i. Open Active Directory Users and Computers from Control Panel -> Administrative Tools.

ii. Right Click on Users and select New User, give it a FirstName, LastName, logon name etc and click Next.

iii. Type a password, enter the same in the Confirm Password, select your password options, click Next.

iv. Make sure "Create an Exchange Mailbox" is checked and click Next.

v. Click on Finish to create the user.

vi. Right Click on the created user and select properties.

vii. Naviagate to the "Member of" Tab, click on Add, type Administrators, click ok, ok.

viii. Open the Exchange System Manager.

ix. Expand the Organization

x. Right click (on the top node) and choose Delegate control.

a. Click next and then Add and Browse. From the object picker choose the user (the user that we just created) you want to grant access and click ok.

b. Make sure the Exchange View Only Administrator is chosen and click OK.

c. Click Next and Finish

How to enable the Security tab for the organization object in Exchange 2000 and in Exchange 2003

http://support.microsoft.com/default.aspx?scid=kb;EN-US;264733

xi. Next expand the Administrative Groups container

xii. Expand <administrative group name>, Servers container, <server name>, the Storage Group and <storage group name>

a. Right click on the store containing the mailboxes you want to grant access to and choose properties

b. Click on the security tab and choose the user from the list. If the user was added as part of a group at the View Only Administrator level then that individual user will need to be added at this time if the entire group is not going to be granted Receive As permissions here.

c. Scroll down the list of permissions and check allow for the Send As and Receive As permission and then click ok

The Information store may cache this data and it can take up to 2 hours for this cache to be flushed. Dismount and remount the store to flush this cache immediately or reboot the machine for this cache to reflect the permissions immediately.

Go to Options : Preferences and then double click the padlock icon and enter the password (The default is "Admin" with a capital "A", but this can be changed in the Customize Endpoint Installer tool.

Click OK on Preferences window.

Now go to the Schedule : Backup Schedule window. Check the purge settings to make sure they are correct.

You can also check the backup log sent by this Endpoint. It is in this Endpoint's root directory on the RBS Server.

Search the logs.zip folder in this Endpoint's root directory. Arrange them in modified date/time format. Check few of the recent backup logs and confirm if these files were backed up correctly.

If you have set the purge/retention settings incorrectly and files really are missing there is nothing you can do inside RBackup to recover them. However, you may still be able to recover them from the Recycle Bin, or you may be able to use one of the many "Unerase" utilities to un-delete them from the Server.