Some backup solutions, such as those leveraging VMware Consolidated Backup, can make backups of the contents of SAN LUNs using a physical Windows proxy server. The SAN LUNs are presented to the Windows proxy server in the same manner they are presented to the ESX/ESXi hosts, and the backup software reads data from the LUNs.
If a physical Windows server mounts and writes to existing filesystems on SAN LUNs used by virtual machines, data corruption can occur. It is imperative that the Windows server be configured to not mount filesystems on the SAN LUNs.
This article summarizes information from the Configuring Windows on the VCB Proxy section of the VMware Virtual Machine Backup Guide for ESX/ESXi 3.5-4.0.
All versions of Windows Server OS, except Windows Server 2003 Enterprise Edition and Windows Server 2003 Datacenter Edition, assign drive letters to each visible NTFS and FAT volume. To be able to use Consolidated Backup or similar backup strategies, you need to clear any unused drive letter assignments and then ensure that the backup destinations are visible.
diskpart
automount
Automatic mounting of new volumes enabled.
automount disable
automount scrub
exit
VMFS LUNs appear in Windows Disk Management as Healthy, but are marked as Unknown Partition and are not assigned drive letters. Backup software, such as VMware Consolidated Backup, accesses the storage device directly when performing backups, not through a drive letter. To ensure that the devices are visible:
Healthy (Unknown Partition)
because Windows does not natively understand the contents of a VMFS Datastore.バックアップのために ESX 制御のストレージを Windows Server で使用できるようにする