CA VM:Backup restores all base files before it restores any alias files. This restore order ensures that the base files are in place before the aliases are created. When a base file is restored to an alternate file space, the files restored are considered "copies" of the base file. If an alias was present in the original base file, it is not restored to the alternate file space unless the owner of the base file gave the alternate file space alias authorization to that file. If the original file space had a base file that had given another file space alias authority, the base file would be restored to the alternate filespace, but the alias authorization would not exist between the alternate and other file space.
The alias is not created if the base file no longer exists, or if the authorization to the base file was revoked before the restore. Aliases are created only if authorizations exist for the alternate file space over the base files in the original file space before the restore is completed. The restore job detail listing contains an entry for any aliases that are not restored.
Depending on the order in which user storage groups are restored and on whether there are any aliases that cross user storage group boundaries, you may experience inconsistent results when you restore an entire file pool through separate jobs submitted on a storage group by storage group basis. Therefore, if several user storage groups need to be restored for a particular file pool, you should perform a file pool restore that specifies the user storage groups you want to restore.
|
Copyright © 2014 CA Technologies.
All rights reserved.
|
|