make_net_recovery problems

[Velda]

Dear all,
First basics : I have PARISC HPUX 11.23 machines.
I usually make OS backups on DAT tapes (of vg00 only) using make_tape_recovery command, and it works beautifully. No problem there.
BUT
I have two vpars which have no DAT access, and I thought to back up their vg00 with make_net_recovery command, and it did not work.
*********
Here is the sequence I used :
make_net_recovery -x inc_entire=vg00 -s my-ignite-server -a my-ignite-server:/location-on-ignite-server/my-client-HPUX
*********
And I got the following error message :
* Archiving contents of ds21d via tar to
/var/opt/ignite/recovery/arch_mnt/2009-09-07,11:39.

gzip: stdout: File too large
ERROR: The gzip command failed (exit status 1).

ERROR: The make_sys_image command failed. The system recovery archive will
not be created.
************
Now I looked up the used space for vg00 for both servers, and it is 19G and 27G. Used vg00 space on servers where I use make_tape_recovery is much bigger, and it is no problem.
Any ideas?

[Johnson Punniyalingam]

Hi ,

how about your Ignite Server got enough space ? to hold you ignite Client image while you perfrom the make_net_recovery ?

Example :-

My Ignite Server /var/opt/ingnite/recovery/archives.

/dev/vg00/lvol9 41943040 25813728 16003328 62% /var/opt/ignite/recovery/archives

Thanks,
Johnson

[Velda]

Dear Sir,
Thank you for the suggestion.
I will check, but I think it should be no problem, since free space on Ignite is 56G, and the user vg00 on vpar servers is 19G and 27G respectfully.

[Velda]

Hmm, tried again, and I closely followed the tar file that is the result of the make_net_recovery command.
The whole thing crashed when the resulting file was between 2-3G?????
There was more than ample space available on the location (more than 50G).

[Torsten. · Accepted solution]

Is the destination configured with "largefiles"?

[Velda]

YES!!!
Thank you, it is this problem.
And it got you 10 pts (would be more if I coud give you more) :-)))
*********
Now back to business :
I already have some files there (and it is a LVM FS). Also an entry in the /etc/fstab :
-------------------
/dev/vg_ignite/lvol_ignite1 /ignite_backup vxfs rw,suid,delaylog,datainlog 0 2
-------------------
Any URL with directions of turning this into FS fit for large files?

[Torsten.]

See

http://docs.hp.com/en/B3929-90011/ch01s16.html

...
You can switch capabilities on a mounted file system with the fsadm command:


# fsadm -F vxfs -o largefiles|nolargefiles mount_point

[Velda]

THNKS
If I understand it correctly with fsadm command I change it to "largefiles" online, but only until next restart.
If I want the state to be permanent, I have to change the /etc/fstab in something like this :
----------------
/dev/vg_ignite/lvol_ignite1 /ignite_backup vxfs rw,suid,largefiles,delaylog,datainlog 0 2
----------------
Please confirm, and onwards I go!
Just a little comment : I do not have online JFS... I think it does not matter, but a comment just in case...

[Dennis Handly]

>If I understand it correctly with fsadm command I change it to "largefiles" online, but only until next restart.

This is permanent.

>I do not have online JFS. I think it does not matter, but a comment just in case.

You don't need it.

[Velda]

Thank you!
I will do it at once.
If there are any problems (hope not!) I will post again, if not I will close the thread.
Best regards!