Veritas InfoScale™ 7.4.1 Release Notes - Windows

Last Published:
Product(s): InfoScale & Storage Foundation (7.4.1)
Platform: Windows
  1. Release notes for Veritas InfoScale
    1.  
      About this document
    2.  
      Requirements
    3. Changes introduced in 7.4.1
      1.  
        Changes related to licensing
      2.  
        Support for service group configuration wizards in IPv6 environments
      3.  
        Support for Microsoft SQL Server 2017
      4.  
        AWS EBSVol agent
      5.  
        New high availability agents for Google Cloud Platform (GCP)
      6.  
        Support for InfoScale configurations in Google Cloud
      7.  
        Deprecated support for co-existence of Veritas InfoScale products
    4.  
      Fixed issues
    5. Limitations
      1. Deployment limitations
        1.  
          Log on to remote nodes before installation
        2.  
          Silent installation does not support updating license keys after install
        3.  
          UUID files are always installed to the default installation path
        4.  
          SnapDrive service fails to start after InfoScale Availability or InfoScale Enterprise is uninstalled
      2. Cluster management limitations
        1.  
          Undocumented commands and command options
        2.  
          Unable to restore user database using SnapManager for SQL
        3.  
          MountV agent does not work when Volume Shadow Copy service is enabled
        4.  
          WAN cards are not supported
        5.  
          System names must not include periods
        6.  
          Incorrect updates to path and name of types.cf with spaces
        7.  
          VCW does not support configuring broadcasting for UDP
        8.  
          Undefined behavior when using VCS wizards for modifying incorrectly configured service groups
        9.  
          Service group dependency limitation - no failover for some instances of parent group
        10.  
          Unable to monitor resources if Switch Independent NIC teaming mode is used
        11.  
          Windows Safe Mode boot options not supported
        12.  
          MountV agent does not detect file system change or corruption
        13.  
          MirrorView agent resource faults when agent is killed
        14.  
          Security issue when using Java GUI and default cluster admin credentials
        15.  
          VCS Authentication Service does not support node renaming
        16.  
          An MSMQ resource fails to come online after the virtual server name is changed
        17.  
          Configuration wizards do not allow modifying IPv4 address to IPv6
        18.  
          All servers in a cluster must run the same operating system
        19.  
          Running Java Console on a non-cluster system is recommended
        20.  
          Cluster Manager console does not update GlobalCounter
        21.  
          Cluster address for global cluster requires resolved virtual IP
        22.  
          Cluster operations performed using the Symantec High Availability dashboard may fail
      3. Storage management limitations
        1.  
          SFW does not support disks with unrecognized OEM partitions
        2.  
          Only one disk gets removed from an MSFT compatible disk group even if multiple disks are selected to be removed
        3.  
          Cannot create MSFT compatible disk group if the host name has multibyte characters
        4.  
          Fault detection is slower in case of Multipath I/O over Fibre Channel
        5.  
          FlashSnap solution for EV does not support basic disks
        6.  
          Incorrect mapping of snapshot and source LUNs causes VxSVC to stops working
        7.  
          SFW does not support operations on disks with sector size greater than 512 bytes; VEA GUI displays incorrect size
        8.  
          Database or log files must not be on same volume as Exchange or SQL Server
        9.  
          Operations in SFW may not be reflected in DISKPART
        10.  
          Disk signatures of system and its mirror may switch after ASR recovery
        11.  
          Adding a storage group that contains many disks and volumes causes SFW and Microsoft Exchange System Manager to respond very slowly.
        12.  
          SFW does not support growing a LUN beyond 2 TB
        13.  
          SCSI reservation conflict occurs when setting up cluster disk groups
        14.  
          Snapshot operation fails when the Veritas VSS Provider is restarted while the Volume Shadow Copy service is running and the VSS providers are already loaded
        15.  
          When a node is added to a cluster, existing snapshot schedules are not replicated to the new node
        16.  
          Restore from Copy On Write (COW) snapshot of MSCS clustered shared volumes fails
        17.  
          Dynamic Disk Groups are not imported after system reboot in a Hyper-V environment
        18.  
          Storage Agent cannot reconnect to VDS service when restarting Storage Agent
        19.  
          SFW does not support transportable snapshots on Windows Server
        20.  
          vxsnapsql restores all SQL Server databases mounted on the same volume
        21.  
          Windows Disk Management console does not display basic disk converted from SFW dynamic disk
        22.  
          SharePoint components must have unique names
        23.  
          DCM or DRL log on thin provisioned disk causes all disks for volume to be treated as thin provisioned disks
        24.  
          After import/deport operations on SFW dynamic disk group, DISKPART command or Microsoft Disk Management console do not display all volumes
        25.  
          Restored Enterprise Vault components may appear inconsistent with other Enterprise Vault components
        26.  
          Enterprise Vault restore operation may fail for some components
        27.  
          Shrink volume operation may increase provisioned size of volume
        28.  
          Reclaim operations on a volume residing on a Hitachi array may not give optimal results
        29.  
          Storage migration of Hyper-V VM on cluster-shared volume resource is not supported from a Slave node
        30.  
          In a CVM environment, disconnecting and reconnecting hard disks may display an error
        31.  
          Limitations of SFW support for DMP
      4. Multi-pathing limitations
        1.  
          DSM ownership of LUNs
      5. Replication limitations
        1.  
          Resize Volume and Autogrow not supported in Synchronous mode
        2.  
          Expand volume not supported if RVG is in DCM logging mode
        3.  
          Fast failover is not supported if the RLINK is in hard synchronous mode
      6. Solution configuration limitations
        1.  
          Virtual fire drill not supported in Windows environments
        2.  
          Solutions wizard support in a 64-bit VMware environment
        3.  
          Solutions wizards fail to load unless the user has administrative privileges on the system
        4.  
          Discovery of SFW disk group and volume information sometimes fails when running Solutions wizards
        5.  
          DR Wizard does not create or validate service group resources if a service group with the same name already exists on the secondary site
        6.  
          Quick Recovery wizard displays only one XML file path for all databases, even if different file paths have been configured earlier
        7.  
          Enterprise Vault Task Controller and Storage services fail to start after running the Enterprise Vault Configuration Wizard if the MSMQ service fails to start
        8.  
          Limitation on SnapManager for Exchange
        9.  
          VCS locks shared volumes during Exchange recovery
        10.  
          Schedule backups on online nodes
        11.  
          Wizard fails to discover SQL Server databases that contain certain characters
      7. Internationalization and localization limitations
        1.  
          Systems in a cluster must have same system locale setting
      8. Interoperability limitations
        1.  
          ApplicationHA Heartbeat agents are not supported in VCS cluster configurations
        2.  
          NBU restore changes the disk path and UUID due to which VMwareDisks resource reports an unknown state
        3.  
          Lock by third-party monitoring tools on shared volumes
        4.  
          SFW cannot coexist with early Veritas Anti-virus software
    6. Known issues
      1. Deployment issues
        1.  
          "Run Configuration Checker" link available on the CD browser only downloads the Configuration Checker
        2.  
          Reinstallation of an InfoScale product may fail due to pending cleanup tasks
        3.  
          Delayed installation on certain systems
        4.  
          Installation may fail with the "Windows Installer Service could not be accessed" error
        5.  
          Installation may fail with "Unspecified error" on a remote system
        6.  
          The installation may fail with "The system cannot find the file specified" error
        7.  
          Installation may fail with a fatal error for VCS msi
        8.  
          In SFW with Microsoft failover cluster, a parl.exe error message appears when system is restarted after SFW installation if Telemetry was selected during installation
        9.  
          Side-by-side error may appear in the Windows Event Viewer
        10.  
          FlashSnap License error message appears in the Application Event log after installing license key
        11.  
          VCS uninstallation halts and displays an error message; uninstall continues after clearing the message
        12.  
          Uninstallation may fail to remove certain folders
        13.  
          Error while uninstalling the product if licensing files are missing
        14.  
          The vxlicrep.exe may crash when the machine reboots after InfoScale Enterprise is installed
      2. Cluster management issues
        1. Cluster Server (VCS) issues
          1.  
            The VCS Cluster Configuration Wizard may not be able to delete a cluster if it fails to stop HAD
          2.  
            Deleting a node from a cluster using the VCS Cluster Configuration Wizard may not remove it from main.cf
          3.  
            NetAppSnapDrive resource may fail with access denied error
          4.  
            Mount resource fails to bring file share service group online
          5.  
            Mount agent may go in unknown state on virtual machines
          6.  
            AutoStart may violate limits and prerequisites Load Policy
          7.  
            Enterprise Vault Configuration Wizard may fail to connect to SQL Server
          8.  
            File Share Configuration Wizard may create dangling VMDg resources
          9.  
            For volumes under VMNSDg resource, capacity monitoring and automatic volume growth policies do not get available to all cluster nodes
          10.  
            For creating VMNSDg resources, the VMGetDrive command not supported to retrieve a list of dynamic disk groups
          11.  
            First failover attempt might fault for a NativeDisks configuration
          12.  
            Resource fails to come online after failover on secondary
          13.  
            Upgrading a secure cluster may require HAD restart
          14.  
            New user does not have administrator rights in Java GUI
          15.  
            HTC resource probe operation fails and reports an UNKNOWN state
          16.  
            Resources in a parent service group may fail to come online if the AutoStart attribute for the resources is set to zero
          17.  
            VCS wizards may fail to probe resources
          18.  
            Changes to referenced attributes do not propagate
          19.  
            ArgListValue attribute may not display updated values
          20.  
            The Veritas High Availability Engine (HAD) service fails to stop
          21.  
            Engine may hang in LEAVING state
          22.  
            Timing issues with AutoStart policy
          23.  
            The VCS Cluster Configuration Wizard (VCW) supports NIC teaming but the Symantec High Availability Configuration Wizard does not
          24.  
            VCS engine HAD may not accept client connection requests even after the cluster is configured successfully
          25.  
            Hyper-V DR attribute settings should be changed in the MonitorVM resource if a monitored VM is migrated to a new volume
          26.  
            One or more VMNSDg resources may fail to come online during failover of a large service group
          27.  
            VDS error reported while bringing the NativeDisks and Mount resources online after a failover
          28.  
            SQL Server service resource does not fault even if detail monitoring fails
          29.  
            Delay in refreshing the VCS Java Console
          30.  
            NetBackup may fail to back up SQL Server database in VCS cluster environment
        2. Cluster Manager (Java Console) issues
          1.  
            Cluster connection error while converting local service group to a global service group
          2.  
            Repaint feature does not work properly when look and feel preference is set to Java
          3.  
            Exception when selecting preferences
          4.  
            Java Console errors in a localized environment
          5.  
            Common system names in a global cluster setup
          6.  
            Agent logs may not be displayed
          7.  
            Login attempts to the Cluster Manager may fail after a product upgrade
        3. Global service group issues
          1.  
            VCW configures a resource for GCO in a cluster without a valid GCO license
          2.  
            Group does not go online on AutoStart node
          3.  
            Cross-cluster switch may cause concurrency violation
          4.  
            Declare cluster dialog may not display highest priority cluster as failover target
          5.  
            Global group fails to come online on the DR site with a message that it is in the middle of a group operation
        4. VMware virtual environment-related issues
          1.  
            VMwareDisks resource cannot go offline if VMware snapshot is taken when VMware disk is configured for monitoring
          2.  
            Guest virtual machines fail to detect the network connectivity loss
          3.  
            VMware vMotion fails to move a virtual machine back to an ESX host where the application was online
          4.  
            VCS commands may fail if the snapshot of a system on which the application is configured is reverted
          5.  
            VMWareDisks resource cannot probe (Unknown status) when virtual machine moves to a different ESX host
          6.  
            Error while unconfiguring the VCS cluster from the Symantec High Availability tab
          7.  
            The Symantec High Availability Configuration Wizard gives an error for invalid user account details if the system password contains double quotes (")
          8.  
            The Symantec High Availability view does not display any sign for the concurrency violation
          9.  
            The Symantec High Availability installer may fail to block the installation of unrelated license keys
          10.  
            The Symantec High Availability configuration wizard fails to configure the VCS cluster if UAC is enabled
          11.  
            Symantec High Availability Configuration wizard may fail to configure monitoring for the selected mount points
      3. Storage management issues
        1. Storage Foundation
          1.  
            In Microsoft Azure environment, InfoScale Storage cannot be used in cluster configurations that require shared storage
          2.  
            In a Microsoft Azure environment SFW fails to auto discover SSD media type for a VHD
          3.  
            Disks may appear in "Failing" state with an I/O error on multipathed-LUNs
          4.  
            Incorrect message appears in the Event Viewer for a hot relocation operation
          5.  
            A volume state continues to appear as "Healthy, Resynching"
          6.  
            After a mirror break-off operation, the volume label does not show on the Slave node
          7.  
            CVM cluster does not support node names with more than 15 characters
          8.  
            For CSDG with mirrored volumes, sometimes disks incorrectly shows the yellow warning icon
          9.  
            SSD is not removed successfully from the cache pool
          10.  
            On fast failover enabled configurations, VMDg resource takes a longer time to come online
          11.  
            On some configurations, the VSS snapshot operation may fail to add volumes to the snapshot set
          12.  
            Using Failover Cluster Manager you cannot migrate volumes belonging to Hyper-V virtual machines to a location with VMDg or Volume Manager Shared Volume resource type
          13.  
            Performance counters for Dynamic Disk and Dynamic Volume may fail to appear in the list of available counters
          14.  
            VSS snapshot of a Hyper-V virtual machine on SFW storage does not work from NetBackup
          15.  
            Virtual machine created using Failover Cluster Manager cannot be monitored and managed using SCVMM 2012 and 2012 R2
          16.  
            In some cases, when 80 or more mirrored volume resources fail over to another node in CVM, some volume resources fault causing all to fault
          17.  
            In CVM, if subdisk move operation for CSDG fails because of a cluster reconfiguration, it does not start again automatically
          18.  
            Stale volume entries under MountedDevices and CurrentControlSet registries not removed after the volume is deleted
          19.  
            Some arrays do not show correct Enclosure ID in VDID
          20.  
            In some cases, EV snapshot schedules fail
          21.  
            In CVM, Master node incorrectly displays two missing disk objects for a single disk disconnect
          22.  
            DRL plex is detached across CVM nodes if a disk with DRL plex is disconnected locally from the node where volume is online
          23.  
            Error while converting a Microsoft Disk Management Disk Group created using iSCSI disks to an SFW dynamic disk group
          24.  
            Snapshot schedules intermittently fail on the Slave node after failover
          25.  
            In VEA GUI, Tasks tab does not display task progress for the resynchronization of a cluster-shared volume if it is offline
          26.  
            Snapback operation from a Slave node always reports being successful on that node, even when it's in progress or resynchronization fails on Master
          27.  
            For cluster-shared volumes, only one file share per Microsoft failover cluster is supported
          28.  
            After cluster-shared volume resize operation, free space of the volume is not updated on nodes where volume is offline
          29.  
            Issues due to Microsoft Failover Clustering not recognizing SFW VMDg resource as storage class
          30.  
            If fast failover is enabled for a VMDg resource, then SFW volumes are not displayed in the New Share Wizard
          31.  
            Volume information not displayed for VMDg and RVG resources in Failover Cluster Manager
          32.  
            Failover of VMDg resource from one node to another does not mount the volume when disk group volume is converted from LDM to dynamic
          33.  
            vxverify command may not work if SmartMove was enabled while creating the mirrored volume
          34.  
            After installation of SFW or SFW HA, mirrored and RAID-5 volumes and disk groups cannot be created from LDM
          35.  
            Some operations related to shrinking or expanding a dynamic volume do not work
          36.  
            VEA GUI displays error while creating partitions
          37.  
            For dynamic disk group configured as VMNSDg resource, application component snapshot schedules are not replicated to other nodes in a cluster if created using VSS Snapshot Scheduler Wizard
          38.  
            In Microsoft failover cluster, if VxSVC is attached to Windows Debugger, it may stop responding when you try to bring offline a service group with VMDg resources
          39.  
            In some cases, updated VSS components are not displayed in VEA console
          40.  
            Storage reclamation commands do not work when SFW is run inside Hyper-V virtual machines
          41.  
            Unknown disk group may be seen after deleting a disk group
          42.  
            Wrong information related to disk information is displayed in the Veritas Enterprise Administrator (VEA) console. Single disk is displayed as two disks (harddisk and a missing disk)
          43.  
            SFW Configuration Utility for Hyper-V Live Migration support wizard shows the hosts as Configured even if any service fails to be configured properly
          44.  
            System shutdown or crash of one cluster node and subsequent reboot of other nodes resulting in the SFW messaging for Live Migration support to fail
          45.  
            Changing the FastFailover attribute for a VMDg resource from FALSE to TRUE throws an error message
          46.  
            A remote partition is assumed to be on the local node due to Enterprise Vault DNS alias check
          47.  
            After performing a restore operation on a COW snapshot, the "Allocated size" shadow storage field value is not getting updated on the VEA console
          48.  
            Messaging service does not retain its credentials after upgrading SFW and SFW HA
          49.  
            Enterprise Vault (EV) snapshots are displayed in the VEA console log as successful even when the snapshots are skipped and no snapshot is created
          50.  
            On a clustered setup, split-brain might cause the disks to go into a fail state
          51.  
            Takeover and Failback operation on Sun Controllers cause disk loss
          52.  
            Microsoft failover cluster disk resource may fail to come online on failover node in case of node crash or storage disconnect if DMP DSMs are installed
          53.  
            The Veritas Enterprise Administrator (VEA) console cannot remove the Logical Disk Management (LDM) missing disk to basic ones
          54.  
            After breaking a Logical Disk Manager (LDM) mirror volume through the LDM GUI, LDM shows 2 volumes with the same drive letter
          55.  
            Unable to failover between cluster nodes. Very slow volume arrival
          56.  
            VDS errors noticed in the event viewer log
          57.  
            Restore with -a option for component-based snapshot fails for Exchange mailboxes on a VCS setup
          58.  
            An extra GUI Refresh is required to ensure that changes made to the volumes on a cluster disk group having the Volume Manager Disk Group (VMDg) resource gets reflected in the Failover Cluster Manager Console
          59.  
            DR wizard cannot create an RVG that contains more than 32 volumes
          60.  
            Allow restore using the vxsnap restore command if mailbox is removed or missing
          61.  
            Scheduled VSS snapshots of an Exchange mailbox database configured under a VCS cluster setup starts with some delay of around two to three minutes
          62.  
            Event viewer shows error message "Could not impersonate Veritas Scheduler Service login user ....." when VSS restore and snapback operations are performed
          63.  
            For a cluster setup, configure the Veritas Scheduler Services with a domain user account
          64.  
            Snapshot metadata files are not deleted after VSS Snapback and PIT Restore operation
          65.  
            If an inaccessible path is mentioned in the vxsnap create CLI, the snapshot gets created and the CLI fails
          66.  
            If snapshot set files are stored on a Fileshare path, then they are visible and accessible by all nodes in the VCS cluster
          67.  
            Sharing property of folders not persistent after system reboot
          68.  
            Microsoft Disk Management console displays an error when a basic disk is encapsulated
          69.  
            Results of a disk group split query on disks that contain a shadow storage area may not report the complete set of disks
          70.  
            Extending a simple volume in Microsoft Disk Management Disk Group fails
          71.  
            SFW cannot merge recovered disk back to RAID5 volume
          72.  
            Request for format volume occurs when importing dynamic disk group
          73.  
            Logging on to SFW as a member of the Windows Administrator group requires additional credentials
          74.  
            Certain operations on a dynamic volume cause a warning
          75.  
            Avoid encapsulating a disk that contains a system-critical basic volume
          76.  
            Sharing property of folders in clustering environment is not persistent
          77.  
            Entries under Task Tab may not be displayed with the correct name
          78.  
            Attempting to add a gatekeeper device to a dynamic disk group can cause problems with subsequent operations on that disk group until the storage agent is restarted
          79.  
            ASR fails to restore a disk group that has a missing disk
          80.  
            Mirrored volume in Microsoft Disk Management Disk Group does not resynchronize
          81.  
            Expand volume operation not supported for certain types of volumes created by Microsoft Disk Management
          82.  
            MirrorView resource cannot be brought online because of invalid security file
          83.  
            Known behavior with disk configuration in campus clusters
        2. VEA console issues
          1.  
            Login to VEA on an IPv6-enabled system with the Logged On User on this computer option may cause incorrect privileges to be assigned
          2.  
            VEA may fail to start when launched through the SCC, PowerShell, or Windows Start menu or Apps menu
          3.  
            On Windows operating systems, non-administrator user cannot log on to VEA GUI if UAC is enabled
          4.  
            VEA GUI sometimes does not show all the EV components
          5.  
            VEA GUI incorrectly shows yellow caution symbol on the disk icon
          6.  
            Reclaim storage space operation may not update progress in GUI
          7.  
            VEA GUI fails to log on to iSCSI target
          8.  
            VEA does not display properly when Windows color scheme is set to High Contrast Black
          9.  
            VEA displays objects incorrectly after Online/Offline disk operations
          10.  
            Disks displayed in Unknown disk group after system reboot
        3. Snapshot and restore issues
          1.  
            Vxsnap restore CLI command fails when specifying a full path name for a volume
          2.  
            Restoring COW snapshots causes earlier COW snapshots to be deleted
          3.  
            COW restore wizard does not update selected volumes
          4.  
            Snapshot operation requires additional time
          5.  
            Incorrect message displayed when wrong target is specified in vxsnap diffarea command
          6.  
            Restore operation on SQL Server component with missing volume fails
          7.  
            Snapshot operation of remote Sharepoint database fails when it resides on local SharePoint server
          8.  
            Snapshot of Microsoft Hyper-V virtual machine results in deported disk group on Hyper-V guest
          9.  
            Enterprise Vault restore operation fails for remote components
          10.  
            Persistent shadow copies are not supported for FAT and FAT32 volumes
          11.  
            Copy On Write (COW) snapshots are automatically deleted after shrink volume operation
          12.  
            Shadow storage settings for a Copy On Write (COW) snapshot persist after shrinking target volume
          13.  
            Copy On Write (COW) shadow storage settings for a volume persist on newly created volume after breaking its snapshot mirror
          14.  
            Conflict occurs when VSS snapshot schedules or VSS snapshots have identical snapshot set names
          15.  
            Microsoft Outlook 2007 Client (caching mode enabled) does not display restore messages after VSS Exchange restore operation completes
          16.  
            VSS Writers cannot be refreshed or contacted
          17.  
            Time-out errors may occur in Volume Shadow Copy Service (VSS) writers and result in snapshots that are not VSS compliant
          18.  
            vxsnapsql restore may fail to restore SQL Server database
          19.  
            VSS objects may not display correctly in VEA
          20.  
            VSS Snapshot of a volume fails after restarting the VSS provider service
          21.  
            Snapshot operation fails if components with the same name exist in different Exchange virtual servers
          22.  
            CLI command, vxsnap prepare, does not create snapshot mirrors in a stripe layout
          23.  
            After taking a snapshot of a volume, the resize option of the snapshot is disabled
          24.  
            If the snapshot plex and original plex are of different sizes, the snapback fails
        4. Snapshot scheduling issues
          1.  
            Snapshot schedule fails as result of reattach operation error
          2.  
            Next run date information of snapshot schedule does not get updated automatically
          3.  
            VEA GUI may not display correct snapshot schedule information after Veritas Scheduler Service configuration update
          4.  
            Scheduled snapshots affected by transition to Daylight Savings Time
          5.  
            In a cluster environment, the scheduled snapshot configuration succeeds on the active node but fails on another cluster node
          6.  
            After a failover occurs, a snapshot operation scheduled within two minutes of the failover does not occur
          7.  
            Unable to create or delete schedules on a Microsoft failover cluster node while another cluster node is shutting down
          8.  
            Quick Recovery Wizard schedules are not executed if service group fails over to secondary zone in a replicated data cluster
          9.  
            On Windows Server, a scheduled snapshot operation may fail due to mounted volumes being locked by the OS
      4. Multi-pathing issues
        1.  
          Multi-pathing may be disabled on Windows Server 2016 systems
        2.  
          Changes made to a multipathing policy of a LUN using the Microsoft Disk Management console, do not appear on the VEA GUI
        3.  
          vxdmpadm's deviceinfo and pathinfo with disk specified in p#c#t#l# parameter displays information only by one path
      5. Replication issues
        1.  
          VVR replication may fail if Symantec Endpoint Protection (SEP) version 12.1 is installed
        2.  
          VVR replication fails to start on systems where Symantec Endpoint Protection (SEP) version 12.1 or 12.1 RU2 is installed
        3.  
          RVGPrimary resource fails to come online if VCS engine debug logging is enabled
        4.  
          "Invalid Arguments" error while performing the online volume shrink
        5.  
          vxassist shrinkby or vxassist querymax operation fails with "Invalid Arguments"
        6.  
          In synchronous mode of replication, file system may incorrectly report volumes as raw and show "scan and fix" dialog box for fast failover configurations
        7.  
          VxSAS configuration wizard doesn't work in NAT environments
        8.  
          File system may incorrectly report volumes as raw due to I/O failure
        9.  
          NTFS errors are displayed in Event Viewer if fast-failover DR setup is configured with VVR
        10.  
          Volume shrink fails because RLINK cannot resume due to heavy I/Os
        11.  
          Online volume shrink operation fails for data volumes with multiple Secondaries if I/Os are active
        12.  
          RLINKs cannot connect after changing the heartbeat port number
        13.  
          On a DR setup, if Replicated Data Set (RDS) components are browsed for on the secondary site, then the VEA console does not respond
        14.  
          Secondary host is getting removed and added when scheduled sync snapshots are taken
        15.  
          Replication may stop if the disks are write cache enabled
        16.  
          Discrepancy in the Replication Time Lag Displayed in VEA and CLI
        17.  
          The vxrlink updates command displays inaccurate values
        18.  
          Some VVR operations may fail to complete in a cluster environment
        19.  
          IBC IOCTL Failed Error Message
        20.  
          Pause and Resume commands take a long time to complete
        21.  
          Replication keeps switching between the pause and resume state
        22.  
          VEA GUI has problems in adding secondary if all NICs on primary are DHCP enabled
        23.  
          Pause secondary operation fails when SQLIO is used for I/Os
        24.  
          Performance counter cannot be started for VVR remote hosts in perfmon GUI
        25.  
          VVR Graphs get distorted when bandwidth value limit is set very high
        26.  
          BSOD seen on a Hyper-V setup
        27.  
          Unable to start statistics collection for VVR Memory and VVR remote hosts object in Perfmon
        28.  
          Bunker primary fails to respond when trying to perform stop replication operation on secondary
        29.  
          CLI shows the "Volume in use" error when you dismount the ReFS data volumes on the Secondary RVG.
      6. Solution configuration issues
        1.  
          Exchange 2010 Configuration Wizard does not allow to select the application databases
        2.  
          Permission issues after upgrading an Exchange cluster
        3.  
          Exchange service group does not fail over after installing ScanMail 8.0
        4.  
          Error while performing Exchange post-installation steps
        5.  
          Resource for Exchange Information Store may take time to online
        6.  
          Oracle Enterprise Manager cannot be used for database control
        7.  
          Unexplained errors with DR wizard and QR wizard
        8.  
          VCS FD and DR wizards fail to configure application and hardware replication agent settings
        9. Disaster recovery (DR) configuration issues
          1.  
            The Disaster Recovery Configuration Wizard or the Fire Drill Wizard cannot proceed when configuring an application in an EMC SRDF replication environment
          2.  
            The DR Wizard does not provide a separate "GCO only" option for VVR-based replication
          3.  
            The Disaster Recovery Wizard fails if the primary and secondary sites are in different domains or if you run the wizard from another domain
          4.  
            The Disaster Recovery Wizard may fail to bring the RVGPrimary resources online
          5.  
            The Disaster Recovery Wizard requires that an existing storage layout for an application on a secondary site matches the primary site layout
          6.  
            The Disaster Recovery Wizard may fail to create the Secondary Replicator Log (SRL) volume
          7.  
            The Disaster Recovery Wizard may display a failed to discover NIC error on the Secondary system selection page
          8.  
            Service group cloning fails if you save and close the configuration in the Java Console while cloning is in progress
          9.  
            If RVGs are created manually with mismatched names, the DR Wizard does not recognize the RVG on the secondary site and attempts to create the secondary RVG
          10.  
            Cloned service group faults and fails over to another node during DR Wizard execution resulting in errors
          11.  
            DR wizard may display database constraint exception error after storage validation in EMC SRDF environment
          12.  
            DR wizard creation of secondary RVGs may fail due to mounted volumes being locked by the OS
          13.  
            DR wizard with VVR replication requires configuring the preferred network setting in VEA
          14.  
            DR wizard displays error message on failure to attach DCM logs for VVR replication
          15.  
            Disaster Recovery (DR) Wizard fails to automatically set the correct storage replication option in case of SRDF
          16.  
            Disaster Recovery (DR) Wizard reports an error during storage cloning operation in case of SRDF
        10. Fire drill (FD) configuration issues
          1.  
            Fire Drill Wizard may fail to recognize that a volume fits on a disk if the same disk is being used for another volume
          2.  
            Fire drill may fail if run again after a restore without exiting the wizard first
          3.  
            Fire Drill Wizard may time out before completing fire drill service group configuration
          4.  
            RegRep resource may fault while bringing the fire drill service group online during "Run Fire Drill" operation
          5.  
            Fire Drill Wizard in an HTC environment is untested in a configuration that uses the same horcm file for both regular and snapshot replication
          6.  
            FireDrill attribute is not consistently enabled or disabled
          7.  
            MountV resource state incorrectly set to UNKNOWN
        11. Quick recovery (QR) configuration issues
          1.  
            Quick Recovery Wizard allows identical names to be assigned to snapshot sets for different databases
      7. Internationalization and localization issues
        1.  
          Only US-ASCII characters are supported
        2.  
          Use only U.S. ASCII characters in the SFW or SFW HA installation directory name
        3.  
          Language preference in Veritas Enterprise Administrator (VEA) must be set to English (United States) or Japanese (Japan)
        4.  
          VEA GUI cannot show double-byte characters correctly on (English) Windows operating system
        5.  
          VEA can't connect to the remote VEA server on non-English platforms
        6.  
          Unable to output correct results for Japanese commands
        7.  
          SSO configuration fails if the system name contains non-English locale characters [2910613]
        8.  
          VCS cluster may display "stale admin wait" state if the virtual computer name and the VCS cluster name contains non-English locale characters
        9.  
          Issues faced while configuring application monitoring for a Windows service having non-English locale characters in its name
      8. Interoperability issues
        1.  
          Backup Exec 12 installation fails in a VCS environment
        2.  
          Symantec Endpoint Protection security policy may block the VCS Cluster Configuration Wizard
        3.  
          VCS cluster configuration fails if Symantec Endpoint Protection 11.0 MR3 version is installed
        4.  
          VCS services do not start on systems where Symantec Endpoint Protection (SEP) version 12.1 is installed
        5.  
          Several issues while you configure VCS on systems where Symantec Endpoint Protection (SEP) version 12.1 is installed
      9. Miscellaneous issues
        1.  
          Cluster node may become unresponsive if you try to modify network properties of adapters assigned to the VCS private network
        2.  
          SharePoint 2010 resource faults with an initialization error
        3.  
          Sharepoint 2010 resource fails to come online on non-central administrator node
        4.  
          MSMQ resource fails to come online if the MSMQ directory path contains double byte characters
        5.  
          Error while switching global service groups using Veritas Operations Manager 3.0
        6.  
          Saving large configuration results in very large file size for main.cf
        7.  
          AutoStart may violate limits and prerequisites load policy
        8.  
          Trigger not invoked in REMOTE_BUILD state
        9.  
          Some alert messages do not display correctly
        10.  
          If VCS upgrade fails on one or more nodes, HAD fails to start and cluster becomes unusable
        11.  
          Custom settings in the cluster configuration are lost after an upgrade if attribute values contain double quote characters
        12.  
          Options on the Domain Selection panel in the VCS Cluster Configuration Wizard are disabled
        13.  
          Live migration of a VM, which is part of a VCS cluster where LLT is configured over Ethernet, from one Hyper-V host to another may result in inconsistent HAD state
        14.  
          If a NIC that is configured for LLT protocol is disabled, LLT does not notify clients
        15. Fibre Channel adapter issues
          1.  
            Emulex Fibre Channel adapters
          2.  
            QLogic Fibre Channel adapters
        16.  
          Storage agent issues and limitations in VMware virtual environments
    7.  
      Documentation errata

Enterprise Vault Configuration Wizard may fail to connect to SQL Server

In the Enterprise Vault Configuration Wizard, if SQL Server is previously configured for high availability, you must enter the name in the virtualServerName\instanceName format. Sometimes, even though you specify the SQL Server instance name in the required format, you may encounter an error after you click Next. The error message states that Enterprise Vault failed to connect to the SQL Server instance. (2432332)

Workaround:

In the appropriate field, delete the virtual server name and add the physical server name in the physicalServerName\instanceName format.

Click Next, and after the next panel appears, click Back.

Re-enter the virtual server name in virtualServerName\instanceName format, and click Next.

Step through the wizard to complete the task.