Data Protector Express User Guide (TC330-96005, September 2011)

Start the Data Protector Express and SQL Server services
1. Start the Data Protector Express service by using one of the following methods:
a. Using the Windows Command Line
i. Open a command prompt.
ii. Switch to the following directory:
C:\Program Files\HP\Data Protector Express
iii. Type the following command at the command prompt:
ytwinsvc -s
This command starts the Data Protector Express service on the local machine.
b. Using the Microsoft Management Console (MMC)
i. Right-click the My Computer icon and select Manage.
ii. In the left pane of the window, select Services and Applications Services.
iii. In the right pane of the window, locate the Data Protector Express service.
iv. Right-click the service and select Start.
2. Restart the SQL Server service using the SQL Server Enterprise Manager.
Restore the msdb database
When restoring the msdb database, consider the following:
• The msdb database supports SQL Executive and provides a storage area for scheduling
information. The schedules that you implement using SQL Enterprise Manager are maintained
in the msdb database. This includes such things as the tasks that you schedule from the Task
Scheduling window, the automatic backups you schedule from the Database Backup/Restore
window and all replication tasks, which are automatically created by the system if the server
is configured as a replication distributor.
• During installation of a server, the setup program automatically creates two devices (of 2MB
and 1MB) on the same disk drive as the master database and then places the msdb database
on the 2MB device (MSDBDATA) and its transaction log on the 1MB device (MSDBLOG).
Scheduling information is then stored in this database.
• During a rebuild of the master database, the setup program drops and re-creates the msdb
database, which results in a loss of all scheduling information.
Restoring Microsoft SQL Server 7 master databases
A damaged master database is evident by the failure of the SQL Server to start, by segmentation
faults or input/output errors or by a report from DBCC. An example of an error might be damage
caused by media failure in the area in which master database is stored.
The procedure used to recover a damaged master database is different from the procedure used
to recover user databases. If the master database becomes unusable, it must be restored from a
previous dump. All changes made to the master database after the last dump are lost when the
dump is reloaded and therefore must be reapplied.
It is strongly recommended that the master database be backed up each time it is changed. This
is best accomplished by prohibiting the creation of user-defined objects in the master database
and by being aware of the statements and system procedures, and the equivalent actions in SQL
Enterprise Manager, that modify it.
The most common statements and system procedures that modify master are:
• DISK INIT
• CREATE DATABASE
• ALTER DATABASE
58 Working with Third-Party Applications