Active IQ Unified Manager Discussions
Active IQ Unified Manager Discussions
Hello,
I am getting below snapshots on volume "primary filer " . I have checked in most of the volumes "dfpm_base" snapshot is eating lot of space ?
9% ( 0%) 3% ( 0%) Feb 28 13:31 exchsnap__HOST1_02-28-2013_14.30.21
27% (21%) 10% ( 7%) Feb 26 20:06 eloginfo__HOST1_02-26-2013_21.00.33 (snapvault)
39% (22%) 17% ( 7%) Feb 20 21:45 dfpm_base(HOST1.3918)conn1.0 (acs)
Can I delete this "dfpm_base" snapshot. I believe in above scenario my base snapshot is the one with (snapvault).
Is there any impact of delete dfpm_base snapshot ?
Will it effect future snapvault updates ?
Protection Manager uses this snapshot. Pls dont delete it. I will come back with what is the exact use of that snapshot.
Regards
adai
Hello Arumugam,
Thanks for your reply, Please elaborate on this.
As in below example, base snapshot for SnapVault is already exist. What is use of keeping (acs) snapshot. It is unnecessary eating space. What are consequences after deletion of "dfpm_base(HOST1.3918)conn1.0 (acs)" snapshot ?
9% ( 0%) 3% ( 0%) Feb 28 13:31 exchsnap__HOST1_02-28-2013_14.30.21
27% (21%) 10% ( 7%) Feb 26 20:06 eloginfo__HOST1_02-26-2013_21.00.33 (snapvault)
39% (22%) 17% ( 7%) Feb 20 21:45 dfpm_base(HOST1.3918)conn1.0 (acs)
The snapvault update will allow you to reduce the space used.
This seems to be used by the Protection Manager. Please elaborate on this.
As in below example, base snapshot for SnapVault is already exist. What is use of keeping (acs) snapshot. It is unnecessary eating space. What are consequences after deletion of "dfpm_base(HOST1.3918)conn1.0 (acs)" snapshot ?
9% ( 0%) 3% ( 0%) Feb 28 13:31 exchsnap__HOST1_02-28-2013_14.30.21
27% (21%) 10% ( 7%) Feb 26 20:06 eloginfo__HOST1_02-26-2013_21.00.33 (snapvault)
39% (22%) 17% ( 7%) Feb 20 21:45 dfpm_base(HOST1.3918)conn1.0 (acs)
I'm sure, https://kb.netapp.com/support/index?page=content&id=3011179 will explain what exactly you are looking to understand... as far as i understand, deletion of (acs) snapshot won't affect anything as long as your snapvault relationship is working (and there is no issue if you are using cascading i.e. snapmirror to snapvault or vice-versa)
Essentially, ACS tagging gives SnapVault the ability to use a ‘named’ snapshot. Another benefit of ACS tagging is it excludes these snapshots from Snapshot autodelete until the SnapVault destination sends a signal to remove the soft-lock. Additionally, if your retention policy for SnapVault is set to 1 snapshot, the ACS snapshot will not be counted as that snapshot. This ensures you keep your baseline snapshot and can use the ACS snapshot for performing incremental backups.
https://communities.netapp.com/docs/DOC-6393
See the attachment for details, which have in above link. You can get clear idea.
- Sathish