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 additional line to the backup.bat file to copy
the .dat file from this shared directory to the HP Web Jetadmin temporary directory. Now the
backup.bat script is never disrupted and can continue from that point.
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. Proper testing involves using
the same groups, alerts, and so on as the production HP Web Jetadmin installation.
• Many individuals simultaneously access HP Web Jetadmin. Multiple installations of HP Web
Jetadmin improve performance. Duplicate settings and lists of devices across all installations are
easiest to manage.
• If there is a failure on a production HP Web Jetadmin installation that takes it out of service, a
duplicate backup installation assumes the duties of the installation presenting the failure
(redundancy).
• It is necessary to migrate from a 32-bit operating system to a 64-bit operating system.
Cloning procedure
Cloning is not a designed feature or function of HP Web Jetadmin. There might be cases where not
everything can be cloned. Limitations of cloning are explained in the next section. These instructions
are provided only as an example of how to create a duplicate copy (or clone) of HP Web Jetadmin.
Method 1 for cloning
One technique for cloning an HP Web Jetadmin installation involves restoring an HP Web Jetadmin
backup that was created by using the script described in Run the backup script
on a different machine
than the machine where the backup was performed. This is the most complete cloning technique
because it clones the database that contains the device settings and the Settings directory that
contains the archived reports, firmware repository, archived data exports, file repositories, and so on.
Make sure that the new HP Web Jetadmin installation (clone) runs on the same drive letter and the
same directory on that drive letter as the original installation. The drive letters must match because
there are many references in the files that are copied to the new machine that point to the drive letter
that is used on the old machine.
1. Back up the original HP Web Jetadmin installation by using the procedure in Run the backup
script.
2. On the original HP Web Jetadmin installation, export all of the templates. In the Device
Management navigation pane, expand Configuration, right-click Templates, and then select
Export configuration templates. In the Export Templates wizard, select all of the templates, click
the Next button, and then complete the wizard.
Note This step is required if there are templates that contain passwords
3. On the original HP Web Jetadmin installation, export the XTP tickets. In the Device Management
navigation pane, expand Configuration, click XML Ticket Repository, select all XTP tickets, select
Export, type in a password, click OK, type in a filename, and then click Save.
Note XTP tickets are only present if this has been licensed. The export option for XTP tickets
is available in HP Web Jetadmin 10.4 SR2 and later.
(54 páginas)
Manymanuals.com
Manymanuals.de
Manymanuals.fr
Manymanuals.it
Manymanuals.pl
Manymanuals.cz
Manymanuals.es
Manymanuals-pt.com
Comentários a estes Manuais