- Notes, cautions, and warnings
- Introduction to this guide
- OneFS backup and recovery
- Data replication with SyncIQ
- Protecting data with SyncIQ
- Creating replication policies
- Managing replication to remote clusters
- Managing replication policies
- Managing replication to the local cluster
- Managing replication performance rules
- Managing replication reports
- Managing failed replication jobs
- Managing changelists
- Configuring SyncIQ Failover/Failback Policies
- NDMP backup and recovery
- NDMP backup and restore models overview
- NDMP two-way backup
- NDMP three-way backup
- Support for NDMP sessions on Generation 6 hardware
- Setting preferred IPs for NDMP three-way operations
- NDMP multi-stream backup and recovery
- NDMP file list backup overview
- Snapshot-based incremental backups
- NDMP backup and restore of SmartLink files
- NDMP protocol support
- Supported DMAs
- NDMP hardware support
- Sharing tape drives between clusters
- NDMP backup limitations
- NDMP performance recommendations
- Excluding files and directories from NDMP backups
- Administering NDMP
- NDMP backup and recovery tasks
- Configuring basic NDMP backup settings
- Managing NDMP user accounts
- Managing NDMP environment variables
- Managing NDMP contexts
- Managing NDMP sessions
- Managing NDMP Fibre Channel ports
- Managing NDMP preferred IP settings
- Managing NDMP backup devices
- NDMP dumpdates file overview
- Managing snapshot based incremental backups
- NDMP restore operations
- Managing file list backups
- Managing cluster performance for NDMP sessions
- Managing CPU usage for NDMP sessions
- Configuring NDMP backups with NetWorker
- Configuring NDMP backup with Veritas NetBackup
- Configuring NDMP backup with CommVault Simpana
- Configuring NDMP backup with IBM Tivoli Storage Manager
- Sparse file support
PowerScale OneFS 9.8.0.0 Backup and Recovery Guide
Initiating data failover and failback with SyncIQ
You can fail over from one PowerScale cluster to another if, for example, your primary cluster becomes unavailable. You can fail back when the primary cluster becomes available again. You can revert failover if you decide that the failover was unnecessary or if you failed over for testing purposes.
NOTE:Data failover and failback are supported for both compliance SmartLock directories and enterprise SmartLock directories. Compliance SmartLock directories can be created only on clusters that have been set up as compliance mode clusters during initial configuration. You cannot rename folders after creation in compliance mode.
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please select whether the article was helpful or not.
Comments cannot contain these special characters: <>()\