Consider the time table of any expansion. Analysts note that overall storage costs (e.g., disk, port and HBA costs) are declining over time, and more features are always being added. This means a massive scaling project implemented in the near term may actually wind up costing more and offering fewer features than a systematic upgrade effort that takes place periodically over time. This can be true even when factoring in potential savings of upfront bulk purchases. Once you have an accurate knowledge of growth rates, compare product costs and see what makes more financial sense for your organization.
Migration should be included in the scaling process. When storage capacity is scaled with more disks or additional storage systems, some data may need to be moved in order to take advantage of faster disks, more capacity, or faster connectivity. Time is also essential when an older device is being decommissioned because the longer that migration is delayed, the more your company must pay to operate and support both systems. Migration is a mission-critical task, but it's typically overlooked until new hardware is sitting on the data center floor. Data classification can help ease the migration process, especially when using data classification and migration automation tools to classify and move data according to your existing policies.
Remember to also scale backup and disaster recovery. Any time that storage and storage networks are added or expanded, it's important to consider any adverse side-effects on data protection policies and practice. Increased storage will demand larger backup windows. Changes in tiered storage may alter backup or snapshot policies -- not all data may need to be protected in the same way. In extreme cases, improved backup technologies may be required. For example, tape may give way to disk (e.g., virtual tape library or disk-to-disk storage) and space-saving tactics like data deduplication. Similarly, backup changes will impact disaster recovery tasks such as remote replication. If backup software licensing is priced "per terabyte", increasing storage can dramatically increase backup costs.
Evaluate changes to management requirements and processes. Scaling a storage network can also influence established and documented procedures such as backups or provisioning. For example, implementing iSCSI in a workgroup or integrating an iSCSI SAN with an existing FC SAN can cause substantial procedural changes that should be considered during any scaling project. Also weigh the management overhead that may accompany an upgrade. Experts note that additional storage capacity rarely adds significant management overhead, but adding new technologies or processes to the storage environment may require more labor. For example, another 10 terabytes of disk space may be readily manageable with existing staff, but implementing a new remote replication scheme for data protection might require additional attention.
Track performance before and after scaling. It's important for an enterprise to monitor network, server, and storage fabric performance before and after any scaling project. For example, industry experts suggest watching inter-switch local and long distance links to identify points of congestion and ensure required service levels. Testing allows IT staff to draw a performance benchmark prior to an expansion, then measure the benefits, optimize any new hardware, and spot any unexpected bottlenecks which can be addressed or tabled for future upgrades.
This was first published in April 2007