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
vxsnap create
For Exchange operations:
vxsnap -x <Filename> create [-g <dynamicdiskgroupname>] source=<Volume>[/DriveLetter=<DriveLetter>][/DrivePath=<DrivePath>] [/Newvol=<NewVolName>][/Plex=<PlexName>]... [writer=<WriterName>] [component=<ComponentName>] [backuptype=<Backuptype>] [-e] [-o] [-c] [secHosts=<SecondaryHosts>]
Creates snapshot(s) of the specified volume(s) or component. Allows the volumes to be snapshotted simultaneously.
Separate source volumes and attributes with forward slashes, not spaces. Source and snapshot volume attributes are paired. You must specify the source volume if you choose to specify the snapshot volume plex, drive letter, drive path, or volume name.
The following attributes apply:
-x <Filename> | Indicates the name to be assigned to the XML metadata file that is created with the command. The file name must include the ".xml" extension. To specify a location other than the default location for the file, you must enter the full path for the file (e.g. J:\XML\Image1.xml). |
-g <DynamicDiskGroupName> | Name of the disk group that contains the source volume. Required when specifying volume name. |
source=<Volume> | Indicates the source volume for the split-mirror snapshot specified by a drive letter, drive path (mount point), or volume name of the form "\\?\Volume{GUID}\". Repeat this parameter for each volume associated with the specified component (for example, Exchange storage group). |
[/plex=<PlexName>] | Specifies the name of the mirror or plex that is to be detached. Use this parameter if there are multiple snap plexes available to be snapshotted. |
[/DriveLetter=<DriveLetter>] | The drive letter to be assigned to the new snapshot volume. |
[/DrivePath=<DrivePath>] | The drive path to be assigned to the new snapshot volume. The drive path must reference an empty local NTFS folder, which was created beforehand. The path must include the drive letter and folder to be mounted, for example, C:\DB1VOL. |
[/Newvol=<NewVolName>] | Specifies the name of the new snapshot volume that is created. If the name is not specified, then the default snapshot volume name begins with "SnapV" followed by a 12 character alphanumeric string. The 12 character alphanumeric string is a coded hexadecimal timestamp based upon the time that the snapshot was taken. For example, a default Snap Volume Name would be "SnapV4A7337AE038A". The full device path becomes: \Device\HarddiskDmVolumes \<DiskGroupName>\<NewVolName> |
writer=<WriterName> | Unique ID of the VSS writer, for example, "Microsoft Exchange Writer" or "Microsoft Exchange Writer Replica". If you plan to be able to do a roll-forward recovery to the point of failure, you must specify the writer. |
component=<ComponentName> | Name of the component; for Exchange, this is the storage group name found in the Exchange System Manager, for example, "First Storage Group". If you plan to be able to do a roll-forward recovery to the point of failure, you must use this component. |
backuptype=<Backuptype> | Specifies the type of backup, either a Full or Copy. If no option is specified then Copy is the default. Copy backup creates a copy of the database and transaction logs volumes. Full backup creates a copy of the database and transaction logs volumes, runs Eseutil to check for consistency, and if consistent, truncates the transaction logs. |
-e | Runs the Eseutil consistency check for database and log files. Eseutil is run automatically with a full backup, but must be optionally specified for a copy backup. |
-o | Allows an existing XML file of the same name to be overwritten. If -O is not specified the vxsnap create command does not overwrite an existing XML file of the same name and the operation fails. |
-c | Specifies a COW snapshot. In preparation for a COW snapshot, the vxsnap diffarea command must be used to create the shadow storage volume. The following vxsnap attributes are not compatible with COW snapshots and result in an error:
|
sechosts=<SecondaryHosts> | Applies to Volume Replicator (Volume Replicator) environment only. Comma-separated list of secondary hosts on which a synchronized snapshot is to be taken. |
Note:
Any text string that contains spaces must be enclosed in quotation marks.
This example creates a snapshot of the replica of the component mailbox. It specifies that the VSS Writer, Microsoft Exchange Writer Replica, is used for the snapshot.
vxsnap -x snapdata.xml create -C writer="Microsoft Exchange Writer" component=mb1 backuptype=COPY -E
Creates a COW snapshot of component mb1 of Exchange server. A copy backup is created and an Eseutil consistency check is performed on the snapshot volumes.
For Enterprise Vault operations:
vxsnap -x <Filename> create writer=<WriterName> [site=<SiteName>[/VSG=<VSGName>[VS=<VSName>]]] [[/]component=<ComponentName>[backuptype=FULL|COPY] [-o]
Creates snapshot(s) of the Enterprise Vault components. Allows the volumes to be snapshotted simultaneously.
The following attributes apply:
-x<Filename> | Indicates the name to be assigned to the XML metadata file that is created with the command. The file name must include the ".xml" extension. To specify a location other than the default location for the file, you must enter the full path for the file (e.g. J:\XML\Image1.xml). |
writer=<WriterName> | Unique ID of the VSS writer, for example, EnterpriseVault. Required if you specify the component. |
site=<SiteName> | Name of the Enterprise Vault site. |
VSG=<VSGName> | Name of the Enterprise Vault Vault Store Group. |
VS=<VSName> | Name of the Enterprise Vault Vault Store. |
component=<ComponentName> | Name of the Enterprise vault component. For example, Vault Store database, Fingerprint database, or Volume component, such as index, partitions, etc. |
backuptype=FULL|COPY | Specifies the type of backup, either a Full or Copy. If no option is specified then Copy is the default. |
-o | Allows an existing XML file of the same name to be overwritten. If -o is not specified the vxsnap create command does not overwrite an existing XML file of the same name and the operation fails. |
Note:
Any text string that contains spaces must be enclosed in quotation marks.
Additional information about the create operation for Enterprise Vault:
Specifying only the writer attribute (as in vxsnap -x xmlfile create writer=EnterpriseVault), results in the snapshot of the components of the entire Enterprise Vault farm. This would include the Enterprise Vault directory database, monitoring database, audit database, and reporting database.
Specifying the site attribute (as in vxsnap -x xmlfile create writer=EnterpriseVault Site=Site1), results in the snapshot of the components at the Enterprise Vault site level. This prepares the directory database and all the components (SQL and volume) in the specified site.
Specifying the vault store group attribute (as in vxsnap -x xmlfile create writer=EnterpriseVault Site=Site1/VSG=VSG1), results in the snapshot of the fingerprint database and all the components in all vault stores in the specified vault storage group.
Specifying the vault store attribute (as in vxsnap -x xmlfile create writer=EnterpriseVault Site=Site1/VSG=VSG1/VS=VS1), results in the snapshot of the vault store database and all the partitions in the specified vault store.
Specifying the component attribute (as in vxsnap -x xmlfile create writer=EnterpriseVault Site=Site1/VSG=VSG1/VS=VS1 Component=<Component Name>), results in the snapshot of the specified component. The component can be an Enterprise Vault SQL database or a volume component (e.g.vault store database, fingerprint database, directory database, monitoring database, reporting database, audit database, partition, index volume, etc.).
For vault store components: When the vault store database component is specified, the open partition in the vault store is also snapshotted.
For vault store components: When the open partition component is specified, the vault store database in the vault store is also snapshotted.
For different components: When different components reside on a common volume, the volume is snapshotted only once.
Upon completion of the operation, the status (successor failure) of the selected components is recorded in a log, %VMPATH%\logs\EVStatus.log. The log contains information about the success or failure of the operation for the components. In the event that the snapshot of a volume for a component fails, the operation does not snapshot the remaining volumes of the component nor any other requested components that are remaining. If the operation succeeds for all the volumes of a component, then the status of the component is logged as SUCCESS. If the operation fails for any one of the volumes of the component, then the status of all the components of that EnterpriseVault server is logged as FAILED along with the cause of the failure. The status of all components that had been already snapshotted earlier before the failed components are logged as SUCCESS, and the status of the remaining components that had not been snapshotted are logged as SKIPPED.
Examples
vxsnap -x snapdata.xml create writer=EnterpriseVault site=site1/vsg=vsg1/vs=vs1 site=site2 component="Index Location (V:)" component="Directory DB"
This example makes a snapshot of vault store "vs1" of site1/vsg1, "Index Location (V:)" of site2 and component "Directory DB".
vxsnap -x snapdata.xml create writer=EnterpriseVault site=site1
This example makes a complete snapshot of site1 (including the directory database).
For SQL operations:
vxsnap -x <Filename> create [-g <dynamicdiskgroupname>] source=<Volume>[/DriveLetter=<DriveLetter>][/DrivePath=<DrivePath>] [/Newvol=<NewVolName>][/Plex=<PlexName>]... [writer=<WriterName>] [component=<ComponentName>] [server=ServerName] [instance=InstanceName] [backuptype=FULL|COPY] [-o] [-c] [secHosts=<SecondaryHosts>]
Creates snapshot(s) of the specified volume(s) or SQL database. Allows the volumes to be snapshotted simultaneously.
Separate source volumes and attributes with forward slashes, not spaces. Source and snapshot volume attributes are paired. You must specify the source volume if you choose to specify the snapshot volume plex, drive letter, drive path, label, or volume name.
The following attributes apply:
-x <Filename> | Indicates the name to be assigned to the XML metadata file that is created with the command. The file name must include the ".xml" extension. To specify a location other than the default location for the file, you must enter the full path for the file (e.g. J:\XML\Image1.xml). |
-g <DynamicDiskGroupName> | Name of disk group that contains the source volume. Required when specifying volume name. |
source=<Volume> | Indicates the source volume for the split-mirror snapshot specified by a drive letter, drive path (mount point), or volume name of the form "\\?\Volume{GUID}\". Repeat this parameter for each volume associated with the specified component. |
[/plex=<PlexName>] | Specifies the name of the mirror or plex that is to be detached. Use this parameter if there are multiple snap plexes available to be snapshotted. |
[/DriveLetter=<DriveLetter>] | The drive letter to be assigned to the new snapshot volume. |
[/DrivePath=<DrivePath>] | The drive path to be assigned to the new snapshot volume. The drive path must reference an empty local NTFS folder, which was created beforehand. The path must include the drive letter and folder to be mounted, for example, C:\DB1VOL. |
[/Newvol=<NewVolName>] | Specifies the name of the new snapshot volume that is created. If the name is not specified, then the default snapshot volume name begins with "SnapV" followed by a 12 character alphanumeric string. The 12 character alphanumeric string is a coded hexadecimal timestamp based upon the time that the snapshot was taken. For example, a default Snap Volume Name would be "SnapV4A7337AE038A". The full device path becomes: \Device\HarddiskDmVolumes \<DiskGroupName>\<NewVolName> |
writer=<WriterName> | Unique ID of the VSS writer, for example, SQLServerWriter or the GUID for the writer. Required if you specify the component. |
component=<ComponentName> | Name of the database. The command prepares mirrors for both the database and log volumes of the SQL database. |
server=ServerName | SQL Server server name. |
instance=InstanceName | SQL Server instance name. |
backuptype=FULL|COPY | Specifies the type of backup, either a Full or Copy. If no option is specified then Copy is the default. To back up logs in SQL Server so that you can restore the database using SQL log replay, at least one Full backup must have been created earlier. |
-o | Allows an existing XML file of the same name to be overwritten. If -o is not specified the vxsnap create command does not overwrite an existing XML file of the same name and the operation fails. |
-c | Specifies a COW snapshot. In preparation for a COW snapshot, the vxsnap diffarea command must be used to create the shadow storage volume. The following vxsnap attributes are not compatible with COW snapshots and result in an error:
|
sechosts=<SecondaryHosts> | Applies to Volume Replicator (Volume Replicator) environment only. Comma-separated list of secondary hosts on which a synchronized snapshot is to be taken. |
Note:
Any text string that contains spaces must be enclosed in quotation marks.
Examples
vxsnap -x billing_DB.xml create source=G:/Newvol=billing_data source=H:/Newvol=billing_log writer=SQLServerWriter component=billing_DB backuptype=full
This example creates a snapshot set based on the component billing_DB which contains volume G, the database volume, and volume H, the log volume. The snapshot volumes are named billing_data and billing_log, respectively. The XML file, billing_DB.xml, is used to store the VSS metadata that identifies the snapshot set. This file is used in the command to reattach the snapshot set to resynchronize it and in the command to recover the database using the snapshot set.
vxsnap -x snapdata.xml create -C writer=sqlserverwriter component=testDB server=localhost
Creates a COW snapshot of SQL database testDB used in the default instance of the localhost.
For volume operations:
vxsnap -x <Filename> create [-g <dynamicdiskgroupname>] source=<Volume>[/DriveLetter=<DriveLetter>][/DrivePath=<DrivePath>] [/Newvol=<NewVolName>][/Plex=<PlexName>]...[-o] [-c]
Creates snapshot(s) of the specified volume(s). Allows volumes to be snapshotted simultaneously.
Separate source volumes and attributes with forward slashes, not spaces. Source and snapshot volume attributes are paired. You must specify the source volume if you choose to specify the snapshot volume plex, drive letter, drive path, label, or volume name.
The following attributes apply:
-x <Filename> | Indicates the name to be assigned to the XML metadata file that is created with the command. The file name must include the ".xml" extension. |
-g <DynamicDiskGroupName> | Name of disk group that contains the source volume. Required when specifying volume name. |
source=<Volume> | Indicates the source volume for the split-mirror snapshot specified by a drive letter, drive path (mount point), or volume name of the form "\\?\Volume{GUID}\". Repeat this parameter for each volume associated with the specified component. |
[/plex=<PlexName>] | Specifies the name of the mirror or plex that is to be detached. Use this parameter if there are multiple snap plexes available to be snapshotted. |
[/DriveLetter=<DriveLetter>] | The drive letter to be assigned to the new snapshot volume. |
[/DrivePath=<DrivePath>] | The drive path to be assigned to the new snapshot volume. The drive path must reference an empty local NTFS folder, which was created beforehand. The path must include the drive letter and folder to be mounted, for example, C:\DB1VOL. |
[/Newvol=<NewVolName>] | Specifies the name of the new snapshot volume that is created. If the name is not specified, then the default snapshot volume name begins with "SnapV" followed by a 12 character alphanumeric string. The 12 character alphanumeric string is a coded hexadecimal timestamp based upon the time that the snapshot was taken. For example, a default Snap Volume Name would be "SnapV4A7337AE038A". The full device path becomes: \Device\HarddiskDmVolumes \<DiskGroupName>\<NewVolName> |
-o | Allows an existing XML file of the same name to be overwritten. If -o is not specified the vxsnap create command does not overwrite an existing XML file of the same name and the operation fails. |
-c | Specifies a COW snapshot. In preparation for a COW snapshot, the vxsnap diffarea command must be used to create the shadow storage volume. The following vxsnap attributes are not compatible with COW snapshots and result in an error:
|
Note:
Any text string that contains spaces must be enclosed in quotation marks.
Examples
vxsnap -x snapdata.xml create source=E:\Data\DB1/DrivePath=E:\Backup\DB1 source=E:\Data\DB2/DrivePath=E:\Backup\DB2
This command does not specify a specific storage group (component) but rather creates snapshots from the volumes mounted on E:\Data\DB1 and E:\Data\DB2. The resulting snapshot volumes are assigned mount points E:\Backup\DB1 and E:\Backup\DB2, respectively. The metadata involved in this operation is stored in snapdata.xml.
vxsnap -x snapdata.xml create -C source=D:
Creates a COW snapshot of volume D: