Restore of a week old Directory DB

[glad69]

Hi we have the issue described in http://seer.entsupport.symantec.com/docs/326380.htm after the upgrade of our EV environment to V8 last week.

Since the upgrade, normal operation presumed, so the creation of new archives, archiving runs, mailbox sync's etc.

If we follow the article, we need to revert to a week old directory DB, does anyone have any ideas of potential problems?

The first thing that springs to mind, is archives created after the upgrade, will disappear leaving all associated vaulted items orphaned.

Other than exporting the archive before we restore the old DB, is there any other methods we could use to stop this data from becoming orphaned.

Any other gotcha, we should be aware of?


Lastly, seems a drastic measure, just to get the vaults to be converted to V8 Vault Store Groups, is this really the only option?

Thanks,

[JesusWept3]

genuinely if you dont see the vault store groups in ev8 then you need to roll back immediately regardless of newly archived users etc
there simply isnt any other choice

you may have to disable and re-enable newly enabled users since then, but you have to roll back the entire environment and then move forward

[GianniCool]

So, everything that was updated since Saturday would have to be rebuilt/redone?

[Liam_Finn1]

Not sure if this will work in your case seeing as you went through an upgrade

If since you ungraded the first time and you had restarted archiving after the upgrade. There might be the possibility that if you have your truncated SQL logs since then that you could replay the logs and repopulate the database. 

Seeing as the archived files are still there and the database could possible be replayed to repopulate the data then you could update your indexes and get back on track


Note that I have never tried this in a situation like yours. There was issues with your upgrade and I'm not sure how it will affect the replay seeing as some aspects of the upgrade failed to complete. But if the database was successful in the upgrade and the data archived after your first upgrade is good then in theory this may work but you will need to test it in a LAB environment first to ensure it does not screw up your environment

I have done this for a SQL failure and it works great but as I said you need to test it in a LAB first