InfoScale™ 9.0 Storage Foundation 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 Enterprise Vault
- Using the VSS snapshot wizards with Microsoft SQL
- Copy on Write (COW)
- 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
- Volume encryption
- Secure file system (SecureFS) for protection against ransomware
- 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
- vxschadm
- sfcache
- Tuning SFW
- Appendix B. VDID details for arrays
- Appendix C. Executive Order logging
vxsnap reattach
For Enterprise Vault operations:
vxsnap -x <Filename> [-f] [-b] reattach [writer=<WriterName> [site=<SiteName>[/VSG=<VSGName>[VS=<VSName>]]] [[/]component=<ComponentName>
This command reattaches and resynchronizes the snapshot volumes in the snapshot set to the original Enterprise Vault component volumes.
The following attributes apply:
-x<Filename> | The file that is created by the vxsnap create command. Each snapshot set must have a unique name for the metadata file. Note: This file is deleted after the reattach operation has completed successfully. |
-f | Forces the reattach. Make sure that the volume is not in use by another application before using this command. Use this option with care. |
-b | Resynchronizes the volume in the background. A new snapshot cannot be made until the resynchronization is complete. |
writer=<WriterName> | Unique ID of the VSS writer, for example, EnterpriseVault or the GUID for the writer. |
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. |
Note:
Any text string that contains spaces must be enclosed in quotation marks.
Note:
Upon completion of the operation, the status (success or 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 reattach of a volume for a component fails, the operation continues to reattach the remaining volumes of the component and any other requested components. The components that successfully complete the operation are removed from the snapshot set. If the operation succeeds for all the volumes of a component, then the status of the component is logged as a success. If the operation fails for any one of the volumes of the component, then the status of the component is logged as a failure along with the cause of failure.
Example
vxsnap -x snapdata.xml reattach writer=EnterpriseVault site=site1/vsg=vsg1/vs=vs1 site=site2 component="Index Location (V:)" component="Directory DB"
This example reattaches all the snapshot volumes for the vault store vs1 of site1/vsg1, "Index Location (V:)" of site2 and "Directory DB".
For SQL operations:
vxsnap -x <Filename> [-f] [-b] reattach[writer=<WriterName>] [secHosts=<SecondaryHosts>]
This command reattaches and resynchronizes the snapshot volumes in the snapshot set to the original database volumes.
The following attributes apply:
-x <Filename> | The file that is created by the vxsnap create command. Each snapshot set must have a unique name for the metadata file. Note: This file is deleted after the reattach operation has completed successfully. |
-f | Forces the reattach. Make sure that the volume is not in use by another application before using this command. Use this option with care. |
-b | Resynchronizes the volume in the background. A new snapshot cannot be made until the resynchronization is complete. |
writer=<WriterName> | Unique ID of the VSS writer, for example, SQLServerWriter or the GUID for the writer. |
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:
Make sure that the snapshot volumes are not in use before using this command.
Example
vxsnap -x billing_DB.xml reattach writer=SQLServerWriter
This command uses the information in the snapdata.xml file to reattach and resynchronize all the volumes in the snapshot set. This xml file is deleted after the reattach operation has completed successfully. The snapshot volumes remain synchronized with the original volumes until the vxsnap create command is issued.
Note:
Any text string that contains spaces must be enclosed in quotation marks.
For volume operations:
vxsnap -x <Filename> [-f] [-b] reattach
This command reattaches and resynchronizes the snapshot volumes in the snapshot set to the original database volumes.
The following attributes apply:
-x <Filename> | The file that is created by the vxsnap create command. Each snapshot set must have a unique name for the metadata file. Note: This file is deleted after the reattach operation has completed successfully. |
-f | Forces the reattach. Make sure that the volume is not in use by another application before using this command. Use this option with care. |
-b | Resynchronizes the volume in the background. A new snapshot cannot be made until the resynchronization is complete. |
Note:
Make sure that the snapshot volumes are not in use before using this command.
Example
vxsnap -x snapdata.xml reattach
This command uses the information in the snapdata.xml file to reattach and resynchronize all the volumes in the snapshot set. This xml file is deleted after the reattach operation has completed successfully. The snapshot volumes remain synchronized with the original volumes until the vxsnap create command is issued.