- Notes, Cautions, and Warnings
- Introduction
- Monitoring The FluidFS NAS Solution
- Using Volumes
Shares And Quotas
- NAS Volumes
- Shares And Exports
- Managing NFS Exports
- Managing CIFS Shares
- Creating Home Shares
- Setting Access Control Lists And Share Level Permissions On FluidFS
- Quotas
- Protecting Data
On The FluidFS NAS Cluster Solution
- Snapshots
- Replication
- Backing Up And Restoring Data
- Using Antivirus Applications
- Managing The
FluidFS NAS Solution
- Managing The System
- Managing Client Access
- Managing Administrator Users
- Managing Local Users For CIFS And NFS Access
- Managing Local Groups
- Authentication
- Active Directory
- Synchronizing The NAS Cluster Solution With The Active Directory Server
- Network Configuration Overview
- Configuring DNS
- Managing Static Routes
- Defining File System Protocols
- Configuring CIFS Parameters
- Configuring System Time Parameters
- Managing Licenses
- Configuring E-mail Parameters On PowerVault NX3500/NX3600/NX3610 NAS Solutions
- Configuring SNMP
- Troubleshooting
- Troubleshooting CIFS Issues
- Misconfigured AV Host Settings Result In Access Denied To CIFS files
- CIFS Access Denied
- CIFS ACL Corruption
- CIFS Client Clock Skew
- CIFS Client Disconnection On File Read
- CIFS Client General Disconnection
- CIFS Client Login Failure
- CIFS Connection Failure
- CIFS Delete On Close Denial
- CIFS File Access Denied
- CIFS File Sharing Conflict
- CIFS Guest Account Invalid
- CIFS Locking Inconsistency
- CIFS Maximum Connections Reached
- CIFS Share Does Not Exist
- CIFS Path Share Not Found
- CIFS Write To Read Only Volume
- Troubleshooting NFS Issues
- Cannot Mount NFS Export
- NFS Export Does Not Exist
- NFS File Access Denied
- NFS Insecure Access To Secure Export
- NFS Mount Fails Due To Export Options
- NFS Mount Fails Due To Netgroup Failure
- NFS Mount Path Does Not Exist
- NFS Owner Restricted Operation
- NFS Write To Read-Only Export
- NFS Write To Read-Only Volume
- NFS Write To Snapshot
- NFS Access Denied To A File Or Directory
- Troubleshooting Replication Issues
- Replication Configuration Error
- Replication Destination Cluster Is Busy
- Replication Destination FS Is Busy
- Replication Destination Is Down
- Replication Destination Is Not Optimal
- Replication Destination Volume Is Busy Reclaiming Space
- Replication Destination Volume Is Detached
- Replication Disconnection
- Replication Incompatible Versions
- Replication Internal Error
- Replication Jumbo Frames Blocked
- Replication Destination Does Not Have Enough Space
- Replication Source Is Busy
- Replication Source Is Down
- Replication Source Is Not Optimal
- Replication Source Volume Is Busy Reclaiming Space
- Troubleshooting Active Directory Issues
- Troubleshooting NAS File Access And Permissions Issues
- Troubleshooting Networking Issues
- Troubleshooting NAS Manager Issues
- Troubleshooting Backup Issues
- Troubleshooting System Issues
- Troubleshooting Dell NAS Initial Deployment Utility (IDU) Issues
- Troubleshooting CIFS Issues
- Maintaining
The NAS Cluster Solution
- Shutting Down The NAS Cluster Solution
- Turning On The NAS Cluster Solution
- Restoring NAS Volume Configuration
- Restoring Cluster Configuration
- Formatting File System
- Installing The Service Pack
- Expanding The NAS Cluster Storage Capacity
- Running Diagnostics
- Reinstalling The NAS Cluster Solution
- Expanding The NAS Cluster
- Replacing A NAS Cluster Solution Controller
- NAS Manager Features In Degraded Mode
- Internationalization
- Frequently Asked Questions
- Secured Management
- Getting Help
Dell FluidFS NAS Solutions Administrator's Guide
Replication Disconnection
|
Description |
Replication between the NAS source volume and the NAS destination volume fails because the connection between source and destination systems is lost. |
|
Cause |
Network infrastructure disconnection between the source and the destination. |
|
Workaround |
The administrator must check if the replication is automatically restored. If the replication is not automatically restored, check the network communication between the source cluster and the destination cluster. Network communication can be checked by using a third party system in the same subnet that can ping both the source and destination clusters. |
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: <>()\