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

Path “Directory_PathDirectory” does not exist!

However, the directory path in concern has been removed from the backup source already.

The message suggests that the mentioned path is still being selected as part of the backup source. This warning message can also be flagged if a backup filter is still being set to be applied on the mentioned directory path.

To resolve the issue, please ensure that the corresponding directory path is removed from the backup source of the affected backup set. Please also verify if there is any filter that may be applied to the directory path in concern.

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

Incomplete backup file deleted because the file was not updated within the last 48 hours.. Deleting backup file – ServerPath=’User_HomeFile’ BackupSet=’Backup_Set(Backup_ID)’ BackupJob=’Current’ ClientPath=’Directory_PathFile’ Type=’F’ RunByBackupJob=’YYYY-MM-DD-hh-mm-ss

The message suggests that the upload of the corresponding file has not been completed, and there is no update on the file within the next 48 hours. Thus, the incomplete file is removed from the GBData server.

Since the incomplete file has been removed from the GBData server, the file would be uploaded again when the next backup job is performed. If the issue only occurs occasionally, you can safely ignore the error.

In the cases where the issue persist, please ensure that the connection to the GBData server can be established during the backup process.

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

Unable to log to server. Error=”[YYYY/MM/DD hh:mm][Http.doPost] Error=’Connection

timed out: connect’. Still Fail After Retry!!!!”
The message suggests that there is problem with the connection between the GBDataOBM / GBDataACB client and the GBData server.

If the issue only occurs occasionally, you can safely ignore the error. In most cases, GBDataOBM / GBDataACB will attempt to re-establish connection to the GBData server.

In the cases where the issue persist, please ensure that the connection to the GBData server can be established during the backup process.

When performing a file backup on network drive, the following warning messages are received in the backup report:

“\Network_PathDirectory” The specified username is invalid.

Skip backing up “\Network_PathDirectory” (network drive is not accessible)

The message suggests that the login credentials entered in the “User Authentication for Windows” setting for the affected backup set does not have sufficient permission to access the network drive.

To resolve the issue, please ensure that the login credentials specified in the “User Authentication for Windows” setting does have sufficient right to access the network drive.

Example on GBDataOBM:

User ID

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 network drive. Alternatively, instead of “Local System”, please try running the backup scheduler service with a Windows account that has sufficient permission right(s) to access the network drive. You can do so by following the instructions below:

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

Notes:
For issue with GBDataACB, please edit the Login Credentials for the backup scheduler service [Online Backup Scheduler (GBData A-Click Backup)] instead.

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

Orphan checksum pair file. Deleting backup file – ServerPath=’User_HomeUserfilesBackup_IDCurrentxxxxxxxxxxxxxxxx*.chk’ BackupSet=’Backup_Set(Backup_ID)’ BackupJob=’Current’ ClientPath=’Directory_PathFile’ RunByBackupJob=’YYYY-MM-DD-hh-mm-ss’

The message suggests that the GBData server located a checksum file on server, but the corresponding data file cannot be found (or vice versa).

To resolve the issue, please contact technical to rebuild your data.

When performing a backup of any type, the following job status is received in the backup report:

Backup Interrupted by System Error “Maximum retry reached”

Upon further investigation, the following informative / warning message is received in the client log:

[YYYY-MM-DD hh:mm:ss][erro] Backup Interrupted by System Error “[Thread][BackupSet Dispatcher][BackupSet][BackupSetDispatcher.sendRequest] Maximum retry reached”

The message suggests that there is problem with the connection between the GBDataOBM client and the GBData server. Furthermore, the maximum number of attempts to re-establish the connection has been reached. Thus, the backup is then terminated by the system.

If the issue only occurs occasionally, you can safely ignore the error.

In the cases where the issue persists, please ensure that the connection to the GBData server can be established during the backup process.

When performing a file backup, the following informative message is received in the backup report.

“Directory_PathFile” has been removed already

The message suggests that during the uploading stage of a backup job, the corresponding file(s) identified in the file comparison stage no longer exists on the client machine. This usually happens to temporary file(s) that is created and removed frequently.

To further explain, when a backup job is started, the following actions are performed by GBDataOBM.

1. Pre-command(s)
2. Create Volume Shadow Copy (if necessary)
3. Download the remote file list from the GBDataOBS server
4. Compare the local files with the remote file list determine the list of file(s) to be uploaded
5. Upload the data listed in Step 4
6. Post-command(s)
7. Remove the created Volume Shadow Copy

The message “…has been removed already” is flagged when a file(s) that was listed in the local file list (Step 4) no longer exists on the client machine in the file upload stage (Step 5).

Furthermore, this problem can also occurs if an incorrect Volume Shadow Copy snapshot of the file has been created, or if the affected file is not included in the Volume Shadow Copy snapshot.

Finally, for GBDataOBM / GBDataACB version prior to 5.5.1.0, this issue can also occurs if the “Temporary directory for storing backup files” assigned for the affected backup set has been set to a directory that does not exist.

To resolve the issue, please follow the instructions below:

If In-file delta is enabled for the backup set in concern, please ensure that the “Temporary directory for storing backup files” setting of GBDataOBM is set to a writable directory with sufficient disk space.

Please also verify if the file(s) in concern is temporary file. If it is, please un-select these files from the backup source to resolve the issue.

In the cases where the issue is caused by incorrect snapshot of Volume Shadow Copy, please follow the instructions below:

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.

Notes:
If you are running an older version of GBDataOBM / GBDataACB (Pre-5.2.4.0), you could consider patching the GBDataOBM / GBDataACB software to the latest patch release. The instruction can be found by Clicking Here.

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

[BackupSet.append] Checksum incorrect. File=’Directory_PathFile’ Location=’User_HomeUsernamefilesBackup_IDCurrentxxxxxxxxxxxxxxxxFile’ Recd=A Cald=B

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

Please contact GBData technical to rebuild your data.

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

[BackupSetFileSystem.resetNumDeltaMade] No full backup found for this checksum file. Job=’Current’ File=’Directory_PathFile’

Please contact technical support to rebuild your data.

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

[BackupSet.append] Uploaded file size incorrect. File=’Directory_PathFile’ Location=’User_HomeUserfilesBackup_IDCurrentxxxxxxxxxxxxxxxxFile’ ExpectedFileSize=A UploadedFileSize=B
or

File size incorrect (expected=A found=B). Deleting backup file -ServerPath=’User_HomeUserfilesBackup_IDCurrentxxxxxxxxxxxxxxxxFile’ BackupSet=’Backup_Set(Backup_ID)’ BackupJob=’Current’ ClientPath=’Directory_PathFile’ RunByBackupJob=’YYYY-MM-DD-hh-mm-ss’

The message suggests that the GBData server detected a size difference between the file size received and the file size that it was expecting. Some possible causes of this issue can be network instability, packet drop, etc.

If the issue only occurs occasionally, you can safely ignore the error.

In the cases where the network between the GBData server and the GBDataOBM client remain unstable, you can try decreasing the transfer block size. You can do so by logging into your GBDataOBM console, select [Setting], and modify [Transfer Block Size].