As a rule of thumb, Disk Magic can be considered to be software agnostic. Therefore for most models, Disk users do not need to worry about what software applications are running in the environment being modeled.
From Disk Magic perspective, a workload can be treated as a group of I/Os. The profile of such I/O can be determined through one of the data capture procedures described in Disk Magic's Printed Help Guide.
However, there are applications that have unique performance requirements that do not result in accurate recommendations nor projections from Disk Magic. Additional care has to be taken when trying to create models for one of these cases.
In general, these applications are very demanding of the Disk Storage Subsystems and tend to have unusual I/O patterns that are not taken into consideration in your typical Disk Magic model.
The following two applications should NOT be sized using Disk Magic.
EPIC is a popular health care software solution. It provides patient care capabilities including: registration and scheduling; clinical systems for medical personnel,; systems for lab technicians,; and billing systems for insurers.
Due to the nature of the SLAs (Service Level Agreement) imposed by EPIC on the storage used in the back end, only pre-certified configurations are acceptable for production deployments. Typically the sizing process for EPIC involves resources specializing in EPIC solution sizing. EPIC is characterized by big bursts that do not model well in the Disk Magic tool.
Protectier is a high performance, real time backup and restore solution with in-line deduplication capabilities. Protectier solutions can easily reach 2,500MB/s or more in throughput, and due to the high throughput alongside intense access to meta-data, sizing can be tricky and most follow rigid rules. It is also best practice to use a dedicate disk subsystem for this application. Protectier solutions should be sized using the PT Planner Tool. The Storage Techline Tape team can assist with this activity.
The following application can be modeled by Disk Magic, but with additional caveats:
VDI (Virtual Desktop Infrastructure) is a desktop-oriented service that hosts user-desktop environments on remote servers and/or blade PCs. Users accessed the desktops over a network using a remote display protocol. A connection-brokering service connects users to their assigned desktop sessions. For users, this means they can access their desktop from any location, without having to use a single client device.
VDI environments have two different workload profiles that are important to consider when trying to model a solution in Disk Magic:
Early morning and early evening, where the users are booting or shutting down the virtual clients(Boot-storm)
During usual business hours where users are doing their daily work (Steady-state Workload)
Typically, VDI solutions will deploy SSD or Flash storage to handle the Boot-storm performance requirements. Meanwhile, traditional HDDs handle the State-state workload. This approach allows an enterprise to minimize deployment costs while sustaining the performance required by the environment.
With the knowledge of this deployment plan, it is possible to adjust your data capture strategy to let you have visibility into both workload profiles. From there you can properly adjust your Disk Magic models to let you size the Boot-storm workload and the Steady-state workload components by identifying their specific individual peaks.
In conclusion, Disk Magic is for most part software agnostic. However, there can exist some applications that are not modeled accurately by Disk Magic. Disk Magic is not always the best tool to size those solutions. For VDI deployments, Disk Magic can be leveraged, but users just have to make sure that the models they created take into consideration the specifics of that workload's duality.