more backup / retore options + cron

[infiltrator]

system backup:
1 ) i'd like to be able to backup the server with different options like there is availeble now.

2 ) i'd like to add more then 1 backup job, so i can backup the mysql dayly , but also the user pages on weekly base

3 ) i'd like to see what backup jobs are currently running / sheduled and have the option to delete / edit them.

4 ) the admin/ user backup: i'd like to also store it local and have the option to copy it on a ftp server , so i have 2 copy's. Also cleaning the old backup files localy.

5) i'd like the option to clean backup's ( system backup or admin / user backups ) but with an time you can set, like i would be able to auto clean files older then a week / month / ? days...

6) i'd like a great restore function, now i cant restore system backups made through system backup...

7) i'd like a restore system that can restore parts of a backup...

 

[nobaloney]

The system backup has been deprecated for general use for some time now, since the Admin reseller backup was created. It's left in the system because it's useful for backing up non-user-level files.

One of it's main problems is that it's really impossible to create an automated restore for it; there are too many variables involved.

Jeff

 

[infiltrator]

Then i'd like more options for users...

example, i have several websites on my server , a few highly visited and more not.

i'd like to backup all the mysql data dayly for the whole server, but the pages weekly, becourse pages dosent change that often..

Now you can only choose a user, so you have to backup the whole user dayly if you want it backup up...

i have a user with +2.5gig backup... and other around 1gig...
dayly base..
after a week....
my hard disk issent very large...

If the backup system dont use different dirs a day, the backups get overwritten, so thats also no good...

1 website was hacked, but only seen after 1.5 days, if there was not a backup from before the hack...

 

[floyd]

If the backup system dont use different dirs a day, the backups get overwritten, so thats also no good...

This has been discussed before. Create a backup folder for each day of the week and create a different cron job to run the backup each day to backup to the corresponding folder for the day. 7 days of backup, very easy.

 

[infiltrator]

Cool thx again...

 

[floyd]

you can also create a cron job to do just a mysqldump every day for just backing up the databases.

 

[congkai]

well, i think DA has to implement better backup system.. seriously.

or maybe setup a Rsync easilly? i have a hard time setting up Rsync year back... and make me give up in trying..

 

[BLAST3R]

I'd second that, maybe something to make load balancing and redundancy easier to be realized. If I'm not mistaken Cpanel already had such feature.

 

[asmar]

This has been discussed before. Create a backup folder for each day of the week and create a different cron job to run the backup each day to backup to the corresponding folder for the day. 7 days of backup, very easy.

What about if you want to keep a whole month of backups?
Any quick solution?

 

[nobaloney]

Same thing; create more folders and more cronjobs. Or one cronjob complex enough to figure out which bckup to run.

You can also rotate automatically.

Jeff

 

[mmgenius]

I also would find it usefull if you could setup local AND ftp backup together. Because now we do a local backup and after it a ftp backup, but then he needs to create 2 times the .tar.gz files. Better should be that he does a local backup and if he is finished he does a ftp-copy, then he only needed to create the .tar.gz file 1 time. (or can you do it with the ..._post.sh custom scripts?)

 

[DirectAdmin Support]

Hello,

It can currently be done with the user_backup_post.sh:
http://www.directadmin.com/features.php?id=951

copy the $file to another location on disk.

This script is run before the backup is transferred via ftp, fyi, so you can't just rename the tar.gz to save some disk access hits.

If there is enough demand, I can also add a checkbox option in the backup settings at the bottom of each backup page to not delete after an ftp upload. However DA currently creates ftp backups in /home/tmp/reseller/user.tar.gz before upload, so leaving them there isn't really an option. They'd have to be moved either way and DA would need to know where they're supposed to be moved to. I guess it could assume to /home/Reseller/user_backups for Resellers, and /home/Admin/admin_backups for Admins.

John

 

[mmgenius]

If you would change it, I think the best thing is that you just change the radio-buttons (name=where) in step 3 (in front of 'Local' and 'Ftp') with checkboxes. So you can backup 'local', 'ftp' or 'local + ftp'. In the 2 first cases nothing changes, and in the last case ('local + ftp') he just makes the local file and afterwards he copy it with ftp.

 

[wattie]

Sorry for reviving such old thread, but "I can also add a checkbox option in the backup settings at the bottom of each backup page to not delete after an ftp upload." will be a great addition.