make_tape_recovery:Link name is longer than 100 chars.

[DrWatson_1]

the make_tape_recovery retourn error: pax :file-name Link name is longer than 100 chars.
the backup is good ?
thanks for support

[V. Nyga]

Hi,

I don't think so!
But maybe you can give us the whole make_tape_recovery log?

Volkmar

[DrWatson_1]

ok.
this is the make_tape_recovery log.
thanks for support

[Dennis Handly]

The backup should be fine, as long as you don't care about those 6 files with long links.

pax(1) says they are not stored.
Here are some other links about this:
http://forums.itrc.hp.com/service/forums/questionanswer.do?threadId=221640
http://forums.itrc.hp.com/service/forums/questionanswer.do?threadId=964027
http://forums.itrc.hp.com/service/forums/questionanswer.do?threadId=1043934

[V. Nyga]

Hi again,

the backup should work.
If you need these files, I would put it into a tar file and extract it after ignite installation.

Also you should think about if you need /QoSManData and /QoSManager in your ignite configuration, it's not os related.
Normally you should backup it with fbackup or similar.

HTH
Volkmar

[DrWatson_1]

the tar command retourn link too long.
how to use fbackup ?
use fbackup in place of tar......
thanks for support

[Steven Schweda]

> the tar command retourn link too long.

Which "tar" command?

As the thread in one of those previously
cited links suggests, GNU "tar" extends the
original "tar" format to accomodate file
names longer than 100 characters. I don't
know if "pax" does or not. Of course, when
you don't reveal your OS version or patch
status, it's hard to know what you should
expect from "pax".

Naturally, if you need a "tar" program better
than the one HP supplies when you create the
thing, then you'll also need it when you
restore the thing.

[TTr]

I would not mess with any gnutar or anything else. The fact is that you have what you have on the OS whose image you created on the ignite tape and you should stick with it.

The tape is still good and will recover and ignite a new server. However the new server will NOT have those links. You can print a listing of those links from the OLD OS and create them manually on the NEW OS after you use the ignite tape.

[Steven Schweda]

> I would not mess with any gnutar or
> anything else. [...]

> You can print a listing [...]

I would not mess with printing a listing, and
creating anything manually. Obviously, the
approach to choose depends on what you call a
mess.

You could dump the whole disk to paper, too.

[TTr]

> I would not mess with printing a
> listing, and creating anything manually.
> Obviously, the approach to choose
> depends on what you call a mess.

> You could dump the whole disk to paper, too.

I don't know what kind of environment you live in but if it is a strick validated environment (SEC, FDA) you have to use what you 've got and can not install any gnutar etc. A better suggestion would have been to upgrade and patch the OS to the latest HP-UX 11iv3 so that tar does not spit out those errors. Printing 6 lines to a piece of paper and attaching that to the ignite tape is NOT the same as dumping the whole disk to paper

[V. Nyga]

Hi again,

'man fbackup' or use 'sam' - 'backup and recovery' section. There is fbackup used.

The question is if it's a link or the file itself, where the path is too long!
Or should he print the file? ;-)

Volkmar

[Steven Schweda]

> I don't know what kind of environment you
> live in [...]

Cold, generally, except in summer, but who
cares? My environment and your environment
may have little to do with the environment of
the fellow with the long file names.

> A better suggestion [...]

Perhaps the fellow with the problem is in one
of those restrictive environments where such
upgrades/updates are not allowed. Certainly,
little is known about it from the information
provided, but you're free to assume what you
wish about its "strickness".