This is a restore from Production to Test, so I want the alerts to go to email rather Had I been able to restore from this backup I would then need to spend some timeĪlerts and notifications all need to be set to the correct values! For example, Level 16, State 1, Line 2 RESTORE DATABASE is terminating abnormally. Version of the server () than this server ().
Msg 3168, Level 16, State 1, Line 2 The backup of the system database on theĭevice C:\msdb.bak cannot be restored because it was created by a different MSDB running! This will not be a surprise when you've done a test restore or two. SQL Server Management Studio can't do a database restore from the GUI without Keep in mind that with MSDB out of commission you will need Test or QA version of a production instance or, in this case, the production version Instance of the same version/build number over my corrupt ones. Data lossĪt this point is a given, my next best option is to restore a backup from a similar So now what? I have an unrecoverable MSDB and no backup to restore. Uh oh! I have no backup to recover! Plan "B" - Grab another SQL Server Instance's MSDB Backup (our backup tool) it informed me that it had not been configured on this server. Panic when something goes wrong for real, but when I started NetApp SnapManager I've done this a few times as practice which helps prevent some of the The process for recovering MSDB from backup Has been you can get up to 100% recovery. On the problem, how often you backup the transaction logs and how active the database "Sure", I thought, "I'll just go get lastv night'sįrom the backup is my first option because it has the least risk of data loss. Solution Plan "A" - Recover SQL Server MSDB from a Backup
0 kommentar(er)
