similar to: How to use mbuffer with zfs send/recv

Dear all, given a DVD drive and DAT Tape Drive, and using Solaris 10 U7 (5/09), how can we plan for a total backup of ZFS root disk and procedure to recover that? Previously using UFS, we just need to use boot from Solaris OS DVD media, also using ufsdump, ufsrestore and installboot. Anybody can point me on how to achieve the same thing when the whole system disk are busted? Thanks in

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hi, On 10/2/20 4:59 am, Francis Augusto Medeiros-Logeay wrote: > What I do: > > 1 - I ran a maildirlock command to my mail folder 2 - I then rsync > the folder where my maildirs are, as well as the indexes, to a > remote location If rsync is not fast... then how about doing a snapshot and then rsync off the snapshot? (I do rsync

I looked into backing up ZFS and quite honostly I can''t say I am convinced about its usefullness here when compared to the traditional ufsdump/restore. While snapshots are nice they can never substitute offline backups. And although you can keep quite some snapshots lying about it will consume diskspace, one of the reasons why people also keep offline backups. However, while you can make

Apologies up front for failing to find related posts... Am I overlooking a way to get ''zfs send -i fs at 0 fs at 1 | zfs receive -n -v ...'' to show the contents of the stream? I''m looking for the equivalent of ufsdump 1f - fs ... | ufsrestore tv - . I''m hoping that this might be a faster way than using ''find fs -newer ...'' to learn

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 hi, i have two systems, A (Solaris 10 update 5) and B (Solaris 10 update 6). i''m using ''zfs send -i'' to replicate changes on A to B. however, the ''zfs recv'' on B is running extremely slowly. if i run the zfs send on A and redirect output to a file, it sends at 2MB/sec. but when i use ''zfs send

In the process of tar''ing up files in an older ZFS partition (23.6.2005), the tar command seized up. Truss showed it hanging in stat64(), so I went looking for symptoms. In "zpool status -ve", I found "4" in the SUM column. Being from the old school, I did "dmesg", expecting to see some kernel error message about the disk but found nothing. Is there

I know i''m probably doing something REALLY stupid.....but for some reason i can''t get send/recv to work over ssh. I just built a new media server and i''d like to move a few filesystem from my old server to my new server but for some reason i keep getting strange errors... At first i''d see something like this: pfexec: can''t get real path of

On Wed 07/01/09 20:31 , Carsten Aulbert carsten.aulbert at aei.mpg.de sent: > Brent Jones wrote: > > > > Using mbuffer can speed it up dramatically, but > > this seems like a hack> without addressing a real problem with zfs > > send/recv.> Trying to send any meaningful sized snapshots > > from say an X4540 takes> up to 24 hours, for as little as 300GB

Using build 70, I followed the zfsboot instructions at http:// www.opensolaris.org/os/community/zfs/boot/zfsboot-manual/ to the letter. I tried first with a mirror zfsroot, when I try to boot to zfsboot the screen is flooded with "init(1M) exited on fatal signal 9" Than I tried with a simple zfs pool (not mirrored) and it just reboots right away. If I try to setup grub

After looking through the archives I haven''t been able to assess the reliability of a backup procedure which employs zfs send and recv. Currently I''m attempting to create a script that will allow me to write a zfs stream to a tape via tar like below. # zfs send -R pool at something | tar -c > /dev/tape I''m primarily concerned with in the possibility

Hi all, We are having some problems getting a solaris 9(sparc) file server running samba 2.2.2 to authenticate aginst a windows NT 4 PDC. Let me say first that this was all working at one time, then we had some data corrumption on our NFS mounted /usr/local, and had to restore from tape. Due to some issues with solaris ufsdump and ufsrestore, stuff was not quite put back properly. We do

I''m looking for a way to backup my entire system, the rpool zfs pool to an external HDD so that it can be recovered in full if the internal HDD fails. Previously with Solaris 10 using UFS I would use ufsdump and ufsrestore, which worked so well, I was very confident with it. Now ZFS doesn''t have an exact replacement of this so I need to find a best practice to replace it.

If I were to lose my main hard drive, I would like to have the opportunity to do the same as I can do using Windows: restore from my USB and have a working system. If I were to rsync everything on the main drive (excluding the backup drive, of course and a few other directories) to my USB drive, could I restore using some CD based version of Linux e.g. Knoppix? Todd -- Ariste Software 2200

I''ve tried ssh blowfish and scp arcfour. both are CPU limited long before the 10g link is. I''vw also tried mbuffer, but I get broken pipe errors part way through the transfer. I''m open to ideas for faster ways to to either zfs send directly or through a compressed file of the zfs send output. For the moment I; zfs send > pigz scp arcfour the file gz file to the

Assuming in a secure and trusted env, we want to get the maximum transfer speed without the overhead from ssh. Thanks. Fred -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.opensolaris.org/pipermail/zfs-discuss/attachments/20121213/654f543f/attachment-0001.html>

Hello, Was thinking it would be wise to backup my server, in case anything "bad" ever happened, so that I could quickly get up to speed. 1. clone the whole drive -- which might be the best to ensure I keep the whole system working. 2. But, what about, if I just wanted to backup my Email server components? Postfix - which I think is just config files, and Dovecot - I think there is a

Hi folks, I''m having (as the title suggests) a problem with zfs send/receive. Command line is like this : pfexec zfs send -Rp tank/tsm@snapshot | ssh remotehost pfexec zfs recv -v -F -d tank This works like a charm as long as the snapshot is small enough. When it gets too big (meaning somewhere between 17G and 900G), I get ssh errors (can''t read from remote host). I tried

It seems we are hitting a boundary with zfs send/receive over a network link (10Gb/s). We can see peak values of up to 150MB/s, but on average about 40-50MB/s are replicated. This is far away from the bandwidth that a 10Gb link can offer. Is it possible, that ZFS is giving replication a too low priority/throttling it too much?

Hello I''ve set up a simple system. It seems to work for a short while, but now I''ve got batches of 100''s of these messages. Also I can''t connect through that box any more. It''s as if forwarding died. Has anyone any advice? Regards John

Does anyone have a solution for the problem of file and directory names containing characters which are OK in DOS/Windows but illegal (or at least unwise) in Unix? I have Windows clients who have written directory names containing "$" characters to Samba shares on a Solaris box. This is fine for the clients, but plays havoc with Solaris programs needing to access the files, eg. backups