archiving to disk then onto an Ignite server

[Isralyn Manalac_1]

We are currently managing 10 HP-UX servers, 5 of which are located remotely. As per security requirement, we were not allowed to configure an Ignite server. We’re looking for other means for us to perform OS image backups of these machines without having to go to our 2nd data center yet still conforming with the security requirement. One option being considered is to define each of the 5 servers as an Ignite server and a client itself. After archiving the OS image onto disk, we’ll transfer the image via scp onto a “master” Ignite server located in the 1st data center. Afterwhich, we’ll create a bootable tape. I have yet to test this, though…Would you have any other ideas? Any feedback will be greatly a

[alec pringle]

Hi,

I don't think you need to define each client as an Ignite server - that would be quite an admin overhead. You might want to try creating an image from make_sys_image and save_config which are available from the Ignite client install:

make_sys_image is used to create a system archive of a running single
user or multi-user system. This archive can be in cpio or tar format,
and can be compressed with either compress or gzip make_sys_image can be called as a post config script by Ignite-UX as part of the install
process, or invoked at the command line on a running system. The
archive can be written to a file, to a tape, or to a raw disk device
on a remote system or to the local system. If the archive destination
is a remote system, that system must have a .rhosts entry for the
local system, or an nfs mount available. The options for this command
can be a combination of command line arguments and environment
variables passed in with the Ignite-UX config file via env_vars keyword.

The archives created by make_sys_image are designed for use with
Ignite-UX as part of an archive based ignition process. Before the
archive is used for installing systems, the file system impacts of the
archive must be obtained. See archive_impact(1M). make_sys_image
does not capture file system or disk layout information.


# make_sys_image -s -d /var/ -n image.gz

The -s flag indicates the IP address of the server where the image will be created.

The -d flag indicates the directory into which the archive will be created.

The -n flag indicates the name of the archive.

By default the archive will be in gzip'd tar format.