9 Jun 2016
10:47 UTC
Bytemark Engineer
Servers with backup spaces on waltz have had new backup spaces created on other backup servers. Using "servername.backup.bytemark.co.uk" as the hostname will redirect to the new space.
It is still possible to access the old backups on waltz in a read-only fashion at waltz.bytemark.co.uk::space_name (for rsync).
4 May 2016
16:51 UTC
James Carter
The backup spaces will currently be visible, but read only. As they are moved to a new server they will become writable, but empty. It will still be possible to access the existing read-only backups at waltz.bytemark.co.uk::space_name (for rsync).
4 May 2016
14:17 UTC
Matthew Bloch
After some investigation, we've decided this particular backup server can't be reliably and practically put back into service.
It has been made available again, but to ensure its continued reliability, it will only allow data to be read, not writtedn.
Any customers who have used their backup space in the last month: over the next 48hrs you will have a fresh backup space created on a new server, and your DNS changed, but your data won't be moved (the data will still be available & frozen at the old address). This should allow fully automated backups to continue, and we will not delete it.
In the long run we are about to announce that our backup space service will be shut down. We're putting a post together with timescale & alternatives, but we will continue to maintain the current servers until further notice.
29 Apr 2016
16:17 UTC
James Carter
We are continuing to have problems with Waltz failing discs and have taken the decision to take it offline for the weekend to avoid risking data integrity. We will be contacting the affected customers on Tuesday with details of alternative arrangements.