AIR replication restart
Hello
I have a question regarding deduplication and AIR : when a replication is interrupted for any reason (link failure, server reboot, ....) are the block already sent to the other site totaly lost ? With other words, when the replication is restarted (from 0 of course) , is it really not optimized (supposing it is the first time it runs) or the first part of the replication can take advantage of already sent blocks ?
I imagine the blocks received by the remote MSDP are stored then could be potentially be used ... but maybe they are flagged "to be deleted" when the replciation process is broken and then can not be used ...
If anybody has knowlegde or ideas on this point ....
Best regards
Hello,
refer to GarbageCheckRemainDCCount parameter in Dedup Guide:
The number of containers from failed jobs not to check for garbage. Afailed backup or replication job still produces data containers. Because
failed jobs are retried, retaining those containers means NetBackup
does not have to send the fingerprint information again. As a result,
retried jobs consume less time and fewer system resources than when
first run.
Rgds