Comprehensive data protection for all workloads
Post Reply
ASHERZ
Novice
Posts: 7
Liked: never
Joined: Jun 14, 2012 4:40 pm
Full Name: Asher
Contact:

Vds replcation Between 2 vCenters

Post by ASHERZ »

I have the same VDS names in the source and target vCenter.
The job works well only when I explicitly did the network mapping.
Without the mapping the job failed with no item ..
Do you have any idea?
I’m just before a very large project to replicate my entire environment and would like to
Avoid the manual process.

Thanks,
Asher
Gostev
Chief Product Officer
Posts: 31524
Liked: 6700 times
Joined: Jan 01, 2006 1:01 am
Location: Baar, Switzerland
Contact:

Re: Vds replcation Between 2 vCenters

Post by Gostev »

Can you please clarify what is the problem with having to specify network mapping? It is no different from all other essential job settings (for example, selecting VMs to replicate and choosing their placement on target).

I suppose, you could automate this with PowerShell if you want... but not very clear why you are having problems with this specific setting in the first place.

Thanks!
ASHERZ
Novice
Posts: 7
Liked: never
Joined: Jun 14, 2012 4:40 pm
Full Name: Asher
Contact:

Re: Vds replcation Between 2 vCenters

Post by ASHERZ »

I have about 100 VDS definition.
I understood from the user manual that it’s not a must to define the mapping if the VDS name is the same for both vCenters.
I like your idea to do it via a powershell script
But anyway I would like to know if this behavior is a bug or I miss something?

Thanks,
Asher
Gostev
Chief Product Officer
Posts: 31524
Liked: 6700 times
Joined: Jan 01, 2006 1:01 am
Location: Baar, Switzerland
Contact:

Re: Vds replcation Between 2 vCenters

Post by Gostev »

You do not miss anything, and it is not a bug either - just how it works today. When replicating between vCenter, network mapping must be performed manually.
Post Reply

Who is online

Users browsing this forum: Semrush [Bot] and 108 guests