[opensuse] Backing Up Via rsync
I am currently backing up my OSE12.3 to an external SAS hard drive using this rsync command: /usr/bin/rsync -avWHu --delete --exclude-from=/root/rsync.excludes / /external/ose3/ where /root/rsync.excludes currently contains: /external /lost+found /media /mnt /proc /sys /var/lib/ntp/proc Are there additional entries I should be excluding such as /run, /var/run, /var/spool, etc? I want to be able to restore the system from the backup, possibly using Relax and Recover (which did a fantastic job of restoring a Liinux VM at work using NetBackup). Thank you, Lucky Leavell -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Am 08.12.2013 18:58, schrieb SuSE List:
I am currently backing up my OSE12.3 to an external SAS hard drive using this rsync command:
/usr/bin/rsync -avWHu --delete --exclude-from=/root/rsync.excludes / /external/ose3/
where /root/rsync.excludes currently contains:
/external /lost+found /media /mnt /proc /sys /var/lib/ntp/proc
Are there additional entries I should be excluding such as /run, /var/run, /var/spool, etc?
Additionally I also exclude /tmp/* /dev/* /var/tmp/* /var/spool/* /var/cache/* /var/lock/* /var/run/* /var/lib/ntp/* /run/* Daniel -- Daniel Bauer photographer Basel Barcelona professional photography: http://www.daniel-bauer.com google+: https://plus.google.com/109534388657020287386 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Le 08/12/2013 18:58, SuSE List a écrit :
Are there additional entries I should be excluding such as /run, /var/run, /var/spool, etc?
here my notes :-) http://dodin.info/wiki/index.php?n=Doc.Sauvegarde-complete jdd -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Sunday 08 of December 2013 12:58:56 SuSE List wrote:
I am currently backing up my OSE12.3 to an external SAS hard drive using this rsync command:
/usr/bin/rsync -avWHu --delete --exclude-from=/root/rsync.excludes / /external/ose3/
where /root/rsync.excludes currently contains:
/external /lost+found /media /mnt /proc /sys /var/lib/ntp/proc
Are there additional entries I should be excluding such as /run, /var/run, /var/spool, etc?
These directories, except for /lost+found and /var/spool, can be automatically excluded with the option -x, which prevents traversing across file-system boundaries. This includes possible chrooted environments, /dev etc. Note that If /boot is on a different filesystem and you need it backed up, you'll have to include it explicitly.
Thank you, Lucky Leavell
Regards, Peter -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Mon, 09 Dec 2013, SuSE List wrote:
I am currently backing up my OSE12.3 to an external SAS hard drive using this rsync command:
/usr/bin/rsync -avWHu --delete --exclude-from=/root/rsync.excludes / /external/ose3/
where /root/rsync.excludes currently contains:
/external /lost+found /media /mnt /proc /sys /var/lib/ntp/proc
Are there additional entries I should be excluding such as /run, /var/run, /var/spool, etc?
I want to be able to restore the system from the backup, possibly using Relax and Recover (which did a fantastic job of restoring a Liinux VM at work using NetBackup).
Thank you, Lucky Leavell
I normally add -X to my rsync. This preserves extended attributes. I think selinux uses them in / -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 12/08/13 20:20, Michael Hamilton wrote:
On Mon, 09 Dec 2013, SuSE List wrote:
I am currently backing up my OSE12.3 to an external SAS hard drive using this rsync command:
/usr/bin/rsync -avWHu --delete --exclude-from=/root/rsync.excludes / /external/ose3/
where /root/rsync.excludes currently contains:
/external /lost+found /media /mnt /proc /sys /var/lib/ntp/proc
Are there additional entries I should be excluding such as /run, /var/run, /var/spool, etc?
I want to be able to restore the system from the backup, possibly using Relax and Recover (which did a fantastic job of restoring a Liinux VM at work using NetBackup).
Thank you, Lucky Leavell
I normally add -X to my rsync. This preserves extended attributes. I think selinux uses them in /
And -A is missing, otherwise ACLs get lost. Concerning the list of above directories (if one doesn't use -x, beyond the additions of Daniel Bauer), some people have automounter active for /net. Then it should be excluded as well. Cheers, Joachim -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Joachim Schrod, Roedermark, Germany Email: jschrod@acm.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
I'm used to rsync my home directory to external disc. I also use YaST backup module (I think I can recommend it) to backup any other system data. I then rsync regular backup together with my data. So that I can restore software, settings etc using YaST and my data with rsync. It could make Your backing up easier. All the best, Vojtěch Dne Ne 8. prosince 2013 12:58:56, SuSE List napsal(a):
I am currently backing up my OSE12.3 to an external SAS hard drive using this rsync command:
/usr/bin/rsync -avWHu --delete --exclude-from=/root/rsync.excludes / /external/ose3/
where /root/rsync.excludes currently contains:
/external /lost+found /media /mnt /proc /sys /var/lib/ntp/proc
Are there additional entries I should be excluding such as /run, /var/run, /var/spool, etc?
I want to be able to restore the system from the backup, possibly using Relax and Recover (which did a fantastic job of restoring a Liinux VM at work using NetBackup).
Thank you, Lucky Leavell
-- Vojtěch Zeisek Komunita openSUSE GNU/Linuxu Community of the openSUSE GNU/Linux http://www.opensuse.org/ http://trapa.cz/
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 12/9/2013 6:15 AM, Vojtěch Zeisek wrote:
I'm used to rsync my home directory to external disc. I also use YaST backup module (I think I can recommend it) to backup any other system data. I then rsync regular backup together with my data. So that I can restore software, settings etc using YaST and my data with rsync. It could make Your backing up easier. All the best, Vojtěch
Its probably redundant for the people on this list, but, at the risk of sounding pedantic, I'll toss it out anyway: Rsync isn't a backup tool. You can delete a mountain of stuff, corrupt a zillion files, and not notice it till AFTER the next rsync run, which will dutifully clobbers your backup in the same way. For years I've been running the (non-free, not cheep) BRU, (tolisgroup.com) and stacking compressed backups on an external drive. I can get a year's worth of backups on that drive. I backup system areas once a month, and user space + data storage daily (changed files only) as well as monthly (all user+data files). Side note: Having moved to Linux from a Novel Netware environment, I really missed the "Salvage" facility that Novel had. It would keep multiple copies of changed files so you could step backward through each changed version of a file till you found the last known good version. So I wrote a little shell script to copy user+critical-data every 10 minutes to a salvage area each date-stamped. It is self maintaining in that it removes the "salvage" files after a period of time sufficient for the the BRU backup to captures them. The storage is requirement is surprisingly minimal. - -- _____________________________________ - ---This space for rent--- -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (MingW32) iEYEARECAAYFAlKmIrkACgkQv7M3G5+2DLJwbQCeIZruQ6qNLG4ab3RBciRpz6dm D58AmQGABdkJsfLS6vMUYFKT4YucyNGQ =zdy2 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 12/9/2013 3:06 PM, John Andersen wrote:
Rsync isn't a backup tool. a rose by any other name... It does make a nice backup tool for me.
You can delete a mountain of stuff, corrupt a zillion files, and not notice it till AFTER the next rsync run, which will dutifully clobbers your backup in the same way. I understand that risk. I have at least partially accounted for that in my setup by having a two stage backup. I have three disk drives; drive 1 for the main drive, drive 2 for backup number 1 and drive 3 for backup number 2. each night I rsync drive 2 to drive 3, then rsync drive 1 to drive 2. It gives me one day to realize that I did something stupid. I believe that there were two occasions over the years where I made such a mistake and was able to recover from the third drive.
OK, so it isn't a perfect setup but it works nicely as a backup tool for me.
Having moved to Linux from a Novel Netware environment, I really missed the "Salvage" facility that Novel had. It would keep multiple copies of changed files so you could step backward through each changed version of a file till you found the last known good version. reminds me of VAX/VMS. I did like that version feature.
Damon Register -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Damon Register wrote:
On 12/9/2013 3:06 PM, John Andersen wrote:
Having moved to Linux from a Novel Netware environment, I really missed the "Salvage" facility that Novel had. It would keep multiple copies of changed files so you could step backward through each changed version of a file till you found the last known good version. reminds me of VAX/VMS. I did like that version feature.
Reminds me of GEORGE 3 :) It had the feature over a decade earlier. Dunno whether MULTICS had it? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 12/11/2013 04:34 AM, Dave Howorth wrote:
Damon Register wrote:
On 12/9/2013 3:06 PM, John Andersen wrote:
Having moved to Linux from a Novel Netware environment, I really missed the "Salvage" facility that Novel had. It would keep multiple copies of changed files so you could step backward through each changed version of a file till you found the last known good version. reminds me of VAX/VMS. I did like that version feature. Reminds me of GEORGE 3 :)
It had the feature over a decade earlier. Dunno whether MULTICS had it? Take at look at btrfs and zfs. I believe they both have these features/
-- Joseph Loo jloo@acm.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2013-12-11 13:57, Joseph Loo wrote:
On 12/11/2013 04:34 AM, Dave Howorth wrote:
Damon Register wrote:
On 12/9/2013 3:06 PM, John Andersen wrote:
reminds me of VAX/VMS. I did like that version feature. Reminds me of GEORGE 3 :)
It had the feature over a decade earlier. Dunno whether MULTICS had it? Take at look at btrfs and zfs. I believe they both have these features/
Not really, you have to tell the system to make a snapshot. On vax, you edited a file several times, and you got several copies of the same file in its own directory. If I recall correctly, named like this: file.txt;1 file.txt;2 file.txt;3 as many versions as the admin had configured, automatically. -- Cheers / Saludos, Carlos E. R. (from 12.3 x86_64 "Dartmouth" at Telcontar)
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 12/11/2013 5:50 AM, Carlos E. R. wrote:
On 2013-12-11 13:57, Joseph Loo wrote:
On 12/11/2013 04:34 AM, Dave Howorth wrote:
Damon Register wrote:
On 12/9/2013 3:06 PM, John Andersen wrote:
reminds me of VAX/VMS. I did like that version feature. Reminds me of GEORGE 3 :)
It had the feature over a decade earlier. Dunno whether MULTICS had it? Take at look at btrfs and zfs. I believe they both have these features/
Not really, you have to tell the system to make a snapshot.
On vax, you edited a file several times, and you got several copies of the same file in its own directory. If I recall correctly, named like this:
file.txt;1 file.txt;2 file.txt;3
as many versions as the admin had configured, automatically.
When we wrote our "salvage" replacement script, we tried putting them in the current directory as hidden files, with date stamped extensions but abandoned this fairly early. The reasons are lost to history, but I think it caused too much directory clutter if you ever turned on "show hidden" and people's eyeballs exploded. Or it might have been that we were keeping our salvage copies on a different drive. Like I say, we've been doing it for in excess of 20 years since we moved off of Netware. - -- _____________________________________ - ---This space for rent--- -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (MingW32) iEYEARECAAYFAlKosK4ACgkQv7M3G5+2DLKzOgCgkc9R/yamVBkAC80iARf0nMDx 3b8AoKW489fh3L30Yg2UkR4OdOP0+ea4 =+KpD -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Le 09/12/2013 21:06, John Andersen a écrit :
Rsync isn't a backup tool.
You can delete a mountain of stuff, corrupt a zillion files, and not notice it till AFTER the next rsync run, which will dutifully clobbers your backup in the same way.
the problem is not rsync (you can use it and never delete anything), but the target of the copy. Anything writable online can be corrupted. a real backup is tightly depending of the use one have high availability, small chunks of data versus large data files... the best backup, but probably the more expensive is professional external write only backup (you write your backup to professional server). I have an host that can even make mirrors through datacenters (the two copies may be on different continents) but, for example, I have a cron / rsync backup of the server of my LUG on my own server and it's perfectly enough for this purpose jdd -- http://www.dodin.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Monday 09 of December 2013 12:06:17 John Andersen wrote:
Rsync isn't a backup tool.
I've been using it for years as a backup tool and it serves this purpose fine.
You can delete a mountain of stuff, corrupt a zillion files, and not notice it till AFTER the next rsync run, which will dutifully clobbers your backup in the same way.
Agreed, but this does not mean it isn't a backup tool.
Having moved to Linux from a Novel Netware environment, I really missed the "Salvage" facility that Novel had. It would keep multiple copies of changed files so you could step backward through each changed version of a file till you found the last known good version.
So I wrote a little shell script to copy user+critical-data every 10 minutes to a salvage area each date-stamped. It is self maintaining in that it removes the "salvage" files after a period of time sufficient for the the BRU backup to captures them. The storage is requirement is surprisingly minimal.
rdiff-backup does something similar. It takes a full backup, then incremental with diffs against the full backup, which saves a lot of space, and you can set the number of incrementals to preserve. This way I keep several months of versions of important files. Btrfs should make this easier and more robust in the future. Be warned that the last version of rdiff-backup was released in 2009 and it appears not to be maintained any more. Regards, Peter -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 12/09/2013 02:06 PM, auxsvr@gmail.com wrote:
Be warned that the last version of rdiff-backup was released in 2009 and it appears not to be maintained any more.
I've been using rdiff-backup for years! Are there any alternatives if/when it finally breaks? Regards, Lew -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Monday 09 of December 2013 14:22:04 Lew Wolfgang wrote:
I've been using rdiff-backup for years! Are there any alternatives if/when it finally breaks?
btrfs with snapper should have the essential features of rdiff-backup, but I'm not sure how robust or mature they are at the moment. It also has the advantage that the backups are done atomically.
Regards, Lew
Regards, Peter -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 12/9/2013 2:35 PM, auxsvr@gmail.com wrote:
On Monday 09 of December 2013 14:22:04 Lew Wolfgang wrote:
I've been using rdiff-backup for years! Are there any alternatives if/when it finally breaks?
btrfs with snapper should have the essential features of rdiff-backup, but I'm not sure how robust or mature they are at the moment. It also has the advantage that the backups are done atomically.
Regards, Lew
Regards, Peter
But wait, isn't the btrfs snapper simply snapshots on the same drive? That's hardly the same thing as a differential backup. -- _____________________________________ ---This space for rent--- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Monday 09 of December 2013 14:45:34 John Andersen wrote:
But wait, isn't the btrfs snapper simply snapshots on the same drive? That's hardly the same thing as a differential backup.
Yes, however, if both filesystems are btrfs, then snapshots can be transferred across volumes with the send/receive function. I'm not sure whether snapper supports this or not. I mentioned snapper, because it maintains limits for the number of snapshots per time period, just like rdiff-backup, and it is supposed to make the entire process more user-friendly. Regards, Peter -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 12/09/2013 02:35 PM, auxsvr@gmail.com wrote:
On Monday 09 of December 2013 14:22:04 Lew Wolfgang wrote:
I've been using rdiff-backup for years! Are there any alternatives if/when it finally breaks? btrfs with snapper should have the essential features of rdiff-backup, but I'm not sure how robust or mature they are at the moment. It also has the advantage that the backups are done atomically.
Maybe it's just me, but I rather like the UNIX concept of simple and small tools that can be combined for more complicated tasks. A differential backup system built into an already rather complicated file system would make me nervous. For example, would one be able to read btrfs/snapper backups 10-years from now on a completely foreign and not yet existing file system? As an aside, once upon a time I asked Hans Reiser how to do backups of a Reiserfs file system. It doesn't have dump/restore after all. He got rather huffy and said that tar will work just fine, thank you. Regards, Lew -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 12/9/2013 3:12 PM, Lew Wolfgang wrote:
As an aside, once upon a time I asked Hans Reiser how to do backups of a Reiserfs file system. It doesn't have dump/restore after all. He got rather huffy and said that tar will work just fine, thank you.
If he gets huffy answering the obvious, one can only wonder what his wife asked him. /running and ducking..... -- _____________________________________ ---This space for rent--- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 12/09/13 23:22, Lew Wolfgang wrote:
On 12/09/2013 02:06 PM, auxsvr@gmail.com wrote:
Be warned that the last version of rdiff-backup was released in 2009 and it appears not to be maintained any more.
I've been using rdiff-backup for years! Are there any alternatives if/when it finally breaks?
How about dirvish? http://www.dirvish.org/ It's the standard backup tool of Debian. It's not developed further either; but IMO that's because it's finished. Joachim -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Joachim Schrod, Roedermark, Germany Email: jschrod@acm.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Personally, this is the shell script I use to back up my server at home. It backs up to an external USB drive that's been encrypted with TrueCrypt. One copy sits in the lock box at the bank, and the other is at home being used, and they're rotated out regularly. That way if a tornado hits our house or whatever, we'll have fairly recent data stored somewhere safe. I decided to encrypt the backup volume so that if the drive gets stolen out of the car or whatever, they won't be able to do anything nefarious with our stuff. #!/bin/bash #Make sure that script isn't already running; die if it is. SCRIPTNAME=`basename $0` PIDFILE=/var/run/${SCRIPTNAME}.pid if [ -f ${PIDFILE} ]; then #verify if the process is actually still running under this pid OLDPID=`cat ${PIDFILE}` RESULT=`ps -ef | grep ${OLDPID} | grep ${SCRIPTNAME}` if [ -n "${RESULT}" ]; then echo "Backup already running! Exiting." exit 255 fi fi #grab pid of this process and update the pid file with it PID=`ps -ef | grep ${SCRIPTNAME} | head -n1 | awk ' {print $2;} '` echo ${PID} > ${PIDFILE} mount | grep backup > /dev/null if [ ! "$?" -eq "0" ]; then echo Mounting Backup volume /usr/bin/truecrypt -d echo Some_Magic_Password_For_Truecrypt_Goes_Here | /usr/bin/truecrypt -t -k '' --protect-hidden=no /dev/sdc1 /mnt/backup/ fi mount | grep backup > /dev/null if [ ! "$?" -eq "0" ]; then echo Backup volume not mounted, fail. exit 2 fi echo Getting installed package list... /bin/rpm -qa | /bin/sort > /home/backup/installed_packages.lst echo Starting backup... #r = recursive #l = preserve symlinks #p = preserve permissions #t = preserve mod times #g = preserve group #D = preserve device and special files #v = verbose #H = preserve hard links #h = human-readable #X = preserve extended attributes #E = preserve executability #A = preserve ACLs #o = preserve owner /usr/bin/rsync -rlptgDEvHhXAo --delete --delete-excluded --exclude-from /home/scripts/backup.lst / /mnt/backup/files/ echo Backup finished. echo echo df -hx tmpfs #Automatically run fsck on the volume on the first day of the month so that it won't complain #about the volume being mounted so many times without being fsck'd set `date +%d` TODAY=$1 if [ $TODAY -eq 1 ] then echo . echo . echo First day of month, running fsck. umount /mnt/backup #unmounting volume so that we can fsck it volraw=`/usr/bin/truecrypt -l` #get the truecrypt volume list volnum=`echo $volraw | /bin/sed -e 's/.*\/dev\/mapper\/truecrypt\([0-9]\+\).*/\1/g'` #figure out what volume is mounted tcvol=/dev/mapper/truecrypt${volnum} /sbin/fsck -p -f $tcvol fi echo Unmounting backup volume. /usr/bin/truecrypt -d echo Spinning down the hard drive HD=`/usr/bin/sg_map | /bin/grep sdc | /bin/awk '{print $1}'` /sbin/sdparm -C stop $HD mount | grep backup > /dev/null if [ ! "$?" -eq "0" ]; then echo Backup volume unmounted. fi if [ -f ${PIDFILE} ]; then rm ${PIDFILE} fi The exclude file is as such: #include + /dev/console + /dev/initctl + /dev/null + /dev/zero #exclude - /proc/* - /tmp/* - /backup/* - /dev/* - /sys/* - /mnt/* - lost+found/ - /.journal - /.fsck - /var/lib/named/proc/* - /var/lib/ntp/proc/* - /var/run/* - /var/tmp/* - /var/spool/* - /var/cache/* - /var/lock/* - /run/* - /home/isos/* I run it via cron at 3am, and have it mail me the results: #Backup server hard drive 0 3 * * * /home/scripts/backup.sh | mail -s 'Daily rsync report' my_email_address@domain.com -- -r 'root@myserver.com' -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 12/09/2013 11:15 PM, Christopher Myers wrote:
Personally, this is the shell script I use to back up my server at home. [...]
I also use a little wrapper around "rsync", and have 24 hourly, 7 daily, 4 weekly and 12 monthly backups of my /home partition. The crucial part about such scripts is race conditions: what happens if the machine goes down in the middle of such a backup? Will the next run create a full-blown fresh copy? Or will it cripple older backups? The question with backups is always: against what do you want to protect yourself? Against randomly overwritten/deleted files? Disk failure? Fire? ...? You always have to find the solution which fits your needs. An frequent, incremental backup to a distant machine would probably always be the best, but then you have to think about other issues like bandwidth and security during/after transfer. Never ending discussion, though. Have a nice day, Berny -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
John Andersen said the following on 12/09/2013 03:06 PM:
Having moved to Linux from a Novel Netware environment, I really missed the "Salvage" facility that Novel had. It would keep multiple copies of changed files so you could step backward through each changed version of a file till you found the last known good version.
One of the problems I've faced over the decades of trying to move people to UNIX and Linux from other systems, VMS, RSTS, and even MS-Windows is that while there are tools and facilities that do the same job, often do the job better, they do it differently, have a different name, or a different UI/Gui. Sometimes the context is different and issue the tool on the old system simply doesn't exist on UNIX/Linux because the need is not there. Sometimes this bites in a different way. A recruiter might want want someone with "Websphere" experience and not realise that means "apache" + "java" + CORBA + MQ and some connector/server stuff. Some people have a hangup about names. The thing is that Linux does have a backup facility that keeps however many copies you tell it of whatever files you tell it, if your file system supports the capability of notifying the kernel when a file is changed. Some FS won't tell the system when things change. Don't ask this of NTFS! Default is things changed when Yast/Zypper installs a new item or update so that you can roll it back, but there's no reason you can't set it up as a 'poor mans CVS'. Of course using a proper development GUI/UI rather than the manual shell/vi/cc appraiser might automate things as well. It may have many other advantages as well. One of my buzz-lines is "Context is everything" and the mechanisms built in to late-model file systems, LVM, RAID as well as SDKs might address specific contexts more suitably than traditional backup models. I've seen 'traditional' backup models which are not aligned with business needs actually disrupt business operations. If you have the hangup about names you might want to make use of the aliasing mechanisms available with Linux or write a shell wrapper for the utility called 'snapper'. Never forget, its not the backup process that counts, its the ability to restore business operations that matters. -- When you know that you're capable of dealing with whatever comes, you have the only security the world has to offer . -- Harry Browne -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Mon, 2013-12-09 at 12:06 -0800, John Andersen wrote:
On 12/9/2013 6:15 AM, Vojtěch Zeisek wrote:
I'm used to rsync my home directory to external disc. I also use YaST backup module (I think I can recommend it) to backup any other system data. I then rsync regular backup together with my data. So that I can restore software, settings etc using YaST and my data with rsync. It could make Your backing up easier. All the best, Vojtěch
Its probably redundant for the people on this list, but, at the risk of sounding pedantic, I'll toss it out anyway:
Rsync isn't a backup tool.
..
So I wrote a little shell script to copy user+critical-data every 10 minutes to a salvage area each date-stamped. It is self maintaining in that it removes the "salvage" files after a period of time sufficient for the the BRU backup to captures them. The storage is requirement is surprisingly minimal.
Just wondering.. A couple of time i noticed people scripting around rsync for doing backups. Isn't rsnapshot supposed to be the tool for doing this? Hans -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 11/12/13 21:45, Hans Witvliet wrote:
Just wondering.. A couple of time i noticed people scripting around rsync for doing backups. Isn't rsnapshot supposed to be the tool for doing this?
It's what I use here. And http://www.tarsnap.com for offsite backups. Bob - -- Bob Williams System: Linux 3.7.10-1.16-desktop Distro: openSUSE 12.3 (x86_64) with KDE Development Platform: 4.11.4 Uptime: 18:00pm up 7 days 6:07, 3 users, load average: 0.04, 0.16, 0.22 -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlKo46oACgkQ0Sr7eZJrmU5LWACfaU7VHUCRgUZRNbQ8kXsIwjoU /HUAn22AeDxL9d29sy0i3flkCCUEnEo5 =4kvX -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2013-12-11 22:45, Hans Witvliet wrote:
On Mon, 2013-12-09 at 12:06 -0800, John Andersen wrote:
Just wondering.. A couple of time i noticed people scripting around rsync for doing backups. Isn't rsnapshot supposed to be the tool for doing this?
Yes, rsnapshot uses rsync. But you may want to do it your own way, so you do your own script. -- Cheers / Saludos, Carlos E. R. (from 12.3 x86_64 "Dartmouth" at Telcontar)
Hans Witvliet wrote:
On Mon, 2013-12-09 at 12:06 -0800, John Andersen wrote:
On 12/9/2013 6:15 AM, Vojtěch Zeisek wrote:
I'm used to rsync my home directory to external disc. I also use YaST backup module (I think I can recommend it) to backup any other system data. I then rsync regular backup together with my data. So that I can restore software, settings etc using YaST and my data with rsync. It could make Your backing up easier. All the best, Vojtěch
Its probably redundant for the people on this list, but, at the risk of sounding pedantic, I'll toss it out anyway:
Rsync isn't a backup tool.
..
So I wrote a little shell script to copy user+critical-data every 10 minutes to a salvage area each date-stamped. It is self maintaining in that it removes the "salvage" files after a period of time sufficient for the the BRU backup to captures them. The storage is requirement is surprisingly minimal.
Just wondering.. A couple of time i noticed people scripting around rsync for doing backups.
Been doing that for years. We do daily copies of essential data+config to harddisk in a separate building. For larger amounts of data (typically on LVM), we snapshot and copy to tape.
Isn't rsnapshot supposed to be the tool for doing this?
It's virtually the same thing. -- Per Jessen, Zürich (-0.8°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (20)
-
Anton Aylward -
auxsvr -
auxsvr＠gmail.com
-
Bernhard Voelker -
Bob Williams -
Carlos E. R. -
Christopher Myers -
Damon Register -
Daniel Bauer -
Dave Howorth -
Hans Witvliet -
jdd -
Joachim Schrod -
John Andersen -
Joseph Loo -
Lew Wolfgang -
Michael Hamilton -
Per Jessen -
SuSE List -
Vojtěch Zeisek