carlopmart wrote:
Hi all,
I am doing some tests using AVS suite on OpenSolaris 2009.06 without
look. First, I will describe my deployment:
a) NodeA: OpenSolaris 2009.06 with two disks: one disks with os only
and another with data (96GB). All is installed on my laptop and
virtualized under vmware server 2.0.1
b) NodeB: OpenSolaris 2009.06 with two disks: one disks with os only
and another with data (96GB). All is installed under an ESX 4 host.
Ok, I need to sync some volumes created under this 96GB disk from
nodeA to nodeB, and here my problems starts.
On nodeA I have created a zfs pool like this: zpool create -f
datapool c9t0d0. Under this zpool I have created a 16GB volume to
use as iSCSI volume for another virtual machines. I need to sync
this volume to nodeB and now my questions:
a) How can I calculate bitmap for this zfs volume? Under AVS
documentation describes only how do this using disks partitions.
# dsbitmap -r /dev/zvol/rdsk/datapool/<16GB LUN name>
b) Can I use async mode to sync this volume??
Regardless of the replication type (asynchronous or synchronous), an
initial volume sync is always done synchronously.
Of course there is a way to avoid the 100% of the sync, and that is to
provision the ZVOL and its bitmap volume on the SNDR primary and
secondary nodes, then enable SNDR with "sndradm -E ...", meaning the
both ZVOLs are equal, as uninitialized data equals Uninitialized data.
Now enable these ZVOLs for use with vmware.
c) And what success when node primary is rebooted?? How can I
restablish sync with nodeb?? This situation will appears every day
(remember, nodeA is my laptop).
AVS was designed from the ground up to recover after system reboots,
panics, link failures, etc. The ability to restablish sync with nodeb,
can be done manually "sndradm -m ...", or automatically "sndradm -
a ...".
I have tested this last point using disk partitons and all goes very
bad. I suffer a lot of errors and I can't restablish synchronization.
It would be helpful to know what type of errors, on what nodes, and
what data services are impacted.
Something worth noting. AVS, or more specifically SNDR is remote
mirroring software. This means that is when SNDR replication is
active, one can not access the SNDR secondary volume, as the on disk
metadata and data are changing.
Some doc or howto to accomplish this situation??
http://docs.sun.com/app/docs?p=coll%2FAVS4.0
- Jim
--
CL Martinez
carlopmart {at} gmail {d0t} com
_______________________________________________
storage-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/storage-discuss
_______________________________________________
storage-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/storage-discuss
