OnTap has a beautiful feature of snapshots – it is very useful to restore the data of a volume from a certain point in time in the past. Snapshots are taken on volume, and % of volume space is reserved for snapshot data. Below mentioned are a set of commands which I’ve used to manage snapshots:
To set snap autodelete on RW volumes:
“snap autodelete” defines a set of policies which are applied in order to contain the growth of snapshots.
netapp1> snap autodelete ibd_share1_gs2
snapshot autodelete settings for ibd_share1_gs2:
state : off
commitment : try
trigger : volume
target_free_space : 20%
delete_order : oldest_first
defer_delete : user_created
prefix : (not specified)
destroy_list : none
netapp1> snap autodelete vol1 commitment try
netapp1> snap autodelete vol1 trigger snap_reserve
netapp1> snap autodelete vol1 target_free_space 10
netapp1> snap autodelete vol1
snapshot autodelete settings for vol1:
state : off
commitment : try
trigger : snap_reserve
target_free_space : 10%
delete_order : oldest_first
defer_delete : user_created
prefix : (not specified)
destroy_list : none
To set up snap schedule:
netapp1>snap list
Volume vol0
working…
%/used %/total date name
———- ———- ———— ——–
0% ( 0%) 0% ( 0%) May 22 15:00 hourly.0
1% ( 0%) 0% ( 0%) May 22 11:00 hourly.1
1% ( 0%) 0% ( 0%) May 22 00:00 nightly.0
5% ( 4%) 0% ( 0%) May 21 00:00 nightly.1
5% ( 0%) 0% ( 0%) May 20 00:00 nightly.2
5% ( 0%) 0% ( 0%) May 19 00:00 nightly.3
6% ( 0%) 0% ( 0%) May 18 00:00 weekly.0
6% ( 0%) 0% ( 0%) May 17 00:00 nightly.4
Set snap schedule
netapp1>snap sched 4 25 2@11,15 (4 weekly, 25 nightlys, 2 during the day at 11:00 and 15:00)
netapp1>snap sched
Volume vol0: 4 25 2@11,15
It set the schedule on vol0 (the root volume). Any subsequent volume will pick up this schedule which can be changed per volume basis.
To disable snapshots on volume:
netapp1>vol options vol1 nosnap on
No comments yet.