Re: [BackupPC-users] How to move to a new remove server?

2012-04-10 Thread Tim Fletcher

On 08/04/12 00:31, Alexander, Clint Mr ARMY GUEST USA USAMC USA wrote:


Hello everyone.

I'm joining the list for the first time in attempts to figure out a 
problem I cannot find a solution for no matter what keywords I have 
searched for...


I have 2 servers at a hosting company; an old one having a long and 
large pool of BackupPC data on it. The new one is replacing the old one.


The hard drive cannot be removed from the old server and added to the 
new one. It simply  needs to be copied from one location to the other 
via the internal GB network (no backup tapes or CD's or anything else, 
strictly network copy only).


My question is, How?




On the old server:

dd if=/dev/oldbackuppcfs bs=1M | ssh -c arcfour -l root newserver dd 
of=/dev/newbackuppcfs


This is the best way to move a backuppc filesystem by just copying the 
raw filesystem about.


--
Tim Fletchert...@night-shade.org.uk

--
Better than sec? Nothing is better than sec when it comes to
monitoring Big Data applications. Try Boundary one-second 
resolution app monitoring today. Free.
http://p.sf.net/sfu/Boundary-dev2dev___
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
List:https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki:http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/


Re: [BackupPC-users] How to move to a new remove server?

2012-04-07 Thread Les Mikesell
On Sat, Apr 7, 2012 at 6:31 PM, Alexander, Clint Mr ARMY GUEST USA
USAMC USA clint.alexan...@us.army.mil wrote:

 I have 2 servers at a hosting company; an old one having a long and large
 pool of BackupPC data on it. The new one is replacing the old one.



 The hard drive cannot be removed from the old server and added to the new
 one. It simply  needs to be copied from one location to the other via the
 internal GB network (no backup tapes or CD's or anything else, strictly
 network copy only).

 My question is, How?

 I have used Rsync with archive and preserve hard link mode but I still get
 duplicate files and run out of space on the new server, when the new server
 has more space available than the old.

Rsync needs the -H option to recreate the hardlinks.  There are some
practical limits to the size of a pool that can be copied in a
reasonable amount of time because identifying and recreating the
hardlinks is somewhat inefficient - and you have to include the entire
tree in one pass for it to work.

 I've also mounted the new location on
 the old server and followed the instructions to use the BackupPC_tarPCCopy
 but this does not preserve hardlinks across hard drives either.

You can't make hardlinks across drives.  You have to have everything
on one filesystem.

 How do I (we) correctly copy the entire pool (and any other important
 information) to a new server?

I've always found it easier to just stop making new backups on the old
server but keep it around until the new one has accumulated the
history you need.

-- 
Les Mikesell
  lesmikes...@gmail.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@lists.sourceforge.net
List:https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki:http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/


Re: [BackupPC-users] How to move to a new remove server?

2012-04-07 Thread Alexander, Clint Mr ARMY GUEST USA USAMC USA
 Rsync needs the -H option to recreate the hardlinks.  There are some
 practical limits to the size of a pool that can be copied in a
 reasonable amount of time because identifying and recreating the
 hardlinks is somewhat inefficient - and you have to include the entire
 tree in one pass for it to work.

I found this as well (even though most instructions give the archive mode
(-a) without the hard-link switch).


What about the requirements of the two directory structures:
__topdir__/data/pc  __topdir__/data/cpool

If I only copy the pc directory to another server, I noticed that my new
installation of BackupPC apparently reads it just fine and displays the
previous full and incrementals that we've collected over the years. The
backuppc service seems to look for existence and ownership of cpool, but
does not complain that it is empty (which it is in my test environment). 

Do we really need the cpool directory? Will backuppc rebuild this in some
way?


// Clint Alexander


 -Original Message-
 From: Les Mikesell [mailto:lesmikes...@gmail.com]
 Sent: Saturday, April 07, 2012 8:34 PM
 To: General list for user discussion, questions and support
 Subject: Re: [BackupPC-users] How to move to a new remove server?
 
 On Sat, Apr 7, 2012 at 6:31 PM, Alexander, Clint Mr ARMY GUEST USA USAMC
 USA clint.alexan...@us.army.mil wrote:
 
  I have 2 servers at a hosting company; an old one having a long and
  large pool of BackupPC data on it. The new one is replacing the old
 one.
 
 
 
  The hard drive cannot be removed from the old server and added to the
  new one. It simply  needs to be copied from one location to the other
  via the internal GB network (no backup tapes or CD's or anything else,
  strictly network copy only).
 
  My question is, How?
 
  I have used Rsync with archive and preserve hard link mode but I still
  get duplicate files and run out of space on the new server, when the
  new server has more space available than the old.
 
 Rsync needs the -H option to recreate the hardlinks.  There are some
 practical limits to the size of a pool that can be copied in a
 reasonable amount of time because identifying and recreating the
 hardlinks is somewhat inefficient - and you have to include the entire
 tree in one pass for it to work.
 
  I've also mounted the new location on
  the old server and followed the instructions to use the
  BackupPC_tarPCCopy but this does not preserve hardlinks across hard
 drives either.
 
 You can't make hardlinks across drives.  You have to have everything on
 one filesystem.
 
  How do I (we) correctly copy the entire pool (and any other important
  information) to a new server?
 
 I've always found it easier to just stop making new backups on the old
 server but keep it around until the new one has accumulated the history
 you need.
 
 --
 Les Mikesell
   lesmikes...@gmail.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@lists.sourceforge.net
 List:https://lists.sourceforge.net/lists/listinfo/backuppc-users
 Wiki:http://backuppc.wiki.sourceforge.net
 Project: http://backuppc.sourceforge.net/


--
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@lists.sourceforge.net
List:https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki:http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/


Re: [BackupPC-users] How to move to a new remove server?

2012-04-07 Thread Les Mikesell
On Sat, Apr 7, 2012 at 7:49 PM, Alexander, Clint Mr ARMY GUEST USA
USAMC USA clint.alexan...@us.army.mil wrote:
 Rsync needs the -H option to recreate the hardlinks.  There are some
 practical limits to the size of a pool that can be copied in a
 reasonable amount of time because identifying and recreating the
 hardlinks is somewhat inefficient - and you have to include the entire
 tree in one pass for it to work.

 I found this as well (even though most instructions give the archive mode
 (-a) without the hard-link switch).


 What about the requirements of the two directory structures:
 __topdir__/data/pc  __topdir__/data/cpool

That's where the hardlinks that provide pooling happen.   They must be
in the same filesystem.

 If I only copy the pc directory to another server, I noticed that my new
 installation of BackupPC apparently reads it just fine and displays the
 previous full and incrementals that we've collected over the years.

The copies that are made only to the pc directory won't be shared.
Depending on how you copied them, they may still have the hard links
to each other, but they need the cpool link if you want to be able to
match up the content on new backups.

 The
 backuppc service seems to look for existence and ownership of cpool, but
 does not complain that it is empty (which it is in my test environment).

 Do we really need the cpool directory? Will backuppc rebuild this in some
 way?

If you use rsync, new backups will make hardlinks to files where the
names and content match the reference backup, but these won't be added
back to the pool.  And if you add new targets, their files will make
links into the pool, but these will continue to be separate instances
from the ones you copied under /pc/ without the pool links.
Everything should actually work correctly, but you'll never regain the
space until all of the copied backups expire.

-- 
Les Mikesell
  lesmikes...@gmail.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@lists.sourceforge.net
List:https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki:http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/