topic Re: Ignite Server - Cron in Operating System - HP-UX

Ignite Server - Cron

Eric Buckner — Wed, 22 Jan 2003 21:13:37 GMT

Hey everyone. I can't figure out the proper command string to do what I want from cron and thought I would ask you guys. I have been using the Ignite GUI and am not sure exactly what it is doing.

I have an Ignite - UX / Data Protector (Omniback) server that backs up all of our data. I want to put a cron entry into each of our machines to do a make_net_recovery to that box as well and only keep 1 current archive. And then later on issue a make_tape_recovery on the Ignite Side w/ Omniback shutdown.

So far our total size from the make_net_recovery is about 8GB and our OB2 database is almost 3GB. Using DDS3 tapes I am hoping I will be able to fit all of this on 1 tape.

Thanks!
Eric

Re: Ignite Server - Cron

Ian Kidd_1 — Thu, 23 Jan 2003 00:17:29 GMT

We run make_net_recovery in a script that called from cron. The line we use to invoke make_net_recovery on the client side is:

/opt/ignite/bin/make_net_recovery -s myserver -a myserver:/var/images/myclient -v -d "myclient recovery archive" >> /tmp/ignite.log 2>&1

fyi, "myserver" is the ignite server and "myclient" is the ignite client (not real names)

-s indicates the ignite server -a indicates the ignite_server:path where the images are

-v is verbose messaging

-d gives the image a description

We send the output off to a logfile for verification purposes. The script wraps this around some alerting/messaging stuff.

we don't specify the number of archives kept, giving it a default of 2, but if we wanted only one, we'd use -n 1 for a syntax of:

/opt/ignite/bin/make_net_recovery -s myserver -a myserver:/var/images/myclient -v -d "myclient recovery archive" -n 1 >> /tmp/ignite.log 2>&1

We still haven't converted over to make_tape_recovery - still on the old make_recovery, so I don't have the syntax for it.

Re: Ignite Server - Cron

Patrick Wallek — Thu, 23 Jan 2003 00:48:29 GMT

Assuming all of your stuff is in vg00, the make_tape_recovery command you should use is:

# /opt/ignite/bin/make_tape_recovery -a /dev/rmt/0mn -I -v -x inc_entire=vg00

Replace the /dev/rmt/0mn with whatever your appropriate tape drive is.

You MIGHT be able to get all of your stuff on a DDS3, but it'll be close. The make_net_recovery images are already compressed, so they won't change. The OB2 DB and the rest of your VG00 is the question. If I were you, I'd feel more comfortable with a DDS4 (20 GB native), but I don't know if you have the money to spend on one of those.

Re: Ignite Server - Cron

Eric Buckner — Thu, 23 Jan 2003 16:44:59 GMT

Thanks for the info guys. This is exactly what I was looking for!!

10 pts for both of ya!

Re: Ignite Server - Cron

Ian Dennison_1 — Thu, 23 Jan 2003 16:49:45 GMT

Eric,

small point of order,....

ignite 2>&1 >>/tmp/log

The above command will only capture Stdout and Stderr. Ignite will produce error output that is not captured by this method.

ignite 2>&1 | tee -a /tmp/log

The command above will actually capture all output (including all error text) and append it to the file.

Kind of daft that Ignite would not correctly output using stderr, but this has caused me problems in the past!

Share and Enjoy! ian