Keeping more data stores means doing more administration, performance and capacity management tasks. Make sure you consider the balance between the number of data stores and data store performance when doing this. Once you know your VMs' disk space requirements, you can design your data stores. Be sure to consider your storage needs carefully. A disk consumes its maximum size from a data store even when it contains no data, which means the provisioned size is always the same as the consumed size. This means calculating the required capacity for each VM, and then mapping those VMs to specific data stores. When you size your storage for vSphere, begin by figuring out your VM and application requirements.
Once you figure this out, you can more easily design the rest of your storage setup. The first thing you should consider when designing your storage is the size of your data stores. Specific vSphere alarms should warn you about space consumption, one at 20%, which means you should pay attention to capacity, plan to grow the data store or delete snapshots taking up space and one at 5%, which means you must take immediate action to free up space or risk losing data. You can expand the VMDK file, as well as increase OS partition size to free up space. VMs grow at different rates, so you must always have capacity available on a data store.
0 kommentar(er)
