In the mid-1990s, I was working as a programmer and system administrator for a food broker company here in Nashville. On one occasion, we had garbage data show up on a report. When I investigated the cause, I found that a hard drive controller failure was causing data to be written to the wrong tracks on the hard drive. We had daily backups to tape, but the backup system hadn't reported any errors, because it was making accurate copies of the already-garbled data. I had to replace the faulty hardware, do a clean reinstall of the operating system, then restore from backup. If that data was bad, I had to wipe the file system again, reinstall from the previous day's backup, etc. Finally, two weeks back, I found data that wasn't garbled, because it preceded the drive controller failure. It took the company a month to get completely up-to-date, because we had to have customers who had submitted orders during that two-week period resubmit the orders to us, while checking with the vendors to make sure they had received the orders correctly. In the meanwhile, new orders were also coming in, which had to be processed in the normal manner. Moral of the story: you need to not only check that your backup system didn't report errors, but also check that the backed-up data is usable.

On 05/18/2016 04:14 PM, Kent Perrier wrote:
Awesome. That is what this list is about! And bare metal restores of linux boxes was one of those things I always tried to avoid when I did DR tests. :D Especially because in the healthcare field every one was a special snowflake that had been lovingly hand crafted by the vendor. :(

Kent

On Wed, May 18, 2016 at 4:00 PM, Michael L <[email protected] <mailto:[email protected]>> wrote:

    I'm, again, thankful to be on this email list.
      M

    On Wed, May 18, 2016 at 2:59 PM, Chris McQuistion
    <[email protected] <mailto:[email protected]>> wrote:

        Thumbs up for Relax and Recover (REAR).  I just got this
        installed on a couple of our physical services (most are
        virtual).  You can do a 100% bare metal recovery with REAR and
        that is something that has always me nervous about our
        physical servers.  The backup target can be a number of
        different things.  It can be an attached USB drive, a remote
        NFS server, a remote Bacula server, and lots of other options.

        Sure, we have backups of data, but to completely rebuild an
        OS, reconfigure it and put all the data back in place is a
        pain in the rear on the best day.  With this system, you can
        just reboot a working system and choose Relax and Recover from
        the boot mode or burn a CD and boot from that (which is
necessary in the case of a hard drive failure or something.). You can restore the entire machine pretty easily. This makes
        me sleep a little better knowing that our VoIP server and
        primary DHCP/DNS servers are backed up in such a way that I
        can restore those entire machine in a matter of minutes,
        rather than hours to rebuild and then restore from backups.

        Chris

        P.S.  I do have to acknowledge that REAR is not the same thing
        as long term archiving, but it could be used for that
        purpose.  You can even backup to tape for those that are into
        that sort of thing...

        On Tue, May 17, 2016 at 7:21 PM, Kent Perrier
        <[email protected] <mailto:[email protected]>> wrote:

            If you want to look at bare-metal restores, take a look at
            http://relax-and-recover.org/

            Red Hat just included this in RHEL.

            Kent

            On Tue, May 17, 2016 at 6:49 PM, Howard White
            <[email protected] <mailto:[email protected]>> wrote:

                On 05/17/2016 05:44 PM, Michael L wrote:

That sounds like something I would like to try. I'm thankful for
                    getting to be on this email list.
                      M


                Michael,

                Your original post speaks to a broad topic that gets
                short shrift in most circles because backup is
                boring.  And try as we might, the backups we _do_ make
                are never enough.

                First point, the term "backup" is ambiguous.

                Second point (to which you originally alluded), backup
                != archive.

                Let's take a swing at the difference.  Backups are
about providing recovery for an information system. Archives are about replicating, indexing and
                preserving data.

                So you need to ask yourself: self, what to I expect to
                accomplish with these [ backups | archives ].  There
                are four reasons to backup and even more reasons to
                archive.

                B1 - hardware failure, and not just hard drives.
                B2 - software failure, and not just operating system
                or applications.
                B3 - security failure (can you say crypto-locker?)
                B4 - human failure, and not just rm -rvf /

                Bacula is a terrific backup solution that I have never
                had the patience to get to work; I am jealous of Ben
                and Steven Critchfield for their abilities to get that
                system working.  I personally have an instance of
                BackupPC running but it could use an upgrade and some
                verification testing.  Neither of these are truly
                archives.

                Oh, but you want to do a bare metal restore?  A bare
                metal restore is an operation by which one may take a
                backup "volume" and through the magic of television
                cause a new instance of a given system to be running.
                Personally for that requirement, I take images of
                critical systems with Clonezilla.  A Clonezilla image
                allows me to create a system instance even though I
                may have to overlay critical data from other backups
                to complete a recovery.

                Oh wait!  You've got databases??  Add a whole 'nother
                layer of storing journals and database unloads to your
                plan.  Databases may be complex data storage systems
                that are not so easy to replicate.

                Having fun yet?

                Howard


-- -- You received this message because you are subscribed
                to the Google Groups "NLUG" group.
                To post to this group, send email to
                [email protected]
                <mailto:[email protected]>
                To unsubscribe from this group, send email to
                [email protected]
                <mailto:nlug-talk%[email protected]>
                For more options, visit this group at
                http://groups.google.com/group/nlug-talk?hl=en

                --- You received this message because you are
                subscribed to the Google Groups "NLUG" group.
                To unsubscribe from this group and stop receiving
                emails from it, send an email to
                [email protected]
                <mailto:nlug-talk%[email protected]>.
                For more options, visit
                https://groups.google.com/d/optout.


-- -- You received this message because you are subscribed to
            the Google Groups "NLUG" group.
            To post to this group, send email to
            [email protected] <mailto:[email protected]>
            To unsubscribe from this group, send email to
            [email protected]
            <mailto:nlug-talk%[email protected]>
            For more options, visit this group at
            http://groups.google.com/group/nlug-talk?hl=en

            ---
            You received this message because you are subscribed to
            the Google Groups "NLUG" group.
            To unsubscribe from this group and stop receiving emails
            from it, send an email to
            [email protected]
            <mailto:[email protected]>.
            For more options, visit https://groups.google.com/d/optout.


-- -- You received this message because you are subscribed to the
        Google Groups "NLUG" group.
        To post to this group, send email to
        [email protected] <mailto:[email protected]>
        To unsubscribe from this group, send email to
        [email protected]
        <mailto:nlug-talk%[email protected]>
        For more options, visit this group at
        http://groups.google.com/group/nlug-talk?hl=en

        ---
        You received this message because you are subscribed to the
        Google Groups "NLUG" group.
        To unsubscribe from this group and stop receiving emails from
        it, send an email to [email protected]
        <mailto:[email protected]>.
        For more options, visit https://groups.google.com/d/optout.


-- -- You received this message because you are subscribed to the Google
    Groups "NLUG" group.
    To post to this group, send email to [email protected]
    <mailto:[email protected]>
    To unsubscribe from this group, send email to
    [email protected]
    <mailto:nlug-talk%[email protected]>
    For more options, visit this group at
    http://groups.google.com/group/nlug-talk?hl=en

    ---
    You received this message because you are subscribed to the Google
    Groups "NLUG" group.
    To unsubscribe from this group and stop receiving emails from it,
    send an email to [email protected]
    <mailto:[email protected]>.
    For more options, visit https://groups.google.com/d/optout.


--
--
You received this message because you are subscribed to the Google Groups "NLUG" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nlug-talk?hl=en

---
You received this message because you are subscribed to the Google Groups "NLUG" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected] <mailto:[email protected]>.
For more options, visit https://groups.google.com/d/optout.

--
--
You received this message because you are subscribed to the Google Groups 
"NLUG" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/nlug-talk?hl=en

--- You received this message because you are subscribed to the Google Groups "NLUG" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to