Timeline for Order to restore system and user databases
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 3, 2015 at 13:51 | comment | added | GHauan | We did not have to do anything with the SIDs, and all users and jobs were restored with the msdb, however the linked servers did not work, they needed to be recreated. I don't think the databases were suspect (can't really remember), just empty since the files were not there. One importent thing though: when restoring system-dbs from old server, make sure that the disk paths (i.e F:\ E:\ etc) also exists on the new server, or you will get some problems. | |
| Feb 3, 2015 at 12:02 | comment | added | Alocyte | Thanks for the update. Did your user databases SIDs need to be corrected? Did the logins have to be recreated? So, post master restore, the databases were "there" but only showed up as "suspect" or something? | |
| Feb 3, 2015 at 10:04 | comment | added | GHauan | Hi again. Some feedback after our restore. We restored the system dbs first. What happened then, was that all the user dbs was listed, but without any real contents. Then we could restore over the "existing" user db. | |
| Jan 9, 2015 at 12:57 | vote | accept | GHauan | ||
| Jan 7, 2015 at 12:04 | comment | added | GHauan | Hi. Thanks for your answer. Yes, it is from-to SQL SERVER 2008 R2. We will upgrade to 2014, but will do this after the restore. | |
| Jan 7, 2015 at 9:39 | history | answered | Alocyte | CC BY-SA 3.0 |