1826496 Members
2812 Online
109692 Solutions
New Discussion

Pax errors with Ignite

 
NPD USER
Regular Advisor

Pax errors with Ignite

I'm am receiving the following error when I perform a network recovery backup with Ignite:

pax:/var/tmp/pax_test: Optional ACL entries are not backed up.

It tells me to install the latest pax patch which I have done already. If I bypass this, then I receive this error:

WARNING: The pax command returned a non-zero exit status (exit status 1)

Do I need to install more patches other than the pax patch and it's dependencies?
4 REPLIES 4
Sridhar Bhaskarla
Honored Contributor

Re: Pax errors with Ignite

Hi,

The following document suggests that you install an additonal dependency patch for pax.

http://www2.itrc.hp.com/service/cki/docDisplay.do?docLocale=en_US&docId=200000062767698

It says PHKL_19991 but I am sure it might have been superceded atleast twice by now. Search for it in the patches section of itrc.

-Sri

You may be disappointed if you fail, but you are doomed if you don't try
S.K. Chan
Honored Contributor

Re: Pax errors with Ignite

Did you install the latest pax cumulative patches plus its dependencies ? For example S800 11.0 ..
PHCO_25418 => pax cumulative
which needs dependency patch ..
-> PHKL_22677 => fixes mmap & I/O coherency
--> which needs dependency patch ..
---> PHKL_18543 => PM/VM/async ..
and so on. For my case I stopped after PHKL_22677 because I already have PHKL_18543 loaded.
Eileen Millen
Trusted Contributor

Re: Pax errors with Ignite

I think we get this message about NFS mounted file systems. They should'nt be archived anyway. If that is the case, you could just stop the automounter during the archive.

Which OS version is this on and what version of Ignite?

Eileen
NPD USER
Regular Advisor

Re: Pax errors with Ignite

Thanks.. I have the latest pax patch (PHCO_25418) installed but I don't have the latest dependency patch installed. I currently have PHKL_19991 and PHKL_18543 installed. I'll install patch PHKL_22677 (which supersedes PHKL_19991) and see if that resolves the problem.

Thanks,
Scott