HP Web Jetadmin Software - Backup and Cloning of an HP Web Jetadmin Installation

ManualsBrandsHP ManualsSoftwareHP Web Jetadmin Software

BACK UP, RESTORE, AND CLONE AN HP

WEB JETADMIN INSTALLATION

CONTENTS

Overview ................................................................................................................................ 2

Why back up HP Web Jetadmin? ............................................................................................... 2

Back up an HP Web Jetadmin installation that is configured for a local database ............................ 2

Run the backup script ............................................................................................................ 4

Restore an HP Web Jetadmin installation ..................................................................................... 5

Run the restore script ............................................................................................................. 6

Back up an HP Web Jetadmin installation that is configured for a remote database ......................... 7

Clone or migrate HP Web Jetadmin ........................................................................................... 8

Cloning procedure ................................................................................................................ 8

Method 1 for cloning ......................................................................................................... 8

Method 2 for cloning ......................................................................................................... 9

Limitations of cloning ........................................................................................................... 10

Data synchronization .............................................................................................................. 11

Alternate synchronization method ......................................................................................... 11

Export groups and configuration templates ................................................................................ 11

Summary ............................................................................................................................... 12

Summary of content (12 pages)

PAGE 1
BACK UP, RESTORE, AND CLONE AN HP WEB JETADMIN INSTALLATION CONTENTS Overview ................................................................................................................................2 Why back up HP Web Jetadmin?...............................................................................................2 Back up an HP Web Jetadmin installation that is configured for a local database ............................2 Run the backup script ..............................................
PAGE 2
OVERVIEW Files are typically backed up to perform fault tolerance in case a failure occurs on the machine where HP Web Jetadmin is installed. A significant effort might have been involved in configuring the HP Web Jetadmin settings, such as alerts or groups. Saving the key files that store these configurations as a safety precaution is always wise. Installing a duplicate installation of HP Web Jetadmin (cloning) without having to reconfigure these settings might also be desirable.
PAGE 3
The .bat files include commands that copy the files and launch the .sql files. The .sql files include commands that back up and restore the database. The backup and restore scripts must be run on NTFS file systems. NTFS file permissions are integral to HP Web Jetadmin and can be restored only when both the backup and restore scripts are run in NTFS. The backup and restore scripts stop the HP Web Jetadmin service.
PAGE 4
Some server backup programs might not be able to read the SQL files on the HP Web Jetadmin installation host. The SQL files remain in use while the HP Web Jetadmin service runs. The HP Web Jetadmin service must be stopped to allow the backup to execute correctly. When HTTPS is enabled in HP Web Jetadmin, the customer provides a server-specific SSL certificate.
PAGE 5
6. The .sql script runs the following command to create the HPWJA_DB_BACKUP.dat file and copy the file to the WJABackupRestore directory: copy %DB_BACKUP_DIR%\%DB_BACKUP_FILENAME% %DB_BACKUP_FILENAME% where DB_BACKUP_DIR=C:\HPWJA_DB_BACKUP DB_BACKUP_FILENAME=HPWJA_DB_BACKUP.dat 7.
PAGE 6
information, see item 3 in Limitations of cloning. If there are templates that contain passwords, see items 2 and 5 in Limitations of cloning. The following settings and data are required to restore HP Web Jetadmin:  A file-set from a previously performed backup using the backup.
PAGE 7
BACK UP AN HP WEB JETADMIN INSTALLATION THAT IS CONFIGURED FOR A REMOTE DATABASE It might be necessary to run scheduled backups of an HP Web Jetadmin installation that points to a remote SQL Server database instead of the local SQL Server Express database. HP Web Jetadmin provides a script to back up the default SQL Server Express database instance that is installed with the base product. The script also backs up the HP Web Jetadmin configuration settings.
PAGE 8
CLONE OR MIGRATE HP WEB JETADMIN There might be cases when an administrator wants to make a duplicate copy of an existing HP Web Jetadmin installation. The following are some of the reasons for making a duplicate copy of HP Web Jetadmin:  A new or beta version of HP Web Jetadmin requires testing, and it would be ideal to test on a separate machine without interfering with the production installation.
PAGE 9
tables are updated for the new installation. To prevent a restore of the Settings directory from downgrading the settings file, remove the Settings directory from the backup before restoring the backup (C:\Program Files\Hewlett-Packard\Web Jetadmin 10\WJABackupRestore\Settings). The database tables are updated for the new services, and the Settings directory has the default values of the new installation. 4.
PAGE 10
Limitations of cloning Cloning cannot duplicate every single item from the original machine. The following limitations exist with a cloned machine: 1. If alerts that involve traps were configured on the original machine, the alerts settings are copied to the new machine during cloning. However, nothing has instructed the devices to start sending traps to the new HP Web Jetadmin installation.
PAGE 11
DATA SYNCHRONIZATION Multiple installations of HP Web Jetadmin can share their device information with each other to eliminate unnecessary network traffic and improve the redundancy of device information in each installation.
PAGE 12
installation. This technique eliminates the need to re-create all of the groups or configuration templates. Right-clicking a group or configuration template provides options to export or import the groups or templates. Some restrictions apply when exporting groups and configuration templates. When exporting groups, the associated policies are not exported. Templates that have user-defined settings can be exported from HP Web Jetadmin 10.3 SR6 and later.