Sun StorageTek[TM] Availability Suite 3.2: Missing Remote Mirror Sets After a Host Boot
Last updated on NOVEMBER 21, 2013
Applies to:Sun Storage Availability Suite - Version 3.0 and later
It is very common to be surprised when Remote Mirror does not show a set or sets configured after a system boot.
This usually happens when Remote Mirror is newly configured.
The symptoms after system booting are :
(a) Previously created Remote Mirror configuration is NOT shown by commands
"sndradm -i" or "sndradm -P"
(b) Conflicting Remote Mirror configuration information.
Although no Remote Mirror configuration is shown by command "sndradm -i", the configuration
database ( output of "dscfg -l" ) indicates that there is existing SNDR configuration.
# dscfg -l | grep sndr
sndr: pri-host /dev/md/rdsk/d0 /dev/md/rdsk/d2 sec-host /dev/md/rdsk/d0 /dev/md/rdsk/d2 ip sync - - setid=1; - dsvol: /dev/md/rdsk/d0 - sndr dsvol: /dev/md/rdsk/d2 - sndr
(c) Attempts to delete and then enable the set fail.
DISABLING ( sndradm -d ):
# sndradm -nd pri-host /dev/md/rdsk/d0 /dev/md/rdsk/d2 sec-host /dev/md/rdsk/d0 /dev/md/rdsk/d2 ip sync
RE-ENABLING ( sndradm -E ):
# sndradm -ne pri-host /dev/md/rdsk/d0 /dev/md/rdsk/d2 sec-host /dev/md/rdsk/d0 /dev/md/rdsk/d2 ip sync sndradm: Error: bitmap /dev/md/rdsk/d2 is already in use by StorEdge Network Data Replicator
Network hostname or name services reconfiguration; followed later by a system reboot.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms