We have a Linux master server running 7.6.0.2. It has a separate file system for /usr/openv. Recently, it had a spike in growth and was 99% utilized. File system at that time was 1.0 TB in size. Added 400 GB LUN to the file system to create a 1.4 TB file system and the space issue was alleviated. Unfortunately, the 400GB was on the slowest disks we have in the data center. Now, when we look at large image files that are 2 or 3 months old, the system slows to a crawl while the catalog data that is over 30 days old is uncompressed - iowait time goes to 40 to 50%. Our storage group is going to provide a new 1.4 TB LUN to use instead that has faster disks and a faster communication link, but it will require copying everything from the existing /usr/openv file system to a new file system using the faster disks. Had asked about doing a SAN replication, but the old and new file systems are using the same fabric so the replication option is not available. So, the plan is:
- bring up the new file system as /usr/nbtemp or something like that
- rsync /usr/openv to /usr/nbtemp while NetBackup is running but while activity is relatively low
- Once that initial rsync is complete, shut down NetBackup, remount /usr/openv to a temp location
- remount /usr/nbtemp as /usr/openv
- run a second rsync from the original /usr/openv file system to the new /usr/openv to catch all files that changed
- restart NetBackup using new file system
Should this work?