Backup and Restore the HPOM for Windows 8.16 Management Server

Size: px
Start display at page:

Download "Backup and Restore the HPOM for Windows 8.16 Management Server"

Transcription

1 Backup and Restore the HPOM for Windows 8.16 Management Server White Paper version 2.0 Backup and Restore the HPOM for Windows 8.16 Management Server... 1 Change record... 2 Conceptual Overview... 3 Understanding the HPOM for Windows 8.16 Backup and Restore... 3 Backup... 3 Restore... 3 Backup workflow... 4 Downloading migration data to perform a full backup of the management server... 4 Backing up the management server database... 5 Scheduled task policy VP_SM_DB_Backup... 5 Restore Workflow... 6 Restoring your management server using the downloaded migration data... 6 Restoring the management server database... 7

2 Change record Version Date Changes 1.0 April 2010 First version for standalone servers 2.0 June 2010 Additional steps for clustered installations

3 Conceptual Overview Understanding the HPOM for Windows 8.16 Backup and Restore HPOM for Windows 8.16 introduced a new, centralized workflow for backup and restore, that enables the user to take care about all data necessary to restore a management server while significantly reducing the steps needed to backup and restore the server compared to earlier versions of HPOM for Windows. The backup/restore mechanism handles all management server data such as instrumentation, configuration (registry values, XPL configuration), certificates (necessary for the newly introduced HTTPS communication), model (nodes, services etc.), messages, etc. Backup To backup all relevant data of the management server, you should perform the following two tasks: 1. Export the migration data as described in the Installation and Migration Guide of HPOM for Windows 8.16 and then save it on a secure medium (e.g. a DVD). 2. Backup the management server database The export of the migration data should be performed at least once after the installation of the management server. The saved data contains all information that is necessary to restore the management server and enable it to communicate with the managed nodes. Performing this task is required for restoring the communication with the managed nodes after a complete failure of the management server. Since the export of migration data is rather time consuming, it is possible to backup the HPOM for Windows database in addition. The database backup includes all nodes, node groups, tools, services, and service types stored in the WMI repository, all messages, and all policies and policy groups (incl. the ones that have been created after the last database backup). However, it does not include the instrumentation installed by new SPIs, changes in the server configuration, changes to the WMI class model (often done by SPI installations), and modified server certificates. For that reason, it is recommended to export the migration data (task 1) once right after the installation of the management server and then repeat it whenever significant changes are performed on the management server such as installing/removing SPIs or changing the management server certificates. In addition, it is recommended to perform a nightly backup of the management server database (task 2) using a scheduled task policy. Restore To restore the management server: 1. reinstall the HPOM for Windows Server and upload the previously exported migration data and/or 2. restore the management server database. Perform step 1 if the management server system crashed (e.g. hardware failure) or got corrupted/damaged. However, to roll back from some recent changes to the management server, step two might be sufficient. You can also combine step 1 and 2, for example to restore management server state from last night (before the crash).

4 Backup workflow This chapter describes the necessary steps to perform a backup of the management server. As described in the Conceptual Overview chapter, it depends on the actual scenario which mechanism for backup you should choose. Downloading migration data to perform a full backup of the management server To perform a migration data download, it is necessary to use the HPOM for Windows 8.16 installation medium that was used to install the management server and the latest installation patch, if existent. Also, you need enough free disk space on a local disk to store the downloaded data. In case of a clustered HPOM for Windows installation, download the migration data from the active node only, as described in the HPOM Migration guide. While downloading the migration data, it is not necessary to stop the management server or any Windows services. Your management server will remain functional during the download. To launch the migration data download, start the program setup.exe from the HPOM for Windows 8.16 installation medium. After a welcome message, the following screen appears: Select the option to export migration data and choose a local folder to store the downloaded files. The user under which the installation wizard is running as well as the HP-OVE-User and the HP-OVE-DelegUser should have full access rights to the folder you choose. Then click Next. The migration data download will now start. It may take some time until the data export is finished. After the successful download, the following screen shows up:

