Please enter search query.
Search <book_title>...
Veritas InfoScale 7.3.1 Release Notes - Windows
Last Published:
2017-12-15
Product(s):
InfoScale & Storage Foundation (7.3.1)
- Release notes for Veritas InfoScale
- Limitations
- Deployment limitations
- Cluster management limitations
- Storage management limitations
- Multi-pathing limitations
- Replication limitations
- Solution configuration limitations
- Internationalization and localization limitations
- Interoperability limitations
- Known issues
- Deployment issues
- Cluster management issues
- Cluster Server (VCS) issues
- Cluster Manager (Java Console) issues
- Global service group issues
- VMware virtual environment-related issues
- Cluster Server (VCS) issues
- Storage management issues
- Storage Foundation
- VEA console issues
- Snapshot and restore issues
- Snapshot scheduling issues
- Storage Foundation
- Multi-pathing issues
- Replication issues
- Solution configuration issues
- Disaster recovery (DR) configuration issues
- Fire drill (FD) configuration issues
- Quick recovery (QR) configuration issues
- Internationalization and localization issues
- Interoperability issues
- Miscellaneous issues
- Fibre Channel adapter issues
- Deployment issues
When a node is added to a cluster, existing snapshot schedules are not replicated to the new node
When you create snapshot schedules in a clustered environment, schedule-related registry entries are created on all cluster nodes. When a failover occurs, the failover node can continue to run the schedules. However, if a new node is added to a cluster after the schedules are created, the schedules are not replicated to the new node. If the service group fails over to the node that was added, the scheduled snapshot tasks do not occur.
Workaround: Start the Quick Recovery Configuration Wizard from the Solutions Configuration Center (Synchronizing Schedules panel shows that synchronization between cluster nodes is complete. Click to exit the wizard.
> > ). Continue through the wizard until the