-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 08.03.2010 13:55, Erik Trimble wrote:
> Svein Skogen wrote:
>> Let's say for a moment I should go for this solution, with the rpool
>> tucked away on an usb-stick in the same case as the LTO-3 tapes it
>> "matches" timelinewise (I'm using HP C8017A  kits) as a zfs send -R to
>> a file on the USB stick. (If, and that's a big if, I get amanda or
>> bacula to do a job I'm comfortable with that has been verified. Not a
>> stab at those software projects, more a stab at them being an unknown
>> entity for me), how would I go about restoring:
>>
>> a) the boot record
>> b) the rpool (and making it actually bootable off the usb stick)
>> c) the storage zpool (probably after I get the system back up after a
>> and b, but please humor me).
>>
>> Reason I'm coming back here, is ... well the performance with Linux
>> (that I actually have software for which I'm comfortable with) wasn't
>> quite what I've grown used to with FreeBSD and Solaris.
>>
>> //Svein
>>   
> Assume your machine has died the True Death, and you are starting with
> new disks (and, at least a similar hardware setup).
> 
> I'm going to assume that you named the original snapshot
> 'rpool/ROOT/whate...@today'
> 
> (1)   Boot off the OpenSolaris LiveCD
> 
> (2)   Do a basic install, using whichever disk you intend to be the new
> root.
> 
> (3)   Reboot to your new "virgin" system
> 
> (4)   Mount the USB stick
> 
> (5)   Make a new Boot Environment to do the restore into:         #
> beadm create New
> 
>      - there should now be a zfs filesystem named 'rpool/ROOT/New'
> 
> (5)   Do a 'zfs receive', using the stream stored on the USB stick, and
> the destination the rpool. You should likely need to rename the incoming
> snapshot.        # cat <usb_mounted_stream> | zfs receive rpool/ROOT/myroot
> 
> (6)   A 'zfs list -t all -r rpool' will now show use the
> 'rpool/ROOT/myr...@today' snapshot and 'rpool/ROOT/myroot' filesystem
> 
> (7)   Make sure the mountpoint is /               # zfs set mountpoint=/
> rpool/ROOT/myroot
> 
> (8)   Destroy the restored snapshot:            # zfs destroy
> rpool/ROOT/myr...@today
> 
> (9)   Replace your "New" filesystem with the restored one:
>        # zfs rename rpool/ROOT/New rpool/ROOT/Old
>        # zfs rename rpool/ROOT/myroot rpool/ROOT/New
>        # zfs destroy rpool/ROOT/Old
> 
> (10)  Activate the restored BE:
>        # beadm activate New
> 
> 
> You should now be all set.   Note:  I have not /explicitly/ tried the
> above - I should go do that now to see what happens.  :-)
> 
> 
> Restoring the data pool is dirt simple.  Create your zpool, and simply
> 'zfs receive' from the tapes you have. Likely, it's easier to install
> Amanda (or whatever backup program you're using) and have it do the
> restore/tape management for you.
> 
> 
> 
> 

Thank you for taking the time to explain this to me, I finally feel like
I am getting somewhere. ;)

As I started out, I'm a FreeBSD and Windows-user normally, and ... have
been spoiled by one-click backup solutions like Acronis and
DataProtector Express, and by opensource install setups like the
ports-collection in FreeBSD. I've always known that "solaris exists, it
is rock solid, and is a master at heavy-io-tasks", but my
hands-on-experience has been slim...

I probably should apologize to the entire list for some of my behavior
in this question-setup. In retrospect I can see that I've been
disrespectful, and probably looking a lot like a troll. This has not
been the intention. My only excuse is the reason for ditching Microsoft
Windows Storage Server 2008 as the backend. A forthnight ago, I had one
of those reasons I make backups, and needed a restore. After that
restore, I found that Windows Storage Server + DataProtector Express had
basically "lied to me". It had said everything was backed up and
verified, but that was not the case. On the storage volume, the SIS
(Single Instance Storage, Microsofts file-level-deduplication) had
fooled it. The backup software had correctly backed up the
reparse-points for the sis-managed files, but it had failed to back up
the SIS Common Storage, and as a result I lost the 1500 best
photographies I had since 2003. I think everybody on this list can ...
visualize the mood I was in when I started out. And having this in mind,
I reacted impolitely to people suggesting things like "you will never
need that backup", etc. Alas I took out my temper over those who replied
directly to my mailbox (and not on the list) towards the person who I
misinterpreted to be "yet another of those, but this one's on the list",
and did a believable impersonation of a genuine internet troll. Again, I
apologize.

