Skip to main content

We've Moved!

Product Documentation has moved to docs.hitachivantara.com
Hitachi Vantara Knowledge

Downloading dump files

You can use dump files to troubleshoot the system and check the system configuration. You can use the Dump tool to download the dump file to the management client.

Downloading dump files

Use the Dump tool to download dump files onto a management client. The downloaded dump files can be used to:
  • Troubleshoot the system. Use the Dump tool to download dump files from the SVP and give it to the support personnel.
  • Check system configuration. First, click File Refresh All to update the configuration information, and then use the Dump tool to download the dump files.
  • Before deleting the storage management software and the SVP software. Collect the dump files of the SVP system information.

There are two types of dump files:

  • Normal Dump includes all information about the SVP and the minimum information about the storage system. Select this when you have a less serious problem such as incorrect display.
  • Detail Dump includes all information about the SVP and the storage system. Select this when Device Manager - Storage Navigator has a serious problem (for example, Device Manager - Storage Navigator does not start) or when you need to determine if the storage system has a problem.

Before you begin

  • You must be logged into the SVP.
  • Device Manager - Storage Navigator must be running.
  • The configuration information must be refreshed by selecting File Refresh All in Device Manager - Storage Navigator.
  • All other users (including the SVP user) must stop using the Dump tool.
  • Stop all maintenance operations.
  • Dump tools from other storage systems must not be used during the process.
  • The installation directory of Storage Navigator must be excluded from the real time virus scan targets by the virus detection program. For the virus detection program settings, see GUID-E05CAF41-742F-45BA-B895-FAE712A1B7F4.
Note

If the error is in regards to Device Manager - Storage Navigator starting up, collect information about the SVP using the Dump tool, without Device Manager - Storage Navigator running.

Procedure

  1. Close all Device Manager - Storage Navigator sessions on the SVP.

  2. Open a Windows command prompt with administrator permissions.

  3. Move the current directory to the folder where the tool is available. (For example: <SVP-root-directory>\DKC200\mp\pc).

  4. Specify the output destination of the dump file and execute Dump_Detail.bat or Dump_Normal.bat.

    For example, if you are storing the result of Dump_Detail.bat to C:\Result_832000400001, enter the following:

    C:\MAPP\wk\832000400001\DKC200\mp\pc>Dump_Detail.bat C:\Result_832000400001
    Note
    • A space is required between Dump_Detail.bat and C:\Result.
    • The dump file name is hdcp.tgz. To manage dump files by storage systems, we recommend adding a serial number to the output folder name. For example, if the serial number is 832000400001, the folder name should be C:\Result_832000400001.
    • When the tool is being executed, Executing is displayed in the command prompt. When the execution is completed, the following is displayed:
      zSv_AutoDump.exe is completed.
      NoteIf the execution fails, zSv_AutoDump.exe is failed is displayed.
    • You cannot specify the folders under the network drive as the output folder.
    • The dump file capacity might become approximately 3 GB depending on the usage of the storage system.
  5. A completion message box displays. Press any key to acknowledge the message and close the message box.

    hdcp.tgz: This is the dump file. Give this file to the maintenance personnel. If you save too many dump files in the SVP storage, space might not be available. Therefore, move the dump file outside of SVP storage. zSv_AutoDump.log: This is the log file of the dump tool. If the dump file is not output, give this log file to the maintenance personnel. If the dump file is output, delete the log file.
  6. Close the Windows command prompt.

Collecting dump files manually

You can collect dump files manually if the dump tool is unavailable or is causing an error in the dump files.

Note
  • installDir indicates the installation directory of the storage management software and the SVP software (for example, C:\Mapp).
  • %USERPROFILE% indicates the installation login user of the SVP (for example, C:\Users\<user name>).
  • %WINDIR% indicates the Windows folder in the system drive (for example, C:\Windows).
  • [Storage system number](Example) When the storage system number is 832000400001, the folder name is as follows:. <installDir>\wk\832000400001\DKC200\mp\pc\*.trc
  • Note that some files do not exist depending on the operating environment.

