Believe it or not, this actually goes hand in hand with the “Richweb / Globalweb Hosting and MySQL Database Backups” post I’ve made.
We already backup the databases each night, on the database cluster, using a full mysql dump.
Quote
root@db1 10:49:39 > /data/BACKUP/db # find ./ | grep vh
./[CLIENTNAME]
./[CLIENTNAME]/[CLIENTNAME]-MySQL-db-2016-11-22-localhost.db.gz
./[CLIENTNAME]/[CLIENTNAME]-MySQL-db-2016-11-26-localhost.db.gz
./[CLIENTNAME]/[CLIENTNAME]-MySQL-db-2016-11-23-localhost.db.gz
./[CLIENTNAME]/[CLIENTNAME]-MySQL-db-2016-11-24-localhost.db.gz
./[CLIENTNAME]/[CLIENTNAME]-MySQL-db-2016-11-27-localhost.db.gz
./[CLIENTNAME]/[CLIENTNAME]-MySQL-db-2016-11-25-localhost.db.gz
./[CLIENTNAME]/[CLIENTNAME]-MySQL-db-2016-11-28-localhost.db.gz
We already backup the filesystem too – nightly rsync off site on even days and nightly rysnc onsite on odd days.
And there are 2 historical files – full tarballs – of the site kept as well back 45 days or so:
Quote
2016-10-20_data_gwebvs3.tar.gz 2016-11-20_data_gwebvs3.tar.gz
My problem with php web app driven backups is they:
Write the backups into the web files, making the backups ever larger;
They never get deleted;
Rely on wget of a url to run, which means they run from the web process, which is shoddy (error prone), timeouts, etc; and
They can easily be deleted or damaged accidentally or intentionally via an ftp client mistake.
We prefer (well insist) the backups be kept on separate disks/locations etc.
If you want an extra level of backups, you can setup a job to run once a month, and then have a script that logs in via ftp and pulls them back to your site if you want. We can create a script that pushes our backups to an ftp server of your choice too, just would take a little time to set it up.
Backups I see now:
Quote
root@vs3 10:52:18 > /var/www # find [CLIENTNAME]/backups/
[CLIENTNAME]/backups/
[CLIENTNAME]/backups/files
[CLIENTNAME]/backups/files/1480345342.zip
[CLIENTNAME]/backups/files/1475001754.zip
[CLIENTNAME]/backups/database
[CLIENTNAME]/backups/database/1477667989@@[CLIENTNAME].sql.zip
[CLIENTNAME]/backups/database/1480345326@@[CLIENTNAME].sql.zip
[CLIENTNAME]/backups/database/1475001736@@[CLIENTNAME].sql.zip
root@vs3 10:52:21 > /var/www # ls -alt [CLIENTNAME]/backups/database/1477667989@@[CLIENTNAME].sql.zip
-rw-r–r– 1 www-data www-data 554256 Oct 28 11:20 [CLIENTNAME]/backups/database/1477667989@@[CLIENTNAME].sql.zip
root@vs3 10:52:27 > /var/www # ls -alt [CLIENTNAME]/backups/database/1480345326@@[CLIENTNAME].sql.zip
-rw-r–r– 1 www-data www-data 556997 Nov 28 10:02 [CLIENTNAME]/backups/database/1480345326@@[CLIENTNAME].sql.zip
« Last Edit: December 03, 2017, 11:23:32 pm by Doug Hazard »
Logged
Doug “Bear” Hazard
@BearlyDoug | @GridironHistory | @Hogville | http://gridironhistory.com
Co-Host of Two Cents Radio, powered by the SportsManCave.com Radio Network, Wednesday Nights from 8 PM to 10 PM Central, covering SEC and Sun Belt Sports.
Listen at SMCRadio.com and follow @TwoCentsRadio on Twitter!
Offline Doug Hazard
Richweb Staff (Admin)
Newbie
*
Posts: 30
CFB / MBB Junkie
http://twocentsradio.net
Re: Customer Self-Backups and Richweb Backups
« Reply #1 on: December 03, 2017, 11:23:43 pm »
Quote
Our wordpress customers are hosted on our standalone vmwp nodes which is a quad core (full cores) vm with 10G of ram and typically a block of 8 to 12 ips and 12 to 15 sites.
Each vmwp node has a built in load balancer and content acceleration engine but the database is pointed at one of the MySQL storage nodes.
The vmwp nodes backup their content each nite to a replication server. This is all of the website files, images, php code, js and css files, etc – all media and code files.
Odd nites use an on site replica server, even nites are pushed to QTS for offsite backup.
Once a month a full snapshot is taken. We keep 2 months of snapshots.
The databases are backed up each nite (full snap) and pushed the same way – evens and odds. 10 days of backups are kept, and then monthly archives for 1 year are kept.
If you have need to recover old data its best to ask quickly, before backups are over-written. Recovering data from 6 months ago for example can be a challenge.
Full snaps of the filesystem web dirs are stored in: /data/BACKUP/content/
And can be uncompressed to fetch files as needed.
We can also ship backups to a customer ftp site if desired. And we can arrange for longer term storage of backups if needed, like plugging in the GlobalWeb RBS system for long term storage of file backups.