- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Re: Backup does not create default ACL's
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-20-2006 03:36 AM
03-20-2006 03:36 AM
Backup does not create default ACL's
$ backup user19:[jones.data...] project0:[stemcell.data...]/by_owner=parent
will copy the files setting the owner to that of the parent directory (a resource ID in this case) however no default acl's will be created on the output files making them unusable. A second step is required to re-establish the security of the output files:
$ set security/default project0:[stemcell.data...]*.*;*
Which will propagate the default acl's down the directory. This has the negative side effect of setting all the revision dates to now. On ODS-2 volumes, using the /interchange backup qualifier would work around this issue. Now, with ODS-5 volumes, using /interchange IMPLIES /convert which is not the desired result. It would be very useful if backup had an option to create default acl's for the target files (i.e. NOT preserve the ACL's of the input files).
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-20-2006 03:56 AM
03-20-2006 03:56 AM
Re: Backup does not create default ACL's
Parhaps you could go to
http://www.hpuseradvocacy.org/
and submit a new issue.
Purely Personal Opinion
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-20-2006 03:59 AM
03-20-2006 03:59 AM
Re: Backup does not create default ACL's
1) one procedure which uses F$FILE_ATTRIBUTES to query the creation and revision date and store it together with the file name in a data file.
2) another procedure which reads that data file and uses the |FILE| utility to change the CDT and RDT back to its old values.
I very well understand that this hides changes to a (group of) file(s) and that the changes (e.g. modification of ownership, protection mask or ACL) is not shipped in the next incremental backup.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-20-2006 05:35 AM
03-20-2006 05:35 AM
Re: Backup does not create default ACL's
I believe you can use backup/interchange and /by_owner=parent as an output qualifier to do what you want. Backup/interchange does not save the input files' ACL. The output files will inherit default ACEes as you would expect. I seem to recall that the /by_owner=parent was necessary.
Bill
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-21-2006 03:11 AM
03-21-2006 03:11 AM
Re: Backup does not create default ACL's
(/interchange implies /convert)!
I'm going to open a support call on this.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-21-2006 03:55 AM
03-21-2006 03:55 AM
Re: Backup does not create default ACL's
This does work if you use an intermediate on-disk saveset.
$ backup user19:[jones.data...] saveset.bck/save
$ backup/interchange saveset.bck/save project0:[stemcell.data...]/by_owner=parent
Use the /interchange qualifier only on the restore of the saveset.