warning in make_tape_recovery

[Ionut Grigorescu_2]

Hi,

I have attached the log file from make_tape_recovery. I'm concerning of the warnings regarding the long file names. Could that be a problem for a recovery from the Ignite tape ? - I can backup those directory via sam or Omniback, too ,but I want to know if the tape is usable after those warnings.

Thanks in advance,
ionut

[John Dvorchak · Accepted solution]

I am afraid that you are not going to be happy with the results if you try to restore with that Ignite image. Pax has a 100 character limitation and according to Bill Hassel in a previous thread: (I found it with a goolge search on pax 100 charaters)

"It is a pax limitaton and must be avoided by using smaller path lengths."

Then he goes on to tell the easiest way to avoid this problem is to move the directory tree to another volume group, other than vg00, and create a symlink to the target directory.

In any event, I think I'd just slap the person responisble for such a long name, until that feeling passes.

[Pete Randall]

Your problem stems from the fact that you're using Ignite to back up non Root volume groups. You're backing up vg00 - good. Then you're backing up vgdb, vgdb01, vgnms, and vgosspkg1, if not more. While Ignite has been enhanced to let you back up additional vg's, it really is not the appropriate tool. It's a recovery tool, designed to recover your root volume. Your data volumes should be backed up by conventional means like fbackup, omniback, or even tar, that give you more control and flexibility, like incremental backups and scheduled backups and tape volume tracking. Then, when you recover your vg00, your backup software is available to you. You import (or create) your volume groups and use the backup software to restore the data to them. The way you've got it set up, recovery (as in Disaster Recovery at a DR site) may not even be possible because the device files for all your other vg's are going to be different.

Use Ignite for your root volume, keep data out of your root volume, and use conventional backup means for that data. Ignite is not a backup tool.


Pete

[Dietmar Konermann]

It's in fact a tar(1) format limitation not to allow path lenghts >100 (according to X/Open CAE Specification XCU 4.2). This limit applies to pax(1) in tar mode also.

[Michael Steele_2]

LOL

"...In any event, I think I'd just slap the person responisble for such a long name, until that feeling passes...."

You are incorrigible Mr. Dvorchak

Still LOL.

[Steven E. Protter]

Try this.

#!/usr/bin/sh
/opt/ignite/bin/make_tape_recovery -Av -x inc_entire=vg00


If you want to make an image of an entire system, thats a Golden image.

Look into using the make_sys_image command. You can still do that to tape if you want. You are getting errors because you are trying to back up open databaes and stuff.

SEP

[Luigi Cicconi]

The link warning is from a tar limitation as the others have mentioned. You can use the "-m cpio" with make_tape_recovery to use cpio in the place of tar. This should resolve your warning message. Without renaming you links.



Luigi

[Ionut Grigorescu_2]

Dear all.

thank you for your answers. I have allready used -x inc_entire=vg00 option. The problem is I cannot slap the person who wrote the Java application for he didn't know about pax limitations for sure (:-)). My question wasn't why did I get the warning but if the recovery will be satisfactory not taking into account the incriminated directory - that with the long path names