Gerald Brandt wrote:
> 
> ----- "Les Mikesell" <lesmikesell AT gmail DOT com> wrote:
>  > Gerald Brandt wrote:
>  > > Hi Chris,
>  > >
>  > > The storage will be iSCSI (over gigabit), and offsite backups will be
>  > > done via an archive done once a week.  Does that sound sane?
>  >
>  > What kind of archive are you planning? As is frequently discussed here
>  > it is difficult to copy a large backuppc system in any way other than
>  > making an image copy of the raw filesystem because of the time it takes
>  > to duplicate the large number of hardlinks.
>  >
> 
> Hi,
> 
> Basically, I plan to have a cycle of 3 offsite backup disks, and I'll 
> use the backuppc archive command to archive the latest version.  I'll 
> then copy that archive to the remote disks.

The backuppc archive host setup is (a) somewhat hard to automate, and 
(b) gives a complete tar image per host.  You not only lose the history 
here but you have to store multiple copies of anything redundant.  If 
you back up many machines storing copies of the same large files it is 
possible that a single archive export will be larger than the whole 
stored (and pooled) history of the machines.  On the other hand, you 
don't need any special tools to recover the exported tar copy.

-- 
   Les Mikesell
    lesmikesell AT gmail DOT com

------------------------------------------------------------------------------
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and easy
Join now and get one step closer to millions of Verizon customers
http://p.sf.net/sfu/verizon-dev2dev 
_______________________________________________
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/