When performing a backup of any type, the following error message is received in the backup report:

[StartBackupRqt] IP=’User-IP-Address’ User=’Username’ BackupSet=’Backup Set (BackupID)’ BackupJob=’YYYY-MM-DD-hh-mm-ss’ StartTime=’YYYY-MM-DD hh:mm:ss’ CurrentTime=’YYYY-MM-DD hh:mm:ss’ Error=’null’. Client agent will retry shortly.

The message suggests that the request for a backup set’s file list from the GBData server has timed out.

When a backup job is initiated, the GBDataOBM client would request for a backup set’s file list from the GBData server. As the request is made, the GBData server will generate the file list and compress this information to “block” file(s), where the block(s) are then sent to the GBDataOBM client (as each block is generated).

During the generation of the file list , if the time taken exceeded the timeout period for GBDataOBM, the retry message is flagged. GBDataOBM would also submit this retry null error to GBData server.

When performing a backup of any type, the following informative message is received in the backup report:

No checksum file found. File “Directory_PathFile” is being backed up in its entirety along with its checksum file

The message suggests that the checksum file of the corresponding data file on the GBData server is missing or corrupted.

You can safely ignore the message, as the checksum file along with the data file would be uploaded again when the current backup job is performed.

Please also verify if there are hardware or I/O issues with the corresponding User Home partition.

When performing a backup of any type, the following error message is received in the backup report:

Checksum of file User_HomeUsernamefilesBackup_IDCurrentxxxxxxxxxxxxxxxxFile is incorrect. Deleting backup file – ServerPath=’User_HomeUserfilesBackup_IDCurrentxxxxxxxxxxxxFile’ BackupSet=’Backup_Set(Backup_ID)’ BackupJob=’Current’ ClientPath=’Directory_PathFile’ Type=’C’ RunByBackupJob=’YYYY-MM-DD-hh-mm-ss’

The message suggests that the checksum value of the corresponding data file on the GBData server is not correct.

You can safely ignore the error, as the incorrect file has been removed from the GBData server, the file would be uploaded again when the current backup job is performed.

Please also verify if there are hardware or I/O issues with the corresponding User Home partition.

When performing a file backup, the following error messages are received in the backup report:

File=”\Network_DriveDirectoryFile” Error=”Access is denied.”

The message suggests that the login credentials specified in the “User Authentication for Windows” setting of the file backup set does not have sufficient right to access the file or directory specified.

Please ensure that the login credentials specified in the “User Authentication for Windows” setting does have sufficient right to access the file or directory.

Example with GBDataOBM

network drive

If the problem persist, please also verify if the “Log on” account of the GBDataOBM / GBDataACB scheduler service has sufficient permission right(s) to access the temporary directory.

Alternatively, instead of “Local System”, please try running the GBDataOBM / GBDataACB scheduler service with a Windows account that has sufficient permission right(s) to access the temporary directory. You can do so by following the instructions below:

1. Open [Control Panel] -> [Administrative Tools] -> [Services] -> [Online Backup Scheduler (GBData Online Backup Manager / GBData A-Click Backup)] -> [Log on]
2. Select the [This Account] option
3. Enter the Login Credentials
4. Restart the [Online Backup Scheduler (GBData Online Backup Manager / GBData A-Click Backup)] service

When performing a file backup, the following informative messages are received in the backup report:

[Shadow Copy] (1/10) Will retry in 60 Sec.

[Shadow Copy] (2/10) Will retry in 60 Sec.

…

[Shadow Copy] (10/10) Will retry in 60 Sec.

[ERROR] VSS_E_WRITER_INFRASTRUCTURE

Notes:

Since a shadow copy cannot be created, the error above will usually result with the following error being flagged as well:

[Error][Updated File] File=”C:Directory_PathFile” Error=”The process cannot access the file because it is being used by another process.”

This is a Microsoft Volume Shadow Copy issue.

