Sun Microsystems Sun StorEdge Availability Suite 3.2 Instrukcja Użytkownika

Sun Microsystems, Inc.www.sun.comSubmit comments about this document at: http://www.sun.com/hwdocs/feedbackSun StorEdge™Availability Suite 3.2 Softwar

x Sun StorEdge Availability Suite 3.2 Software Troubleshooting Guide • December 2003

1CHAPTER1Point-in-Time Copy SoftwareTroubleshooting TipsThis chapter describes how to avoid or troubleshoot problems that might occurwhen using the po

2 Sun StorEdge Availability Suite 3.2 Software Troubleshooting Guide • December 2003Checking Log FilesYou can check the status of the point-in-time co

Chapter 1 Point-in-Time Copy Software Troubleshooting Tips 3Safeguarding the VTOC InformationCaution – When creating shadow volume sets, do not create

4 Sun StorEdge Availability Suite 3.2 Software Troubleshooting Guide • December 2003

5CHAPTER2Remote Mirror SoftwareTroubleshooting TipsThis section describes how to avoid or troubleshoot any problems might occur whenusing the remote m

6 Sun StorEdge Availability Suite 3.2 Software Troubleshooting Guide • December 2003Troubleshooting ChecklistThis table shows the troubleshooting chec

Chapter 2 Remote Mirror Software Troubleshooting Tips 7Checking Log FilesCheck the following files to troubleshoot problems: /var/opt/SUNWesm/ds.logT

8 Sun StorEdge Availability Suite 3.2 Software Troubleshooting Guide • December 2003Checking the /etc/nsswitch.conf FileIf entries in the /etc/nsswitc

Chapter 2 Remote Mirror Software Troubleshooting Tips 9where: -T tcp specifies the transport that the service uses. hostname is the name of the mach

PleaseRecycleCopyright©2003SunMicrosystems,Inc.,4150NetworkCircle, SantaClara,California95054,U.S.A. Allrightsreserved.SunMicrosystems,Inc.hasintellec

10 Sun StorEdge Availability Suite 3.2 Software Troubleshooting Guide • December 2003 The /etc/name_to_major file is missing an entry for the /dev/rd

Chapter 2 Remote Mirror Software Troubleshooting Tips 11Testing with ifconfigUse the ifconfig command to make sure that the network interface is confi

12 Sun StorEdge Availability Suite 3.2 Software Troubleshooting Guide • December 2003In the first example, the command is issued from the primary host

Chapter 2 Remote Mirror Software Troubleshooting Tips 13Correcting Common User ErrorsThis section describes user errors encountered often when using t

14 Sun StorEdge Availability Suite 3.2 Software Troubleshooting Guide • December 2003This example shows the newfs -N command completing successfully:T

Chapter 2 Remote Mirror Software Troubleshooting Tips 15For example, this command updates the volume on the secondary host calamarifrom the primary ho

16 Sun StorEdge Availability Suite 3.2 Software Troubleshooting Guide • December 2003▼ To Find the Volume Set Name1. If you are unsure of the volume s

Chapter 2 Remote Mirror Software Troubleshooting Tips 17The order of write operations must be maintained within a group. Therefore, theseout of order

18 Sun StorEdge Availability Suite 3.2 Software Troubleshooting Guide • December 2003

19CHAPTER3Error MessagesError messages during the installation process are described in the Sun StorEdgeAvailability Suite 3.2 Software Installation G

iiiContentsPreface v1. Point-in-Time Copy SoftwareTroubleshooting Tips 1Troubleshooting Checklist 1Checking Log Files 2Improving Performance 2Safeguar

20 Sun StorEdge Availability Suite 3.2 Software Troubleshooting Guide • December 2003Abort failedPITC iiadm could not abort a copy or update operation

Chapter 3 Error Messages 21Bitmap reconfig failed %s:%sKernel A request to reconfigure the bitmap on the local hosthas failed. This can happen for two

22 Sun StorEdge Availability Suite 3.2 Software Troubleshooting Guide • December 2003cannot find SNDR set<shost>:<svol> in configRM Remote

