Veritas Storage Foundation Release Notes

70
Storage Foundation Release Notes
Known issues
Workaround
If you have not done authentication setup, set umask to a less strict value before
running the sfae_auth_op -o setup or sfae_auth_op -o import_broker_config
commands.
To set umask to a less strict value
◆
Use the command:
# umask 022
If you have already done authentication setup, perform the following steps.
To resolve the problem if you have already done authentication setup
1 Shut down the authentication broker, if it is running.
# /opt/VRTSdbed/at-broker/bin/sfaeatd.sh stop
2 Change the permissions for files and directories that are required to be
readable by non-root users.
# chmod o+r /etc/vx/vxdbed/admin.properties
# chmod o+rx /var/vx/vxdba/auth/users
# find /opt/VRTSdbed/at-broker -type d -exec chmod o+rx {} \;
Clone operation failure might leave clone database in
unexpected state (2512664)
If the clone operation fails, it may leave the clone database in an unexpected state.
Retrying the clone operation might not work.
Workaround
If retrying does not work, perform one the following actions depending on the
point-in-time copy method you are using:
■
■
■
For FlashSnap, resync the snapshot and try the clone operation again.
For FileSnap and Database Storage Checkpoints, destroy the clone and create
the clone again.
For space-optimized snapshots, destroy the snapshot and create a new
snapshot.
Contact Symantec support if retrying using the workaround does not succeed.