Storage Foundation 8.0 Administrator's Guide - Windows
- Overview
- Setup and configuration
- Function overview
- About the client console for Storage Foundation
- Recommendations for caching-enabled disks
- Configure basic disks (Optional)
- About creating dynamic disk groups
- About creating dynamic volumes
- Set desired preferences
- Using the GUI to manage your storage
- Working with disks, partitions, and volumes
- Adding storage
- Disk tasks
- Remove a disk from the computer
- Veritas Disk ID (VDID)
- General Partition/Volume tasks
- Mount a volume at an empty folder (Drive path)
- Expand a dynamic volume
- Shrink a dynamic volume
- Basic disk and volume tasks
- Automatic discovery of SSD devices and manual classification as SSD
- Volume Manager space allocation is SSD aware
- Dealing with disk groups
- Disk groups overview
- Delete a dynamic disk group
- Detaching and attaching dynamic disks
- Importing and deporting dynamic disk groups
- Partitioned shared storage with private dynamic disk group protection
- Fast failover in clustered environments
- iSCSI SAN support
- Settings for monitoring objects
- Event monitoring and notification
- Event notification
- Configuring Automatic volume growth
- Standard features for adding fault tolerance
- Performance tuning
- FlashSnap
- FlashSnap components
- FastResync
- Snapshot commands
- Dynamic Disk Group Split and Join
- Dynamic disk group join
- Using Dynamic Disk Group Split and Join with a cluster on shared storage
- Dynamic Disk Group Split and Join troubleshooting tips
- Fast File Resync
- Volume Shadow Copy Service (VSS)
- Using the VSS snapshot wizards with Microsoft Exchange
- Using the VSS snapshot wizards with Enterprise Vault
- Using the VSS snapshot wizards with Microsoft SQL
- Copy on Write (COW)
- Using the VSS COW snapshot wizards with Microsoft Exchange
- Using the VSS COW snapshot wizards with Microsoft SQL
- Configuring data caching with SmartIO
- Typical deployment scenarios
- About cache area
- Configuring SmartIO
- Frequently asked questions about SmartIO
- Dynamic Multi-Pathing
- Configuring Cluster Volume Manager (CVM)
- Configuring a CVM cluster
- Administering CVM
- Access modes for cluster-shared volumes
- Storage disconnectivity and CVM disk detach policy
- Unconfiguring a CVM cluster
- Command shipping
- About I/O Fencing
- Administering site-aware allocation for campus clusters
- SFW for Hyper-V virtual machines
- Introduction to Storage Foundation solutions for Hyper-V environments
- Live migration support for SFW dynamic disk group
- Preparing the host machines
- Configuring the SFW storage
- Administering storage migration for SFW and Hyper-V virtual machine volumes
- Optional Storage Foundation features for Hyper-V environments
- Microsoft Failover Clustering support
- Configuring a quorum in a Microsoft Failover Cluster
- Implementing disaster recovery with Volume Replicator
- Troubleshooting and recovery
- Using disk and volume status information
- Resolving common problem situations
- Commands or procedures used in troubleshooting and recovery
- Rescan command
- Repair volume command for dynamic mirrored volumes
- Additional troubleshooting issues
- Disk issues
- Volume issues
- Disk group issues
- Connection issues
- Issues related to boot or restart
- Cluster issues
- Dynamic Multi-Pathing issues
- vxsnap issues
- Other issues
- CVM issues
- Appendix A. Command line interface
- Overview of the command line interface
- vxclustadm
- vxvol
- vxdg
- vxclus
- vxdisk
- vxassist
- vxassist (Windows-specific)
- vxsd
- vxedit
- vxdmpadm
- vxcbr
- vxsnap
- vxscrub
- sfcache
- Tuning SFW
- Appendix B. VDID details for arrays
Creating a virtual machine service group
To create a virtual machine service group, add a virtual machine on the active failover cluster node.
Note:
Virtual machine and virtual hard disk (.vhd) must be stored in the VMDg resource. This is required to make the virtual machine highly available.
To make the shared storage, i.e, the VMDg resource, available to the virtual machine, you must create the virtual machine on a cluster node that owns the storage. You can either create a new virtual hard disk (.vhd), use an existing .vhd as shown in the procedure below, or you can create it later.
To create a virtual machine
- Click Start > Administrative Tools > Failover Cluster Manager.
If you are not connected to the cluster node that owns the shared storage connect to it.
- Click on Service and Applications > Virtual Machine > New > Virtual Machine from the left pane of the Failover Cluster Manager snap-in.
- The New Virtual Machine Wizard is launched. Review the information on the welcome page.
Click Next.
- On the Specify Name and Location page, specify a name for the virtual machine, for example, VM1.
- Enable the Store the virtual machine in a different location check box, and then type the full path. You can also click Browse and copy the virtual hard disk (VHD) file to the Volume Manager Disk Group (VMDg1) resource created in earlier section of this document for storing the virtual machine.
- On the Memory page, specify the amount of memory that is required for the operating system that will run on this virtual machine.
- On Configure Networking page, select the network adapter that is configured to use for Hyper-V.
- On the Connect Virtual Hard Disk page, three options are shown:
Create a new virtual hard disk
Use existing virtual hard drive
Create virtual hard disk later
Select the required option and give the path to the VHD (.vhd) file on the Volume Manager Disk Group (VMDg) resource.
The VHD (.vhd) file must be stored in a location where the VMDg resource is located.
- Click Finish to close the wizard.