Subscribe
Accepted Solution

Snapvault Configuration Info

[ Edited ]

Hi guys,

 

Can anyone you help me with these values?

 

snapvault-configuration-info

 

Describes the elements of the snapvault configuration entry.

 

primary-path

 

string

The   primary path that will be used as the source for this relationship as well as   for baseline transfer. This can be either in UTF8 or ASCII/extended ASCII   depending on whether or not 'is-primary-path-utf8-encoded' flag is set. If   option 'is-primary-path-utf8-encoded' is not specified, then the primary-path   considered as in ASCII/extended ASCII.

primary-system

 

string

The   primary system for this relationship as well as for the baseline transfer.   This input will be used by the secondary system to establish contact with the   primary. Therefore this input is expected to be a hostname that the primary   can resolve.

secondary-path

 

string

The   secondary path that will be used as destination for this relationship as well   as baseline transfer. The secondary path will be created during the baseline   transfer and hence it must not exist when issuing this request.

 

I’m trying to understand what these parameters should contain. But I didn’t figure out yet.

 

Do you have any guess? And an example, will be, also great.

 

 

Thanks.

Re: Snapvault Configuration Info

Julio -

Primary system - The filer with the data you're backing up with SnapVault.

Primary Path - The Qtree or directory you're backing up - /vol/myvolume/myqtree.

Secondary Path - The Qtree you want to use for your SnapVault backups.

Example (On the secondary):

snapvault start -r -S primary:/vol/myvolume/myqtree /vol/svvolume/myqtree

See the man page for snapvault:

http://now.netapp.com/NOW/knowledge/docs/ontap/rel734/html/ontap/cmdref/man1/na_snapvault.1.htm

I hope this response has been helpful to you.

At your service,

Eugene Kashpureff
NetAppU Instructor and Independent Consultant
(P.S. I appreciate points for helpful or correct answers.)

Re: Snapvault Configuration Info

Hi Eugene, thanks for the reply.

I got your point... but can I use the same format as for snapmirrors?

  • "snapmirror-initialize" -> "source-location" -> "<filer>:<volume>"

assuming that:

  • source "<filer>" - Primary system

  • source "<volume>" - Primary Path

  • destination "<volume>" - Secondary Path

As I don't know if I will have a lun or a share inside it... so I will copy the whole volume.

Another problem I'm having is for the snapvault-schedules. I'm getting the following error:

  • "Unexpected type name: volume-name"

for the below parameter:

  • "snapvault-primary-set-snapshot-schedule" -> "snapshot-schedule" -> "volume-name" (The primary volume for which this schedule has been  configured) -> "testRemote"

  • <results status="passed">
            <volumes>
                    <volume-info>
                            <name>testRemote</name>
                            <uuid>2ce52782-e31b-11df-90fc-00a098129e44</uuid>
                            <type>flex</type>
                            <state>online</state>
                            <size-total>52428800</size-total>
                            <size-used>163840</size-used>
                            <size-available>52264960</size-available>
                            <percentage-used>0</percentage-used>
                            <snapshot-percent-reserved>20</snapshot-percent-reserved>
                            <snapshot-blocks-reserved>12800</snapshot-blocks-reserved>
                            <reserve-required>0</reserve-required>
                            <reserve>0</reserve>
                            <reserve-used>0</reserve-used>
                            <reserve-used-actual>0</reserve-used-actual>
                            <files-total>1896</files-total>
                            <files-used>109</files-used>
                            <quota-init>0</quota-init>
                            <is-snaplock>false</is-snaplock>
                            <owning-vfiler>vfiler0</owning-vfiler>
                            <containing-aggregate>aggr0_Server2</containing-aggregate>
                            <compression-info>
                                    <is-compression-enabled>false</is-compression-enabled>
                                    <compressed-data>0</compressed-data>
                                    <compression-saved-percentage>0</compression-saved-percentage>
                            </compression-info>
                            <space-reserve>none</space-reserve>
                            <space-reserve-enabled>true</space-reserve-enabled>
                            <raid-size>8</raid-size>
                            <raid-status>raid4</raid-status>
                            <checksum-style>block</checksum-style>
                            <is-checksum-enabled>true</is-checksum-enabled>
                            <is-inconsistent>false</is-inconsistent>
                            <is-unrecoverable>false</is-unrecoverable>
                            <is-invalid>false</is-invalid>
                            <mirror-status>unmirrored</mirror-status>
                            <disk-count>2</disk-count>
                            <plex-count>1</plex-count>
                            <plexes>
                                    <plex-info>
                                            <name>/aggr0_Server2/plex0</name>
                                            <is-online>true</is-online>
                                            <is-resyncing>false</is-resyncing>
                                    </plex-info>
                            </plexes>
                    </volume-info>
            </volumes>
    </results>

Thanks all.

Re: Snapvault Configuration Info

Just one more question... if anyone can find the problem:

  • <snapvault-secondary-create-relationship>
    <configuration>
    <primary-path>/vol/testRemote/0</primary-path>
    <primary-system>BF-LAB-NA2</primary-system>
    <secondary-path>/vol/testRemote_Snapvault/0</secondary-path>
    <tries-count>5</tries-count>
    </configuration>
    </snapvault-secondary-create-relationship>

I'm sending the command above... and getting the same error as in the schedules:

  • "Unexpected type name: primary-path"

Cannot find where I'm doing anything wrong.

rle Former NetApp Employee

Re: Snapvault Configuration Info

Try this:

<snapvault-secondary-create-relationship>
    <configuration>
         <snapvault-configuration-info>        
             <primary-path>/vol/testRemote/0</primary-path>
             <primary-system>BF-LAB-NA2</primary-system>
             <secondary-path>/vol/testRemote_Snapvault/0</secondary-path>
             <tries-count>5</tries-count>
        </snapvault-configuration-info>
    </configuration>
</snapvault-secondary-create-relationship>
   - Rick -

Re: Snapvault Configuration Info

Thanks Rick,

it worked... at least now I'm throwing another error.

  • "Snapshot creation aborted: snapshot target not  configured."

Not sure what the API is telling me... going to investigate tomorrow, as I'm done for today.

rle Former NetApp Employee

Re: Snapvault Configuration Info

The way to implement the XML is to place the XML in a file and execute apitest accordingly:

apitest -I filer user passwd < xml_file

   - Rick -