Difference between revisions of "Talk:Full system backup with rsync"

From ArchWiki
Jump to: navigation, search
(Errors: Close fix error.)
(retract "one-liner is broken"; turns out that was wrong)
(9 intermediate revisions by 6 users not shown)
Line 1: Line 1:
===<s> Restore title</s> ===
 
I cannot move it back to the same title without admin intervention. They have to delete the redirect first. Sorry for changing the name in the first place; I didn't realize subsections worked only for user pages. [[User:Pwd|pwd]] 13:27, 23 December 2009 (EST)
 
:Oops! Sorry; didn't realize that was the cause of the hold-up. I've removed the redirect. -- [[User:Pointone|pointone]] 13:34, 23 December 2009 (EST)
 
 
::Moved the page even though I don't like the title. I really don't think the naming scheme suits it; should be ''Full system backup with rsync'', in my opinion. <small>[[User:Pwd|pwd]]</small> 14:10, 23 December 2009 (EST)
 
 
 
== Comments ==
 
== Comments ==
  
Line 40: Line 34:
 
--[[User:Scheuref|Scheuref]] ([[User talk:Scheuref|talk]]) 14:03, 19 September 2012 (UTC)
 
--[[User:Scheuref|Scheuref]] ([[User talk:Scheuref|talk]]) 14:03, 19 September 2012 (UTC)
  
== <s> Errors </s> ==
+
-----
  
I'm getting the following error with this script, unless I use --delete-excluded, although that was declared unnecessary:
+
Indeed, great article. One small comment, I had to recreate initramfs due to the filesystem being different on the target disk. The previous initramfs didn't have the correct fsck tool for the new disk. Running mkinitcpio -p linux is really simple, but it would be nice to prepare the reader of this case. [[User:Haritak|Haritak]] ([[User talk:Haritak|talk]]) 04:40, 19 April 2013 (UTC)
cannot delete non-empty directory: lib
+
could not make way for new symlink: lib
+
cannot delete non-empty directory: lib64
+
could not make way for new symlink: lib64
+
--[[User:Malstrond|Malstrond]] ([[User talk:Malstrond|talk]]) 00:31, 8 September 2012 (UTC)
+
  
:Rsync doesn't delete... You must have modified the script? --[[User:DSpider|DSpider]] ([[User talk:DSpider|talk]]) 06:10, 8 September 2012 (UTC)
+
-----
 
+
::I had the same problem, turned out that I had forgotten that the script needs to be called with a destination argument. It doesn't check for this situation and will use an empty $1, which causes it to be ignored and it'll try make a backup to your root directory.. very scary!  I've now added a check to the script to prevent accidental misuse. [[User:Timusan|Timusan]] ([[User talk:Timusan|talk]])
+
  
 
== What about hard links and delete options ==
 
== What about hard links and delete options ==
Line 60: Line 47:
 
Thank you,
 
Thank you,
 
Xwang
 
Xwang
 +
 +
== What happened to this page? ==
 +
 +
Ok, I started this page, so I'm biased. It used to be clearly written, with an easy to understand example on how to use rsync and its exclude format. Now it's a one liner with the excludes mashed together and most of the page is dedicated to setting up your fstab. Why?
 +
[[User:Wooptoo|Wooptoo]] ([[User talk:Wooptoo|talk]]) 19:47, 6 March 2013 (UTC)
 +
 +
==<s> Doesn't Work</s> ==
 +
 +
The current version here does not work. When attempting to use this as a guide for writing my own short rsync-based backup script, I found that the excludes do not work as given. I put a "--exclude" for each item and left off the leading "/" as rsync takes all excludes to be relative. This needs to be updated with a tested, working version (or possibly rolled back to a working version).
 +
[[User:BlueG|BlueG]] ([[User talk:BlueG|talk]]) 02:22, 28 May 2013 (UTC)
 +
:Agreed. It just does infinite loops on media. I employed your solution, it works. -- [[User:Oldarney|Oldarney]] ([[User talk:Oldarney|talk]]) 04:47, 2 June 2013 (UTC)

Revision as of 17:59, 28 September 2013

Comments

Thanks! Neat method for a sync-type backup! The only question I have is what happens if you dd the boot sector (first 512 bytes) instead of running GRUB? --VitaminJ 22:18, 11 November 2009 (EST)


I don't know if it works with dd, since the partitioning scheme can be different on the two harddrives.

  • I vote for merging this with rsync.
  • I second the vote.

Wooptoo 07:14, 2 December 2009 (EST) --Keiichi 20:59, 2 December 2009 (EST)


Yep, I think you are right, I think that GRUB hardcodes the path to menu.lst in the GRUB boot program, so if you change around disks it won't work.

As an alternative, an article on using tar instead might be useful because rsync may improperly preserves permissions across filesystems. For example if you backup from ext3 to XFS, and try to restore back to ext3.

The only issue would be doing it with FAT or NTFS were permissions just aren't possible. Coincidentially, I've done this exact setup using XFS and ext4 wihout anything breaking down. I only had problems between reiserfs and *, but that was due to SELinux context. Dres 21:22, 18 January 2010 (EST)

I think its a good idea to mention dirvish here. --Moere 03:37, 1 March 2010 (EST)


on the same topic, you can also look at a free script that i wrote to backup the whole disk with rsync here: http://blog.pointsoftware.ch/index.php/howto-local-and-remote-snapshot-backup-using-rsync-with-hard-links/

It uses file deduplication thanks to hard-links, uses also MD5 integrity signature, 'chattr' protection, filter rules, disk quota, retention policy with exponential distribution (backups rotation while saving more recent backups than older). It was already used in Disaster Recovery Plans for banking companies, in order to replicate datacenters, using only little network bandwidth and transport encryption tunnel.

Can be used locally on each servers or via network on a central remote backup server. windows server could also be backuped by using a linux box that mount smb shares from them.

i hope it will be useful to you guys --Scheuref (talk) 14:03, 19 September 2012 (UTC)


Indeed, great article. One small comment, I had to recreate initramfs due to the filesystem being different on the target disk. The previous initramfs didn't have the correct fsck tool for the new disk. Running mkinitcpio -p linux is really simple, but it would be nice to prepare the reader of this case. Haritak (talk) 04:40, 19 April 2013 (UTC)


What about hard links and delete options

Why the -H option is not added? I've done a quick search in my arch system and there are a lot of hard link in the /usr/share folders. Moreover should the -delet option be added to in order to be sure that the cloned system contains all and only the files which are present in the original one? Thank you, Xwang

What happened to this page?

Ok, I started this page, so I'm biased. It used to be clearly written, with an easy to understand example on how to use rsync and its exclude format. Now it's a one liner with the excludes mashed together and most of the page is dedicated to setting up your fstab. Why? Wooptoo (talk) 19:47, 6 March 2013 (UTC)

Doesn't Work

The current version here does not work. When attempting to use this as a guide for writing my own short rsync-based backup script, I found that the excludes do not work as given. I put a "--exclude" for each item and left off the leading "/" as rsync takes all excludes to be relative. This needs to be updated with a tested, working version (or possibly rolled back to a working version). BlueG (talk) 02:22, 28 May 2013 (UTC)

Agreed. It just does infinite loops on media. I employed your solution, it works. -- Oldarney (talk) 04:47, 2 June 2013 (UTC)