Subscribe

Snapvault for MultiStore vFilers through protection manager Problem

[ Edited ]

We have several MultiStore vFilers which are setup for DR using vfiler DR commands. They are replicating to a DR site at a co-location site. We want to also archive the data that is at DR by using a Protection Policy to backup the DR destination volumes using Snapvault. when I tried to set this up I got errors trying to do that backup that the the volume was read only since it is a DR destination and it could not perform the backup. Is there something that I need to change in the protection policy to get this to work ? I've done this exact scenario with volumes outside of vFilers no problem.

Any ideas ? I think it has to do with the classificatoins of the Nodes within the protection policy but I can't seem to pinpoint it.

Re: Snapvault for MultiStore vFilers through protection manager Problem

There is no support for vfiler DR in Operations Manager, but what you are trying is outside of this... hopefully Adai or someone can reply with the reason it fails.. I assume all volumes on the target are using Volume SnapMirror (no qtrees assigned to the vFiler forcing QSM instead?).

Re: Snapvault for MultiStore vFilers through protection manager Problem

Correct, Volume SnapMirror

Snapvault for MultiStore vFilers through protection manager Problem

So I tried a workaround by creating snapvault relationships to each of the vFiler DR volumes to a new volume on the same controller so that I could import them as external relationships in DFM, but I am not able to see them in DFM as external relationships. Anyone have any other ideas ?

Snapvault for MultiStore vFilers through protection manager Problem

Are these relationship created using the vfiler interface or pfiler(vfiler0) interface.

If its the earlier one then DFM doesnt discover.

Snapvault for MultiStore vFilers through protection manager Problem

The sv relationships I created were from vfiler0, not the vfiler interface.

Snapvault for MultiStore vFilers through protection manager Problem

This is because in your case you would have used the same base snapshot on the VSM destination as the source snapshot for the SV.

But when you do it using normal dataset, DFM(PM) will try to create snapshot on this volume which is readonly.

This can be over come by using Application dataset, where PM doesn't take the snapshot rather it propagates the snapshot that is registered with it.

So you will have to create an app dataset using the API or NMSDK and use the base snap shot of the VSM as the base snapshot for the sv.

PM will take care of creating snapshot on the snapvault destination.

Snapvault for MultiStore vFilers through protection manager Problem

Can you run the following command on both the VSM destination filer and the SV destination filer ?

dfm host discover <filer name/Id>

Re: Snapvault for MultiStore vFilers through protection manager Problem

Thank you for the reply.

Can you expand on the following "create an app dataset using the API or NMSDK and use the base snap shot of the VSM as the base snapshot for the sv" ?

Is this something that is to be scripted outside of DFM ? or is it part of DFM? Or is it a different dataset type? We have only configured our dataset's to contain aggregates, but I am interested in the app dataset, as it might solve the problem for us.

Re: Snapvault for MultiStore vFilers through protection manager Problem

Do you mean that I should perform the host discover after doing SV from the command line? We let the external SV relationship run over night (24hours) so I though it would have polled by then and seen it in DFM, but I can definately try a manual discover.