Hi,
I know this possibility, but our initiator clients are linux and thus
there is no zfs available. I made some tests with mdadm, but this is not
ready jet.
Best regards
Florian
On 09/03/2012 11:06 AM, Andrej Javoršek wrote:
Hello,
slightly off-topic... ...but I'm exporting LUN from each COMSTAR server and
combine them on initiator server as ZFS mirror. That way I'm getting
active-active fail-over with "automatic" replication.
Regards
Andrej
On Sun, Sep 2, 2012 at 5:01 PM, Florian <flor...@acw.at> wrote:
Hi,
I do this.
This is my zfs send receie command:
zfs send -R tank/raid1-0@20120831-2017 | ssh backup@192.168.10.201"/usr/sbin/zfs
receive -Fduv tank/backup_raid"
/man zfs (send):
-p
Include the dataset's properties in the stream.
This flag is implicit when -R is specified. The
receiving system must also support this feature./
Best regards
Florian
Am 02.09.2012 14:54, schrieb Mike La Spina:
I suspect you need to include the zfs properties with your zfs send, -p
will provide them.
Regards,
Mike
http://blog.laspina.ca
-----Original Message-----
From: Florian [mailto:flor...@acw.at]
Sent: Sunday, September 02, 2012 6:40 AM
To: openindiana-discuss@**openindiana.org<openindiana-discuss@openindiana.org>
Subject: [OpenIndiana-discuss] COMSTAR iSCSI fail-over
Hello,
I have one another question.
We use two equal OI Server with COMSTAR iSCSI devices and we want to
backup them.
I backup them with zfs send and receive to each other in a backup
directory.
Has anyone experience with such a setup and how could I get the best
disaster recovery with this combination?
My big problem is, that I can't import a received LU. I get the
following error:
/Error importing stmfadm: meta file error/
With /zfs get stmf_sbd_lu property tank/backup_raid/raid1-0 /I get the
same data like on the sending side, only source is different.
How can I send the meta file, too?
Is there an other method to import the LU or do I need to create new LU
with the received block devices?
Best regards
Florian
______________________________**_________________
OpenIndiana-discuss mailing list
OpenIndiana-discuss@**openindiana.org<OpenIndiana-discuss@openindiana.org>
http://openindiana.org/**mailman/listinfo/openindiana-**discuss<http://openindiana.org/mailman/listinfo/openindiana-discuss>
______________________________**_________________
OpenIndiana-discuss mailing list
OpenIndiana-discuss@**openindiana.org<OpenIndiana-discuss@openindiana.org>
http://openindiana.org/**mailman/listinfo/openindiana-**discuss<http://openindiana.org/mailman/listinfo/openindiana-discuss>
______________________________**_________________
OpenIndiana-discuss mailing list
OpenIndiana-discuss@**openindiana.org<OpenIndiana-discuss@openindiana.org>
http://openindiana.org/**mailman/listinfo/openindiana-**discuss<http://openindiana.org/mailman/listinfo/openindiana-discuss>
_______________________________________________
OpenIndiana-discuss mailing list
OpenIndiana-discuss@openindiana.org
http://openindiana.org/mailman/listinfo/openindiana-discuss
_______________________________________________
OpenIndiana-discuss mailing list
OpenIndiana-discuss@openindiana.org
http://openindiana.org/mailman/listinfo/openindiana-discuss
