rsync all partition contents from one HDD to another

C

ccc

hi

I'd like to migrate FreeBSD from one HDD to another.
Which rsync parameter should I use for hard-links, file/directory permissions etc.?
 
Code: 
# from the source, below represented by the 'dot' ... the root of the copy
# and the destination mounted on /mnt
#dot# rsync -vaH --delete-delay --partial --stats --numeric-ids --inplace --archive --compress --hard-links --one-file-system --bwlimit=2000 . /mnt 
#tmp# rsync...        . /mnt/tmp             #etc, for other next filesystems
It's never failed here. The shell saves history across reboots so I've never had to type it all again except in unusual restore incidences.
I've only a general idea of why it works and am reluctant to ever change the path scheme outlined herein (unknown results sometimes occur.)
For some reason, I copy tmp, usr etc BEFORE /
In many cases, one can up the BWLIMIT to 6000 or so. (Sometimes not.)
...
Re the schg mentioned below, I usually run a script to clear them before the rsync, it does indeed cause trouble on the next incremental upgrade otherwise.
 
  • Thanks
Reactions: ccc
ccc said:
I'd like to migrate FreeBSD from one HDD to another.
Which rsync parameter should I use for hard-links, file/directory permissions etc.?
Click to expand...

If the original filesystems are UFS, use dump(8)/restore(8). Seriously. rsync, even with the file flags patch, has trouble writing files with the schg flag set. There's a bug report with a patch I have not tested: https://bugzilla.samba.org/show_bug.cgi?id=8941

Otherwise, I use axHAX --delete --fileflags --force-change.
 
For completeness, Backup Options For FreeBSD shows how to copy filesystems with dump(8) and restore(8).

When migrating to a new disk, remember that the boot code also must be installed, or it won't boot. An easy way to make sure everything is set up is to do a minimal install to the new disk, then restore over it. That's also described in the document above.
 
  • Thanks
Reactions: ccc
wblock@ said:
Otherwise, I use axHAX --delete --fileflags --force-change.
Click to expand...

Hi,

I use -axHAX --delete --sparse --numeric-ids.

--sparse means that holey files don't grow when copied.

--numeric-ids means I can bring the files back from another host with correct owner/group.

--fileflags --force-change are somewhat of a mystery to me. They are not mentioned in my local (FreeBSD 8.1-RELEASE) rsync man pages, and not anywhere else I looked on the net.

Cheers,
 
  • Thanks
Reactions: ccc
--fileflags is an added feature only available when net/rsync is built with the FLAGS option enabled. It's added to the man page also. --force-change may be part of that same option.

Code: 
--fileflags             preserve file-flags (aka chflags)
...
--force-change          affect user/system immutable files/dirs
 
You must log in or register to reply here.
Back
Top