Symptoms

An Avamar backup fails to complete within the scheduled backup window, reporting in the activity monitor with "Client Time Out - End".

Cause

The Avamar client has not previously achieved a complete backup to this Avamar server.This can be checked by running a command on the Avamar Utility Node as shown below.The output demonstrated shows zero completed backups.Example 1: admin@utility:~/>: mccli backup show --verbose=true --name=/domain/client 0,23000,CLI command completed successfully. Created LabelNum Size Retention Label Plugin Expires Server ------------------------ -------- ------- --------- ----------------------------------------- ------------------- ------------------------ ------ Whilst performing a first-time backup, the client requires a relatively long time to process (chunk, compress, hash) files within the dataset. This might not be achievable within a single backup window.Even for clients which have existing backups on the server there may be situations where the client experiences behavior similar to a L0/initial backup. Changes which could cause this include. The dataset has been redefined to back up a different drive or collection of data. The client is directed to back up to a different storage back-end compared with existing backups (this could mean Data Domain or Avamar server or using a different Data Domain to previous backups) Example 2 below shows output for a mature client. Reviewing the LabelNum, Size, Label, Plugin and Server columns can help identify these kinds of configuration changes.Example 2: admin@utility:~/>: mccli backup show --name=/clients/client1.customer.com --verbose=true 0,23000,CLI command completed successfully. Created LabelNum Size Retention Hostname Location Label Plugin Expires Server ----------------------- -------- ------- --------- ---------------------------- -------- -------------------------------------------- ------------------- ----------------------- ------ 2016-10-28 08:07:30 IST 91 3.0 GB D server.customer.com Local Default Schedule-Galactica Group-1477623600015 Windows File System 2016-12-27 04:00:00 GMT Avamar 2016-10-27 08:01:54 IST 90 3.0 GB D server.customer.com Local Default Schedule-Galactica Group-1477537200014 Windows File System 2016-12-26 04:00:00 GMT Avamar 2016-10-26 08:06:17 IST 89 3.0 GB D server.customer.com Local Default Schedule-Galactica Group-1477450800015 Windows File System 2016-12-25 04:00:00 GMT Avamar 2016-10-25 07:48:37 IST 88 3.0 GB D server.customer.com Local Default Schedule-Galactica Group-1477364400014 Windows File System 2016-12-24 04:00:00 GMT Avamar 2016-10-24 07:38:24 IST 87 3.0 GB DW server.customer.com Local Default Schedule-Galactica Group-1477278000015 Windows File System 2016-12-23 04:00:00 GMT Avamar 2016-10-23 11:34:23 IST 86 2.9 GB D server.customer.com Local Default Schedule-Galactica Group-1477191600014 Windows File System 2016-12-22 04:00:00 GMT Avamar 2016-10-21 06:58:01 IST 85 3.0 GB D server.customer.com Local Default Schedule-Galactica Group-1477018800016 Windows File System 2016-12-20 04:00:00 GMT Avamar 2016-10-20 07:51:01 IST 84 2.9 GB D server.customer.com Local Default Schedule-Galactica Group-1476932400015 Windows File System 2016-12-19 04:00:00 GMT Avamar 2016-10-19 07:56:45 IST 83 2.9 GB D server.customer.com Local Default Schedule-Galactica Group-1476846000014 Windows File System 2016-12-18 04:00:00 GMT Avamar 2016-10-18 08:05:46 IST 82 2.9 GB D server.customer.com Local Default Schedule-Galactica Group-1476759600014 Windows File System 2016-12-17 04:00:00 GMT Avamar 2016-10-17 12:19:52 IST 81 50.0 MB N server.customer.com Local MOD-1476703163000 Windows File System 2016-12-16 12:19:22 GMT Avamar 2016-10-17 12:18:55 IST 80 50.0 MB N server.customer.com Local MOD-1476703110644 Windows File System 2016-12-16 12:18:30 GMT Avamar 2016-10-17 12:17:34 IST 79 50.0 MB N server.customer.com Local MOD-1476703029055 Windows File System 2016-12-16 12:17:08 GMT Avamar 2016-10-17 12:16:27 IST 78 50.0 MB N server.customer.com Local MOD-1476702962378 Windows File System 2016-12-16 12:16:01 GMT Avamar 2016-10-17 12:15:19 IST 77 50.0 MB N server.customer.com Local MOD-1476702892944 Windows File System 2016-12-16 12:14:52 GMT Avamar

Resolution

Configure the client to run with 'overtime' until the next successful backup.Allow the backup to end gracefully at the end of the scheduled window in order that a 'partial' backup can be created on the Avamar server. The client may require several days to complete the backup. This can depend on the dataset size and the amount of new data which must be transferred over the network to Avamar.

Support Cases