Files to collect manually:

  • <installDir>¥wk¥supervisor¥dkcman¥log¥*.*
  • installDir>¥wk¥supervisor¥dkcman¥cnf¥*.*
  • <installDir>¥wk¥supervisor¥rmiserver¥log¥*.*
  • <installDir>¥wk¥supervisor¥rmiserver¥cnf¥*.*
  • <installDir>¥wk¥supervisor¥sdlist¥log¥*.*
  • <installDir>¥wk¥supervisor¥mappiniset¥logs¥MappIniSet¥*.*
  • <installDir>¥wk¥supervisor¥mappiniset¥mpprt¥cnf
  • <installDir>¥wk¥supervisor¥assist¥log¥*.*
  • <installDir>¥wk¥supervisor¥assist¥cfg¥*.*
  • <installDir>¥wk¥supervisor¥assist¥dat¥*.*
  • <installDir>¥wk¥supervisor¥assist¥history¥*.*
  • <installDir>¥wk¥supervisor¥comweb¥logs¥*.*
  • <installDir>¥wk¥supervisor¥microsetup¥log¥*.*
  • <installDir>¥wk¥supervisor¥portmanager¥cnf¥*.*
  • <installDir>¥wk¥supervisor¥portmanager¥logs¥PortManager¥*.*
  • <installDir>¥wk¥supervisor¥restapi¥data
  • <installDir>¥wk¥supervisor¥restapi¥logs
  • <installDir>¥wk¥supervisor¥restapi¥build.json
  • <installDir>¥wk¥supervisor¥restapi¥version.json
  • <installDir>¥wk¥supervisor¥system¥log¥*.log
  • <installDir>¥wk¥[Storage system number]¥DKC200¥mp¥pc¥*.trc
  • <installDir>¥wk¥[Storage system number]¥DKC200¥mp¥pc¥*.dmp
  • <installDir>¥wk¥[Storage system number]¥DKC200¥mp¥pc¥*.dbg
  • <installDir>¥wk¥[Storage system number]¥DKC200¥mp¥pc¥*.dmb
  • <installDir>¥wk¥[Storage system number]¥DKC200¥mp¥pc¥*.ini
  • <installDir>¥wk¥[Storage system number]¥DKC200¥mp¥pc¥*.inf
  • <installDir>¥wk¥[Storage system number]¥DKC200¥san¥SN2¥SN2Files¥logs¥*.*
  • <installDir>¥wk¥[Storage system number]¥DKC200¥san¥SN2¥SN2¥logs¥*.*
  • <installDir>¥wk¥[Storage system number]¥DKC200¥san¥cgi-bin¥utility¥log¥*.*
  • <installDir>¥wk¥[Storage system number]¥DKC200¥others¥commdata¥*.*
  • <installDir>¥wk¥[Storage system number]¥DKC200¥config¥*.cfg
  • <installDir>¥OSS¥apache¥logs¥*.log
  • <installDir>¥OSS¥apache¥logs¥ssl¥*.log
  • <installDir>¥OSS¥jetty¥logs¥*.log
  • %USERPROFILE%¥AppData¥LocalLow¥Sun¥Java¥Deployment¥log
  • %WINDIR%¥system32¥config¥SysEvent.Evt
  • %WINDIR%¥system32¥config¥SecEvent.Evt
  • %WINDIR%¥system32¥config¥AppEvent.Evt
  • %WINDIR%¥minidump¥*.dmp
  • %WINDIR%¥System32¥Winevt¥Logs¥Application.evtx
  • %WINDIR%¥System32¥Winevt¥Logs¥Security.evtx
  • %WINDIR%¥System32¥Winevt¥Logs¥System.evtx
  • %WINDIR%¥system32¥drivers¥etc¥HOSTS*
  • %WINDIR%¥system32¥drivers¥etc¥services*
  • %WINDIR%¥minidump¥*.