S
stephen.black
Well, learned a lesson the hard way. Restorep.exe is intended to be
used for rolling back a plan vs restoring a deleted plan per our MS
Support person. I did read in several posts here stating that you could
use the utility to restore but we corrupted our production db and ended
up having to restore from backup.
So... The question is ... If a plan is deleted by accident, is there a
way to restore the single plan without corrupting the db? I have a
stage and dev env. and was thinking that I could possibly restore the
production db to the dev env. from a date which would contain the lost
plan, then save a local copy of the plan from dev and import back into
production.
My main concern is the project ID and any other project unique
identifiers. Is it possible that importing (not restorep) the plan into
the production db could cause corruption? I am sure someone out here
has experienced this and worked around it. Suggestions would be
welcomed.
Learn from my mistake, the Y option in restorep is very bad If you
don't believe me ask one of our 2950 users who lost access for 6 hrs.
used for rolling back a plan vs restoring a deleted plan per our MS
Support person. I did read in several posts here stating that you could
use the utility to restore but we corrupted our production db and ended
up having to restore from backup.
So... The question is ... If a plan is deleted by accident, is there a
way to restore the single plan without corrupting the db? I have a
stage and dev env. and was thinking that I could possibly restore the
production db to the dev env. from a date which would contain the lost
plan, then save a local copy of the plan from dev and import back into
production.
My main concern is the project ID and any other project unique
identifiers. Is it possible that importing (not restorep) the plan into
the production db could cause corruption? I am sure someone out here
has experienced this and worked around it. Suggestions would be
welcomed.
Learn from my mistake, the Y option in restorep is very bad If you
don't believe me ask one of our 2950 users who lost access for 6 hrs.