|
|
|
|
|
|
|
|
|
 Posted: Wed Aug 13, 2008 8:57 pm
Like the title says, what do you look for in at backup program? The reason I am asking is because I am looking for new ideas to implement into my backup program and I though maybe I should ask what is most wanted from a backup program.
|
 |
|
|
|
|
|
|
|
|
|
|
|
|
|
Posted: Tue Aug 04, 2009 12:18 am
I'd really kill for a program that creates standalone backups, that is, backups that don't require the original app to read them. This is exactly why I never use real backup tools and always end up using plain archives: what if the program ceases to exist or it won't install in my computer?
Notice that I say this as someone who has no idea of how to make a real backup solution... I don't know if implementing this feature is easy or hard confused
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Posted: Wed Aug 05, 2009 9:30 pm
My backup strategy?
Hourly SVN or Git check-in with nightly push to a remote file server. (Only on certain directories.)
OR
tar (optionally piped to bzip2)
sometimes dd (similarly piped)
OR
AMANDA (Actually, I haven't done this yet, but it's in the pipe for the next major maintenance update of my primary server... which will happen some time after Slackware 13 drops.)
Edit: Instead of Bash, have you considered using Bourne Shell? It will make your script far more portable (and I can't imagine you'd need any Bash-isms in such a simple utility).
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Posted: Fri Aug 07, 2009 2:33 pm
-Ability to set time intervals for automatic backup.
-Ability to back up on more than one device simultaneously, with the possibility of setting different intervals (per device) if necessary.
-Notification that said backup is occurring (with possible status bar), as well as in the event that other errors occur.
-Ability to set between auto backup, and manual backup (IE Automatically backup a selected folder if any new content was last added to it, or to do so only during the timed interval.)
Tall orders, but that's what I'd like to see.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Posted: Fri Aug 28, 2009 6:57 am
Da_Nuke I'd really kill for a program that creates standalone backups, that is, backups that don't require the original app to read them. This is exactly why I never use real backup tools and always end up using plain archives: what if the program ceases to exist or it won't install in my computer? Notice that I say this as someone who has no idea of how to make a real backup solution... I don't know if implementing this feature is easy or hard confused That is what my backup script does, it creates a bziped/gziped tar archive that can be unarchived on any Linux system 3nodding (compression is user choice when you first run the script, and can be changed at anytime)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Posted: Fri Aug 28, 2009 7:04 am
Sitwon My backup strategy? Hourly SVN or Git check-in with nightly push to a remote file server. (Only on certain directories.) OR tar (optionally piped to bzip2) sometimes dd (similarly piped) OR AMANDA (Actually, I haven't done this yet, but it's in the pipe for the next major maintenance update of my primary server... which will happen some time after Slackware 13 drops.) Edit: Instead of Bash, have you considered using Bourne Shell? It will make your script far more portable (and I can't imagine you'd need any Bash-isms in such a simple utility). I have not considered using Bourne Shell, I figured because Bash was Bourne's predecessor and the fact that every modern distro I have seen has Bash it would be a good choice, and the Bash-isms are there to help with portability.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Posted: Thu Sep 17, 2009 1:49 pm
vendion Gear Sitwon My backup strategy? Hourly SVN or Git check-in with nightly push to a remote file server. (Only on certain directories.) OR tar (optionally piped to bzip2) sometimes dd (similarly piped) OR AMANDA (Actually, I haven't done this yet, but it's in the pipe for the next major maintenance update of my primary server... which will happen some time after Slackware 13 drops.) Edit: Instead of Bash, have you considered using Bourne Shell? It will make your script far more portable (and I can't imagine you'd need any Bash-isms in such a simple utility). I have not considered using Bourne Shell, I figured because Bash was Bourne's predecessor and the fact that every modern distro I have seen has Bash it would be a good choice, and the Bash-isms are there to help with portability. You have that backwards. Bourne shell was the orignal, Bash is Bourn shell with some nifty extra features. Bashisms can get you into real trouble sometimes, Especially if you put #!/bin/sh at the top of you scripts instead of #!/bin/bash. Debian and it's derivatives (eg. Ubuntu) use Dash instead of Bash as the default shell so your #!/bin/sh scripts get run through a shell that will choke on most Bashisms. Bourne shell is always the safe choice because it's compatible with Bash, Dash, Ash, Korn shell (ksh) and their derivatives.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Reply
