PS Tech Note 066 - Application Consistent Snapshots for SnapVault

by Frequent Contributor on ‎2010-07-06 02:19 PM - edited on ‎2014-09-26 12:01 PM by Community Manager

PS Tech Notes are a weekly explanation of a NetApp command  or feature and other topics related to storage administration.  It is  written for customers as well as Professional Services and Systems  Engineers who sell and install NetApp systems.

 

This tech note discusses how the acs snapshot feature in Data ONTAP 7.3.2+ and ONTAP 8 7-mode preserves SnapVault snapshots. These snapshots can then be used liked a 'named' snapshot for backup purposes thereby improving the functionality of SnapVault.

Comments

Reading the note and the kb article I understand that acs snapshot are related only with smv/sv relationship.

I'm a bit confused because I've a sv/sm2tape relationship and I'm also seeing some acs-tagged snapshot.

Could you please clarify this?

Regards,

Roberto

There must be something in addition that is not explained here. I have a FAS2040 which is snapvault master to a FAS250, which is sv-secondary. No other snapvault/snapmirrors exist. Still, I have some snaps marked as (acs):

  %/used       %/total  date          name

----------  ----------  ------------  --------

  0% ( 0%)    0% ( 0%)  Nov 02 19:21  smvi__vsc_all_stores_hourly_recent

  2% ( 1%)    1% ( 1%)  Nov 02 18:21  smvi__vsc_all_stores_hourly_20111102182001

  3% ( 1%)    1% ( 0%)  Nov 02 18:00  sv_hourly.0    (snapvault,acs)

  4% ( 1%)    2% ( 1%)  Nov 02 17:21  smvi__vsc_all_stores_hourly_20111102172000

  5% ( 1%)    2% ( 0%)  Nov 02 17:00  sv_hourly.1   

  6% ( 2%)    3% ( 1%)  Nov 02 16:21  smvi__vsc_all_stores_hourly_20111102162000

  7% ( 1%)    4% ( 1%)  Nov 02 16:00  sv_hourly.2   

  9% ( 2%)    4% ( 1%)  Nov 02 15:21  smvi__vsc_all_stores_hourly_20111102152000

10% ( 1%)    5% ( 0%)  Nov 02 15:00  sv_hourly.3   

11% ( 2%)    6% ( 1%)  Nov 02 14:21  smvi__vsc_all_stores_hourly_20111102142000

12% ( 1%)    6% ( 1%)  Nov 02 14:00  sv_hourly.4   

14% ( 2%)    7% ( 1%)  Nov 02 13:21  smvi__vsc_all_stores_hourly_20111102132000

15% ( 1%)    8% ( 0%)  Nov 02 13:00  sv_hourly.5   

16% ( 2%)    9% ( 1%)  Nov 02 12:21  smvi__vsc_all_stores_hourly_20111102122000

17% ( 1%)    9% ( 1%)  Nov 02 12:00  sv_hourly.6   

18% ( 2%)   10% ( 1%)  Nov 02 11:21  smvi__vsc_all_stores_hourly_20111102112000

19% ( 1%)   11% ( 1%)  Nov 02 11:00  sv_hourly.7   

20% ( 2%)   12% ( 1%)  Nov 02 10:21  smvi__vsc_all_stores_hourly_20111102102000

21% ( 1%)   12% ( 1%)  Nov 02 10:00  sv_hourly.8   

22% ( 2%)   13% ( 1%)  Nov 02 09:00  sv_hourly.9   

24% ( 2%)   14% ( 1%)  Nov 02 08:00  sv_hourly.10  

26% ( 4%)   16% ( 2%)  Nov 01 22:00  sv_nightly.0   (acs)

27% ( 2%)   17% ( 1%)  Nov 01 19:31  smvi__vsc_all_stores_nightly_recent

31% ( 6%)   20% ( 3%)  Oct 31 22:00  sv_nightly.1  

31% ( 2%)   21% ( 1%)  Oct 31 19:30  smvi__vsc_all_stores_nightly_20111031193000

47% (30%)   40% (20%)  Oct 30 12:00  sv_weekly.0    (acs)

I'd like to understand why it's marked (acs), and why the sv_weekly.0 sv_nightly.0 and sv_hourly.0 are (acs). Just because they are each the newest sv snapshots in their group? I'd imagine that's done in order to no delete them in case of snapshot autodelete when disk space is coming to an end. Right?

Warning!

This NetApp Community is public and open website that is indexed by search engines such as Google. Participation in the NetApp Community is voluntary. All content posted on the NetApp Community is publicly viewable and available. This includes the rich text editor which is not encrypted for https.

In accordance to our Code of Conduct and Community Terms of Use DO NOT post or attach the following:

  • Software files (compressed or uncompressed)
  • Files that require an End User License Agreement (EULA)
  • Confidential information
  • Personal data you do not want publicly available
  • Another’s personally identifiable information
  • Copyrighted materials without the permission of the copyright owner

Files and content that do not abide by the Community Terms of Use or Code of Conduct will be removed. Continued non-compliance may result in NetApp Community account restrictions or termination.