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

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. To set the new HP Web Jetadmin installation to

process the alerts, modify the entries in the trap destination lists of each device. HP Web Jetadmin

provides the ability to modify the device trap destination lists in both single and multiple device

configuration modes.

2. Reports that display information pertaining to which user printed documents are not processed for

the same reason as the alerts issue. By User reports rely on devices sending traps after each print

job. Because HP Web Jetadmin now runs on a new machine, new entries must be made in the

trap tables of all the devices to send traps to the new machine. HP recommends resubscribing to

the By User collections on the new HP Web Jetadmin machine to ensure that the entries are

written to the trap tables.

3. When restoring the settings and database information to the HP Web Jetadmin host, encrypted

data no longer functions if the host or Windows OS instance is different from the host or

Windows OS instance that was used to process the original file-set. In these cases, the encrypted

data can be restored manually by using the HP Web Jetadmin User Interface. The following are

some examples of encrypted data:

 Global device credentials, such as the SNMP Community Name and EWS password

(available under Tools > Options > Shared > Credentials > Device)

 HTTP proxy user and password settings

 XTP tickets

 OXPd Repository items (available under Tools > Options > Device Management >

Configuration)

 Templates that contain encrypted data

Device passwords and configuration templates that contain passwords are encrypted to secure

any passwords that might be stored. To unlock the encryption, a key that is applicable only on the

machine where it was created must be used. Passwords are too important to not be protected as

securely as possible. Therefore, items that pertain to passwords in configuration file templates are

present in the HP Web Jetadmin database, but can no longer be decrypted and are unusable

after the clone operation. For templates that contain passwords and security settings, all of the

passwords and security settings, such as the SNMP Set Community Name, are removed from the

template. All of the other settings, such as the system location, remain the same. These templates

must be edited or re-created on the new HP Web Jetadmin installation.

Workaround: It is possible to export templates that contain passwords by using HP Web

Jetadmin. For instructions, see steps 2 and 5 in Method 1 for cloning.

 If discoveries have been scheduled on the machine that is being cloned, those same

discoveries occur on the new HP Web Jetadmin installation at the exact same time. These

duplicate discoveries result in twice the network traffic. It might be more beneficial to

synchronize the cache on the new installation with the previous installation. For more

information, see Data synchronization.

 If reports were run on the machine that is being cloned, data collections are scheduled to

occur at a particular time and frequency. Cloning causes duplicate collections to occur on the

same devices and increases network traffic.