Subscribe

Prot Man and Vfiler SV relationships

Hello,

I am trying to import an existing snapvault relationship into Protection manager 3.8.  The relationship is on the same single storage controller. The source is from the physical server (vfiler0) to the destination on the vfiler (vfiler1).

This relationship works if done manually, but does not appear in external relationships in PM.  If I attempt to add the relationship in PM, it will create a new SV relationship, but it will be from vfiler0 to vfiler0.

I need to have the relationship read (like when you do a snapvault status) vfiler0 as source and vfiler1 as destination.  this is because of a snapcreator dependancy.  SnapCreator will not instruct PM to update a vault if the snapvault status does not show as "source".  when the relationship is from and to the same controller (vfiler0 to vffiler0) it will show as "snapvaulted"

Anyone encountered this or know of a way to get PM to import an existing relationship like this?

Thanks

Re: Prot Man and Vfiler SV relationships

Hi

DFM 4.0 supports SnapVault relationship on the same controller.

DFM 3.8 does not recognize/discover SnapVault source and destination on the same controller. So import of the same is not possible.

Regards

adai

Re: Prot Man and Vfiler SV relationships

This should work with DFM 4.0. As Adai said, it will not work with 3.8.

Re: Prot Man and Vfiler SV relationships

Thanks for the replies.

Should I be able to see an existing relationship like the one described above in the 'External Relationships' pane?  I am testing this in a lab right now and so far do not see that with version 4.

This is from vfiler0 to a vfiler1 relationship.  any assistnace is appreciated.

Thanks

Re: Prot Man and Vfiler SV relationships

Is the relationship created using the vfiler0 interface for both vfiler0 and vfiler1 ?

As PM discovers only those created with vfiler0 interface and not vfiler1’s interface.

Regards

adai

Re: Prot Man and Vfiler SV relationships

SV relationship was created inside the vfiler1 context as it is the destination.  We configured it in this manner as the Snap Creator application will not perform snap vault updates if the source and destination are on the same controller.  It wants to see "source" in the snapvault status output for the relationship.  When both source and dest are on the same controller, it displays what a typical destination would display for a status, which is "snapvaulted".

A workaround was to create a  vfiler and have the vault relationship going from vfiler0 to vfiler1 on this one controller.  Now, we'd like to pull that vault relationship in PM and manager from there if possible.  Based on your comments, it sounds like PM cannot manage this type of relationships (vfiler0 to vfiler1)

Do we know why this is?

Re: Prot Man and Vfiler SV relationships

PM can manage the type of relationship you are mentioning the only caveat is

The relationship has to be created using the vfiler0 interface for both vfiler0 and vfiler1 and not the other way.

Vfiler0 to Vfiler1 where in vfiler1 uses vfiler0 interface to snapvault.

Can you get us the output of SnapVault status ?

Regards

adai

Re: Prot Man and Vfiler SV relationships

The first one is within the controller vfiler0 to vfiler0. psfonav1 is the "vfiler0".  Snap Creator plays nice with the last three as it wants to confirm that state field as "source".  sorry for the late reposons

===== SNAPVAULT STATUS L ===== Snapvault is ON. Source:                 psfona01:/vol/b01/qb01 Destination:            psfona01:/vol/sv_snapcreator/qb01 Status:                 Idle Progress:               - State:                  Snapvaulted Lag:                    01:29:43 Mirror Timestamp:       Sat Jul  3 22:30:20 PDT 2010 Base Snapshot:          psfona01(0135075343)_sv_snapcreator-base.55 Current Transfer Type:  - Current Transfer Error: - Contents:               Replica Last Transfer Type:     Update Last Transfer Size:     8 KB Last Transfer Duration: - Last Transfer From:     192.168.1.31:/vol/b01/qb01 Source:                 psfona01:/vol/a01/qa01 Destination:            psfonav1:/vol/sv_a01/qa01 Status:                 Idle Progress:               - State:                  Source Lag:                    101:29:54 Mirror Timestamp:       Tue Jun 29 18:30:09 PDT 2010 Base Snapshot:          psfonav1(0135075343)_sv_a01_qa01-src.0 Current Transfer Type:  - Current Transfer Error: - Contents:               - Last Transfer Type:     - Last Transfer Size:     1103940 KB Last Transfer Duration: 00:00:11 Last Transfer From:     - Source:                 psfona01:/vol/b02/qb02 Destination:            psfonav1:/vol/sv_b02/qb02 Status:                 Idle Progress:               - State:                  Source Lag:                    101:29:15 Mirror Timestamp:       Tue Jun 29 18:30:48 PDT 2010 Base Snapshot:          psfonav1(0135075343)_sv_b02_qb02-src.0 Current Transfer Type:  - Current Transfer Error: - Contents:               - Last Transfer Type:     - Last Transfer Size:     175128 KB Last Transfer Duration: 00:00:02 Last Transfer From:     - Source:                 psfona01:/vol/b03/qb03 Destination:            psfonav1:/vol/sv_b03/qb03 Status:                 Idle Progress:               - State:                  Source Lag:                    101:28:40 Mirror Timestamp:       Tue Jun 29 18:31:23 PDT 2010 Base Snapshot:          psfonav1(0135075343)_sv_b03_qb03-src.0 Current Transfer Type:  - Current Transfer Error: - Contents:               - Last Transfer Type:     - Last Transfer Size:     1143020 KB Last Transfer Duration: 00:00:12 Last Transfer From:     -

Re: Prot Man and Vfiler SV relationships

For the last three can you login to the  psfonav1 and execute snapvault status  and post the output ?

Regards

adai

Re: Prot Man and Vfiler SV relationships

Status from psfona01:

psfona01> snapvault status

Snapvault is ON.

Source                  Destination                        State          Lag        Status

psfona01:/vol/b01/qb01  psfona01:/vol/sv_snapcreator/qb01  Snapvaulted    03:44:30   Idle

psfona01:/vol/a01/qa01  psfonav1:/vol/sv_a01/qa01          Source         11:02:54   Idle

psfona01:/vol/b02/qb02  psfonav1:/vol/sv_b02/qb02          Source         11:46:36   Idle

psfona01:/vol/b03/qb03  psfonav1:/vol/sv_b03/qb03          Source         11:46:36   Idle

Status from psfonav1:

psfonav1@psfona01> snapvault status

Snapvault is ON.

Source                  Destination                State          Lag        Status

psfona01:/vol/a01/qa01  psfonav1:/vol/sv_a01/qa01  Snapvaulted    11:03:41   Idle

psfona01:/vol/b02/qb02  psfonav1:/vol/sv_b02/qb02  Snapvaulted    11:47:23   Idle

psfona01:/vol/b03/qb03  psfonav1:/vol/sv_b03/qb03  Snapvaulted    11:47:23   Idle