Network Computing is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them. Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Upgrading Critical Storage: Page 2 of 8

Beware that modifying the configuration and even your applications' source code to use a different disk or CIFS (Common Internet File System) share can cost you plenty in productivity. Try to mirror the configuration of your original storage system. We created one partition on the new Snap server and named and designed it exactly the same as our original NSS NAS, but with more space. We also configured a second volume as iSCSI to facilitate moving portions of NWC Inc. to the NAS that requires block storage.

Dude, Where's My Space?

One thing we forgot to consider: To keep snapshots of the volumes on the new storage box, you'll need 10 percent to 25 percent of the available storage space. Although losing 15 percent of our available space wasn't a problem, it would have gotten ugly if we had sized the drives exactly the same as the disks on the NSS because we'd have come up short on snapshot space. To remedy the situation, we could reinitialize the entire Snap and redo the configuration or turn off snapshotting of SNAP volumes. Fortunately, we had massively oversized each partition to make room for future growth, so it'll be a while before we have to worry about that missing space.

Our plan of attack was simplistic, but it can work for most storage server installations. We configured things so we could drop the NSS and reassign its IP address and host name to the new Snap server before it was time to flip the switch over to the Snap.

Synch Up