And herein lies the main clue. It seems Solaris, like FreeBSD, has the same
lack-of-backup-options for zfs (dump doesn't work), unless you have a secondary
server with at least the same amount of diskspace, running UFS, and willing to
cache zfs sends on that ufs for writing those to the tape.
Replying to my own post (isn't that a sure indicator of insanity starting or
something?)
What are the chances the next Opensolaris x86/x64 livecd including the
statically compiled bacula (or other) binaries allowing the use of that for
disaster-recovery from a backup?
//Svein
--
This message
Svein Skogen wrote:
And herein lies the main clue. It seems Solaris, like FreeBSD, has the same
lack-of-backup-options for zfs (dump doesn't work), unless you have a secondary
server with at least the same amount of diskspace, running UFS, and willing to
cache zfs sends on that ufs for
And again ...
Is there any work on an upgrade of zfs send/receive to handle resuming on next
media?
I was thinking something along the lines of zfs send (when device goes full)
returning
send suspended. To resume insert new media and issue zfs resume IDNUMBER
and receive handling:
zfs
hmmm I guess I have to give amanda another look. I'm on SVN133 (since the yge
driver is present there and not in the older release, and all four NICs on my
server are Marvell 88e8056 yukon chips and I really want dladm to work). Yet
another chicken-and-egg situation...
Does the amanda packages
a number of apps support zfs extended attributes, but not many support backup
up snapshots in a format that can be *easily* recovered (ie - as a regular
snapshot of a filesystem). hopefully this will change in the future ;-)
if you want to backup snapshot too, then perhaps something like:
Is there any work on an upgrade of zfs send/receive to handle resuming
on next media?
See Darren's post, regarding mkfifo. The purpose is to enable you to use
normal backup tools that support changing tapes, to backup your zfs send
to multiple split tapes. I wonder though - During a restore,
I'm falling back to a rather similar solution, but on a different approach.
The FreeBSD istgt daemon can share targets from files, not zvols, and since
it has a plain ascii config file, if I do things less fancy, and use a flat
/storage (for the storage zpool) with subdirectories, that can be
Until now, I've ran Windows Storage server 2008, but the ... lack of iSCSI
performance has gotten me so fed up that I've now moved all the files off the
server, to install opensolaris with two zpools, and nfs+smb+iSCSI sharing
towards my windows clients, and vmware ESXi boxes (two of them). So
Storage that large you might want to consider using backup packages like Bacula
or Amanda. Both should support your changer/LTO3 drive setup.
I believe both package have bare metal restore capability.
I've mostly used bacula with Solaris/Linux/BSD and Amanda is pretty common as
well.
-Rob
--
Is getting bacula up and running a non-trivial task on Opensolaris, and how
would I go about disaster-recovery and getting the zvol's down to tape? (So I
don't have to recreate the vmware solution that handles my mail and webservers
today)
//Svein
--
This message posted from opensolaris.org
On Wed, 2010-03-03 at 11:16 -0800, Svein Skogen wrote:
Is getting bacula up and running a non-trivial task on Opensolaris, and how
would I go about disaster-recovery and getting the zvol's down to tape? (So I
don't have to recreate the vmware solution that handles my mail and
webservers
The disaster-recovery-aspect is what made me ask questions in the first place.
Knowing myself, in a recovery situation (usually due to my own mistakes rather
than natural disasters), I would be on the edge of sanity stress-wise, and a
disaster-recovery-method of reinstalling entire os,
to a real solution. I need something that on regular intervals pushes
this zpool:
storage 4.06T 1.19T 2.87T29% 1.00x ONLINE -
onto a series of tapes, and I really want a solution that allows me to
If you need to write onto a series of tapes, you basically need Amanda, or
The disaster-recovery-aspect is what made me ask questions in the first
This is one of the reasons I like the solution I just wrote in the other
email. The OS itself has nothing special installed on it at all. In a
disaster recovery, I simply perform a vanilla installation of solaris, and
then
15 matches
Mail list logo
