If you can still start SQL, you can restore the latest copy of the master database backup using the Automate master database restore option in Backup Exec’s Restore Job Properties for SQL dialog box and then restore any other databases, if needed.
If the master database is critically damaged and SQL cannot be started, rather than running the Rebuild Master utility, or reinstalling SQL to be able to restart SQL, you can replace the corrupted or missing databases with the copies of the master and model databases that Backup Exec automatically creates and updates whenever backups of those databases are run. After SQL is running again, you can restore the latest copy of the master database using Backup Exec’s Automate master database restore option, and then restore any other databases, if needed.
If copies of the master and model databases were not made, then you must use Microsoft’s rebuildm.exe utility to rebuild the master database and start SQL.
Because all changes made to the master database after the last backup was created are lost when the backup is restored, the changes must be reapplied. If any user databases were created after the master database was backed up, those databases cannot be accessed until the databases are restored from backups or reattached to SQL.