On 10/03/2007 02:20 PM, Dave wrote: > On 10/03/2007 05:00 AM, Jim Dunham wrote: >>> -bash-3.00# sndradm -E eq1-zfs1 /dev/rdsk/c1t0d0s4 /dev/rdsk/c1t0d0s5 >>> eq1-zfs2 /dev/rdsk/c1t0d0s4 /dev/rdsk/c1t0d0s5 ip syncEnable Remote >>> Mirror? (Y/N) [N]: Y >>> sndradm: Error: unable to access configuration >>> >> This statement is an indication the persistent configuration database >> has not been created. By default the AVS data services are SMF disabled, >> and no persistent configuration database exists. If the status of >> "dscfgadm -i" shows no database configured and no services running, just >> type "dscfgadm", and it will perform the first time configuration of AVS. > > Thanks, Jim. I figured this out a few hours after sending the email. > Unfortunately I still can't get sndradm to create the mirror: > > -bash-3.00# sndradm -nE eq1-zfs1 /dev/rdsk/c1t0d0s4 /dev/rdsk/c1t0d0s5 > eq1-zfs2 /dev/rdsk/c1t0d0s4 /dev/rdsk/c1t0d0s5 ip sync g zfs_shared > Remote Mirror: eq1-zfs1 /dev/rdsk/c1t0d0s4 /dev/rdsk/c1t0d0s5 eq1-zfs2 > /dev/rdsk/c1t0d0s4 /dev/rdsk/c1t0d0s5 > Remote Mirror: Error > SNDR: Unable to initialize the kernel thread set > > > Do I have to download the ON bits and NWS project bits to get AVS to > work? Or should a full install of nv_72 be all that I need? > > Should I have done anything else besides dscfgadm before attempting to > create the mirror with sndradm? >
Nevermind. Looks like the nws services weren't running on one of the servers. Looks like it works fine now. _______________________________________________ storage-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/storage-discuss