5 Click Complete to close the installation wizard. The downloaded data should be kept in a safe place. Keep in mind that it is possible to fully restore your management server and the communication to its managed nodes with this data! Backing up the management server database The HPOM management server uses an SQL Server instance with a user-configurable name as core data repository. The HPOM installation suggests the name OVOPS as default name for this instance. The instance might be also shared by other HP Software products, which create other databases in this instance. The full name of the database depends on the location of the 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 HPOM self management includes the scheduled task policy "VP_SM_DB_Backup", which schedules and performs a backup of the openview database. 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: Open the MMC console Open the policy from the following location: PolicyGroups\HPOM Self Management\en\Database Server\VP_SM_DB_Backup Edit the Command field:

6 o 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. o If the database resides on a remote server, you must replace <servername\instancename> with the SQL Server instance name of the remote database instance. 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. 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. Save the policy Deploy the policy to the system where the HPOM database is installed. The database backup files are written into the following directory: <HPOM data files folder>\<instancename>\backup. The database backup consists of the files openview_dat.bak and openview_log.bak. These files are overwritten every time the backup policy is executed. If you want to keep several versions of the backup files, make sure to copy them to another folder before the policy is executed the next time. You may change the location of the backup files by editing the VB script file backup_openview.vbs which is located under: %OvInstallDir%support\backup_openview.vbs %OvShareDir%Instrumentation\Categories\VP_SM_DB\Windows %OvDataDir%bin\instrumentation (when the policy VP_SM_DB_Backup is deployed on the server) You can also perform the database backup manually, by executing the above VB script on the database server, using the same command line and user as specified in the policy editor. Restore Workflow This chapter describes the necessary steps to restore your management server. Depending on your scenario, you might choose to only restore the HPOM database, or to perform a full restore using the downloaded migration data followed by a restore of the HPOM database. To only undo some recent changes, restore only the HPOM database. If your management server failed completely or you want to restore data that is not kept in the database (such as instrumentation, certificates etc.), perform a reinstallation using the previously exported migration data and then restore the latest database backup, to make sure that your management server is completely up-to-date (effectively up-to-date until the time of the last database backup). Restoring your management server using the downloaded migration data To perform a full restore of your management server using the downloaded migration data, you need the HPOM for Windows 8.16 installation medium and the latest installation patch, if existent.

7 Before starting the restore, prepare your system to have the same hostname and IP address as before. If the hostname or IP address has changed, the HTTPS communication to the managed nodes can not be restored. If you are restoring a clustered HPOM for Windows server, please make sure to also use the same virtual server name as on the old system. From the HPOM for Windows 8.16 installation medium, start the installation wizard, using the program setup.exe. After a welcome message, the following screen appears: Select the option to upload migration data and choose the folder that contains the exported data for your server. Also, tick the checkbox Migration from same host machine. Otherwise the restoring will not be able to restore the communication environment. In the following steps of the wizard, use the same installation parameters as you did during the initial installation of your management server. Wait until the installation finishes completely. Install all server, agent and accessories patches you had in your previous installation. After the installation finished successfully, your management server has the configuration state of the time of the migration data download. The communication with the nodes should work correctly. You can now start using the management server or continue with restoring a more recent database backup as described in the following chapter. In case of a clustered installation, install the subsequent nodes after successfully installing the first node. A migration data upload doesn t have to be performed on the subsequent nodes. Restoring the management server database To restore the HPOM database that has been exported using the VP_SM_DB_Backup policy or manually by executing the backup script, please follow these steps: Close all currently opened consoles Stop server processes and services

8 o In case of a clustered installation, make sure to perform the following steps on the active node only. o Execute the command vpstat -3 r stop and wait until all services are stopped. Copy the database backup files to the <HPOM data files folder>\<instancename>\backup folder (the same as the folder where the files have been exported to originally). This folder might be on another system, in case of a remote or clustered database installation. Make sure that your SQL Server service is running. In case you are using a local database installation, the service is stopped after the previous vpstat command above. In this case, use the service control panel to restart the service called SQL Server (<instancename>). Run the following command: cscript.exe %OvInstallDir%\support\restore_openview.vbs and wait for the script to finish.. You don t need to specify the database instance name as a parameter for the script. It is read from the registry automatically. Read the output of the script. In case the restore succeeded, the output shows the message Restore succeeded at the end. You can also find detailed information about the restore in the output. Restart your management server processes by executing the command vpstat -3 r start Your database now has the same configuration state as it had when the database backup was performed.