Step 1 - Don't turn on snapshots as the first stage of your "triple backup" strategy, contrary to your advertised features
Step 2 - Blow up your file system
Step 3 - Blow up your file system so friggin' bad you can't restore your onsite backup (2nd stage of the triple backup strategy)
Step 4 - Make sure your off-site backups are on the oldest hardware possible and make it painfully slow to restore from off site.
Step 1 - Don't turn on snapshots as the first stage of your "triple backup" strategy, contrary to your advertised features
Step 2 - Blow up your file system
Step 3 - Blow up your file system so friggin' bad you can't restore your onsite backup (2nd stage of the triple backup strategy)
Step 4 - Make sure your off-site backups are on the oldest hardware possible and make it painfully slow to restore from off site.
Haven't got a clue as to the specific kind of backups
you are talking about, but that seems to be the standard
operating procedure in the world today.
(PS: Anyone here use K's Replicator?)
I don't mind being called far right.
I have been right so far.
Put this script as the 1st line on the page:
Then I would write an FTP script that takes the entire /vb directory and sub-directories (files / sql database) and copies it
to another server outside of MDhosting on an automated schedule around 3:00 AM.
If MDHosting takes a SH-- on you you again you can simply goto godaddy and redirect
to that platform and all the DNS will update in a few minutes.
Your backups will be good through 3AM that day and you dont rely on a webhost to do it.
All my business clients are hosted on multiple platforms in different clouds where I control DNS and routing.
Last edited by shawnricheson; September 25th, 2018 at 6:20 PM.
Well, I am now not nearly as frustrated as before... I had no idea what a great place to vent CTT was... It was like my fingers were tongue tied for 2 days.
PS... Solitaire is no acceptable backup.
If you do not read the news you are uninformed. If you do you are misinformed. Mark Twain