![]() | Sun System Handbook - ISO 4.1 October 2012 Internal/Partner Edition | ||
|
|
![]() |
||||||||||||
Solution Type Troubleshooting Sure Solution 1399581.1 : Sun Storage 7000 Unified Storage System: Replication starts to a remote appliance but does not complete
Review Sun Storage 7000 Unified Storage System: Resolution Path for Replication Issues [Document 1397959.1] before reading this document In this Document
Applies to:Sun ZFS Storage 7420 - Version: Not ApplicableSun ZFS Storage 7320 - Version: Not Applicable and later [Release: N/A and later] Sun Storage 7410 Unified Storage System - Version: Not Applicable and later [Release: N/A and later] Sun ZFS Storage 7120 - Version: Not Applicable and later [Release: N/A and later] Sun Storage 7210 Unified Storage System - Version: Not Applicable and later [Release: N/A and later] Information in this document applies to any platform. NAS head revision : [not dependent] BIOS revision : [not dependent] ILOM revision : [not dependent] JBODs Model : [not dependent] CLUSTER related : [not dependent] PurposeTo assist in troubleshooting issues with replication between Sun ZFS 7000 Storage appliances where replication starts to a remote appliance but does not complete.To discuss this information further with Oracle experts and industry peers, we encourage you to review, join or start a discussion in the My Oracle Support Community - 7000 Series ZFS Appliances Last Review DateJanuary 24, 2012Instructions for the ReaderA Troubleshooting Guide is provided to assist
in debugging a specific issue. When possible, diagnostic tools are included in the document
to assist in troubleshooting.
Troubleshooting DetailsExamine Maintenance -> Logs -> Alerts in the BUI of the source system. There should be alerts similar to the following : 2011-9-10 11:30:01 Began replicating 'HOMEtest' to appliance 's7120-ftlauder-a'. Click on the "information" symbol to the right of the "failed message" date. Does it specify a reason why the replication failed ? Examine the Alert log on the target system, searching for the date and time that it failed. If there was no alert generated, the possibility exists that the source never made contact with the target. Here, we see that a successful replication did take place the day before. 2011-9-9 09:33:25 Finished replicating project 'HOMEtest' from appliance 's7420-ftlauder-a'. Minor Alert Was there work being performed on the network when the replication failed ? If that work has been completed, then attempt a manual replication to the target system. Might the IP address of either the source or the target system have been changed since the last successful replication. The appliance IP addresses can not change. If done, the old replication package will need to be destroyed and a new one created. Check for messages indicating no route to host in the system log. If those messages exist, from the CLI enter "traceroute <target ip address or hostname>" Review Document ID 1335245.1, "Sun Storage 7000 Unified Storage System: Replication failure due quotas in use on the source machine" Attachments This solution has no attachment |
||||||||||||
|