If I have to create vserver peering, I have to let the source define a new "replicated" peer vserver at destination? 

I cannot use that my regular vserver at dr that is serving data now, and have it paired with a source vserver.

It has to been a new "peered" vserver?

On Nov 3, 2014, at 8:52 PM, tmac <tmacmd@gmail.com> wrote:

In cDOT, you must use svm peer relationships to replicate between svms and cluster peer relationships to replicate between clusters. You should set up node-based intercluster LIFs for replication between clusters. For data staying local (intra-cluster, svm to svm on the same cluster) it will be able to use the backend cluster network.

All replication on cDOT is at the VOLUME level.(NOT qtree, not at all!) qtrees in cDOT really allow for quotas and that's about it. all backup functions are flexvol based

--tmac

On Mon, Nov 3, 2014 at 6:14 PM, Iluhes <iluhes@yahoo.com> wrote:

Hi Folks,

Need your help

I am used to do snapmirrors from within vFilers.

i would add a second nick into vFiler in 7-mode, for network that is used for replication and than setup snapmirror inside the vFiler.

How does it work in CDOT?

Can I setup snapmirror on vserver level?

If yes, than can I add replication network as second LIF inside vserver (if yes, what is the protocal type?)

If not, how is it done? Snapmirror on cluter level? Can I use intercluster LIFS for that?

I dont want the peering relationship, I just want qtree/volume level snapmirror between vserver volumes, but yet over specific replication network

_______________________________________________
Toasters mailing list
Toasters@teaparty.net
http://www.teaparty.net/mailman/listinfo/toasters