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. InfoScale event logging
InfoScale log forwarding
Windows Server event logs can be forwarded from a forwarder (source) system to a collector (target) system within the same domain network. You can leverage this Windows Event Forwarding mechanism to forward InfoScale logs from one or more systems to a centralized collector system.
For details on best practices for configuring event log forwarding on Windows Server systems, refer to the Microsoft documentation.
To ensure that WinRM is set up and running on forwarder and collector systems
- Verify the status of the Windows Remote Management (WinRM) service by running the following command (use the Run as Administrator option):
winrm quickconfig
If WinRM is set up and the service is running, the following message is displayed:
WinRM service is already running on this machine. WinRM is already set up for remote management on this computer.
Otherwise, the following message is displayed:
WinRM is not set up to receive requests on this machine. The following changes must be made: Start the WinRM service. Set the WinRM service type to delayed auto start. Make these changes [y/n]?
At the prompt, type y and press Enter.
For details on configuring WinRM with default settings, refer to the Microsoft documentation.
To ensure that the collector system has access to the forwarder system
- On the forwarder system, open the Computer Management window.
In the left pane, expand System Tools > Local Users and Groups, and click Groups.
In the right pane, double-click Event Log Readers.
- On the Event Log Readers Properties window, on the General tab, click Add.
- On the Select Users, Computers, Service Accounts, or Groups dialog box:
In the Enter the object names to select field, enter the appropriate domain account name, and click Check Names.
Make sure that the account is validated in the domain network before you proceed.
Click Object Types.
On the Object Types dialog box, select the Computers check box, and click OK.
- In the Enter the object names to select field, enter the collector system name, and click Check Names.
Make sure that the system is validated in the domain network before you proceed.
- Click OK to save the changes and close the dialog box, and then close each of the windows opened for this procedure.
To set up the subscription on the collector system
- On the collector system, open the Event Viewer window.
- In the left pane, right-click Subscriptions and click Create Subscription.
- On the Subscription Properties window:
In the Subscription name field, provide an appropriate name for the InfoScale event collection subscription from the forwarder systems.
In the Destination Log dropdown list, select Forwarded Events.
In the Subscription type and source computers section, select Collector initiated and then click Select Computers.
In the collector-initiated subscription type, the collector system contacts the specified forwarder systems to collect event details. This subscription type works well in scenarios with a small, manageable number of forwarder systems.
- On the Computers dialog box, click Add Domain Computers.
- On the Select Computer dialog box, In the Enter the object name to select field, enter the forwarder system name, and click Check Names.
Make sure that the system is validated in the domain network before you proceed.
- Repeat steps 4 and 5 for each of the forwarder systems from which you want to collect the InfoScale event details.
- For each system in the Computers list on the left, click Test.
Make sure that the Event Viewer dialog box displays the Connectivity test succeeded message.
- Click OK to close the dialog boxes.
- On the Subscription Properties window, click Select Events.
- On the Query Filter window, set the various filters to narrow down the specific list of event details that you want the collector system to collect, and then click OK.
- On the Subscription Properties window, click Advanced.
- On the Advanced Subscription Settings dialog box:
Make sure that Machine Account is selected (default).
Select the Event Delivery Optimization option that is appropriate for the frequency of event details delivery as per your organization's needs.
- Click OK to save the changes and close the dialog box, and then close each of the windows opened for this procedure.
Henceforth, events for this subscription begin to appear under Event Viewer > Windows Logs > Forwarded Events, based on the filters set in step 10 and the frequency set in step 12.
- (Optional) Alternatively, on the Subscription Properties window, in the Subscription type and source computers section, you can select Source computer initiated and then click Select Computer Groups.
In the source computer-initiated subscription type, the forwarder systems contact the collector system to forward event details. This subscription type works well in scenarios with a large number of forwarder systems.
For details on creating the source computer-initiated subscription type, refer to the Microsoft documentation.