Submitted by ChrisBlackwell on Thu, 02/18/2010 - 06:06
It would be really useful to be able to assign multiple backup destinations to a single scheduled backup. For example, a nightly backup that saves the file to a local drive and an ftp location.
Currently you have to define multiple scheduled backups, one for each destination required, which causes the backup routine to execute multiple times. This puts unnecessary load on the server and means that the backups to each location can not be guaranteed to be identical (e.g db changes)
There is a work around which is to backup to a local location, then use the post-backup command to copy files to your required destinations, but this requires a knowledge of shell scripting which should not be necessary.
Status:
Closed (fixed)
Comments
Submitted by JamieCameron on Thu, 02/18/2010 - 17:56 Comment #1
That's not a bad idea .. I have added this to my TODO list.
Submitted by juicymedia on Wed, 07/28/2010 - 05:07 Pro Licensee Comment #2
Yeah, this would be great new feature - just about to post the same request. In particular if you could choose a combination such as S3 and FTP.
As Chris states, the current best option is the post backup command.
Submitted by clwheatley on Thu, 08/26/2010 - 12:46 Comment #3
Jamie,
Any ETA or update on this feature?
Submitted by JamieCameron on Thu, 08/26/2010 - 15:27 Comment #4
Sorry, but I haven't done any work on it yet ..
Submitted by clwheatley on Thu, 08/26/2010 - 16:13 Comment #5
No need to apologize. With all the development you guys are doing, I am sure your to do list is fairly long. What would be nice to know is if you have any guestimate about when this could be rolled out? 3.81, 3.82, etc,...
Submitted by JamieCameron on Thu, 08/26/2010 - 16:19 Comment #6
I'd say version 3.82
Submitted by JamieCameron on Thu, 10/14/2010 - 16:32 Comment #7
Implementation of this feature has just been completed, and will be in Virtualmin 3.82.
Submitted by clwheatley on Tue, 10/19/2010 - 12:57 Comment #8
Thanks Jamie.
Submitted by Issues on Tue, 11/02/2010 - 15:20 Comment #9
Automatically closed -- issue fixed for 2 weeks with no activity.