- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- make_Tape_recovery
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-05-2003 03:40 AM
09-05-2003 03:40 AM
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
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-05-2003 03:46 AM
09-05-2003 03:46 AM
Re: make_Tape_recovery
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
Pete
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-05-2003 03:54 AM
09-05-2003 03:54 AM
Re: make_Tape_recovery
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-05-2003 03:55 AM
09-05-2003 03:55 AM
Re: make_Tape_recovery
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-05-2003 04:06 AM
09-05-2003 04:06 AM
Re: make_Tape_recovery
- 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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-05-2003 04:08 AM
09-05-2003 04:08 AM
SolutionThere 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
Pete
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-05-2003 04:09 AM
09-05-2003 04:09 AM
Re: make_Tape_recovery
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...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-05-2003 04:09 AM
09-05-2003 04:09 AM
Re: make_Tape_recovery
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-05-2003 04:09 AM
09-05-2003 04:09 AM
Re: make_Tape_recovery
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
Pete
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-05-2003 04:12 AM
09-05-2003 04:12 AM
Re: make_Tape_recovery
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...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-05-2003 04:14 AM
09-05-2003 04:14 AM
Re: make_Tape_recovery
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
Pete
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-05-2003 04:19 AM
09-05-2003 04:19 AM
Re: make_Tape_recovery
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-05-2003 04:22 AM
09-05-2003 04:22 AM
Re: make_Tape_recovery
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
Pete
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-08-2003 08:09 AM
09-08-2003 08:09 AM
Re: make_Tape_recovery
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...