Ian wrote:
> Hi List,
>
> Apologies if this has been asked before, cant seem to find a good way of
> searching through the archives and in the search results a best practice
> way of doing this:
>
> We have a backuppc server that has been running for more than a year
> unmaintained. Since then, people have come and gone, the network
> infrastructure has changed and all the current hosts are basically null
> and void bar a few of them. What I am wondering is, is there any way to
> archive these backups into say 1 archive and compress the hell out of
> it. The server is currently setup to run on a static IP system, where I
> want to change that to use hostnames as the majority of people run off
> laptops and use DHCP for ease of use. I could just leave the old backups
> there, but it would seem cluttered and there would be a lot of hosts
> that are not being backed up anymore.
>
> Any advice on how to proceed going further?
>
> I am a relative newbie to backuppc, so please excuse any stupid questions :)
The native storage format is as compressed as you can get, will all copies of
any file being a link to a pooled copy. I'd just add the new host names the
way
you want and continue since a different copy of the same machine will not take
much more space, and set $Conf{FullPeriod} to -1 to disable the ones you want
to
stop. Then when the new copies have enough history you can remove the old ones.
--
Les Mikesell
lesmikes...@gmail.com
------------------------------------------------------------------------------
ThinkGeek and WIRED's GeekDad team up for the Ultimate
GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the
lucky parental unit. See the prize list and enter to win:
http://p.sf.net/sfu/thinkgeek-promo
_______________________________________________
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/
