Table 1. vFiler unit support with SnapVault secondary volumes for different
combinations (continued)
Management of SnapVault
secondary volume Ownership of SnapVault secondary volume
Default vFiler unit (vfiler0) Yes Yes
Non-default vFiler unit No No
The management of SnapVault primary in a vfiler context is supported.
Table 2. vFiler unit support with SnapVault primary volumes for different combinations
Management of SnapVault
primary volume Ownership of SnapVault primary volume
Default vFiler unit
(vFiler0)
Non-default vFiler unit
Default vFiler unit (vFiler0) Yes Yes
Non-default vFiler unit No Yes
(From a non-default
vFiler context, you can
only manage volumes
owned by that
non-default vFiler unit.)
DataFabric Manager server support for the management of
SnapVault relationships
DataFabric Manager server supports the management of SnapVault
relationships for volumes through the default vFiler (vFiler0) context only.
When using DataFabric Manager server, the following limitations apply for
SnapVault relationships involving non-default vFiler units.
v You can only view SnapVault relationships configured through the default
vFiler unit (vfiler0). You cannot view any SnapVault relationships
configured through non-default vFiler units.
v You can configure new SnapVault relationships for a volume only through
the default vFiler unit (vfiler0), even if the volume belongs to a non-default
vFiler unit.
Restore engine does not honor any mandatory or advisory locks on files
The destination volume for a restore operation might have files with
mandatory or advisory locks. When you initiate a restore operation to such a
volume, the restore engine does not honor these locks. It ignores these locks
and overwrites the files.
108 IBM System Storage N series: Data ONTAP 8.0.4 7-Mode Release Notes
To Next Page
Loading...
Need help?
General