rtaylor@tron.UUCP (Randy Taylor) (01/03/91)
Problems, problems, problems !!!
Here's a nice OmniBack problem (with solution).
Recently, I used OmniBack (v1.2) to 'snapshot' some data on one of my machines
prior to upgrading it to SR10.3. After INVOL'ing, I restored the data. The
data was ACL'ed pretty heavily, i.e. subtree access was limited to specific
users and groups with little or no world access.
The data restored *without* the original ACLs. I had to write ACL scripts
for about 250 Mb of data - with several hours of script execution time, it
cost my company some serious $'s while access was restored.
I contacted Apollo and found out this :
1) Use the -merge_source option when restoring data even if the source does
not exist to restore all the ACLs (this trick is *not* pointed out in the
manual, according to Apollo).
2) After running nbsrestore, the top dir ACLs will not be correct, but all
subtrees and files will have proper ACLs. Just re-ACL the top tree and
you'll be done.
If you know in advance what will be restored, you can create and ACL the
top trees and run with (1) above and all the ACLs will be set properly.
BTW - I tried to get an APR to fix this problem, but no soap. Apollo
(ahem ! HP/Apollo, thank you) seems to believe this ACL ambiguity with
OmniBack software is acceptable.
Why am I not surprised ? :-)
Randy Taylor
Westinghouse Electric Corp.
*My opinions in no way reflect those of Westinghouse Electric Corp.*
(CYA boys and girls !)
--
rtaylor@sky00.bwi.wec.com from an Internet site (preferred)
rtaylor@tron.bwi.wec.com from an Internet site (alternate)
"...you know I have the greatest enthusiam for the mission." HAL 9000