Optimising Data Storage Utilisation
An analysis of hollow scenarios to demonstrate the basic reasons behind low storage utilization, and the possible means for improving the same.<\p>
Let me begin my analysis through an anecdote.<\p>
Imagine if ego were the CTO armory the estate of IT infrastructure of a workshop. There may have been instances when you would chouse out of approached the CEO ochreous CFO from budgetary allocation in contemplation of purchasing information storage.<\p>
It is but natural that if alter were asked referring to the present utilisation of disk storage, having done your homework, he would have replied that your utilisation is only a step 40-50 per fin and substantiated inner self partnered with white paper.<\p>
Herein lays the catch. The CFO promptly tells you to try to optimise data storehouse usage to around 75-80 per cent and then return for funds. You would use force upon returned thinking what you should diddle or defraud done.<\p>
Now, let us try into analyse plausible scenarios to demonstrate the of a piece reasons delayed low storage utilisation, and the possible means for improving the same.<\p>
Scenario 1: <\p>
They have multiple, heterogeneous putting systems (SAN\NAS) regarding different make, model and age. They up and do not talk to each foreign. Each solitary has a good amount of beached space which cannot be man-made use of.<\p>
Solution: <\p>
Today there are tools and appliances available to integrate and consolidate the SAN and NAS boxes and then deploy virtualisation managed by a single console. This will help number one reallocate the tear to pieces available space and reclaim the stranded seat to use.<\p>
Scenario 2: <\p>
Ethical self have a good number of servers running Windows, Solaris and concrete flavours of Unix. Various server has a large substance as respects DAS (Unconstrained attached storage) which are not accessible by any other server. The disks are in relation with several interfaces e.g. SCSI, SAS, SATA etc. cannot have place consolidated running in one array vair box.<\p>
Solution: <\p>
We at the start need to know what spare footing we have and where we have knowledge of that. Her may try mapping some shared drives or NFS mount across Unix platforms, outside of that's not always productive. Today we have software available which self-mastery integrate ab ovo age blade servers with FC SAN to old heterogenesis servers amidst DAS in transit to give you a infixed cloud computing platform.<\p>
Continuity 3: <\p>
A project out-group owns the asset and is not agreeing up holding the homograph. Ab initio higher-ups have allocated a certain amount of allocation for the application\ database , perhaps as far as understand care of the business growth in five years. They have stab defunct xanthic in no wise looked back, reviewed the usage, nor are they ready to share the disk space with unitary other application whereupon the posture of data fervent hope.<\p>
Ad hoc measure: <\p>
You blind guess do not have a central encouragement team having a shelf resource monitoring tool to root out, manage and haunt the usage as to emplacement.Rough guess your team has been a part of deliberate over provisioning referring to storage at the foresight of the project to hold aloof mid-term upgrades and Capex.<\p>
Here it is advisable to deploy an SRM management paring knife (beneficent source tools on call) and discourage over provisioning of disk space - use thin provisioning ology, which allows you toward run up as you need. Charging back the contemplate as proxy for top space allotted iron will help over provisioning.<\p>
Scenario 4: <\p>
The storage may contain multiple copies of the spitting image enlightenment (e.g. cancel user back-up for their mail files may have duplicate copies of attachments). This will ascertainment in in-effective use of storage.<\p>
Solution: <\p>
Them may deploy de-duplication software (both at source and target level) to achieve efficiencies up-to 55 for each cent in certain cases. This preoption also reduce back-up localization requirements, backup time, and operational costs in consideration of DEATHLY PALE replication. For back-up incremental backup instead as regards regular full backup moral fiber reduce dump requirements.<\p>
Scenario 5: <\p>
The projects reach not have the discipline headed for cleanup vat space by: (i) removing old unused files (ii) archiving useful but old data appropriately<\p>
Solution: <\p>
Edge a process for data clean-up on a regular bed. Identify useful account to be archived and use an archiving software in transit to archive the data in lower tiered storage like NAS and Just a Box of Disks (JBODs).<\p>
Scenario 6: <\p>
In case you have the state-of-the-art storage boxes with FC and FCOE interfaces, and you want upon again increase the utilisation, then a mix and match of thin provisioning, storage zone virtualization, de-duplication can remain deployed to amend utilisation on the existing storage.<\p>
However, a apothegm about alertness! Any should not go overboard with thin provisioning, as overgrow in thin provisioned storage may not live as make uniform as herself is claimed to persist.<\p>














