Capacity Management

Primary Skill: Capacity Management

Secondary Skill: Vmware ESX/VSphere

Role Description:

Undertakes Capacity reviews at regular interval working with the technology towers and presents Capacity reports for the Infrastructure along with recommendation for ensuring existing and future load is provisioned for in timely manner.

General Responsibilities

• To identify and highlight potential capacity/availability issues before they can impact the live service.

• To identify and mitigate risks avoiding costly contingency action.

• To act as conduit between the project teams and the IT delivery teams for capacity/availability.

• To facilitate the impact of technical changes in live (where appropriate)

• To define the IT capacity/availability principles.

• To get more out of existing IT resources and improve IT cost per service unit positions by reuse and tighter capacity management.

• To eliminate redundant work and ensure consistent reporting

• To correctly show availability associated with SLA’s and resilience.

• To provide timely capacity and related cost information for more informed business decisions

• To ensure Project consumption at future growth levels and uncover bottlenecks with sufficient warning to correct before business services are adversely affected The capacity manager will be responsible for driving below listed items ? Midrange (Includes VMware), Storage, Network Ports, SAN Switch Port Reporting & Planning. ? Datacenter Rack Reporting & Planning ? Blade Chassis Reporting & Planning ? Application, Database Capacity Management ? Demand Management – Review Clients requirements based on Business inputs and forecast requirements as part of Capacity Plan

• Trending o Monthly trending on usage, showing thresholds and highlighting forecasted issues. o How has capacity changed over the last months and where will it be next month? o When will we run out of capacity? o How much do we have free? o What is the current pipeline of activity? Will this ‘break the bank’? o Highlighting thresholds with time for rectification activities.

• The project governance process o Are we asking the correct questions, are we involved early enough?

• Reporting & Planning o Do we have the correct tools in place to get the correct information? o Reporting on Storage, Midrange, Physical Racking, power, cooling, switch ports, fibre switch ports, virtualised I/O. o Reporting on CPU/memory or IOPS, disk, memory, transactions, etc. o How many servers do we have and what is used where? o Are our reporting mechanisms correct? o Planning of Storage, Midrange, power, cooling, switch ports, fibre switch ports, virtualised I/O.

• Virtual o Are virtual systems running correctly? Traditional CPU and memory counters will give an incorrect reading of virtual machines. o What is the free space in the hosting platforms including VMware, AIX LPAR’s, Solaris Zones, Virtualised I/O what is free, how can we reuse?

• SAN/Backups o What we have free, what has been requested, what is the pipeline of activity. o Better reporting including ‘hot’ LUNs and activity. o Highlighting thresholds with time for rectification activities. o Thresholds of 85% maximum need to be adopted with enough time to provision space if required. o Alignment of SAN requests Vs backups.

Contact – Nirmala B

Apply now