I am getting ready to move a volume (with 36gb disk) that's internal to the filer to a new volume (with 72gb disk). Have seen some references to rsync in the toasters. I looked at their web page and in the process of building it. How do you folks feel about it? My original plan is to move the data overnight, update the filer exports, cifs and nis, then turn it back over (approx 12 hours of work during a weekend). Seems with rsync I can do the initial copy and then come back over it with an "incremental" and be less intrusive of my engineers? What's been your experience? Please just post reponses to toasters. thx -jc
James C. Coder Guidant CRM email: james.coder@guidant.com Phone: 651-582-4797
On Wed, 21 Mar 2001, Coder, James (STP) wrote:
Have seen some references to rsync in the toasters. I looked at their web page and in the process of building it. How do you folks feel about it?
In general, it rocks. One potential gotcha that I saw with older versions is that the rsync process's memory use could balloon up if you were trying to have it process a large number of files. You also have to think carefully about the 'include' and 'exclude' syntax, if you want to use those features; it probably pays to make a couple of dry runs (-n) before firing it up for real.
On Wed, 21 Mar 2001, Jim Davis wrote:
On Wed, 21 Mar 2001, Coder, James (STP) wrote:
Have seen some references to rsync in the toasters. I looked at their web page and in the process of building it. How do you folks feel about it?
In general, it rocks. One potential gotcha that I saw with older versions is that the rsync process's memory use could balloon up if you were trying to have it process a large number of files.
I went through this not to long ago. Using The File::Rsync perl module in conjunction with Parallel::ForkManager works wonders. My filer was the backend for a webserver farm. Dir structure looked like this:
/htdocs/e/x/example /htdocs/f/o/foo /htdocs/u/s/username
and so on. Whipped up a script that decended to (for example) /htdocs/e/x, and ran an rsync process on each of the userdirectories. Worked fine in testing, although events eventually dictated that I run rsyncs manually.
Noah
Be careful. I got surprised by a rsync with the --delete. If you include rsync'ing the /etc directory, You could run into bug that crashes the system when trying to remove or rename certain files in /etc. it had this file from a previous configuration copied from root volume. Even though I was rsync'ing to a non-root volume, when it tried to remove the /etc/db/quota_names file, it crashed. There are some other sensitive files. check bug numbers 11011, 31124.
At 2:57 PM -0600 3/21/01, Coder, James (STP) wrote:
I am getting ready to move a volume (with 36gb disk) that's internal to the filer to a new volume (with 72gb disk). Have seen some references to rsync in the toasters. I looked at their web page and in the process of building it. How do you folks feel about it? My original plan is to move the data overnight, update the filer exports, cifs and nis, then turn it back over (approx 12 hours of work during a weekend). Seems with rsync I can do the initial copy and then come back over it with an "incremental" and be less intrusive of my engineers? What's been your experience? Please just post reponses to toasters. thx -jc
James C. Coder Guidant CRM email: james.coder@guidant.com Phone: 651-582-4797