Skip to main content
NetApp Knowledge Base

SCV 5.0P1 retention issue in SM-BC setup

  1. Last updated
  2. Save as PDF
Views:
142
Visibility:
Public
Votes:
0
Category:
snapcenter
Specialty:
snapx
Last Updated:

Applies to

  • SnapCenter plugin for VMware (SCV) 5.0x
  • SnapMirror Active Sync (SMBC), also known as SnapMirror Business Continuity

Issue

  • When SM-BC is configured, SCV fails to delete certain snapshots at the end of backup jobs as per the retention settings.
  • While backup references are removed from the SCV repository, snapshots remain on storage.
  • These undeleted snapshots are usually flagged in ASUP with the following message:
Snapshot copy 'snaphost_name' is not successfully replicated for the relationship 'xxxxx-xxxx-xxxx' with source volume DSID 'xxxx' and path '/vol/volpath'. Reason: Failed to write metadata information to source volume snapshot
 

Potential Consequences

  • Storage Consumption: Space issues on source or destination aggregates due to the accumulation of Automated Cloud Sync (ACS) snapshots.
  • SMBC Out of Sync: SnapMirror Business Continuity (SMBC) setups may go Out of Sync if volumes or aggregates run out of space.

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.