08-10-2017 10:21 AM
Solved! Go to Solution.
08-17-2017 11:53 AM
08-10-2017 10:47 AM
See page 268:
https://www.veritas.com/support/en_US/article.000116394
Note that the Master will have to be the same name, so that the storage server previous configured as the MSDP name will work.
08-10-2017 10:54 AM
08-10-2017 06:07 PM
Rebuilding of the failed master is not possible. If we perform phase 1 and phase 2 import, can we able to do the restore from that msdp pool? And also there won't be any over writing happen since we are configuring the same dp under the new master?
08-10-2017 11:12 PM
Yes you should be able to. There will only be written to the MSDP if you have it configured in a storage unit used by one or more policies.
08-10-2017 11:33 PM
thanks! I am wrting the steps here.
From Marianne's post --> The only way MSDP can be added to another master is to add it as media server to other master, change master and emm server name on media server, add storage server on other master, then start with phase 1 import, followed by phase 2 import.
after that I can able to browse the image but I think unable to perform the recovery. Since the media ID of the existing MSDP storage differ if we add it into (next master).
Please suggest, if anyone provide me the steps that would be a great help!
thanks in advance
08-11-2017 12:30 AM
The new master will add new media id for the MSDP pool and import the images with the new media id.
PS
We can see that you have been using NBU for quite a while.
Did you not plan your backup environment with possible disaster recovery in mind?
Considering options for DR after disaster has struck is not a good idea....
08-11-2017 12:36 AM
If I understand you correctly, you can see the images/backups on the MSDP, but are not able to restore because a "mediaid" mismatch. Which suggests that something didn't go quite right with the import.
Can you post the job details for the restore attempt ? Easier to help when we know more about the problem.
08-17-2017 03:35 AM
08-17-2017 04:10 AM
I am not sure I fully understand.
Is this a new master with a new EMM? If so, then it doesn't know anything about the old EMM server.
If this is the old EMM Server, you should be able to re-attach it if you know the original username/password used to create the MSDP storage. If you don't please open a support case.
08-17-2017 04:13 AM
08-17-2017 04:21 AM
With a new EMM it doesn't know about the previous EMM, so your RDSM error is not related to your old EMM.
They are many factors that can cause RDSM errors, most of which have a technote. But we don't have enough details to tell you exactly what to do.
If the previous master was also the MSDP server, then the new Master/MSDP server has to be the same name. The storage server information is stored in the MSDP location is looking for that old name.
I posted this earlier in the thread:
See page 268:
08-17-2017 06:48 AM
"Considering options for DR after disaster has struck is not a good idea...." Marianne for the win.
08-17-2017 11:53 AM
08-17-2017 08:22 PM
Thanks Marianne!
You will need to cleanup and change all entries to point to new master - Could you please help to get the locations, wherever we need to do the cleanup?
Thanks in advance.
08-18-2017 10:05 AM
08-18-2017 06:25 PM
08-18-2017 10:19 PM