BackupPC-users

Re: [BackupPC-users] Moving backuppc to a new machine

2012-04-20 14:40:34
Subject: Re: [BackupPC-users] Moving backuppc to a new machine
From: Kameleon <kameleon25 AT gmail DOT com>
To: "General list for user discussion, questions and support" <backuppc-users AT lists.sourceforge DOT net>
Date: Fri, 20 Apr 2012 13:39:24 -0500
On Fri, Apr 20, 2012 at 1:28 PM, Les Mikesell <lesmikesell AT gmail DOT com> 
wrote:
> On Fri, Apr 20, 2012 at 12:41 PM, Kameleon <kameleon25 AT gmail DOT com> 
> wrote:
>> Currently our backuppc server is a Xen pv domU running Ubuntu 10.04.
>> It has served us well over the past two years. However it is time to
>> move it out of the virtual environment and back onto physical
>> hardware. This is only so that it can be located on the far edge of
>> our campus as far away from the physical servers it backs up as
>> possible while still keeping it on the fiber network. So with that we
>> are looking to install a fresh OS on the new hardware. We could stay
>> with Ubuntu and just load 12.04. Most of our other servers are Centos
>> or Fedora. Is there one distribution that is better than the other for
>> backuppc? I will be moving the /var/lib/backuppc pool (it is on it's
>> own lv) to the new machine. Should I expect any problems with this?
>>
>> Thanks in advance for any and all input.
>
> If you like centos, I'd probably go with a Centos 6.2 since that
> should have a very long life with update support.  But, there are some
> differences in the packaging and directory naming conventions between
> the EPEL rpm and the debian/ubuntu .debs that you might need to
> understand.   I don't think that should affect the archive layout,
> though.  Moving large pools is always a problem if you try to do
> file-level copies. Moving the disks or image copies should work,
> though.
>
> --
>  Les Mikesell
>    lesmikesell AT gmail DOT com
>
> ------------------------------------------------------------------------------
> For Developers, A Lot Can Happen In A Second.
> Boundary is the first to Know...and Tell You.
> Monitor Your Applications in Ultra-Fine Resolution. Try it FREE!
> http://p.sf.net/sfu/Boundary-d2dvs2
> _______________________________________________
> BackupPC-users mailing list
> BackupPC-users AT lists.sourceforge DOT net
> List:    https://lists.sourceforge.net/lists/listinfo/backuppc-users
> Wiki:    http://backuppc.wiki.sourceforge.net
> Project: http://backuppc.sourceforge.net/

When I set this machine up I set the pool to be on a separate logical
volume just for the reason of future expansion. The move to this
machine was the good old "rsync -vrlptgoDH" way and it did take for
ever! That was when we only had roughly 1.5TB of pool storage, while
now we have over 5TB. It is not a possibility to leave the existing
pool where it is as we are pulling the drives to install in a
different machine meaning re-initializing them. Since the pool is on
it's own lv I plan to just export that lv to our SAN temporarily, then
export it to it's final destination once the final machine is setup.
Thanks for the input.

Donny B.

------------------------------------------------------------------------------
For Developers, A Lot Can Happen In A Second.
Boundary is the first to Know...and Tell You.
Monitor Your Applications in Ultra-Fine Resolution. Try it FREE!
http://p.sf.net/sfu/Boundary-d2dvs2
_______________________________________________
BackupPC-users mailing list
BackupPC-users AT lists.sourceforge DOT net
List:    https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki:    http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/