I am still working on this, but I found out the reason I could not change the Data Domain on the EBR. when running the mccli dd edit command, the ddboost user on the new target system has to have the admin role.
I was able to change the Data Domain, but I'm not able to see that the backups have changed location. If the appliance is not aware that I moved the data to a new location, It cannot recover the old backups. After running the mccli dd edit command a recover job reaches 92 percent and hangs. It appears that no data is actually copied and no VM is created.
Is there a procedure for moving the data? We are returning the old Data Domain to EMC at the end of the leasing contract and I would like a way to migrate the data if possible.
I'm working on a similar project and have no real solution yet. There are a few difficult factors that prevent VBA from moving to a new Data Domain.
I have another idea though and am preparing some tests.
What if a new VBA was created on the same Networker and on your new Data Domain.
Then add that new VBA to the policies of your old VBA.
If your data is cloned to tape in Networker then I think you'd be able to run a restore on your new DD assuming that the clients from the old VBA are set up or copied to the new one.
My issue is 95% of the vms no longer exist but the backups need kept for 12 months, so I may try replicating the clients using the Avamar replication (in the VBA, it's a virtual Avamar).
danger-6IDmh
11 Posts
0
July 1st, 2016 04:00
I am still working on this, but I found out the reason I could not change the Data Domain on the EBR. when running the mccli dd edit command, the ddboost user on the new target system has to have the admin role.
gautamgp
226 Posts
0
July 4th, 2016 00:00
from DDOS 5.5 and above ddboost user does not need to be admin.
gautamgp
226 Posts
1
July 4th, 2016 00:00
You can use the mccli dd edit command to edit the information.
danger-6IDmh
11 Posts
0
July 5th, 2016 02:00
I was able to change the Data Domain, but I'm not able to see that the backups have changed location. If the appliance is not aware that I moved the data to a new location, It cannot recover the old backups. After running the mccli dd edit command a recover job reaches 92 percent and hangs. It appears that no data is actually copied and no VM is created.
Is there a procedure for moving the data? We are returning the old Data Domain to EMC at the end of the leasing contract and I would like a way to migrate the data if possible.
Hans_n_Franz
9 Posts
0
July 26th, 2016 07:00
I'm working on a similar project and have no real solution yet. There are a few difficult factors that prevent VBA from moving to a new Data Domain.
I have another idea though and am preparing some tests.
What if a new VBA was created on the same Networker and on your new Data Domain.
Then add that new VBA to the policies of your old VBA.
If your data is cloned to tape in Networker then I think you'd be able to run a restore on your new DD assuming that the clients from the old VBA are set up or copied to the new one.
My issue is 95% of the vms no longer exist but the backups need kept for 12 months, so I may try replicating the clients using the Avamar replication (in the VBA, it's a virtual Avamar).
At this point I'm not sure this will work.