make_Tape_recovery

[LucianoCarvalho]

Hi Guys!
Does anyone know the sintaxe of make_tape_recovery that I can use, so the backup will not record any log file about the recovery??

thanks

[Pete Randall]

Luciano,

I'm not sure what you mean by recording any log file, but this is the syntax I use:

make_tape_recovery -a /dev/rmt/XXmn -I -v -x inc_entire=vg00


If you are using similar syntax and having problems, could you elaborate?


Pete

[Massimo Bianchi]

Hi,
if you want to "cover your tracks", then progress and errors are logged to /var/opt/ignite/logs/makrec.log1.


Delete the files in this directory and you are clean.

Massimo

[LucianoCarvalho]

Actually, I need to runa a backup using make_tape_recovery, but I don't want update the files makrec.log and makrec.last. I don't want that make_tape_recovery update any log file.

[Massimo Bianchi]

Not sure if this answer, but:

- if you do NOT use the option "-C" the makerc.last won't be created and updated.

- If you are really concerned, save those file before the make_tape_recovery run and move back them at the end.

Massimo

[Pete Randall · Accepted solution]

Luciano,

There are no options available to avoid updating makrec.log and makrec.last. I'm afraid you will have to use some sort of manual procedure, or perhaps script your make_tape_recovery command thusly:


cp makrec.log makrec.log.save
cp makrec.last makrec.last.save
make_tape_recovery (insert normal options)
cp makrec.log.save makrec.log
cp makrec.last.save makrec.last



Pete

[James R. Ferguson]

HI:

If you are concerned about the files in the '/var/opt/ignite/logs' directory then it appears that you are running the *old* 'make_recovery'. If you utilize 'make_tape_recovery' then your session's backup information *including* a gratuitous manifest, is written to the '/var/opt/ignite/recovery/latest' directory. You could dispose of those contents afterwards, I suppose. To use 'make_tape_recovery' for vg00 do:

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

Regards!

...JRF...

[LucianoCarvalho]

The reason is not to preserve the files, it's to preserve CPU resources the system will loss updating this files.

[Pete Randall]

Luciano,

Oops, better make that:


cp makrec.log makrec.log.save
cp makrec.last makrec.last.save
make_tape_recovery (insert normal options)
mv makrec.log.save makrec.log
mv makrec.last.save makrec.last



Pete

[James R. Ferguson]

Hi (again):

Oops, too fast. I meant to add that you could eliminate the '-v' option and reduce the content the '/var/opt/ignite/recovery/latest/recovery.log'. The largest file written to the '/var/opt/ignite/recovery/latest' directory is the 'flist'. Eliminating it at the end of the recovery session would regain you the most space.

Regards!

...JRF...

[Pete Randall]

Luciano,

I find it extremely hard to believe that there is very much CPU consumed in the update of these files. Why are you interested in reducing it? Are you having problems with the backup?


Pete

[LucianoCarvalho]

I'm no major problems. But the backup will be done during the time that the users are using the system, so I want to reduce the backup CPU consume at minimum.

[Pete Randall]

Lucian,

I still don't see that you should be seeing major CPU contention. I would recommend, however, that you consider running your make_tape_recovery off-hours via a cron or at job and avoid the contention entirely. Just preload the tape, set up the cron/at job and view the results in the morning.


Pete

[Todd McDaniel_1]

Luciano,

First if your system, is that cpu bound you have other more serious problems that merely copying a file...


_____________________________
The actual make_tape_recovery backup process takes up much more CPU than merely creating a directory and files... under /var/opt/ignite/recovery//*

Besides... these files are created while the make_tape_recovery are running... so there is no way to do this...