Windows XP / Vista:
To resolve the issue, please re-register the Volume Shadow Copy Service. To do so, you could utilize the “RegisterVSS.bat” script available in ${Install-Home}bin. Please also reboot the machine afterward.

Notes:
Please safely ignore the error message(s) displayed during the re-registration, as some of the DLL files are platform specific.

Windows 2003:
To resolve the issue, please follow the instructions below:

1. Please backup the registry key -
   HKEY_LOCAL_MACHINESOFTWAREMicrosoftEventSystem{26c409cc-ae86-11d1-b616-00805fc79216}Subscriptions
2. Remove this registry key along with all its sub-keys
3. Reboot the machine

Although, it is not an official recommendation from Microsoft, this key will get recreated after the machine is restarted.

When performing a file backup, the following informative messages are received in the backup report:

[Shadow Copy] (1/10) Will retry in 60 Sec.

[Shadow Copy] (2/10) Will retry in 60 Sec.

…

[Shadow Copy] (10/10) Will retry in 60 Sec.

[ERROR] VSS_E_PROVIDER_VETO

Notes:

Since a shadow copy cannot be created, the error above will usually result with the following error being flagged as well:

[Error][Updated File] File=”C:Directory_PathFile” Error=”The process cannot access the file because it is being used by another process.”

The message suggests that the file(s) being backed up is on a FAT32 partition and either there is no NTFS partition on an internal drive or that NTFS partition has less than 100MB of free disk space.

The problem can also occur if the disk activity was high when the backup job is performed.

To resolve the issue, please correct the partition issues suggested above and perform the backup again.

Please also verify if there is other application(s) running on the corresponding machine, which may require a high amount of disk resources. Alternatively, you can perform the backup when disk usage is low.

When performing a file backup, the following error message is received in the backup report:

[ERROR] VSS_E_UNEXPECTED_PROVIDER_ERROR

Notes:

Since a shadow copy cannot be created, the error above will usually result with the following error being flagged as well:

[Error][Updated File] File=”C:Directory_PathFile” Error=”The process cannot access the file because it is being used by another process.”

This is a Microsoft Volume Shadow Copy issue.

Windows XP / Vista:
To resolve the issue, please re-register the Volume Shadow Copy Service. To do so, you could utilize the “RegisterVSS.bat” script available in ${Install-Home}bin. Please also reboot the machine afterward.

Notes:
Please safely ignore the error message(s) displayed during the re-registration, as some of the DLL files are platform specific.

Windows 2003:
To resolve the issue, please follow the instructions below:

1. Please backup the registry key -
   HKEY_LOCAL_MACHINESOFTWAREMicrosoftEventSystem{26c409cc-ae86-11d1-b616-00805fc79216}Subscriptions
2. Remove this registry key along with all its sub-keys
3. Reboot the machine

Although, it is not an official recommendation from Microsoft, this key will get recreated after the machine is restarted.

When performing a file backup, the following error messages are received in the backup report:

[Error][New File] File=”Directory_PathFile” Error=”The device is not ready. ”

The message suggests that GBDataOBM / GBDataACB has problem reading the backup source media. Some possible causes of this issue could be hardware problem on the media in concern, Volume Shadow Copy issue, etc.

Windows XP / Vista:
To resolve the issue, please re-register the Volume Shadow Copy Service. To do so, you could utilize the “RegisterVSS.bat” script available in ${Install-Home}bin. Please also reboot the machine afterward.

Notes:
Please safely ignore the error message(s) displayed during the re-registration, as some of the DLL files are platform specific.

Windows 2003:
To resolve the issue, please follow the instructions below:

1. Please backup the registry key -
   HKEY_LOCAL_MACHINESOFTWAREMicrosoftEventSystem{26c409cc-ae86-11d1-b616-00805fc79216}Subscriptions
2. Remove this registry key along with all its sub-keys
3. Reboot the machine

Although, it is not an official recommendation from Microsoft, this key will get recreated after the machine is restarted.