Avamar: VSR not being used even though replication is fully caught up due to network configuration changes
Summary: A change/update to customer IP/DNS on the DD caused all replicated backups to perform AMS(NCR).
This article applies to
This article does not apply to
This article is not tied to any specific product.
Not all product versions are identified in this article.
Symptoms
Customer updated DD DNS.
Reviewing Replication log files shows client X running with VSR Replication for backup #140 :
Reviewing Replication log files shows client X running with VSR Replication for backup #140 :
avtar Info <40200>: id:13 VSR selected because all base files are available
The next Replication job for this client we see backup #141 being replicated however AMS(NCR) is being invoked :
avtar Info <40199>: id:13 NCR selected because all base files are not available for VSR
Cause
Data Domain OS stores replica attributes based on IP address on the target Data Domain system. Changes in the Data Domain DNS which cause a change in its IP address mapping may lead to invalidated replication-base information. Invalidated replication-base information may trigger NCR-replicaiton instead of VSR as a one-time event. Backups will catch up to VSR but there will be a notable replication performance spike.
Resolution
Data Domain has opened RFE to eliminate this issue from occurring when updates to DNS or IP's have transpired.
Additional Information
The problem occurred because the customer changed the host name mapping of the destination on the source system.
Affected Products
AvamarProducts
Avamar, Avamar ClientArticle Properties
Article Number: 000059056
Article Type: Solution
Last Modified: 25 Sep 2024
Version: 3
Find answers to your questions from other Dell users
Support Services
Check if your device is covered by Support Services.