You only relocate a data center once (hopefully), but you manage it day after day. A big part of making your data center more manageable, dressing in all the cables and fiber. This means keeping everything covered, bundled and out of sight:

a) Cabinets have doors and sidewalls.
b) Copper cables are patched within the cabinets using the provided cable management.
c) Cables follow standard paths and do not cut across cabinets.
d) Fiber and copper cables are kept in separate trays.
e) Blanking panels will be used.

Dressing in the miles of cable and fiber required to connect all the data center equipment is an art form. With a little practice you will learn how to comb through the cables to ensure they are aligned and bundled so they stay out of

the way and allow access to the hardware

they connect.

A large part of a well dressed facility is having a solidly designed standardized cabinet layout along with a good structure cable design and power plan. Obviously each category of equipment will require its own layout and each should be considered and planned before any equipment or cable is ever brought into the data center.

All your designs will be a compromise between capacity, initial cost, and management. Since a majority of a data center’s TCO (Total Cost of Ownership) results from the ongoing management and maintenance, spend the time up front and perform the necessary work to keep everything covered, bundled and out of site. You will see the savings over the life of your data center.

Need help with your data center infrastructure? Contact theData Center Solutions experts at Metagyre, Inc. Data center management to data center consolidation putting business value in the data center.

Data Center Design: Keep It Covered, Bundled And Out Of Sight

• Taking advantage of Moore’s Law and increasing capacity through appropriate hardware life cycle management
• Receiving increased value on purchases through solid vendor management practices
• Evaluating future business demand and scheduling appropriate capacity
• Internally developing a service catalog along with a service centered organization
• Outsourcing non-value-add or business differentiating components
• Are considered an internal business partner rather than a cost center

As operational organizations improve and build an enabling enterprise infrastructure, they begin to account for both mandatory and discretionary components.  Most companies recognize that components evolve from discretionary into mandatory infrastructure components.    Mature operational organizations use this evolutionary time period to their advantage.

An example of this evolution is  Internet Messenger (IM).  IM is at a stage where many  companies treat it with a try and see attitude.   There may be an HR usage policy, a firewall rule or two or even a corporate IM server.  However, there are few enterprises that have established an OLA (operations level agreement) equivalent to IM’s older bother, email.  During this period while the service is under the service umbrella of best efforts, mature organizations develop component specific practices for Tier 1, 2 and 3.  They capture metrics and build a technical capability in preparation for a components evolution.

Just as email worked its way into the business fabric, IM is becoming a standard tool in the business arsenal and as such is moving from the discretionary spending bucket to the mandatory operational service delivery catalog.

Effective operational organizations keep the lights on for mandatory components, improve overall operational efficiency and effectively evolve discretionary components.

Need help with your data center infrastructure? Contact theData Center Solutions experts at Metagyre, Inc. Data center management to data center consolidation putting business value in the data center.

Keeping The Lights On, In A Lights Out Data Center

At a high level there are three areas of guidance for a data center migration. Those areas are Data Center Move, Data Center Design and ongoing Data Center Management. Although their are some universals ideals, each company has to develop their own guiding principles. Individualized guiding principles are required since they reflect corporate culture, technology strategy and business goals. For a good start on developing your own data center migration guiding principles consider the following:

Data Center Move Principles:

1. Business Drivers:
   1. Contract renewals are driving the completion date Production cut over must be on or before the current contract expiration date
   2. Down time is expensive and taken as a last resort
   3. The data is the asset and needs to be protected
   4. One-time use equipment or service should be minimized
2. A team approach will be used in the move so that all disciplines are represented on the team.
   1. Storage: design, document, perform and sign-off on all storage component activities. Include vendor management for physical move of the storage component
   2. Networking: design, document perform and sign-off on all network component activities
   3. Systems: design, document, perform and sign-off on all systems component activities
   4. Back office: design, document, perform and sign-off on all back office component activities.
   5. Application Development: provide information, documentation, guidance and sign-off on all application component activities.
   6. Software QA: Test and sign-off on all functionality
   7. NOC (network operations center): Gatekeeper for documentation, escalation and monitoring of move activities
   8. Business Owner: Sign-off and approval of all move activities
3. Extend the network so both spaces look like one
4. Extend the SAN so storage in both spaces looks like one. Vendors will be enlisted in moving and ensuring proper turn up of their storage systems. New storage equipment will be used as a temporary landing zone for data in order to move it off of a subsystem prior to its move and then back onto it after its move
5. Pools of resources will be split and moved in stages. One resource should not need to know the physical location of another resource
6. Designs will be published, reviewed, challenged and revised prior to the move. During the move designs and scripts will be followed

Data Center Design Principles:

1. Plan Ahead:
   1. Data center plans and designs are to support the next three (3) years of anticipated growth.  This growth is estimated at 20% year over year
   2. Environmental monitoring is required in unmanned facilities
   3. Equipment will be maintained on a five (5) year life cycle
2. Keep it Simple:
   1. Aggregate cabling where possible to segregate patching
   2. Standardize on the rack, ladder system, PDUs, Patch Panels and cabinet layout.
   3. Priority deployment of standard computing:
      1. Virtual server on x86 architecture
      2. Blade Center
      3. Standardized x86 based server platform
      4. Other architecture
3. Remain Flexible
   1. Equipment can be placed in the next available cabinet.  There is no intelligence built into the floor plan
   2. New standards should be carried forward and retrofitted only where it makes business sense
4. Think Modular:
   1. Two cabinets make a non-blade center module to be deployed when additional resources are required
   2. One cabinet makes a blade center module to be deployed when additional resources are required
   3. Cabinet modules are outfitted the same for network and cabling
5. Keep things covered, bundled and out of sight:
   1. Cabinets have doors and sidewalls
   2. Copper cables are patched within the cabinets using the provided cable management
   3. Cables follow standard paths and do not cut across cabinets
   4. Fiber and copper cables are kept in separate trays
   5. Blanking panels will be used

Data Center Management Principles:

1. Label Everything:
   1. Racks, PDUs, and environmental monitoring devices are labeled with name as it appears in the book of record
   2. Servers are labeled with name as it appears in the book of record
   3. Network equipment and patch panels are labeled with name as it appears in the book of record
   4. Storage is labeled with name as it appears in the book of record
   5. Fiber, copper and power cables have a matching serialized label at both terminating ends. (should track in the book of record what cable attached to equipment)
2. Configuration Management is paramount:  the book of record contains information on all physical and virtual servers, network equipment, storage systems, racks, PDUs and environmental devices
3. Change Control:
   1. The change approval board ensures the inventory is updated
   2. All work requires a change control
4. Access is Locked Down:
   1. Only 3-5 people have physical access to the data center
   2. The Facilities group manages access to the data center
   3. Change control approval is required to perform work in the data center
   4. The NOC is aware of data center access through the daily production schedule and notices
5. Audit the work: Audits are conducted on
   1. The book of record against the physical data center
   2. Data center sign-in against daily production schedule
   3. The NOC is the Gate Keeper for data center management process adherence

These data center migration principles valid when moving into or out of a collocation facility or an in-house data center.

Need help with your data center infrastructure? Contact theData Center Solutions experts at Metagyre, Inc. Data center management to data center consolidation putting business value in the data center.

Data Center Migration Principles