Backup OS using ignite-UX server

[Nguyen Anh Tien]

I have 2 node Cluster (just named node1,node2). Tape driver DDS4 is externally attached to node2. both server are installed ignite-UX bundle. Now i want to back up node1's OS. How do i configure it? (pls explain step by step for me).
Thank.

[Steven E. Protter]

I don't think the tape drive on node2 is accessible to node1 even if its running serviceguard. If I'm wrong about that, ignore the rest of this post.

Two choices then.

Veritas Netbackup media servers ($5,000 per box) will allow you to make node2's tape drive available to node 1. Then a standatd make_tape_recovery script will do the job.

There are probably other ways to go.

Or you can do a make_sys_image to an NFS share on node 2 and use ssh to archive the image to tape.

Here is how to do that.

1) define an NFS share on node2 edit /etc/exports and make sure the directory has lots of space.

2) exportfs -av make sure you were successful

3) /usr/contrib/bin/make_sys_image -d /images -s local -u

Step 3 assumes you exported a folder called images. The make_sys_image command temporarily disrupts permissions on files and should be run while the system is idle. Other command options might make it less obnoxious. Note that when you run make_tape_recovery that script calls make_sys_image with options.

4) on node 1 in the backup script
ssh root@node2 "/usr/bin/tar /images/filename.gz"

This command will take the file directly to tape.

Caveat Emptor. This process is not fully tested and should require tweaks. It will however get the job done at the end of the day.

SEP

[Nguyen Anh Tien]

Thank SEP.
How about make_net_recovery and make_tape_recovery (using -s option).I want to build node2 as ignite-UX server.and make node1's OS backing up. Whenever node1 fail, I recover node1's OS from recover tape.

[Bernhard Mueller]

Nguyen,

good idea, having a recovery server for the node without tape. However, the thing to consider is that you have a cluster, and typically (though not necessarily) the core IO lan card is used for a seperate, dedicated heartbeat lan.

Now, the issue is that you can only boot over the network via this core IO lan card.

Therefore you need to make sure your ignite server responds to boot requests through the heartbeat lan. I.e. you need to setup a boot IP in /etc/opt/ignite/instl_boottab within the HB-lan and use instl_adm to set the server ip, netmask and route config appropriate.

Run instl_adm -d to display current values.

If you have a chance, test it.

Alternatives are to create a boot CD or use a default install CD to boot from and then you can select a non-core IO lan card to use a certein IP etc. and recover through the default network. The Ignite version on the CD and on your Ignite server should be a relative close match.

HTH
Regards,
Bernhard

[Claudio Martin_1]

Nquyen,
It's a very good idea to config node2 as a ignite server and node1 as a client. But don`t forgot to do a make_tape_recovery -Av of the node2 ( the ignite server . You need a backup of the vg00 of the server too and you have a tape attached to this.

Regards.

[Nguyen Anh Tien]

Thank all.
Just Image that 2 nodes independently. (do not think its made 2 nodes cluster). I can shutdown cluster and run 2 node separately.
Now Image that. I have one Ignite-UX server and want to backup another server'OS. how can i do it.