due to a misbehaving nfs-serving NAS, I need to migrate the seafile-data directory to another NFS-Server. There are about 6 TB in files and it takes a few days via gigabit Ethernet to copy with rsync.
I am lacking the ability to take snapshots of the filesystem to first copy everything from the snapshot and then in a second step copy the rest incrementally, which should be a lot faster and I could limit the downtime. But I was wondering, if this is even necessary, because of the way seafile stores its data. Once stored block-, commit- and fs-objects should not be changed as long as garbage collection is not run, right? So I can just rsync for days again and again without breaking anything?
I wonder what would happen if after the switch some file was missing. Probably the Library would be inaccessible until I synched the missing files from the old storage…
I would be interested in your opinions.