Snapmirror Relationship Schedules Are Not Modified For Existing Volumes; Corrections To The List Of Rsh And Ssh Commands; Corrections To The Snapvault Support On Vfiler Units - IBM N Series Manual

You can include the name of the hosting storage system as part of the vFiler
unit name so that you can easily determine the storage system that contains
the vFiler unit —for example, mycompanyss1_vfiler1.
v The name vFiler0 should not be used because it is the name of the default
vFiler unit.

SnapMirror relationship schedules are not modified for existing volumes

In Data ONTAP 8.0.2 and later releases, if you edit the SnapMirror
relationship schedules in the etc/snapmirror.conf file after executing the
vfiler dr configure command, the vfiler dr resync command does not
modify the SnapMirror relationship schedules for the existing volumes.
For example, if you change the SnapMirror relationship schedule from
asynchronous to semi-synchronous after executing the vfiler dr configure
command, the vfiler dr resync command does not modify the SnapMirror
relationship schedule from semi-synchronous to asynchronous during
resynchronization of the vFiler unit.

Corrections to the List of RSH and SSH commands

"List of RSH and SSH commands" topic lists some commands that are not
supported in Data ONTAP 8.0 and later releases.
The following commands, which are listed in the Data ONTAP 8.0 7-Mode
MultiStore Management Guide, are not supported in Data ONTAP 8.0 and later
releases:
cifs
config
df
dns
echo
fpolicy
nbtstat
nfs
nis
route
sectrace

Corrections to the SnapVault support on vFiler units

The sections "Where to enter SnapVault commands" and "Features and
limitations of the snapvault command" have some incorrect information about
interoperability between SnapVault and MultiStore.
snap
snapmirror
snapvault
vol
vscan
wcc
ypcat
ypgroup
ypmatch
ypwhich
Changes to published documentation
145