That usually means you have less than 5% of disk space on the pool
filesystem - or whatever you configured the threshold to be to stop
running automatically.
Maybe an email once a day to the admin that this threshold has been
reached, and that backups are no longer being scheduled, could be
Chris Bennett wrote:
That usually means you have less than 5% of disk space on the pool
filesystem - or whatever you configured the threshold to be to stop
running automatically.
Maybe an email once a day to the admin that this threshold has been
reached, and that backups are no longer
On 3/16/2010 6:04 PM, Chris Bennett wrote:
The 'host summary' web page shows everything at a glance. Look at
it once in a while if you care what is happening.
I was just curious how the unfamiliar admin would be able to determine
backups have stopped. From what I can tell, the host summary
It doesn't explicitly show why backups didn't run, but if you look down
the 'Last Backup (days)' column, the numbers should all be less than one
if you have daily backups scheduled. If it is more than a day without a
failure mentioned in the 'Last Attempt', it means that it didn't start
I had over 95% file space usage. I deleted some old files that I did not
need. Once I did that, my backups started running again.
Chris Baker -- cba...@intera.com
systems administrator
INTERA -- 512-425-2006
-Original Message-
From: elitejones [mailto:backuppc-fo...@backupcentral.com]
Chris Baker wrote:
I noticed this morning that my backups had not run over the weekend. They
are supposed to be automated and run every day. A full backup runs weekly.
Incremental backups run every night or day. Friday, Saturday, and Sunday
backups were all missed. This was for every single
