erik.ableson said: "Just a quick comment for the send/recv operations, adding
-R makes it recursive so you only need one line to send the rpool and all
descendant filesystems. "
Yes, I know of the -R flag, but it doesn't seem to work with sending loose
snapshots to the backup pool. It obviously
> Just a quick comment for the send/recv operations, adding -R makes it
> recursive so you only need one line to send the rpool and all descendant
> filesystems.
Yes, I am aware of that, but it does not work when you are sending them loose
to an existing pool. Can't remember the error message b
Well I'm so impressed with zfs at the moment! I just got steps 5 and 6 (form my
last post) to work, and it works well. Not only does it send the increment over
to the backup drive, the latest increment/snapshot appears in the mounted
filesystem. In nautilus I can browse an exact copy of my PC, f
Thanks Edward, you understood me perfectly.
Your suggestion sounds very promising. I like the idea of letting the
installation CD set everything up, that way some hardware/drivers could
possibly be updated and yet it still work. On top of a bare metal recovery, I
would like to leverage the incr
Thanks Cindy for the links.
I see that this could possibly be a replacement for ufsbackup/ufsrestore but
unless a further snapshot can be appended to the file containing the recursive
rootpool snapshot, it would still regress from the incremental backup that
ufsbackup has. It would take a long
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
I created a clone from the most recent snapshot of a filesystem, the clone's
parent filesystem was the same as the snapshot itself. When I did a rollback to
a previous snapshot it erased my clone. Yes it was really stupid to keep the
colne on the same filesystem, I was tired and wasn't thinking
I accidentally ran 'zpool create -f' on the wrong drive. The previously zfs
formatted and populated drive now appears blank. The operation was too quick to
have formatted the drive so it must just be the indexes/TOC that are lost.
I have not touched the newly created filesystem at all and the dr
