Hello,
IMHO, you need to clear that.
As far as I recall, these entries hold the identifier for the specific services, and that is random when created. Clearing this will either re-enter the existing id, or it will get the new id when services are installed.
I agree with the above. You would set up and install and configure including all the VSDB layout and then hack it to reflect the orig data. Large effort I have only seen people try in Prod because it is such a PitA.
Thanks both
As luck would have it, I've found an alternative backup of the directory database which I will try to recover from. The backup I have for the directory database is a few weeks more recent than the other backups I have - Is this perhaps going to be a problem (bearing in mind I had absolutely nothing before)?? I'm going to restore it anyway and see where it takes me.
I do have a question though on a EV DR whitepaper that perhaps someone can answer for me.
https://sort.veritas.com/DocPortal/pdf/EV_WhitePaper_DR
The process starts on page 13 - I've rebuilt my EV server and also my SQL server using the same names and IP address as before and so I plan to skip over procedure 3 and go straight to procedure 4 (recovery for this will be via Backup Exec). My question is if I need to complete procedure 5? What does this do and is it necessary? I've no problem in running the SQL script but didn't want to remove stuff from the directory database if I should be skipping this for my recovery scenario.
kind regards
Hello,
IMHO, you need to clear that.
As far as I recall, these entries hold the identifier for the specific services, and that is random when created. Clearing this will either re-enter the existing id, or it will get the new id when services are installed.
Thanks Gertjan
I've run that anyway as I couldn't see it doing anything but helping.
I've hit another problem, but for now..... thanks very much
thanks
Caden
