Hello Les,
Les Mikesell wrote:
Hervé Richard wrote:
This doesn't sound right if you only have one target. Does the
server and the backuppc service run continuously? Maybe it isn't
running the backuppc_nightly job that removes the unneeded
pool/cpool copies.
Yes in fact the server and backuppc run continuously and the server
backup files stored on itself.
I took care of not backing up backuppc files as mentioned in the
backuppc faq.
By the way I have a rotation between two hard drive every 2 weeks.
This done manually.
Localhost config.pl is stored on each hard drive including the backuppc
dir as below:
backuppc/
cpool/
log/
pc/
pool/
trash/
I think there is bad influence on the way backuppc behave.
For backuppc_nightly job:
Maybe :-/
I don't know how to configure/force backuppc_nightly job to removes
unneeded pool/cpool :-/
Maybe it's automatic... check every age of every backuped files and
delete everyone older than configured in:
It is supposed to be automatic and it doesn't pay attention to ages.
It should delete anything in the pools with only one link - meaning
that all references in the pc directories had already been deleted.
If you cd to the cpool directory and 'find . -links 1' you shouldn't
see very many files.
When I execute ' find . -links 1 ' in the cpool directory I see a lot of
files.
In my configuration, files are stored on a RAID volume mounted on a
mount point in home directory.
In the Cpool directory I got directories from : 0 to f and same subdirs
from 0 to f...
For example:
ls cpool -> 0 1 2 3 4 5 6 7 8 9 a b c d e f
and ls cpool/0/ -> same thing as above
ls cpool/0/0/ -> same thing
ls cpool/0/0/0/ -> gives me files with 34 hexa digit.
When I check (with ls -la) files date some are more than 1 year older
than the other (eg: 2006 and 2007)
I have this message in every log:
Cpool nightly clean removed 0 files of size 0.00GB
It doesn't make sense for the cpool dir to be bigger than the pc
directory if you only have one server, since all files that exist in
cpool should have links in the pc dir(s) too. However, du has some
quirks in the way it adds up the space, trying not to count linked
files multiple times. Also, the space you reported for cpool and pc
should really be the same space since all the files should be
hardlinks. And in any case it shouldn't fill the 80 gigs you said you
had. We must be missing something. Is everything on the same filesytem?
Of cource I think it too...
BackupPC main directory and core system is on the OS file system, the
data to be backuped up are on an another file system mounted on home/ as
I said above and the backuped data are on another filesystem on a hard
drive. Every file system are Ext3.
I didn't used symlink to write path to the backuped files in my config.pl.
Here is an overview of the system architecture:
_____
| |
|RAID|
Main FS |_____|
___ /
| | / /home/e-smith/files
|___| /
- OS /
__
- Mounting point <---/---------------------/mnt/hdd1---|__| Backup media
(HDD 80GB) ->backuppc/
- BackupPC core /opt/backuppc/
cpool/
log/
pc/
pool/
trash/
Cheers
Hervé
begin:vcard
fn;quoted-printable:Herv=C3=A9 Richard
n;quoted-printable:Richard;Herv=C3=A9
org:PERIACTES
adr:;;Av. de l'hippodrome, 147;Brussels;;1050;Belgium
email;internet:[EMAIL PROTECTED]
tel;work:+32 (0) 2 649 80 89
tel;fax:+32 (0) 2 648 27 22
x-mozilla-html:FALSE
url:http://www.periactes.com
version:2.1
end:vcard
-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
_______________________________________________
BackupPC-users mailing list
[email protected]
List: https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki: http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/
