Master of Applied Backup Theory
-
-
- WBoro
- Hero Rocketeer
- Posts: 389
- Thanks: 5
-
All of my recent installing and testing of various RT templates and customizing and configuring them has given me a valuable set of skills in 'Applied Backup Theory'. Having worked with computers for a couple of decades, I thought I was already good at that, however I have gone well beyond where I was before.
For each one of different projects, I now have the main production site, and two offline development sites on another server. I make no changes to production, unless they have been tested on the development site that is a duplicate of the production site. The other development site is the latest clean RocketLauncher version of the template, with the latest required extensions, so that I can examine various settings to find out why my customized site may be acting strangely.
Best of all, I can recover the production site in a matter of minutes, regardless of whether it is down due to being hacked or due to something that we did wrong. With current backups run frequently, a restored site is a simple and fast accomplishment. Backups are kept on the same remote web server, a different remote web server and locally.
I've read plenty of posts recommending various backup schemes, and have chosen the parts that work for me. Now, there is a lot less stress involved with my working to get my sites to look just the way I want them to look. Peace.
Greg
-
-
-
- JEM
- Preeminent Rocketeer
- Posts: 17917
- Thanks: 4
-
:arrowu:
x100
www.rockettheme.com/forum/index.php?f=15...04899&rb_v=viewtopic
Please see:
NEVER install the Rocket Launcher without the Sample Data.
ALWAYS – Highly Recommended!
Yes, Joomla is free and you can do amazing stuff with it, but 'free' doesn't equal 'easy'.
Some basic knowledge is required and it doesn't happen in a day.
Many users (members) install Joomla and the template (applied to an existing install or with the RL) and then add a dozen or so 3rd party components / modules / plugins all at once, THEN take a look at the site and ask, 'Why does my site look like this?', etc...
It really doesn't take too much time to install, backup, and check after each extension.
Certainly less time than to troubleshoot which extension is causing a problem after installing all of them at once.
I am totally on your side when it comes to this!
I always test extensions on a dev site before installing them on the production site.
And I backup the production site on a daily basis.
So, I've never had a component / module / plugin that conflicts with the production site and never risk losing more than a day's worth of edits.
(I can't tell you how many posts I've seen with 'I just installed xx and my site is totally messed up and I can't afford to lose six month's work'.)
One word: Akeeba!
www.akeebabackup.com/akeeba-backup-for-joomla/index.html - Thanks,
jim
-
-
-
- WBoro
- Hero Rocketeer
- Posts: 389
- Thanks: 5
-
Yes, I read your post some time ago, and it was very helpful. However, I did encounter some issues with akeebabackup, and decided to go in a different direction. It probably works fine for others, but maybe we have different styles.
The basic thrust being ALWAYS HAVE A RECENT BACKUP ON HAND. These web sites take a lot of time to configure and populate with content. If you have ever lost your only copy of a large web site, the heartbreak will make you a regular 'backer-upper'.
Greg
-
-
-
- JEM
- Preeminent Rocketeer
- Posts: 17917
- Thanks: 4
-
WBoro wrote:
I did encounter some issues with akeebabackup
Curious to know what happened with Akeeba?!
(In my case, I override the default .jpa file settings and always use .zip) - Thanks,
jim
-
-
-
- WBoro
- Hero Rocketeer
- Posts: 389
- Thanks: 5
-
It was primarily a matter of simplicity. I got Akeeba and tried to use it and it was not intuitive for me. I'm not willing to invest more time in understanding it because simple backups are too easy. When backups are simple and straightforward, they give me more confidence that they will always work. I need to be able to depend on the process. I like the basic process that I use now.
Greg
-
Time to create page: 0.060 seconds