--rwlp4HDnqjg7pxzw
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
Hi Ian,
On Mon, Jan 30, 2012 at 12:14:32AM +0000, Ian wrote:
>> in /etc now comes up with one hit, in ntp.conf:
>>
>> > # and admin.curacao.bitfolk.com (nagios)
>> > restrict 212.13.194.71
>>
>> so I changed that to 85.119.80.238 and 85.119.80.244 per the customer
>> information page on the website and restarted ntp.
>
> Looking, I should have added these two ages ago, but I suspect I am not =
=20
> the only one who didn't...
Allowing nagios's IP addresses to query your ntp server is only
required if it's being monitored by BitFolk. So either it makes no
difference or else alerts start firing and you notice. :)
Some relevant links:
http://bitfolk.com/customer_information.html#toc_3_NTP___London__UK
http://lists.bitfolk.com/lurker/message/20110911.044100.9a55e70c.en.html
Cheers,
Andy
--=20
http://bitfolk.com/ -- No-nonsense VPS hosting
--rwlp4HDnqjg7pxzw
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
iEYEAREDAAYFAk8l500ACgkQIJm2TL8VSQvd5QCeIRok26IbmU1oYfHgcHetGSmQ
i78AnRBE/n/ed+UBHgWqbQRXCeDNHu8V
=p+o1
-----END PGP SIGNATURE-----
--rwlp4HDnqjg7pxzw--
From announce-bounces+users=lists.bitfolk.com@??? Tue Jan 31 16:03:15 2012
Received: from localhost ([127.0.0.1] helo=bitfolk.com)
by mail.bitfolk.com with esmtp (Exim 4.72) (envelope-from
<announce-bounces+users=lists.bitfolk.com@???>)
id 1RsGAt-0000BA-D3
for users@???; Tue, 31 Jan 2012 16:03:15 +0000
Received: from andy by mail.bitfolk.com with local (Exim 4.72)
(envelope-from <andy@???>) id 1RsGAo-0000A6-C0
for announce@???; Tue, 31 Jan 2012 16:03:10 +0000
Date: Tue, 31 Jan 2012 16:03:10 +0000
From: Andy Smith <andy@???>
To: announce@???
Message-ID: <20120131160310.GO23380@???>
MIME-Version: 1.0
OpenPGP: id=BF15490B; url=http://strugglers.net/~andy/pubkey.asc
X-URL: http://strugglers.net/wiki/User:Andy
User-Agent: Mutt/1.5.18 (2008-05-17)
X-Virus-Scanner: Scanned by ClamAV on mail.bitfolk.com at Tue,
31 Jan 2012 16:03:10 +0000
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on
spamd1.lon.bitfolk.com
X-Spam-Level:
X-Spam-ASN:
X-Spam-Status: No, score=-0.0 required=5.0 tests=NO_RELAYS shortcircuit=no
autolearn=disabled version=3.3.1
X-Spam-Report: * -0.0 NO_RELAYS Informational: message was not relayed via SMTP
X-BeenThere: announce@???
X-Mailman-Version: 2.1.11
Precedence: list
Content-Type: multipart/mixed; boundary="===============0001861887=="
Sender: announce-bounces+users=lists.bitfolk.com@???
Errors-To: announce-bounces+users=lists.bitfolk.com@???
X-Virus-Scanner: Scanned by ClamAV on mail.bitfolk.com at Tue,
31 Jan 2012 16:03:15 +0000
X-SA-Exim-Connect-IP: 127.0.0.1
X-SA-Exim-Mail-From: announce-bounces+users=lists.bitfolk.com@???
X-SA-Exim-Scanned: No (on mail.bitfolk.com); SAEximRunCond expanded to false
Subject: [bitfolk] Additional monitoring for backups
X-BeenThere: users@???
Reply-To: users@???
List-Id: Users of BitFolk hosting <users.lists.bitfolk.com>
List-Unsubscribe: <https://lists.bitfolk.com/mailman/options/users>,
<mailto:users-request@lists.bitfolk.com?subject=unsubscribe>
List-Archive: <http://lists.bitfolk.com/lurker/list/users.html>
List-Post: <mailto:users@lists.bitfolk.com>
List-Help: <mailto:users-request@lists.bitfolk.com?subject=help>
List-Subscribe: <https://lists.bitfolk.com/mailman/listinfo/users>,
<mailto:users-request@lists.bitfolk.com?subject=subscribe>
X-List-Received-Date: Tue, 31 Jan 2012 16:03:15 -0000
--===============0001861887==
Content-Type: multipart/signed; micalg=pgp-ripemd160;
protocol="application/pgp-signature"; boundary="Qtzb1h6tVL0ohdDu"
Content-Disposition: inline
--Qtzb1h6tVL0ohdDu
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
Hi,
If you don't currently take advantage of BitFolk's free backups
service then the following doesn't apply to you.
Two extra checks were added last night on the backups that BitFolk
manages for you.
All this info is going to go on a page I will create at
https://tools.bitfolk.com/wiki/Backups but you need to know it now.
- Backup age
This checks that your most recent successful=B9 backup is not too
old. The warning threshold is 2.5x the appropriate interval. So if your
backups happen every 4 hours, you'll receive an alert if they are
ever older than 10 hours. If your backups happen daily then
you'll receive an alert if they are ever more than 60 hours old.
And so on.
This alerting replaces the manual process of me being sent
excerpts of log files that say a customer's backups are failing,
then opening a support ticket with the customer to make them
aware.
If you receive this alert then your backups are definitely not
happening.
The alert looks like this:
From: nagios@???
Subject: ** PROBLEM alert - backup0.bitfolk.com/Backup age youraccount =
is CRITICAL **
=20
***** Nagios *****
=20
Notification Type: PROBLEM
=20
Service: Backup age youraccount
Host: backup0.bitfolk.com
Address: 85.119.80.240
State: CRITICAL
Date/Time: Tue Jan 31 12:37:38 UTC 2012
=20
Additional Info:
=20
FILE_AGE CRITICAL: /data/backup/rsnapshot.6-7-4-6/hourly.0/85.119.82.12=
1 is 16842912 seconds old and 4096 bytes
(Those who haven't had a successful backup run in the last couple
of days will have a huge number of seconds listed there because
the backup system was only modified to record last successful
contact recently)
- Backup space usage
This checks that your total backup space usage is not approaching
your current quota. The thresholds are 95% for a warning and 99%
for a critical.
This alerting replaces the manual process of me being warned about
customers who are exceeding their quota and then opening support
tickets with them to discuss what they want to do about it=B2.
If you receive this alert then your backups are still happening,
but you're in danger of (or already are) using more than the
agreed space. If you exceed your quota then we may disable your
backups, so that would eventually cause the above backup age alert
to fire.
Please note that we can't update the measurement of how much space
you're using very often. Backup directories contain hundreds of
millions of files, many of which are copies of each other, but
it's not possible to tell without looking. Adding it all up takes
quite a long time and stresses disk IO quite badly. So we only
update quotas every day at best at the moment.
Also please note that since this is a backup system, deleting
files on your VPS does not immediately result in using less disk
space for backups. It would be a rather pointless backup system if
it threw away deleted files immediately. :) Anything that gets
backed up is going to be kept for as long as your chosen backup
schedule dictates, e.g. 6 months by default. If you have blown
your quota by accidentally allowing large amounts of data to be
backed up, you are still going to have to contact support to get
it deleted.
The alert looks like this:
From: nagios@???
Subject: ** PROBLEM alert - backup2.bitfolk.com/Backup space usage your=
account is WARNING **
=20
***** Nagios *****
=20
Notification Type: PROBLEM
=20
Service: Backup space usage youraccount
Host: backup2.bitfolk.com
Address: 85.119.80.230
State: WARNING
=20
Date/Time: Tue Jan 31 15:52:28 UTC 2012
=20
Additional Info:
=20
WARNING 98.50% (394/400MiB) used
It is possible for the usage to go above 100% because we do allow
you to go over your quota for short periods of time.
Cheers,
Andy
=B9 "Successful" as in, rsync connected to your host, did some stuff
and then exited with a non-error exit code. It does not
necessarily mean that what you think should be backed up is being
backed up. As with any backup solution you need to assure yourself
on a regular basis that it's doing what you expect.
=B2 Generally one or more of:
- Buy some more disk space for backups
- Backup fewer files
- Backup less often
--=20
http://bitfolk.com/ -- No-nonsense VPS hosting
--Qtzb1h6tVL0ohdDu
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
iEYEAREDAAYFAk8oEL4ACgkQIJm2TL8VSQtrvwCgpHnPToXDO8+/ehb9FGMGiXF/
P6MAoJyqosCIvtDzuayFscN2ONIMxlRP
=viem
-----END PGP SIGNATURE-----
--Qtzb1h6tVL0ohdDu--
--===============0001861887==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
_______________________________________________
announce mailing list
announce@???
https://lists.bitfolk.com/mailman/listinfo/announce
-
