This would be considered an incomplete backup therefore nothing from it would be recoverable.
If Drive-D is problematic you could establish a separate policy and dataset for it to effectively isolate its backup from the other devices on the client.
Any data chunks associated with a failed backup are retained in the GSAN I believe for ~7 days so if you were to rerun the job to completion,
it will not need to retransfer these chunks and the job will go relatively quickly up to the point of its original failure.
Backup completed for A,B & C drive and before the D backup started the job failed/cancelled.
The behaviour for failed jobs is different from the behaviour for cancelled jobs.
Any data chunks associated with a failed backup are retained in the GSAN I believe for ~7 days so if you were to rerun the job to completion.
This is true for backup jobs that wrap up cleanly and create a "partial" backup. For example, if a job is cancelled or times out, a partial will be created that can be used as the basis for the next backup. These partial backups also act as "anchors" for the file and hash caches so the client will take full advantage of the cache files as well.
If a backup fails, however, no partial is created. Any chunks associated with that backup could be removed from the system the next time garbage collection runs.
Partial backups are retained for 7 days except when using the Avamar 6.1 client. The Avamar 6.1 client retains partial backups for the full duration that would have been assigned to the completed backup. The partial retention was reverted back to 7 days in Avamar 7.0. There was a good reason for the change (and the subsequent change back) but I don't think I want to open up that can of worms because the explanation is rather complicated.
Partial backups are retained on the Avamar server for 7 days. In the meantime, if the client backup completes then any chunks which belong to the partial backup now belong to the completed backup and do not ‘waste’ any space on the system.
what happens to "partical" backup if a job gets cancelled. For example i have a server that has 5TB file system that system admin forgot to exclude. The backup starts running and gets half through backing up that 5TB file system before it gets cancelled by Avamar admin. What happens to that 2.5TB that was set to Avamar ?
The partial will expire after 7 days and any unused chunks will be garbage collected away. It could take a few days for garbage collection to recover the space (depends on overall capacity, change rate, amount of expired data, etc.).
mradamk
215 Posts
619
0
Posted June 19th, 2014 04:00
This would be considered an incomplete backup therefore nothing from it would be recoverable.
If Drive-D is problematic you could establish a separate policy and dataset for it to effectively isolate its backup from the other devices on the client.
Any data chunks associated with a failed backup are retained in the GSAN I believe for ~7 days so if you were to rerun the job to completion,
it will not need to retransfer these chunks and the job will go relatively quickly up to the point of its original failure.
regards,
Adam