Well, remember that with ARCHIVES, the owner is the user who creates
the archives... I believe this tidbit was on the list not long ago...
but with backups YES, I've seen this problem.... the GUI causes root
to become the owner of all directories and with the command line in
conjunction with the -pick option root also becomes the owner of all
directories...
It has been another person here looking into this here so I can't give
the exact syntax of what they have found that works.... I believe
everything has the proper ownership in the case of full restores.
NOTE: if you've started out with a full restore and used the GUI or
cmd line with the -pick and created the directory structure (which
will have the improper ownership) you'll need to blow it away and let
adsm rebuild it to gain the proper ownerships when you redo the
restore.... I do believe the 2.1.0.5 code helps cure this problem....
but I can't say for sure.... The person running the misc tests is
gone for the holidays..... :-)
later
Dwighht
______________________________ Reply Separator _________________________________
Subject: major glitch in AIX client
Author: ADSM-L (ADSM-L AT VM.MARIST DOT EDU) at unix,mime
Date: 12/19/96 7:49 PM
We just ran into a nasty little glitch in the AIX client for ADSM; has
anyone else hit it, and if so, how do you get around it?
Problem: do an archive of a mount point, with subdir=yes as root (because
there are multiple subdirectory owners within the mount point) -- then
delete the complete directory tree below the mount point. The retrieve will
create all subdirectories under the user-name used for the retrieve! The
same problem exists with backup/restore, except that there's a work-around
-- do the restore with the -subdir=yes option (this doesn't help in retrieve).
Suggestions? Ideas? We were planning on using ADSM for our SAP/R3 - Oracle
Suggestions? Ideas? We were planning on using ADSM for our SAP/R3 - Oracle
enviroments, but if I can't come up with a viable fix or work-around, we'll
have to look at other products.
BTW - I didn't catch the apar number today, but it was noted in the apar
that this was to have been fixed in 2.1, but the code changes were too
extensive.
Tom Kauffman
NIBCO, Inc.
|