7 Replies

Using a single host you will need determine the needed IO characteristics and make sure the local disks being used not only meet size requirement but also IO requirements. The big downside to a single host is that it will not support any availability features (examples- HA / VMotion / FT / DRS, etc…). You will need to use additional software and/ or hardware in order to achieve high availability or in order to backup the VMs.

@John White : We can record for up to 7 days. Accounting for high days is something to consider, but over time our development team has seen little to no substantial evidence that is will affect the overall sizing exercise. You can also delay the recording if needed.

This person is a verified professional.

As for the monthly peaks, I'd just run the tool when your accounting/ERP people are running end of month reports to factor those in. These tools are much more helpful of an awareness of what your peaks are and try to factor them in. (I'd argue just blindly sizing without input or understanding of said peaks leads to people getting crazy oversold more often than undersold based on shorter polling, but both have merits).

Some people don't care if reports take 15 minutes, while other things need really quick processing. Understanding load, as well as application SLA is king.

We can extend the process farther if need to but majority of the time it doesn't make a difference. When talking to the SC they will have the training in hand to identify best practice on recording times.

MAP Kit is a different assessment and it goes from the OS layer and helps in identify workloads.

DPACK is great because it identifies how much I/O you will need from disk to provide to the OS workload layer. A lot of times even through Perfmon it provides an abstract I/O value which can throw off final performance when you implement a solution. That being said it’s been about 5 years since I have used MAP and could have changed somewhat.

Dpack also helps in identifying Spikes. Majority of the time production environments produce such low I/O's it doesn’t matter. It’s the peaks that happen from either boot storms or 90% of the time it’s the backup that saturates I/O.

0

This topic has been locked by an administrator and is no longer open for commenting.