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
vxassist mirror
Use the vxassist mirror command to add a mirror to an existing volume.
vxassist [-b] [-o notrackalign] [-g<DynamicDiskGroupName>] mirror <VolumeName|DriveLetter|VmName|DrivePath> [type=<typename>] [<alloc_attributes ...>] [Column=N] [StripeUnit=<width>] [Site=<sitename1>[,<sitename2>,...]] [<[!]diskname | p#c#t#l#> ...]
The following attributes apply:
-b | Runs the command in the background. |
-o notrackalign | Disable track alignment on the disk where the volume resides. |
-g<DynamicDiskGroupName> | Required only if the internal volume name or internal disk name is used. |
<VolumeName> | the path name of the volume, such as \Device\HarddiskDmVolumes\DG1\Volume1. |
<DriveLetter> | The drive letter of the volume. |
<VmName> | Internal name of the volume; requires the use of the -g option (for example, -gDG1 Volume1). |
<DrivePath> | A volume that is mounted on an NTFS folder; it is indicated by a path to that folder. |
Type=<Type> | Type of volume layout. Types are: - Stripe - Concatenate |
<alloc_attributes> | Allocation attributes for mirroring and striping volumes. Attributes are:
|
Mirror=<n> or Mirror=<n>, diskclass | Number of mirrors to be created for mirrored volumes. (Default is 2.) Optionally specify a diskclass to use in mirroring. For example, Mirror=2,target specifies that volumes are mirrored between SCSI target addresses. Each mirror can contain disks from any number of instances of the diskclass, but different mirrors cannot use disks from the same instance of the diskclass. |
Stripe=diskclass | Volumes are striped across instances of a particular diskclass. For example, Stripe=target specifies that volumes are striped between SCSI target addresses. Each column stripe can contain disks from any number of instances of the diskclass, but different columns cannot use disks from the same instance of the diskclass. |
Wantmirror=diskclass | Specifies a diskclass to use in mirroring. However this constraint is ignored if the requested allocation cannot be satisfied. |
Wantstripe=diskclass | Volumes are striped across instances of a particular disk class. However this constraint is ignored if the requested allocation cannot be satisfied. |
diskclass {[!]diskclass:instance} | Diskclass specifies (or excludes) a particular type of disk grouping. For example, port specifies a group of disks on a port. Instance specifies which grouping. For example, p1 specifies a particular grouping of disks. Each type of diskclass has a particular format for specifying instances of the class. Multiple diskclass instances can be specified separated by a space. Diskclass can be one of the following: - target or t Specifies the disks that have the same SCSI target address of the same port. The target is specified in the form p#t# - enclr, e, or enclosure Specifies the disks belonging to a particular enclosure. - port or p Specifies the disks that are connected to a particular port. - channel or ch Specifies the disks that are connected to a particular channel. |
Column=<n> | Number of columns. Required for RAID-5 and striped volumes. |
StripeUnit=<Width> | Stripe width of RAID-5/striped volumes in blocks (512 Kbytes). Allows the user to specify the stripe unit for RAID-5 and striped volumes. |
Site | Specifies the name of the site on which a site-based volume is to be created or mirrored. |
[!]<DiskName>... | The name of the disk or disks (such as Harddisk2) on which the mirror or mirrors are to be created. The disk name can also be indicated by the internal disk name, which requires the -g option (for example, -gDG1 Disk2). |
[!]<p#c#t#l#> | Another way to indicate a disk; the #s correspond to port, channel, target, and LUN of a disk. |
Warning:
Adding mirrors to a volume involves a certain amount of time for mirror resynchronization. Take care not to perform actions on the volume until the command is complete. Also, if you inadvertently shut down the server or deport the disk group containing the volume before mirror resynchronization completes, any mirrors that were being added to the volume are deleted when the disk group with the volume comes online again.
The SmartMove feature can help reduce mirror resynchronization time.
Note:
Dynamic disks belonging to a Microsoft Disk Management Disk Group do not support track alignment.
Example
vxassist mirror -b Z: Mirror=2 Harddisk4 Harddisk5
The above command line sequence adds two mirrors to volume Z. Harddisk4 and Harddisk5 are used to create the mirrors. The process of adding the two mirrors runs in the background. Instead of using the drive letter Z, you can provide a path name, such as:
\Device\HarddiskDmVolumes\DynDskGrp1\Volume1
To create a mirror for a site-based volume using the site-aware allocation feature, refer to:
See Adding a mirror to a site-based volume through CLI.
See Administering mirrored plexes for site-based allocation.
More Information