I'm now 14 days into trying to get up a proper backend for safekeeping
my work, and ... quite depraved of sleep, so I may keep on asking stupid
questions that quite probably should be answered by friendly pointers to
the Mountain View company's webservices, but I'll post the questions
anyways. (the "how to restore part" has already been answered, but to
get a proper insight, I'll post the entire question-behind-the-question
anyways).


My current setup consists of two VMWare ESXi boxes (currently running
local disks, but supposed to use iSCSI backend for proper backups), each
with two 1000BaseTX connections to my switched backbone network. These
two house my webserver, mailserver, dns, ActiveDirectory DC, and are
quite intertwined with nfs. Those services are primary
FreeBSD-installations, with Windows 2008r2 handling the AD (which is on
2008 functional level, so the builtin smb in opensolaris to my knowledge
can't be a member. Yet.)

What I want from the backend server, which is a hardware raid kit with a
sas autoloader, is basically a setup that _WHEN_ (rather than if) I need
to restore it all, this can be done in a one-button fashion. I trust my
mindset when I need such a restore to be rather flaky.

So for the backend, I need iSCSI towards the clients, and
SAS<--->autoloader for archival. The box should basically be a
self-backing-up iSCSI storage box. Alas I do not have the luxury of
having two locations for a secondary box, nor do I currently have the
budget to consider more hardware.

For the iSCSI bit, and for the bonus of NFS and SMB sharing (at
lightning fast pace, I might add), both OpenSolaris and FreeBSD does a
stellar job. But when it comes to getting proper backups of filesystem
larger than a single tape (which is why I've got a tapeloader) I'm
flying blind here. So far, I've ran glossy gui windows applications for
this that basically was a big "magic happens here" box. My reasons for
going away from windows is the data loss I suffered, which means I'm not
"sleeping well" until I get some solution I can trust.

I know I'm asking a lot here, and has given no real reason for anybody
to want to help me, especially with my recent behaviour, but can someone
please point me towards
"getting-backups-to-run-properly-from-zfs-to-tape-for-really-dummie-trolls"
documentation that I can understand even if I'm desperately short on sleep?

Regards,

Svein Skogen

- -- 
- --------+-------------------+-------------------------------
  /"\   |Svein Skogen       | sv...@d80.iso100.no
  \ /   |Solberg Østli 9    | PGP Key:  0xE5E76831
   X    |2020 Skedsmokorset | sv...@jernhuset.no
  / \   |Norway             | PGP Key:  0xCE96CE13
        |                   | sv...@stillbilde.net
 ascii  |                   | PGP Key:  0x58CD33B6
 ribbon |System Admin       | svein-listm...@stillbilde.net
Campaign|stillbilde.net     | PGP Key:  0x22D494A4
        +-------------------+-------------------------------
        |msn messenger:     | Mobile Phone: +47 907 03 575
        |sv...@jernhuset.no | RIPE handle:    SS16503-RIPE
- --------+-------------------+-------------------------------
         If you really are in a hurry, mail me at
               svein-mob...@stillbilde.net
 This mailbox goes directly to my cellphone and is checked
        even when I'm not in front of my computer.
- ------------------------------------------------------------
                     Picture Gallery:
          https://gallery.stillbilde.net/v/svein/
- ------------------------------------------------------------
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.12 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkuVAKkACgkQSBMQn1jNM7ZM/QCfeNkA4FG5M+nVKQZYIHXr8tN3
dpYAnRiKMBqNLHNsppV47GiFXZDXxcoT
=HJpG
-----END PGP SIGNATURE-----
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss

Reply via email to