Re: [BackupPC-users] : Out of space on the backup volume. (Craig Barratt)

[Holger Parplies]

Hi,

you, Brian Albright, wrote on 08.12.2006 at 16:30:47 [[BackupPC-users] : Out of 
space on the backup volume. (Craig Barratt)]:
 
 [...]
 This reply below seems to state [...]

Mistake 1: the reply is below.
Mistake 2: you're posting a list digest to the mailing list instead of only
   the relevant part of the relevant posting:

Craig Barratt wrote on Wed, 29 Nov 2006 09:46:05 -0800 [Re: [BackupPC-users] 
Out of space on the backup volume.]:
 Daniel writes:
  The thing is... that the nightly cleanups do not happen. And thus, we 
  get this in log files:
 
 My guess is that nothing is getting deleted from the pool since no
 further backups have been deleted.

Had you done this, you might have avoided

Mistake 3: you're not reading what you're replying to.

Craig wrote no further backups *have been deleted*, not no further backups
*are happening*.

$Conf {flame} - off ();
If, in your case, no further backups are being deleted *because* no further
backups are happening, you'll have to decrease the backup counts you're
telling BackupPC to keep, which you apparently did. Maybe you are mistaking
what the Keep options mean and how they interact? BackupPC may be keeping
more full backups if they are needed by incrementals depending on them.
Also, don't expect the amount of storage listed for a to-be-deleted backup
in the New Files size column to be released, because these new files may
(partly) be existing files to a newer backup (and thus need to be kept).

In theory, if you back up data consisting of files which are never changed
but only added to, i.e. you only create new files and never delete or change
already existing files, then deleting older backups will never free any
space at all (and your backup summaries will look quite normal: lots of
existing files, some new files). Of course, that's not the situation most of
us have (at least not that pure), but perhaps it gives a hint of why less
storage is released than you might first think. Efficient handling of
duplicate contents comes at the cost of not saving anything by keeping less
copies of these contents (well, yes, inodes and a few bytes of meta-data).

Sure, you may have a completely different problem, but from the sparse hints
you give (which is mistake 4), it's hard to answer anything else than buy
more storage or keep less backups.

Sorry for getting angry about just one more instance of what happened so
far on backuppc-users  You are not the only one on this list who might
find taking a look at [1] or even [2] quite interesting.

Hope that helps anyway.

Regards,
Holger

[1] http://en.wikipedia.org/wiki/Netiquette
[2] http://tools.ietf.org/html/rfc1855

-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT  business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
___
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/backuppc-users
http://backuppc.sourceforge.net/

[BackupPC-users] : Out of space on the backup volume. (Craig Barratt)

[Brian Albright]

I'm out of space on my backup volume as well.  I changed the config file to
hold less fulls and less incrementals but it won't clean what are my
options.  This reply below seems to state it won't clean up files until it
can do another backup which it can't because the drive is full.
-Original Message-

From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
[EMAIL PROTECTED]
Sent: Thursday, November 30, 2006 12:21 AM
To: backuppc-users@lists.sourceforge.net
Subject: BackupPC-users Digest, Vol 7, Issue 58

Send BackupPC-users mailing list submissions to
backuppc-users@lists.sourceforge.net

To subscribe or unsubscribe via the World Wide Web, visit
https://lists.sourceforge.net/lists/listinfo/backuppc-users
or, via email, send a message with subject or body 'help' to
[EMAIL PROTECTED]

You can reach the person managing the list at
[EMAIL PROTECTED]

When replying, please edit your Subject line so it is more specific
than Re: Contents of BackupPC-users digest...


Today's Topics:

   1. lang=C for tar does not seem to work (Torsten Sadowski)
   2. Re: Out of space on the backup volume. (Craig Barratt)
   3. merging two servers (Klaas Vantournhout)
   4. Re: Rsyncd (Byron Trimble)
   5. NT_STATUS_BAD_NETWORK_NAME (Jean-Michel Beuken)
   6. Re: NT_STATUS_BAD_NETWORK_NAME (Craig Barratt)
   7. Upgrade to 3.0.0beta2 (Jason Hughes)
   8. Re: Rsyncd (Les Mikesell)
   9. Using mod_auth_pam (Alex Schaft)
  10. Re: Using mod_auth_pam (Craig Barratt)


