The free forums are no longer in use. It remains available as read-only archive.
Log In
Home
Topic RSS
12:21 am
February 17, 2011
Offline
Hello. I hope that someone here can assist me. I am running WordPress
3.1.2 on an old Macintosh G4 mini-tower running OSX 10.4.11. I have a
custom installation of PHP5 from Zend software installed in my
Applications folder.
I have zero experience with setting up cron
jobs on a Mac, and would really appreciate some help. I have researched
online regarding how to do this, but it is still a bit beyond my current
understanding.
On theXCloner "Cron Command Setup" page in
WordPress, it offers four commands, and I am pretty sure that I am
supposed to use the first one, and simply change the path to where my
PHP5 installation is actually located in the Applications folder.
However, I have no idea where I am supposed to put that command, or how to get it working.
Since
I first installed XCloner, I've been doing manual backups when I
remember to do them, but that obviously does not give me peace of mind,
as I only remember to do a backup every few days, or even longer.
Anyway, if some kind soul here who is a Macintosh user can walk me through this a step at a time, I'd be most appreciative.
Thanks so much.
4:07 am
September 26, 2010
Offline
In order to run automated cron backups, you first need to look for a cron scheduler for your OSX version, once you find that, you will be able to add the XCloner cron command as detailed on the cron page and also setup the time you want to run it at!
Regards, Ovidiu
4:14 am
February 17, 2011
Offline
Hello Ovidiu,
Actually, after making my previous post, I did in fact conduct some online research, and I discovered a free cron tab program for the Macintosh called Cronnix which easily allowed me to add the right command to my Mac's cron tab. In fact, just ten minutes ago, XCloner performed an automatic backup of my WP setup.
My only complaint is that it did not backup the other mySQL databases that I normally include when I do a manual backup using XCloner.
7:15 pm
September 26, 2010
Offline
To backup the extra databases, you need to select them inside the XCloner Config -> Cron tab, additonal databases area
Hope it helps! Ovidiu
7:52 pm
February 17, 2011
Offline
Hello again. Thanks for your feedback.
Okay, here is what I just did.
I logged into the XCloner config panel.
After clicking on the "Configuration" link, I clicked on the "Cron" tab.
In the "Cron" tab window, I wasn't sure what to do, so I left the "Configuration Name" field blank, being as there is already a file name terminating in ".php" in the command that I added to my cron tab using the Cronnix program on the host machine.
I also left the email field -- and most of the other fields -- blank as well.
All I did was select all of my other databases in the "Mysql Options" section, and I set "Delete older backups" to three days.
After that, I clicked on the "Save" button.
XCloner stated that my configuration had been updated.
After that, I went to the actual machine where I have WP and Cronnix installed.
I manually ran the cron job using Cronnix, in order to see what would happen.
While it was running, I watched the "administrator/backups/" directory to see what would happen.
A new WP backup was created, as well as backups of the other databases as well.
However, once the backup completed, the other files disappeared from the directory.
It was only after I expanded the newly created .tar file, that I realized that XCloner had actually packaged everything nicely -- including the other databases -- in the same .tar file.
In other words, before, when I was doing the backups manually, it would only compress the actual WP blog files, while all of the other databases were left apart, and uncompressed.
At any rate, as I said, I did this manually using Cronnix, and it appears to work great. Later today will come the real test when a scheduled cron job occurs. Hopefully, everything will go smoothly, as it just did.
If not, I'll let you know.
Thanks again for your help, and your plugin. It is a real time saver, and gives me peace of mind, knowing that I won't lose any data due to corruption in my mySQL databases, or whatever.
1 Guest(s)
