Re: [BackupPC-users] Backups vanish nightly...

[Don K. <dk...@op...>]

Will do..

On Jan 21, 2010, at 2:59 PM, Shawn Perry wrote:

> and touch a file in there with the current date/time while you're at it.
> 
> On Thu, Jan 21, 2010 at 2:06 PM, Tino Schwarze <bac...@ti...> wrote:
>> Hi Don,
>> 
>> On Thu, Jan 21, 2010 at 12:49:28PM -0800, Don Krause wrote:
>>> 
>>> On Jan 21, 2010, at 11:30 AM, Craig Barratt wrote:
>>> 
>>>> Don writes:
>>>> 
>>>>> The numbered directories are gone. I only have "0" from last nights backup, which is 0.3 days old, and it replaced the one from the day before..
>>>> 
>>>> Please look in the host's LOG file.  Do you see messages like:
>>>> 
>>>>    2005-02-06 11:20:55 removing old full backup 0
>>>> 
>>>> If not, then it appears something other than BackupPC is
>>>> removing or trashing the files.
>>>> 
>>>> If so, then BackupPC is removing the backups, and the only
>>>> explanation I can think of is the $Conf{FullKeepCnt} ends
>>>> up being 0.  Could you have a syntax error in your main or
>>>> per-PC config.pl files?  Eg: try running this:
>>>> 
>>>>    perl PATH_TO_MAIN_CONFIG/config.pl
>>>>    perl PATH_TO_PER_HOST_CONFIG/config.pl
>>>> 
>>>> Craig
>>>> 
>>> 
>>> 
>>> llupbt2:/export/facility/BackupPC/pc/calib # perl /etc/BackupPC/config.pl
>>> llupbt2:/export/facility/BackupPC/pc/calib # perl /etc/BackupPC/pc/calib.pl
>>> llupbt2:/export/facility/BackupPC/pc/calib #
>>> 
>>> No instances of "removing" in the log files either..
>>> 
>>> Last nights log is interesting in that at 1am it claims to be starting incremental backups..
>>> 
>>> 2010-01-21 01:00:01 Started incr backup on g2disun (pid=31638, share=/)
>>> 2010-01-21 01:00:01 Started incr backup on gantry3 (pid=31639, share=/)
>>> 2010-01-21 01:00:01 Started incr backup on delta (pid=31643, share=/)
>>> 2010-01-21 01:00:04 Started incr backup on gantry2 (pid=31675, share=/)
>>> 2010-01-21 01:00:09 Started incr backup on gantry3 (pid=31639, share=/usr)
>>> 2010-01-21 01:00:14 Started incr backup on gantry2 (pid=31675, share=/usr)
>>> 2010-01-21 01:00:22 Started incr backup on delta (pid=31643, share=/usr)
>>> 2010-01-21 01:00:48 Started incr backup on gantry3 (pid=31639, share=/var)
>>> 2010-01-21 01:00:48 Started incr backup on delta (pid=31643, share=/export)
>>> 2010-01-21 01:00:53 Started incr backup on gantry2 (pid=31675, share=/var)
>>> 
>>> Then, 2 hours later..
>>> 
>>> 2010-01-21 03:51:12 Started full backup on gantry2 (pid=489, share=/)
>>> 2010-01-21 03:52:19 Started full backup on gantry2 (pid=489, share=/usr)
>>> 2010-01-21 03:57:04 Finished crabs (BackupPC_link crabs)
>>> 2010-01-21 03:58:15 Started full backup on gantry3 (pid=452, share=/export/switc
>>> hyard)
>>> 2010-01-21 04:00:00 Next wakeup is 2010-01-21 05:00:00
>>> 2010-01-21 04:04:54 Started full backup on gantry3 (pid=452, share=/export/ingre
>>> s_back)
>>> 2010-01-21 04:04:58 Finished full backup on gantry3
>>> 2010-01-21 04:04:58 Running BackupPC_link gantry3 (pid=569)
>>> 2010-01-21 04:04:59 Started full backup on ebl-recovery (pid=571, share=/)
>>> 2010-01-21 04:05:04 Finished gantry3 (BackupPC_link gantry3)
>>> 2010-01-21 04:05:06 Backup failed on ebl-recovery (Unable to read 4 bytes)
>>> 2010-01-21 04:05:09 Started full backup on g1imgreg (pid=579, share=/)
>>> 2010-01-21 04:11:13 Started full backup on gantry2 (pid=489, share=/var)
>>> 2010-01-21 04:12:07 Started full backup on gantry2 (pid=489, share=/export/gantr
>>> y2)
>> 
>> My bets are on "something or someone is wiping your directories".
>> Try disabling backups for this night, then see what it looks like the
>> next day. I suppose, the directories will look pretty virgin.
>> 
>> Maybe run a cronjob which does an
>> ls -l /export/facility/BackupPC/pc/calib > /tmp/watchit.`date +%Y%m%d-%H%M%S`
>> every minute just to get an idea what's going on.
>> 
>> Tino.
>> 
>> --
>> "What we nourish flourishes." - "Was wir nähren erblüht."
>> 
>> www.lichtkreis-chemnitz.de
>> www.tisc.de
>> 
>> ------------------------------------------------------------------------------
>> Throughout its 18-year history, RSA Conference consistently attracts the
>> world's best and brightest in the field, creating opportunities for Conference
>> attendees to learn about information security's most important issues through
>> interactions with peers, luminaries and emerging and established companies.
>> http://p.sf.net/sfu/rsaconf-dev2dev
>> _______________________________________________
>> BackupPC-users mailing list
>> Bac...@li...
>> List:    https://lists.sourceforge.net/lists/listinfo/backuppc-users
>> Wiki:    http://backuppc.wiki.sourceforge.net
>> Project: http://backuppc.sourceforge.net/
>> 
> 
> ------------------------------------------------------------------------------
> Throughout its 18-year history, RSA Conference consistently attracts the
> world's best and brightest in the field, creating opportunities for Conference
> attendees to learn about information security's most important issues through
> interactions with peers, luminaries and emerging and established companies.
> http://p.sf.net/sfu/rsaconf-dev2dev
> _______________________________________________
> BackupPC-users mailing list
> Bac...@li...
> List:    https://lists.sourceforge.net/lists/listinfo/backuppc-users
> Wiki:    http://backuppc.wiki.sourceforge.net
> Project: http://backuppc.sourceforge.net/
> 

--
Don Krause                                                                   
Head Systems Geek, 
Waver of Deceased Chickens.
Optivus Proton Therapy, Inc.
P.O. Box 608
Loma Linda, California 92354
909.799.8327 Tel
909.799.8366 Fax
dk...@op...
www.optivus.com
"This message represents the official view of the voices in my head."