similar to: zfs scheduled replication script?

I have a backup system using zfs send/receive (I know there are pros and cons to that, but it''s suitable for what I need). What I have now is a script which runs daily, do zfs send, compress and write it to a file, then transfer it with ftp to a remote host. It does full backup every 1st, and do incremental (with 1st as reference) after that. It works, but not quite resource-effective

Fairly new to ZFS. I am looking to replicate data between two thumper boxes. Found quite a few articles about using zfs incremental snapshot send/receive. Just a cheeky question to see if anyone has anything working in a live environment and are happy to share the scripts, save me reinventing the wheel. thanks in advance. -- This message posted from opensolaris.org

Anyone have any creative solutions for near-synchronous replication between 2 ZFS hosts? Near-synchronous, meaning RPO X--->0 I realize performance will take a hit. Thanks, Mike -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.opensolaris.org/pipermail/zfs-discuss/attachments/20091026/765672c8/attachment.html>

Hi, I have two servers running: freebsd with a zpool v28 and a nexenta (opensolaris b134) running zpool v26. Replication (with zfs send/receive) from the nexenta box to the freebsd works fine, but I have a problem accessing my replicated volume. When I''m typing and autocomplete with tab key the command cd /remotepool/us (for /remotepool/users) I get a panic. check the panic @

Sorry for double-post. This thread was posted separately to opensolaris-help and zfs-discuss. So I''m replying to both lists. > I''m wondering what the possibilities of two-way replication are for a > ZFS storage pool. Based on all the description you gave, I wouldn''t call this two-way replication. Because two-way replication implies changes are happening at

All; I have a question about ZFS and how it protects data integrity in the context of a replication scenario. First, ZFS is designed such that all data on disk is in a consistent state. Likewise, all data in a ZFS snapshot on disk is in a consistent state. Further, ZFS, by virtue of its 256 bit checksums is capable of finding and repairing data corruption should it occur. In the case of a

Hi all, I''ll attach a new version zfs-auto-snapshot including some more improvements, and probably some new bugs. Seriously, I have tested it, but certainly not all functionality, so please let me know about any (new) problems you come across. Except from the change log: - Added support to schedule using at(1), see README.zfs-auto-snapshot.txt - take_snapshot will only run if

Hello; Dedup on ZFS is an absolutely wonderful feature! Is there a way to conduct dedup replication across boxes from one dedup ZFS data set to another? Warmest Regards Steven Sim

We are going to be migrating to a new EMC frame using Open Replicator. ZFS is sitting on volumes that are running MPXIO. So the controller number/disk number is going to change when we reboot the server. I would like to konw if anyone has done this and will the zfs filesystems "just work" and find the new disk id numbers when we go to zfs import the pool. Our process would be: zfs

I haven''t seen any mention of it in this forum yet, so FWIW you might be interested in the details of ZFS deduplication mentioned in this recently-filed case. Case log: http://arc.opensolaris.org/caselog/PSARC/2009/571/ Discussion: http://www.opensolaris.org/jive/thread.jspa?threadID=115507 Very nice -- I like the interaction with "copies", and (like a few others) I think

Hi, I may have lost my first zpool, due to ... well, we''re not yet sure. The ''zpool import tank'' causes a panic -- one which I''m not even able to capture via savecore. I''m glad this happened when it did. At home I am in the process of moving all my data from a Linux NFS server to OpenSolaris. It''s something I''d been meaning to do

Hello list, I started playing aroud with Comstar in snv_134. In snv_116 version of ZFS, a new hidden property for the Comstar MetaData has been intoduced (stmf_sbd_lu). This makes it possible to migrate from legacy (iscsi target daemon) to Comstar without data loss, which is great. Before this property you always lost the first 64k of your zvol data where comstar wrote it''s metadata -

This zfs looks great! I really hope this gets put into solaris soon since I don''t think I could live with Solaris express on a production machine. The easy of adding disk and moving directories looks like a life saver, especially for me who deals with trying to store digital media which piles up a couple of gig a day! This message posted from opensolaris.org

Hi Derek, Here''s the latest email I''ve received from the zfs-discuss alias. ------------- Begin Forwarded Message ------------- Date: Mon, 18 Sep 2006 23:55:27 -0400 From: Jonathan Edwards <Jonathan.Edwards@sun.com> Subject: Re: [zfs-discuss] ZFS and HDS ShadowImage To: Eric Schrock <eric.schrock@sun.com> Cc: zfs-discuss@opensolaris.org, Torrey McMahon

I have created a pool on external storage with B114. Then I export this pool and import it on another system with B110.But this import will fail and show error: cannot import ''tpool'': pool is formatted using a newer ZFS version. Any big change in ZFS with B114 leads to this compatibility issue? Thanks Zhihui -------------- next part -------------- An HTML attachment was

It was rumored that Nevada build 105 would have ZFS encrypted file systems integrated into the main source. In reviewing the Change logs (URL''s below) I did not see anything mentioned that this had come to pass. Its going to be another week before I have a chance to play with b105. Does anyone know specifically if b105 has ZFS encryption? Thanks, Jerry -------- Original Message

Hi everyone, Please review the information below regarding access to ZFS version information. Let me know if you have questions. Thanks, Cindy CR 6898657: http://bugs.opensolaris.org/bugdatabase/view_bug.do?bug_id=6898657 ZFS commands zpool upgrade -v and zfs upgrade -v refer to URLs that are no longer redirected to the correct location after April 30, 2010. Description The

It was rumored that Nevada build 105 would have ZFS encrypted file systems integrated into the main source. In reviewing the Change logs (URL''s below) I did not see anything mentioned that this had come to pass. Its going to be another week before I have a chance to play with b105. Does anyone know specifically if b105 has ZFS encryption? Thanks, Jerry -------- Original Message

I believe concerns like this should go to you? Bev. -------- Original Message -------- Subject: [zfs-discuss] zfs discussion forum bug Date: Sat, 29 Jul 2006 00:03:13 -0700 (PDT) From: Andrew <andrewee2@yahoo.com> To: zfs-discuss@opensolaris.org I started three new threads recently, "Feature proposal: differential pools" "Feature proposal: trashcan via auto-snapshot with

We''ve been experimenting with zfs on OpenSolaris 2008.11. We created a pool in OpenSolaris and filled it with data. Then we wanted to move it to a production Solaris 10 machine (generic_137138_09) so I "zpool exported" in OpenSolaris, moved the storage, and "zpool imported" in Solaris 10. We got: Cannot import ''deadpool'': pool is formatted