Error Message

N/A

When the DLO Agent is not showing a “Backup Completion percentage” of 100% there are several factors that could affect this.

• If the DLO User is in a Profile that is running Scheduled backups, files pending the schedule backup will affect the Backup Completion Percentage (See article Understanding DLO Backup Completion % when running Scheduled Backups )
• If PST files are included in the backup selection check the backup method of the PST files.  When using VSS to backup PST files the default setting is to backup PST files every 30 minutes.  If the PST file is changing often it could be in a state where it is waiting for the 30 minutes to elapse before running the backup again which will affect the Backup Completion Percentage.  If PST files are large it is also recommended to increase the time between PST backups to 240 minutes as the PST could be in a constant state of backing up which will also affect the Backup Completion Percentage.
• Agent is unable to connect to DLO server to update the status.
• Scanning of files in backup selections is yet to be completed by clients.
• Backup of all the files included in backup selection is yet to be completed.
• If initial backup data size is far less then subsequent data which is added later.
• Deletion of files and addition of files in the backup selection at the same time.
• On exit and relaunch of Agent, the backup status completion on client shows 0 % and it takes few mins to update the data based on the amount of data backed up (This is on the DLO client console).
• Any Backup failures or exceptions in protecting all the files.
   

The following items can be reviewed to help resolve this issue or to determine if the Backup Percentage showing is normal.

In the DLO Administration console, the "Time of Last Successful Backup" status will include only endpoints with 100% Backup Completion (%).

In DLO 9.5 to track 100 % backup completion for client, refer to Time of Last Successful Backup column.

Time of Last Successful Backup – This column displays the last time when the Desktop Agent backed up user’s data completely. In simpler terms, this is the time stamp when the machine had achieved a 100% Backed up status (all files in the Backup selection backed up). In case of this column being blank for a computer, it could be interpreted as the first backup, as the computer has not been backed up completely even once.

In DLO 9.6 the “Time of Last Successful Backup” column was changed to display “Time of Last Successful 100% Backup” to help eliminate confusion and to show that the agent has successfully backed up all files at some point in time.

In the computer history pane, the column Backup Completion (%) will not be updated for Windows desktop agents prior to DLO 8.0 SP3 and Mac agents prior to DLO 9.1.

In the DLO Admin Console under Setup -> Computers the DLO Agent version is displayed and any client running an older version of the Agent should  be upgraded.

Starting DLO version 9.5 backup completion percentage formula is updated to following which resolves the errors in backup completion percentage value calculation that were in previous versions.

Backup Completion % = ( FileSizeProtected / (FileSizeProtected + FileSizeToProtect) ) * 100

DLO Agent automatically updates the Backup Completion % status every 15 min to the DLO Admin Server and will also update the “Time when Agent was Last Active”

Troubleshooting steps:

1. Check if DLO agent can communicate to DLO server using ping command.
2. Check backup selection in Profile to confirm that only required files are included in backup selection.
   • Certain file types such as application files (.exe, .dll, etc.) should not be in the backup selection as these files could always be open and locked and DLO will not be able to back them up when the application is running.
3. Run DLO Diagnostics on the Agent to make sure that there are not any errors.  Also Verify that the DLO agent is able to access DLO SQL
   database by performing ODBC and UDL SQL connectivity test.  (Refer to related documents for instructions)
4. Identify any network related issues between DLO agent and DLO server/Network user data folder (NUDF).
5. Find out if the user is using BOI or VPN when running backups as this could affect the backup performance of larger files.
6. Check backup history of the user and identify/fix any backup failure issues. The backup history for this user should have some insights on any files that were unable to be backed up.