configure snapvault

http://indiawebsearch.com/content/how-to-configure-snapvault-using-network-appliance-data-ontap-on-a-fas3050-filer

Before we get started, the prerequisites are to have a "Primary" Filer and a "Seondary Filer" . A "Primary System QTree" and a "Secondary System QTree" . In case you did not remember what a QTree is, QTree in Data ONTAP terms from Network Appliance is simply referred to as a folder on a volume, QTrees are just like traditional or flex volumes, with minor differences such as they can not be cloned. A Qtree is just used to group similar data together, apply quotas etc

A Primary Filer is generally referred to as your "onsite" storage system, whose data you want to back up using Data ONTAP Snapvault (eg; source FAS3050 Filer)

A Secondary Filer is your offsite or another storage system where you want your data backed up to (eg; destination FAS3050 filer)

You will normally be performing the Snapvault data backup from the Primary Qtree to the Secondary Qtree. In a disaster recovery scenario, you will be restoring data from your destination FAS2050 filer's qtree to your source or Primary filer.

To configure Snapvault , we need to perform five simple commands. I will show you the Data ONTAP commands, that will configure SnapVault as your backup on FAS3050 filers. In our example, we will call our Primary Filer as Filer1 and our secondary filer as filer2.

Step 1:

- Configure the Primary Filer for Snapvault, add the Snapvault license by using the following command on a terminal session:

license add sv_primary_license

Step 2:

- Enable snapvault on primary by using the following command

options snapvault.enable on

Step 3:

- Specify the name of the secondary storage system on the primary by using the command

options snapvault.access host=NameOfTheSecondaryFilerHere

Note that you can also use the following command to all all hosts as destination filers

options snapvault.access host=all

Step 4:

- Perform steps 1 and 2 on the secondary filer as well

Step 5:

- Enable the compliance clock on the secondary filer by using the command:

date -c initialize

Step 6:

- You can also optionally create a "log volume" for snapvault logs, but we will by pass it here

Step 7:

- Finally on the secondary filer for each qtree you need to backup on the primary, create a initial baseline transfer

For example, if you want the qtree called /vol/wandata/windowsdata on the primary to be backed up to a qtree on secondary called /vol/sv_wandata/windowsdata , you will give the following command:

snapvault start -S filer1:/vol/wandata/windowsdata /vol/sv_wandata/windowsdata

Note that it is a good practiceto name your volumes with sv_ (indicating snapvault volume).

This initialization can take some time to complete., to check the progress, you can give the command:

snapvault status

That is it. The final step is to create a Snapvault schedule on Primary and secondary. Here are the steps

Step 8:

- Create a schedule on Primary by using the following command:

snapvault snap sched -x vol snap_name count [@day_list][@hour_list]

so for example, it will be:

snapvault snap sched -x filer1:/vol/wandata/windowsdata sv_nightly 150@mon-sat 0

meaning, snapvault will create backups with prefix sv_nightly for the primary qtree /vol/wandata/windowsdata at midnight monday to saturday and will retain 150 copies (one for every night)

Step 9:

Similar to step 8 configure the secondary, I will just demonstrate the command for the secondary

snapvault snap sched -x filer2:/vol/sv_wandata/windowsdata sv_nightly 150@mon-sat 0