SQL Backup/Restore issue
Hi Guys,
I have a bit of an odd question and I'm sure someone will know the answer.
Now, when backing up SQL we use the SQL agent and backup all the databases on the server including the system database. When we do a file system backup of the SQL servers we are unable to backup the *. MDF and *.LDF because of the the lock on the files (All ok so far). When I do a restore of the the server we cant restore the SQL databases without reinstalling SQL as the MDF and LDF files for the system databases do no exist causing SQL not to start (This was done using a BMR). I know there is a rebuild command line toold to recreate them using the SQL CD but it doesnt seems to work correctly with SQL 2005 SP3.
With Backup Exec it knows those files should be there and recreates them when restoring the file system so I'm confused why NetBackup is unable to do the same or maybe im missing something!
Thanks for your help in advance!
Comments
SQL Backup/Restore issue
Hi,
Whatever the comparision that you have done with backup exec and netbackup is absolutely correct. In backup exec it used to create the master$4idr as a backup file for the master database but in netbackup the file does not get created.
Also for SQL 2005 there is no rebuildm.exe to recreate the master database but you can use the setup.exe from the cd and rebuild the master database. Once the master and model database is created then you would have the sql service started after which you can restore other databases using netbackup.
http://support.veritas.com/docs/315496
Incase if you wish to restore the latest copy of the master database you put the SQL in the single user mode and then restore the master database from the backup copy.
rgds,
PK
Hi, as I have already said "I
Hi,
as I have already said "I know there is a rebuild command line tool to recreate them using the SQL CD but it doesnt seems to work correctly with SQL 2005 SP3." This does not seems to work with SP3 so I cant recreate the Master databases without reinstalling SQL.
Anyone else run in to this issue? This seems a bit of a funadmental issue when restoring SQL
Would you like to reply?
Login or Register to post your comment.