ACL errors on ignite image

[Rick Elliott]

As part of our patching process we take an ignite image of the server prior to the patching. On two of our servers we have got the following warning when taking the recovery image.

pax:optional ACL's are not backed up.
Warning: the pax command returned a non-zero status

From what I know about ACL's these are simply references and should not effect the validity of the image. I do not have a server to test the image on, so was hoping if anyone could give any advice.

[Ray Brewer]

We have run into this situation before. Your Image should be fine. As the message states the ACL information is not backed up so if you need to use this image to restore the system you will have to manually reset any ACL's that have been configured. If I remember right there is a note in the Ignite documentation that explains this.

[Wodisch · Accepted solution]

Hi,

"pax" is the tool used to create the archive (prior to compression) and it does not support ACLs. So what you could do is to write a script to "find" all files having set ACLs, collect the additional ACL entries (via "getacl" or "lsacl" depending wether your filesystem is VxFS3.3 or HFS), inlude that script's output/result in your "golden image", and start another script at the end of your restoration of the image. That second script would use the data from the output/result of the first script to set those ACLs again (via "setacl" or "chacl").

HTH,
Wodisch

[Rick Elliott]

Thanks for the help, the only question I do have is how are these ACL's created. The reason I say this is that we generally have a standard build and the majority of our servers obviously do not have them. The only filesystem that could possibly have them on our systems is /stand and I'm just interested as to why they would be there.