Back up the HPOM database

• Local database:
  If SQL Server Express is used as HPOM database, the full database instance name is <local host>\<instance name>.
• Remote database:
  If you are using a remote SQL Server database, the name is <server name>\<instance name>.
• Clustered database:
  If the SQL Server database is clustered, the instance name is <virtual SQL server name>\<instance name>.

Scheduled task policy VP_SM_DB_Backup

After you have installed the management server, deploy the policy to the system where the HPOM database is installed. Before deploying the policy, modify it as described below:

1. Go to the policy editor.
2. Open the policy at this location:

   Policy Groups HPOM Self Management en Database Server VP_SM_DB_Backup

3. Edit the Command field:
   • If the database resides on the management server itself, you can remove <servername>\<instancename> from the end of the command line. In this case the SQL Server instance is looked up from the registry.
   • If the database resides on a remote server, you must replace <servername>\<instancename> with the SQL Server instance name of the remote database instance.
4. In the Task tab, edit the Execute as user and the Specify password fields, and add the user account and password of a user with SQL Server administrator permissions.
5. Optional: By default the database backup is scheduled for 0:30 a.m. every morning. If that time does not suit your needs, you can adopt the schedule in the Schedule tab.
6. Deploy the policy to the system where the HPOM database is installed.

Backup and restore related VB scripts

NOTE:
Modification to these scripts requires basic knowledge of the Microsoft Visual Basic script language.

The following backup and restore scripts are located in the %OvInstallDir%\Support\ directory.

• backup_openview.vbs

  This script performs a backup of the openview database and stores the backup files in the directory %OvDataDir%\datafiles\<instance name>\backup.

• restore_openview.vbs

  This script restores the openview database from the backup files created by backup_openview.vbs.

Location and housekeeping of backup files

%OvDataDir%\datafiles\<instance name>\backup

Backup files are named as follows:

• openview_dat.bak (openview database)
• openview_log.bak (openview database transaction log)

These files are overwritten on every new execution of the VP_SM_DB_Backup policy. If you want to keep them you have to ensure that they are stored on a storage device or copied into another location in the meantime.

You may change the location of the backup files by editing the VB script file %OvInstallDir%\Support\backup_openview.vbs.

Monitoring backup execution

The VP_SM_DB_Backup policy will send messages to the active messages browser:

• When the backup starts.
• After a successful backup. (This message also contains the backup duration time.)
• After a backup failure (critical message).

Configuration on a remote database server

Starting the openview database backup manually

cscript "%OvInstallDir%\support\backup_openview.vbs"

NOTE:
If the HPOM database is a remote database, the SQL Server instance name must be added to the command line:
%OvInstallDir%\support\backup_openview.vbs <servername>\<instance name>

Related Topics:

• Restore the HPOM database