SNAPVAULT
Ø Snapvault is license product in Ontap
Ø SnapVault is a disk-based storage backup feature of Data ONTAP
Ø Snapvault enable data stored on multiple storage be backup in centrally
Ø The qtree is the basic unit of SnapVault backup and restore
Ø Data is restored from the secondary qtree to primary qtree
Ø Using Nearstore_option license we can increase the concurrent transfer
Ø In snapvault primary and secondary may be flex-volume to traditional volume.
SNAPVAULT PREREQUISITES:-
Ø License for the snapvault primary is sv_ontap_pri.
Ø License for the snapvault secondary is sv_ontap_sec.
Ø TCP port 10566 and 10000 must be open.
Snapvault snap sched
Using snapvault snap we can take snapshot primary and secondary volume
In snapvault three types of snap schedule
sv_hourly
sv_daily
sv_weekly
Example:
Pri > snapvault snap sched vol1 sv_hourly 10@10-16
This schedule takes every hour snapshot on vol1 and retain last 10 snapshot copies name called sv_hourly in the primary system.
Sec > snapvault snap sched –x vol1 sv_hourly 10@10-16
This schedule takes every hour snapshot on vol1 and retain last 10 snapshot copies name called sv_hourly in the Secondary system.
Using –x for incremental back up, that means secondary snapvault that compare the primary snapshot and if any modified data in the primary snapshot, it will copied the modified date to the secondary system.
NOTE: If you don’t use the -x option, the secondary does not contact the primary. This schedule take snapshot of vol1 without incremental
Ø License for the snapvault primary is sv_ontap_pri.
Ø License for the snapvault secondary is sv_ontap_sec.
Ø TCP port 10566 and 10000 must be open.
Snapvault snap sched
Using snapvault snap we can take snapshot primary and secondary volume
In snapvault three types of snap schedule
sv_hourly
sv_daily
sv_weekly
Example:
Pri > snapvault snap sched vol1 sv_hourly 10@10-16
This schedule takes every hour snapshot on vol1 and retain last 10 snapshot copies name called sv_hourly in the primary system.
Sec > snapvault snap sched –x vol1 sv_hourly 10@10-16
This schedule takes every hour snapshot on vol1 and retain last 10 snapshot copies name called sv_hourly in the Secondary system.
Using –x for incremental back up, that means secondary snapvault that compare the primary snapshot and if any modified data in the primary snapshot, it will copied the modified date to the secondary system.
NOTE: If you don’t use the -x option, the secondary does not contact the primary. This schedule take snapshot of vol1 without incremental
snapvault source configuration
Snapvault primary configuration
Primary controller name : host1
Secondary controller name : host2
Primary controller IP : 192.168.1.5
Secondary controller IP : 192.168.1.6
Primary &Secondary aggregate name: aggr1
Primary &Secondary Vol name: vol1
Cifs shares : share1
PRI> aggr create aggr1 20
PRI> aggr status aggr1
PRI> vol create vol1 aggr1 200m
PRI> vol status vol1
PRI> license add < sv_ontap_pri >
PRI> options snapvault.enable on
PRI> options snapvault.access host=host2
PRI> wrfile -a /etc/hosts 192.168.1.6 host2
PRI> ping 192.168.1.6
PRI> ping host2
PRI> cifs shares -add share1 /vol/vol1
PRI> cifs shares
Switch to windows
start--> run --> type //host1/share1
paste some files for testing purpose
PRI> snapvault destination
Primary controller name : host1
Secondary controller name : host2
Primary controller IP : 192.168.1.5
Secondary controller IP : 192.168.1.6
Primary &Secondary aggregate name: aggr1
Primary &Secondary Vol name: vol1
Cifs shares : share1
PRI> aggr create aggr1 20
PRI> aggr status aggr1
PRI> vol create vol1 aggr1 200m
PRI> vol status vol1
PRI> license add < sv_ontap_pri >
PRI> options snapvault.enable on
PRI> options snapvault.access host=host2
PRI> wrfile -a /etc/hosts 192.168.1.6 host2
PRI> ping 192.168.1.6
PRI> ping host2
PRI> cifs shares -add share1 /vol/vol1
PRI> cifs shares
Switch to windows
start--> run --> type //host1/share1
paste some files for testing purpose
PRI> snapvault destination
Snapvault Secondary configuration
Snapvault Secondary configuration
Primary controller name : host1
Secondary controller name : host2
Primary controller IP : 192.168.1.5
Secondary controller IP : 192.168.1.6
Primary &Secondary aggregate name: aggr1
Primary &Secondary Vol name: vol1
qtree name: qtree_name
Cifs shares : share2
PRI> aggr create aggr1 20
PRI> aggr status aggr1
PRI> vol create vol1 aggr1 200m
PRI> vol status vol1
PRI> license add <snapvault>
PRI> options snapvault.enable on
PRI> snapvault start -S host1:/vol/vol1 host2:/vol/vol1/qtree_name
(qtree name is must, it create automatic )
PRI> snapvault status -l
PRI>
PRI>
PRI>
Primary controller name : host1
Secondary controller name : host2
Primary controller IP : 192.168.1.5
Secondary controller IP : 192.168.1.6
Primary &Secondary aggregate name: aggr1
Primary &Secondary Vol name: vol1
qtree name: qtree_name
Cifs shares : share2
PRI> aggr create aggr1 20
PRI> aggr status aggr1
PRI> vol create vol1 aggr1 200m
PRI> vol status vol1
PRI> license add <snapvault>
PRI> options snapvault.enable on
PRI> snapvault start -S host1:/vol/vol1 host2:/vol/vol1/qtree_name
(qtree name is must, it create automatic )
PRI> snapvault status -l
PRI>
PRI>
PRI>
No comments:
Post a Comment