HP BB118BV - StorageWorks Data Protector Express Package User Manual page 326

Step 4. Apply changes to the master database
1. Go to the SQL Server Enterprise Manger and right-click the SQL server instance. Select Properties to
open the SQL Server Properties window.
2. Under the General tab in the SQL Server Properties window, open the Startup Parameters window
and remove –m from the list of existing parameters.
3. Restart the SQL server instance. (Right-click the SQL server instance and select Stop; right-click the
SQL server instance and select Start.)
If there have been no changes to the master database since the last dump, then proceed to step 5
"Drop invalid databases and database devices."
4. If login IDs or devices have been added to or dropped from the master database since the last backup,
those changes must be reapplied. Restart the server and reapply the changes manually or from saved
batch files.
5. If databases have been created, expanded or shrunk since the last dump of master, those databases
must be dropped and then restored.
6. If you have made many changes and have no recent dump, it is possible that by reloading master in
some cases you can regain data in user databases that has been lost. This technique requires the use of
DISK REINIT and DISK REFIT and can involve manual modifications to the master database tables.
Use DISK REINIT to re-create rows in sysdevices for all database devices that have been added
•
after the most recent dump. DISK REINIT updates sysdevices just as DISK INIT does, but it does
not format the physical disk file, so existing data is preserved.
Use DISK REFIT to re-create rows in sysusages and sysdatabases for all CREATE and ALTER
•
DATABASE statements that were performed after the most recent dump.
DISK REFIT scans the physical file associated with each space that is allocated to databases. It also adds
the corresponding sysdatabases entries. Some of the information is not reconstructed perfectly. For
example, the original virtual device number is not assigned, because it is not known. Instead, virtual
device numbers are assigned sequentially. The database owner is not extracted while scanning the
physical files; ownership is set to the system administrator. It is also not possible to determine how many
sysusages entries originally existed. DISK REFIT inserts a separate entry for each different segment type.
When this is done, correct the entries made by DISK REFIT to sysdatabases and sysusages (if
•
desired) and also add to syslogins any login IDs that were not retained. Then shut down and
restart SQL Server.
Capturing the latest changes made to a database by using DISK REFIT and DISK REINIT to
re-create the master database is possible, but it is preferable to keep the master database current by
dumping it after creating or altering databases. Using DISK REFIT and DISK REINIT is a complicated
process that can result in data loss because many of the changes made to a database often must be
reconstructed manually in the master database. If you feel this technique is necessary, contact your
primary support provider before beginning the recovery process.
Step 5. Drop invalid databases and database devices
1. Use the SQL Enterprise manager to drop any invalid database devices and databases from the newly
restored master database.
If you are recovering from a disaster where you have lost a database device file, the master
database you have just restored still contains a reference to it. Data Protector Express will not be able to