2012-01-27 09:59 AM
We're having some questions with moving legacy SMVI 2 jobs to Oncommand 5.0/HP 1.1
Our config is simple: a FAS2040 holds some LUN/VMFS each on different qtree/volume and a 3210 is our snapvault destination
This issue is the following:
first issue is here: PM created two relationships with datastore1 and datastore2.... hu? why did it start a relationship with for non select object.
then from here i did this:
Now I have my snapvault relationship for datastore2 as external and I don't really want to rebaseline...... how could i fix this and import it into a new vmware dataset??
I'm calling out for some help here, thx in advance!
Solved! SEE THE SOLUTION
2012-01-28 04:50 AM
ok I found on my own.
A VM had 2 disks, a disk on datastore1 and the other one on datastore2. So PM behaved accordingly and started protection on both datastores although i didn't select both of them
Hope this helps others one day...