Chapter 3 Error Messages 23Cannot enable %s:%s ==> %s:%s,secondary in use in another setKernel A set being enabled or resumed has a secondaryvolume

24 Sun StorEdge Availability Suite 3.2 Software Troubleshooting Guide • December 2003Copy failedPITC A copy or update operation could not be initiated

Chapter 3 Error Messages 25Create overflow failedPITC An overflow volume couldn’t be initialized. Possibleerrors:EFAULT: The kernel module tried to re

26 Sun StorEdge Availability Suite 3.2 Software Troubleshooting Guide • December 2003Disable pending on diskq %s, tryagain laterKernel A request to di

Chapter 3 Error Messages 27disk queue volume <vol> must notmatch any primary SNDR volume orbitmapRM The disk queue volume specified for therecon

28 Sun StorEdge Availability Suite 3.2 Software Troubleshooting Guide • December 2003Enable failedPITC Could not enable volume. Possible errors:EFAULT

Chapter 3 Error Messages 29Failed to detach overflow volumePITC iiadm had a problem detaching the overflow volumefrom a set. Possible errors:EFAULT: T

iv Sun StorEdge Availability Suite 3.2 Software Troubleshooting Guide • December 2003Correcting Common User Errors 13Enabled Software on Only One Host

30 Sun StorEdge Availability Suite 3.2 Software Troubleshooting Guide • December 2003hostname tag exceeds CFG_MAX_BUFPITC Because CFG_MAX_BUF is 1k, t

Chapter 3 Error Messages 31Join failedPITC Could not join shadow volume back to the set. Possibleerrors:EFAULT: The kernel module tried to read out-of

32 Sun StorEdge Availability Suite 3.2 Software Troubleshooting Guide • December 2003Memory allocation failurePITC iiadm ran out of memory.Must be sup

Chapter 3 Error Messages 33Overflow list access failurePITC iiadm could not get a list of overflow volumes fromthe kernel. Possible errors:EFAULT: The

34 Sun StorEdge Availability Suite 3.2 Software Troubleshooting Guide • December 2003Reverse sync needed, cannot sync%s:%s ==> %s:%sKernel The user

Chapter 3 Error Messages 35Shadow group %s is suspendedPITC The user attempted to perform a copy or updateoperation on a group with one or more suspen

36 Sun StorEdge Availability Suite 3.2 Software Troubleshooting Guide • December 2003SNDR set does not have a diskqueueRM Set does not have a disk que

Chapter 3 Error Messages 37The volume %s is already in useKernel The data volume in the remote mirror set is already inuse as a bitmap volume or a dis

38 Sun StorEdge Availability Suite 3.2 Software Troubleshooting Guide • December 2003unable to determine hostname:<host>RM Could not determine t

Chapter 3 Error Messages 39unable to obtain unique set id for<shost>:<svol>RM Lookup of the set ID in the configuration database forthis s

vPrefaceSun StorEdge Availability Suite 3.2 Software Troubleshooting Guide helps users solvecommon problems that might arise when using the Sun StorEd

40 Sun StorEdge Availability Suite 3.2 Software Troubleshooting Guide • December 2003Update failedPITC One or more volumes in a group copy or updateco

Chapter 3 Error Messages 41Volumes are not in same disk groupPITC iiadm detected that the master, shadow, and bitmapvolumes are not all in the same cl

42 Sun StorEdge Availability Suite 3.2 Software Troubleshooting Guide • December 2003Related Error MessagesThe Solaris configuration administration ut

vi Sun StorEdge Availability Suite 3.2 Software Troubleshooting Guide • December 2003How This Book Is OrganizedThis book includes the following chapte

Preface viiShell PromptsTypographic ConventionsShell PromptC shell machine-name%C shell superuser machine-name#Bourne shell and Korn shell $Bourne she

viii Sun StorEdge Availability Suite 3.2 Software Troubleshooting Guide • December 2003Related DocumentationApplication Title Part NumberMan pages snd

Preface ixAccessing Sun DocumentationYou can view, print, or purchase a broad selection of Sun documentation, includinglocalized versions, at:http://w