Veeam Home | Support | Downloads
Best Practices for Veeam Backup & Replication 7.0 for VMware

Veeam Management Pack Help Center  > Best Practices for Deployment & Configuration >  Resource Planning and Optimization > Planning for the Source > Example

Example

Previous page Next page Print this Topic

Table of contents

The example below represents an Exchange 2010 server with the OS and Application volumes stored on a VMFS volume, while the Exchange logs and mailbox stores are using virtual raw device mappings individual SAN volumes with spindle counts allocated to handle the required load.

Disk description

Size

Datastore name

RAID level

Spindles

IOP profile

VM configuration
& OS (C:\)

40GB

DS_OS (VMFS)

5

6

Light R/W

Application (D:\)

40GB

DS_OS (VMFS)

5

6

Light R/W

Logs1 (E:\)

100GB

DS_LOGS1 (vRDM)

10

8

Heavy Write

Logs2 (F:\)

100GB

DS_LOGS2 (vRDM)

10

8

Moderate Write

Mailstore1 (G:\)

500GB

DS_MBX1 (vRDM)

10

12

Heavy R/W

Mailstore2 (H:\)

500GB

DS_MBX2 (vRDM)

10

12

Moderate R/W

For vSphere 5.0 and later, snapshots for each virtual disks are created on their individual datastore. The critical thing to keep in mind here is that each datastore will have to keep enough free space to hold the snapshot growth for the duration of the backup. For this reason, Veeam recommends that datastores should be limited to no more than 80% utilization — to leave space available for snapshot operations.

noteNote

In ESXi 5.x, the workingDir parameter is used to specify the location of the snapshot .VMSN file. To revert to the pre-ESXi 5.0 way of storing snapshots in the directory specified by the workingDir parameter, the new snapshot.redoNotWithParent parameter must be added to the virtual machine's .VMX file, as described in VMware KB article 2007563. This can be of use for large volumes.

Table of contents