BACK UP, RESTORE, AND CLONE AN HP WEB JETADMIN INSTALLATION CONTENTS Overview ...

10 Note If there are templates that include OXPd settings, you must import the OXPd files into the cloned HP Web Jetadmin server (step 5), and then e

11 • HTTP proxy user and password settings • XTP tickets • OXPd Repository items (available under Tools > Options > Device Management > Co

12 Installations must be verified before synchronization can proceed. To verify an installation, a local user must be in one of the following groups:

13 SUMMARY Backing up an HP Web Jetadmin installation is always wise so that you can fully restore HP Web Jetadmin if the software is accidentally era

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 sign

3 • osql_restore.sql • WJABackupRestoreInstructions_<language_code>.txt The .bat files include commands that copy the files and launch the .sq

4 Permissions problems related to the HPWJA_DB_BACKUP.dat file might occur. When the restore.bat file runs, OSQL commands are activated by the Network

5 where OSQL=C:\Microsoft SQL Server\90\Tools\Binn\OSQL.EXE 6. The .sql script runs the following command to create the HPWJA_DB_BACKUP.dat file and

6 the host or Windows OS instance that was used to process the original file-set. For more information, see item 3 in Limitations of cloning. If there

7 A message appears in the command window that specifies the number of files that were copied and states that an osql_restore.log file is available fo

8 directory because it does not always exist, an additional permanent directory can be created and shared. The SQL script can be modified by adding an

9 4. If a true clone is required, install a fresh copy of HP Web Jetadmin on the new machine (clone) that is the same release as is installed on the