Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I need to find some backup software to save some of data offsite. We have a new server with a lot of space set up in a new data center and we need to find some software that will let us save some data to it remotely. Here are the requirements for the software.
-scp from linux
-scp from windows
-email notifications
-scheduling
-compress before sending
if anyone know some good backup software ,please let me know.
thanks!
Most admins I know simply write their own scripts to do this. Linux Backup Software is kind of an oximoron; unless you are backing up Windows' registry and locked files, then you'll need special software for that.
Basically you can create tarballs and copy it over to a remote computer or external USB drive. Unlike Windows, tar copies most files even if they are locked. google 'Linux backup scripts'. You may want to get yourself familiar with writing bash scripts.
Why would you use tarballs? Wouldn't running rsync be enough? I admit that I am not doing offsite with rsync right now but I run rsync in a script to back everything up daily to a removable harddrive. The first time it took hours to back up the server this way (about 70gb worth) but the daily routine takes only 5 minutes now. If tarballs were used, I would think the total process time would increase (ie first make the tarballs, then rsync to external site or drive and since the tarball changed, the whole thing would need to be transfered). Would that be correct?
For an rsync script, here is what I use. Now, this is for backup to a removable harddrive, not a external site. If you search on the internet or check out http://samba.anu.edu.au/rsync/ you can figure out how to make this an off site backup.
Code:
#Backup-Script-0.1.sh
#First mount the drive to the /backup folder
mount /dev/sda2 /backup/
#Now the actual rsync call
sudo rsync -av --exclude-from=/path-to-where-my-script-lives/Backup-exclude --delete // /backup/
# Unmount the external drive
umount /dev/sda2
The exclude section ensures that some files aren't backedup. Note, the directory "/backup/" is in the excludes because that is where I mount the external harddrive during the backup.
This isn't by any means perfect but it has worked quite well so far. Much of this I got from this site. I can't find the thread where it was but it is here somewhere.
Why would you use tarballs? Wouldn't running rsync be enough? I admit that I am not doing offsite with rsync right now but I run rsync in a script to back everything up daily to a removable harddrive. The first time it took hours to back up the server this way (about 70gb worth) but the daily routine takes only 5 minutes now. If tarballs were used, I would think the total process time would increase (ie first make the tarballs, then rsync to external site or drive and since the tarball changed, the whole thing would need to be transfered). Would that be correct?
I'd agree not using tarballs every single day. That's just making daily full backups which takes up space.
In my own setup for my personal servers, I have a full weekly script that creates larger tarballs and all other days I have an rsync script that makes the incremental changes.
Why would you use tarballs? Wouldn't running rsync be enough?
rsync stands for remote sync and it does not compress. rsync is better for small non-compressed backups of a few megabytes, but it is not good by itself for full backups of 70GB; then you'll need to compress. rsync is designed to syncronize files in separate systems. Hence the 'sync' in the name. tar stands for Tape Archiver. It was created decades ago exclusively for backing up to tape on Unix systems.
For daily differential or incremental backups use 'find' and 'tar'.
With find you can discover all the files that are less than one day old or less than a week old then you pipe it onto tar to compress and store the tarball onto a remote drive or tape. That's the way most guru's do it.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.