--

Message: 1
Date: Wed, 29 Nov 2006 18:44:06 +0100
From: Torsten Sadowski [EMAIL PROTECTED]
Subject: [BackupPC-users] lang=C for tar does not seem to work
To: backuppc-users@lists.sourceforge.net
Message-ID: [EMAIL PROTECTED]
Content-Type: text/plain;  charset=us-ascii

Hi, 

I ran into exactly the same problem today (quite suddenly, it worked
before). 
I put the LANG=C before sudo and for me it worked:

$Conf{TarClientCmd} =  '$sshPath -l backuppc tmac 
LANG=C /usr/bin/sudo ./GetTar -v -f - -C '

Cheers, Torsten




--

Message: 2
Date: Wed, 29 Nov 2006 09:46:05 -0800
From: Craig Barratt [EMAIL PROTECTED]
Subject: Re: [BackupPC-users] Out of space on the backup volume.
To: Daniel Nowacki [EMAIL PROTECTED]
Cc: backuppc-users@lists.sourceforge.net
Message-ID: [EMAIL PROTECTED]
Content-Type: text/plain;   charset=US-ASCII

Daniel writes:

  This is correct.  Your configuration asks for at least one full
  and at least 6 incrementals.  It looks like this machine isn't
  regularly on the network.  The oldest incremental is quite old
  (10/30) and the 10/24 full has to be kept for this incremental.
  That full won't be deleted until another incremental occurs
  (allowing the 10/30 incremental to be deleted).
  
  In fact, the next time this machine is backed up, another full will
  be done, not an incremental, since the oldest full is more than 7
  days old. At this point, if you want fewer fulls you should either
  reduce the number of old incrementals (see: $Conf{IncrKeepCntMin}
  and $Conf{IncrAgeMax}), or reduce the total number of incrementals
  (see $Conf{IncrKeepCnt}).
  
  The basic point is that the number of incrementals (and their timing)
  affects the number of fulls that needs to be kept.  However, the
  additional storage for each full is more modest than you might
  expect beacuse of pooling.
 
 The thing is... that the nightly cleanups do not happen. And thus, we 
 get this in log files:

My guess is that nothing is getting deleted from the pool since no
further backups have been deleted.

Craig



--

Message: 3
Date: Wed, 29 Nov 2006 19:00:44 +0100
From: Klaas Vantournhout [EMAIL PROTECTED]
Subject: [BackupPC-users] merging two servers
To: backuppc-users@lists.sourceforge.net
Message-ID: [EMAIL PROTECTED]
Content-Type: text/plain; charset=ISO-8859-1

Hi,

In our department, we might combine several backup servers to one big one.

The question is of course, how do you start with that. Can you just copy
all the stuff?

Thanks

klaas
-- 
Several billion trillion tons of superhot
exploding hydrogen nuclei rose slowly above
the horizon and managed to look small, cold
and slightly damp.
Douglas Adams - The Hitch Hickers
Guide to the Galaxy



--

Message: 4
Date: Wed, 29 Nov 2006 15:48:58 -0500
From: Byron Trimble [EMAIL PROTECTED]
Subject: Re: [BackupPC-users] Rsyncd
To: 'Les Mikesell' [EMAIL PROTECTED]
Cc: Backuppc-Users \(E-mail\) backuppc-users@lists.sourceforge.net
Message-ID:
[EMAIL PROTECTED]
Content-Type: text/plain;   charset=iso-8859-1

When I ran rsync target_host::, this is the message that I reeived:

@ERROR: auth failed on module MSSQL
rsync error: error starting client-server protocol (code 5) at main.c(1296)
[receiver=2.6.8]

Any advice on what this error means?

Thanks,

-Original Message-
From: Les