Docstoc

NEC Storage Manager FAQ

Document Sample
NEC Storage Manager FAQ Powered By Docstoc
					                             NEC Storage Manager

                                            FAQ




                                       2010/07/13
                                       Revision 1
                                     NEC Corporation




Note: This FAQ document is based on iSM Ver6.1. Regarding Ver6.2 (or later), translation is in
      progress and to be updated as soon as it completed.
Storage Management

NEC Storage Manager Overview
1. Introduction
 Q1-1 Of what does NEC Storage Manager consist?
 Q1-2 What cluster software programs do NEC Storage disk array devices support?
 Q1-3 What functions does iSMvollist provide? Is there any prerequisite license or product that shoud be installed to
      run it?
 Q1-4 What is the difference between iSM client (Win GUI) and iSM client (Web GUI)?
 Q1-5 Which should I use, iSM client (Web GUI) or iSM client (Win GUI)?
 Q1-6 Is it possible to use iSM client (Web GUI) and iSM client (Win GUI) together on one machine?


2. Troubleshooting
 Q2-1 Are there any notes on using NEC Storage Manager in a Windows server in which the antivirus software
      "NOD32 Antivirus" (NOD32 Kernel Service) is running?


 Q1-1 Of what does NEC Storage Manager consist?
     A NEC Storage Manager consists of the following programs.
          ■ iSM server
            This is a resident program that monitors and controls NEC Storage series disk arrays. It runs on a server
            connected to a disk array by TCP/IP (or fibre channel).
          ■ iSM client
            iSM client provides the NEC Storage Manager GUI. It is started from a PC and connects to iSM Sever by
            TCP/IP, which allows users remote monitoring and control.
            In NEC Storage Manager Ver5.1 or later, iSM client provides the following two GUIs.
               - Web-based GUI
               - Windows-based GUI
            When it is necessary to distinguish these two GUIs, the former is referred to as “iSM client (Web GUI)”
            and the latter is referred to as “iSM client (Win GUI).”
            “iSM client (Win GUI)” is also used for iSM client provided in V4.3 or earlier.
          ■ The iSM server and iSM client provide the following monitoring and control functions.
                                Status monitoring: Detects and reports disk array problems.
                            Configuration settings: Configures disk array nick names. In the D series, S1000 /
                                                    S2000 / S2800 series, and S4900, this function allows for
                                                    configuration of logical disks.
                          Performance monitoring: Monitors disk array performance, collects and accumulates
                                                  performance information, and displays performance in real time.
                                   Access control: Allows access only to application servers that are necessary
                                                   among servers connected to storage by fibre channel.
                         Replication management: Creates a replica of a logical disk (volume).
 Q1-2 What cluster software programs do NEC Storage disk array devices support?
     A NEC Storage disk array devices support cluster software programs such as MC/ServiceGuard and
       ExpressCluster.
 Q1-3 What functions does iSMvollist provide? Is there any prerequisite license or product that should be installed to
      run it?
     A For an application server that uses logical disks by connecting to NEC Storage, iSMvollist reports how disk
       names (such as special names and drive names) that are recognized by the application server’s OS and logical
       disk names given by NEC Storage Manager are associated. iSMvollist is provided as an application that works
     independently for OSes (Windows and Linux). It can be used even if NEC Storage Manager is not running.
     It is recommended to use iSMvollist to check that your target logical disk is recognized by the application server
     correctly after logical disks are allocated to the application server by using AccessControl or other software
     programs. Note that iSMvollist is automatically installed on a server where ControlCommand is installed. This is
     because ControlCommand uses the disk association information created by iSMvollist.
Q1-4 What is the difference between iSM client (Win GUI) and iSM client (Web GUI)?
   A iSM client (Win GUI) uses the dedicated GUI provided in Ver4.3 or earlier for disk array monitoring and control.
     The dedicated program must be installed on a machine in advance.
     iSM client (Web GUI) uses the new Web browser provided in Ver5.1 or later to connect to iSM server, and
     monitors and contorls disk arrays. It is also necessary to install iSM client (Win GUI) on a machine you use.
     However, it is not necessary to install it in advance because the installer can be downloaded after iSM server is
     connected.

     In principle, both provide the same functions. However, basically use iSM client (Web GUI) since disk arrays
     from the D series can only be monitored or controlled by iSM client (Web GUI).
Q1-5 Which should I use, iSM client (Web GUI) or iSM client (Win GUI)?
   A In principle, use iSM client (Web GUI) because disk arrays from the D series can only be monitored or
     controlled by iSM client (Web GUI).
     Use iSM client (Win GUI) only when you are not using the D series and need to continue operation through the
     same iSM client (Win GUI) GUI from Ver4.3 or earlier.
Q1-6 Is it possible to use iSM client (Web GUI) and iSM client (Win GUI) together on one machine?
   A Yes. Install iSM client (Win GUI) on a machine in advance.
     To start iSM client (Web GUI), use the Web browser. To start iSM client (Win GUI), use the Start menu or the
     shortcut icon on the desk top.
     Note that only one of iSM client (Web GUI) and iSM client (Win GUI) can connect to iSM server from Ver5.1 on
     (it is specified in the environment settings of iSM server).
Q2-1 Are there any notes on using NEC Storage Manager in a Windows server in which the antivirus software
     "NOD32 Antivirus" (NOD32 Kernel Service) is running?
   A In a Windows machine in which NEC Storage Manager is installed and the antivirus software "NOD32
     Antivirus" (NOD32 Kernel Service) is running, the iSM server may not be launched or other problems may
     occur due to the timing.
     It is already confirmed that if this antivirus software scans files that NEC Storage Manager internally uses, an
     error will occur due to file conflicts. Because of this, when you are using NEC Storage Manager, stop scanning
     by the antivirus software by the procedure described in (1) for iSM server and by the procedure described in
     either (1) or (2) for iSM client (Web GUI) and iSM client (Win GUI).
           1     Exclude the following folders and files that are used by NEC Storage Manager from scanning:
                 For information on how to exclude particular folders and files from scanning, see the NOD32
                 Antivirus's manual.
                 (1)   When iSM server is used:
                       -    Folders excluded from scanning
                            -    The installation folder and its sub folders of iSM server (default:C:\Program
                                 Files\NEC\iSMsvr (for 64 bit OS, C:\Program Files (x86)\NEC\iSMsvr))
                            -    Folders specified by the environment settings
                       -    Files excluded from scanning
                            -    <The installation folder of ESMPRO/ServerManager>
                                 \NVWORK\PUBLIC\MENUITEM\iSMCL.def (only when ESMPRO/ServerManager
                                 is installed and association with iSM is estabilished) (defualt value of the
                                 installation folder:C:\Program Files\ESMPRO (for 64 bit OS, C:\Program Files
                                 (x86)\ESMPRO))
                            -    Files specified by command arguments
          In addition to the above mentioned, the following should be excluded from scanning when
          the E1 series should be monitored by iSM server.
          -   Folders to be excluded from scanning
              -    The installation folder and its sub folders of iSM Express Connector (default:
                   C:\Program Files\NEC\iSMconn (for 64 bit OS, C:\Program Files
                   (x86)\NEC\iSMconn))
    (2)   When iSM client (Win GUI) is used:
          -   Folders excluded from scanning
              -    The installation folder and its sub folders of iSM client (Win GUI) (default:
                   C:\Program Files\NEC\iSMClient(for 64 bit OS, C:\Program Files
                   (x86)\NEC\iSMClient))
              -    Folders specified by iSM client
                   Example: Folder to store information that is specified when the function to collect
                   failure information is used
          -   Files excluded from scanning
              -    <Installation folder of ESMPRO/ServerManager>
                   \NVWORK\PUBLIC\MENUITEM\iSMCL.def (only when ESMPRO/ServerManager
                   is installed and association with iSM is estabilished) (default value of the
                   installation folder:C:\Program Files\ESMPRO (for 64 bit OS, C:\Program Files
                   (x86)\ESMPRO))
    (3)   When iSM client(Web GUI) is used:
          -   Folders excluded from scanning
              -    The installation folder and its sub folders of iSM client (Win GUI) (default:
                   C:\Program Files\NEC\iSMClient(for 64 bit OS, C:\Program Files
                   (x86)\NEC\iSMClient))
              -    <System drive>\Documents and Settings\<login user name>\Application Data\NEC
                   (with hidden attribute)
                   Example:C:\Documents and Settings\Administrator\Application Data\NEC
                   For Windows Vista and Windows Server 2008
                   <System drive>\user\<login user name>\AppData\Roaming\NEC (with hidden
                   attribute)
              -    Folders specified by iSM client
                   Example: Folder to store information that is specified when the function to collect
                   failure information is used
          -   FIles excluded from scanning
              -    \NVWORK\PUBLIC\MENUITEM\iSMCL.def (only when ESMPRO/ServerManager
                   is installed and association with iSM is established) (default value of the installation
                   folder:C:\Program Files\ESMPRO (for 64 bit OS, C:\Program Files
                   (x86)\ESMPRO))
2   Stop the following service temporarily while using iSM client:
          NOD32 Kernel Service
Storage Management

NEC Storage Manager Setup
1. Introduction
          Q1-1 The NEC Storage Manager Setup program is started automatically when I set the NEC Storage
               Manager CD on Windows OS. What does does this program do?
          Q1-2 Can I use NEC Storage Manager Setup on Linux?


2. Installation
          Q2-1 How do I use the quick installation and the custom installation?
          Q2-2 What should I do to install the D1 series/D3 series/D4 series and the S series at the same time?
          Q2-3 The software program of an older version is installed. Is it necessary to uninstall it before executing NEC
               Storage Manager Setup?
          Q2-4 The “Install JRE” option and the “Install Storage Manager Client (Win GUI)” option are shown after
               Install Storage Manager Client is selected. Is it necessary to install both?
          Q2-5 Is it OK to perform auto update after JRE is installed?
          Q2-6 I misatakenly installed iSM Express Connector on a Hyper-V virtunal machine. Wheat should I do to
               remove iSM Express Connector?
          Q2-7 Are there any notes on using the NEC Storage Manager Setup in a machine where security software (*)
               is installed?
               (*) Software to prevent information leakage, to block unauthorized accesses or computer viruses, etc.


3. Troubleshooting
          Q3-1 What should I do when a failure occurs while executing NEC Storage Manager Setup?
          Q3-2 When I selected Control Panel, Design, Display, and Smaller - 100%(default) for the size of texts on
              windows and other items in Windows Server 2008 R2 or Windows 7, the window format became
              distorted or the mouse did not work. How can I solve this problem?


          Q1-1 The NEC Storage Manager Setup program is started automatically when I set the NEC Storage
               Manager CD on Windows OS. What does this program do?
              A NEC Storage Manager is a program to install software contained in the CD.
                By following the procedure as prompted by the wizard page, you can easily install the software.
          Q1-2 Can I use Linux NEC Storage Manager Setup on Linux?
              A No. When you are using Linux, use the rpm command to install the software.
          Q2-1 How do I use the quick installation and the custom installation?
              A Select the quick installation when you install the D1 series /D3 series/D4 series for the first time or
                additionally. Using the quick installation allows for easy installation with simple configuration. In other
                cases or if you need detailed settings in installation of the D1 series/D3 series/D4 series, select the
                custom installation.
          Q2-2 What should I do to install the D1 series/D3 series/D4 series and the S series at the same time?
              A Install the D1 series/D3 series/D4 series first. Configure the S series from environment settings of iSM
                server after installing the D1 series/D3 series/D4 series.
          Q2-3 The software program of an older version is installed. Is it necessary to uninstall it before executing NEC
               Storage Manager Setup?
              A It is not necessary to uninstall the older version because it is uninstalled during the course of “NEC
                Storage Manager Setup” execution.
                Note that iSM client (Win GUI) is overwritten in installation.
          Q2-4 The “Install JRE” option and the “Install Storage Manager Client (Win GUI)” option are shown after
               Install Storage Manager Client is selected. Is it necessary to install both?
   A To use iSM client (Web GUI), select “Install JRE” only. In this case, the installation window for iSM client
     (Win GUI) is shown when iSM server is successfully connected. Install iSM client (Win GUI) as prompted
     by the instruction.
     To use iSM client (Win GUI), select “Install Storage Manager Client (Win GUI)” only.
Q2-5 Is it OK to perform auto update after JRE is installed?
   A If auto update is performed, there is a risk that JRE is updated to an unsupported version.
     Because of this, it is recommended to disable the auto update of JRE.
Q2-6 I mistakenly installed iSM Express Connector on a Hyper-V virtual machine in the E series. What should
     I do to remove iSM Express Connector?
   A If iSM Express Connector is installed on a Hyper-V virtual machine by mistake, it can be removed by
     following the procedures below.
     There are two ways to remove it. Select the method that suits your environment.


      *      “Add or Remove Programs” is “Programs and Features” in Microsoft(R) Windows Vista(R) and
             Microsoft(R) Windows Server(R) 2008.



      1      If “iSM Express Connector” is found in “Add or Remove Programs”:
      -----------------------------------------------------
      (1)    Stop iSM server.
             If iSM server is running, stop iSM server through the service user interface screen.
      (2)    Remove iSM Express Connector.
             Remove “iSM Express Connector” in the Add or Remove Programs tool.
      (3)    Delete the iSM Express Connector folder.
             Start Explorer. If the following folder exists, right-click the folder to select Delete.
             Ex)     If iSM Express Connector is installed in “C:\Program Files\NEC\iSMConn\”,
                     the iSMConn folder in C:\Program Files\NEC\iSMConn
             For 64-bit OS
                     By default, iSM Express Connector is installed in “C:\Program
                     Files△(x86)\NEC\iSMConn.”
      (4)    Delete registries.
             Start the registry editor and delete the following registries if any.
                   - HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows
                     \WindowsError Reporting\LocalDumps
                     \iSMConnIsmComm.exe
                   - HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows
                     \WindowsError Reporting\LocalDumps
                     \iSMConnLogManage.exe
                   - HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows
                     \WindowsError Reporting\LocalDumps
                     \iSMConnMConnect.exe
                   - HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows
                     \WindowsError Reporting\LocalDumps
                     \iSMConnMInformation.exe
                   - HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows
                     \WindowsError Reporting\LocalDumps
                     \iSMConnTimerControl.exe
                   - HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows
               \WindowsError Reporting\LocalDumps
               \iSMConnWInterface.exe
             - HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows
               \WindowsError Reporting\LocalDumps
               \iSMExpressConnectorMain.exe
             - HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet
               \Services\Eventlog\Application\iSMConnLogManage
             - HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet
               \Services\Eventlog\Application\iSMExpressConnectorMain


       For 32-bit OS
             - HKEY_LOCAL_MACHINE\SOFTWARE\NEC\iSMConn


       For 64-bit OS
             - HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node
               \NEC\iSMConn



2.     If “iSM Express Connector” does not exist in “Add or Remove Programs”:
-----------------------------------------------------
(1)    Stop iSM server.
       If iSM server is running, stop iSM server through the service user interface screen.
(2)    Execute the command prompt.
       Use the command prompt to navigate to where iSM Express Connector is installed.
       Ex)     If iSM Express Connector is installed in “C:\Program Files\NEC\iSMConn\”,
               run the following from the command prompt.
               >c:
               >cd \Program Files\NEC\iSMConn\sbin
       For 64-bit OS
               By default, iSM Express Connector is installed in “C:\Program Files (x86)\NEC\iSMConn.”
       For Microsoft(R) Windows 2008 Server
               Select Run as Administrator to run a command from the command prompt.
(3)    Run the command for deletion.
       >iSMExpressConnectorMain.exe -uninstall
       Close the command prompt when running the command is finished.
(4)    Delete the iSM Express Connector folder.
       Start Explorer. If the following folder exists, right-click the folder to select Delete.
       Ex)     If iSM Express Connector is installed in “C:\Program Files\NEC\iSMConn\”,
               the “ iSMConn” folder in C:\Program Files\NEC\iSMConn
       For 64-bit OS
               By default, iSM Express Connector is installed in “C:\Program Files (x86)\NEC\iSMConn.”
(5)    Delete the registry.
       Start the registry editor and delete the following registries if any.
             - HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows
               \WindowsError Reporting\LocalDumps
                  \iSMConnIsmComm.exe
                 - HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows
                   \WindowsError Reporting\LocalDumps
                   \iSMConnLogManage.exe
                 - HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows
                   \WindowsError Reporting\LocalDumps
                   \iSMConnMConnect.exe
                 - HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows
                   \WindowsError Reporting\LocalDumps
                   \iSMConnMInformation.exe
                 - HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows
                   \WindowsError Reporting\LocalDumps
                   \iSMConnTimerControl.exe
                 - HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows
                   \WindowsError Reporting\LocalDumps
                   \iSMConnWInterface.exe
                 - HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows
                   \WindowsError Reporting\LocalDumps
                   \iSMExpressConnectorMain.exe
                 - HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet
                   \Services\Eventlog\Application\iSMConnLogManage
                 - HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet
                   \Services\Eventlog\Application\iSMExpressConnectorMain


           For 32-bit OS
                 - HKEY_LOCAL_MACHINE\SOFTWARE\NEC\iSMConn


           For 64-bit OS
                 - HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node
                   \NEC\iSMConn


Q2-7 Are there any notes on using the NEC Storage Manager Setup in a machine where security software (*)
     is installed?
     (*) Software to prevent information leakage, to block unauthorized accesses or computer viruses, etc.
   A NEC Storage Manager Setup creates folders/files in the following folder to store log files.


       -   <system drive>:\Documents and Settings\<login user name>\Application Data
             *   For Windows Vista and Windows Server 2008, the following is used.
                 <system drive>:\user\<login user name> \AppData\Roaming


           If security software restricts the creation of these folders and files, the NEC Storage Manager will
           not be set up normally. Change the software settings to prevent the restriction.
Q3-1 What should I do when a failure occurs while executing NEC Storage Manager Setup?
   A See “Related Software for NEC Storage, Information to be collected when a failure occurs” to collect
     necessary information.
Q3-2 When any option other than Smaller - 100%(default)(S) is selected on the Display dialog box, which is
     opened by selecting Control Panel and Design, on Windows Server 2008 R2 or Windows7, display is
 distorted or mouse operation is disturbed. What should I do?
A This problem may be experienced when Ver6.1 is used and a size other than Smaller -
  100%(default)(S) is configured. Choose the default settings Smaller - 100%(default)(S).
Storage Management

iSM server
1. Introduction
      Q1-1 What is NEC Storage Manager (iSM)?


2. Installation
      Q2-1 If multiple NEC Storage disk arrays are installed, is it necessary to have sets of iSM server as many as the
           number of disk arrays to monitor them? If NEC Storage disk arrays are added, is it necessary to add sets of
           iSM server as many as the number of new disk arrays?
      Q2-2 Do I need multiple iSM servers for monitoring from multiple iSM clients at a time?
      Q2-3 How many NEC Storage disk arrays can NEC Storage Manager monitor?
      Q2-4 The port numbers of iSM server that iSM client (Web GUI) connects to are 8020 and 8070 but they are
           already used on a machine where iSM server runs. Can I change the port numbers?
      Q2-5 The TCP/IP port number of iSM server to which iSM client (Win GUI) connects is 8020 but it is already used
           on a machine where iSM server runs. Can I change the port number?
      Q2-6 iSM server messages are not reported in syslog. What should I do?
      Q2-7 Where Can I find log files reported by iSM server and how large are they?
      Q2-8 Which should I choose for monitoring of disk arrays from iSM server, via FC (Fibre Channel) or via TCP/IP?
      Q2-9 What should I note when disk arrays are monitored via LAN (TCP/IP)?
     Q2-10 What should I note when the IP address of the management server is restricted by the disk array network
           settings?
     Q2-11 Is it possible to run iSM server on an application server?
     Q2-12 Are the configuration settings inherited when iSM server is upgraded?
     Q2-13 Are there any notes on upgrading an iSM server?
     Q2-14 The message iSM10316 is not reported to syslog after upgrading NEC Storage Manager from V2.1/V2.2 to
           V3.1. Are there any messages like this?
     Q2-15 Does the mail link function of NEC Storage Manager support POP before SMTP and SMTP authentication
           mail servers?
     Q2-16 What should I note to install iSM server on nodes that constitute a cluster?
     Q2-17 Why does the NEC Storage Manager management server have the FTP server settings? Do I need to use
           the FTP server?
     Q2-18 Which port numbers should be open in an environment where a firewall is installed?
     Q2-19 To upgrade iSM server (Windows) Ver4.1 or later, which of the following should I choose in the screen to
           select configuration setting shown at the installation?
           - Set the required minimum with the wizard
           - Set all functions by dialog
           - Do it later
     Q2-20 How much disk capacity and memory amount do I need to use iSM server?
     Q2-21 What are the specifications for node names and host names in NEC Storage Manager?
     Q2-22 Are there any notes on iSM server when an existing disk array is replaced with a disk array from the NEC
           Storage D1 series or D3 series or D4 series?
     Q2-23 Are there any notes on installing iSM server on a Windows Server 2008 Hyper-V virtual machine?
     Q2-24 Are there any notes on using an iSM server in a Windows machine where security software(*) is installed?
           (*) Software to prevent information leakage, to block unauthorized accesses or computer viruses, etc.


3.Operation
      Q3-1 iSM server is started automatically when the system starts up. What should I do to prevent iSM server from
           startint up automatically?
      Q3-2 Is it OK to monitor single disk array by two or more iSM servers?
      Q3-3 Which iSM processes should be monitored for restart after an iSM server failure?
      Q3-4 When the event link function is not used, what should I do to prevent the iSM06029 or iSM06040 message
           from being reported?
      Q3-5 Is remote operation through terminal service client or remote desktop possible?
      Q3-6 What should I do to send a test message to the mail address defined in the event link function?


4. Troubleshooting
      Q4-1 What should I do for the message “Error occurred at the time of deleting environment variable.” shown when
           installation of iSM in Windows fails?
           What should I do for the message “Storage Manager Server installer was interrupted.” shown when the
           quick installation for NEC Storage Manager Setup, which is supported from V5.1, is selected?
      Q4-2 What should I do for the message “Failed in getting systempath of environment variable.” shown while iSM
           server in Windows is uninstalled?
      Q4-3 What should I do when disk arrays cannot be monitored via TCP/IP?
      Q4-4 What should I do when disk arrays cannot be monitored via FC?
      Q4-5 Though rarely, monitoring disk arrays via TCP/IP stops, What should I do?
      Q4-6 What information should I collect when a trouble occurs on iSM server and the cuase is unknown?
      Q4-7 Nothing was reported in the operation logs because iSM server could not be started. What should I do?
      Q4-8 Mail link does not work. What are coneivable causes?
      Q4-9 Shell script (batch file) link does not work. What are conceivable causes?
     Q4-10 Nothing is described in the message sent by the mail link. What should I do?
     Q4-11 Iometer, which is provided by Intel for the Windows environment, does not work when iSM server installed.
           What should I do?
     Q4-12 What should I do when iSM01408 error is shown after iSMsvr start is executed?
     Q4-13 A file named iSMgather.tar.Z is not created after collecting failure information (running iSMgahter) in the
           environment where Red Hat Enterprise Linux Version 2.1 is used for OS. What should I do?
     Q4-14 What causes automatic restart of iSM server?
     Q4-15 The following message is reported when the command to encrypt a password (iSMcipherpw) is executed.
           Incorrectly built binary which accesses errno or h_errno directly.
           Needs to be fixed.
           The encrypted value is reported as well. Has the encryption been completed successfully?
     Q4-16 CPUs of a process for iSM server in Windows are highly loaded. What causes the high CPU load?
     Q4-17 When I selected Control Panel, Design, Display, and Smaller - 100%(default) for the size of texts on
           windows and other items in Windows Server 2008 R2 or Windows 7, the window format became distorted or
           the mouse did not work. How can I solve this problem?



5. Migration
      Q5-1 How do I migrate iSM server?



      Q1-1 What is NEC Storage Manager (iSM)?
         A NEC Storage Manager (iSM) is a program product for storage management that controls disk array devices
           provided by the NEC Storage series. iSM consists of the server part that manages storage and the client
           part that is responsible for monitoring and operation. It allows for remote and centralized management of
           storage.
      Q2-1 If multiple NEC Storage disk arrays are installed, is it necessary to have sets of iSM server as many as the
           number of the disk arrays to monitor them? If NEC Storage disk arrays are added, is it necessary to add
     sets of iSM server as many as the number of new disk arrays?
   A It is not necessary to have iSM server sets as many as the number of devices.
     You can use one set of iSM server to monitor multiple NEC Storage disk arrays.
     (Write multiple IP monitoring targets in the environment definition of iSM server or specify auto monitoring
     for FC connection.)
     Note the following about NEC Storage Manager version.
         - If you have two or more NEC Storage Manager media, use the latest version of NEC Storage
           Manager. Older versions of NEC Storage Manager do not support new NEC Storage disk arrays.
         - When a latest model of NEC Storage disk array is added, NEC Storage Manager that has been used
           must be updated to the latest version.
         - The version of NEC Storage Manager Client must be the same as the version of server.
         - If RemoteDataReplication is installed, iSM server and iSM client that monitor devices must be in the
           latest version.
Q2-2 Do I need multiple iSM servers for monitoring from multiple iSM clients at a time?
   A You do not need multiple iSM servers.
     You need one iSM server that monitors NEC Storage disk arrays, and connect the multiple iSM clients to the
     iSM server.
     NEC Storage disk arrays cannot be monitored by multiple iSM servers at a time.
     If iSM servers are clustered and ExpressCluster is used, set one-way standby clustering to allow monitoring
     from one server at a time.
Q2-3 How many NEC Storage disk arrays can NEC Storage Manager monitor?
   A It depends on iSM server, a server program of NEC Storage Manager.
     Up to 64 disk arrays can be monitored by Linux iSM server and 32 disk arrays can be monitored by
     Windows iSM server.
Q2-4 The port numbers of iSM server that iSM client (Web GUI) connects to are 8020 and 8070 but they are
     already used on a machine where iSM server runs. Can I change the port numbers?
   A You can change the port numbers. When you have changed the port numbers, restart iSM server.
       1) To change the port number 8020:
          In UNIX, use “iSMsvr_port” in the client section of the environment definition file.
          In Windows, configure the iSM client connecting port number on the state monitoring window of
          environment settings.
       (2) To change the port number 8070:
          In UNIX, use “web_port_no” in the web section of the environment definition file.
          In Windows, configure the iSM client Web GUI port number for which connection is permitted on the
          state monitoring window of environment settings.
Q2-5 The TCP/IP port number of iSM server to which iSM client (Win GUI) connects is 8020 but it is already used
     on a machine where iSM server runs. Can I change the port number?
   A You can change the port number. When you have changed the port number, restart iSM server.
     In UNIX, use “iSMsvr_port” in the client section of the environment definition file.
     In Windows, configure the iSM client connecting port number on the state monitoring window of the
     environment settings.
Q2-6 iSM server messages are not reported in syslog. What should I do?
   A Check description in the configuration file of syslog (syslog.conf). The facility of iSM server is daemon.
     Check how the facility where daemon is selected is configured including level and destination.
Q2-7 Where can I find log files reported by iSM server and how large are they?
   A There are two types of log files reported by iSM server:
       (1) Log files that report iSM server messages
       (2) Trace files used for failure analysis
      (1) Log files that report iSM server messages
             ■ Location
               By default, the log files are reported to /opt/iSMsvr/etc/log/iSM_Log.log in Linux and (installation
               folder)\etc\log\iSM_Log.log in Windows.
               Generation files (backup files) are saved in the same directory (folder) as iSM_Lognn.log (nn is
               from 01 through 99).
               You can change the location where the log files are reported by configuring the environment
               settings.
             ■ Capacity
               By default, up to 100 MB (Maximum of 100 x 1-MB files) operation logs are saved.
               You can save up to 1000 MB operation logs by configuring the environment settings of the file
               size.


      (2) Trace files used for failure analysis
             ■ Location
               The files are reported in the /opt/iSMsvr/etc/trace directory for Linux and in the (installation
               folder)\etc\trace folder for Windows.
             ■ Capacity
               Capacity depends on the environment where iSM server is used. Use the following figures as a
               guide.
                    iSM server fixed value:Maximum 32 MB
                    Add maximum of 4 MB for each disk array
                    Add maximum of 2 MB for each iSM client.
                    Add maximum of 1 MB if the ALIVE report is set.
Q2-8 Which should I choose for monitoring of disk arrays from iSM server, via FC (Fibre Channel) or via TCP/IP?
   A Disk arrays can be monitored from iSM server via FC or via TCP/IP. It is strongly recommended to monitor
     via TCP/IP because monitoring via FC may cause the following problems.
         - Monitoring via FC may be disabled due to a LD failure.
         - When accessing the FC path selected for the control path of iSM server is prohibited by access control
           settings, monitoring from iSM server via FC is disabled and cannot be cancelled.
         - Access conflict may occur because both business applications and iSM server use FC for access.
Q2-9 What should I note when disk arrays are monitored via LAN (TCP/IP)?
   A You should do/note:
         - Read the guidebooks of disk arrays and check the LAN connectors used for connecting iSM server.
           Make sure not to confuse LAN connectors with MNT connectors used for connecting maintenance PC.
         - By default, the same IP address is assigned to two SVPs of a disk array. When you use them, set a
           different IP address to each of them.
         - For two SVPs in a disk array, assign IP addresses that comply to the network to which SVPs belong. If
           the two SVPs connect to the same network, assign different IP addresses with the same network
           address. If each SVP connects to a different network, assign an IP address with the corresponding
           network address.
         - If a firewall is installed, the NEC Storage port 2730, which is used by iSM, must be opened. The port
           2730 is used for access from iSM server to NEC Storage.
         - If the initialization wizard is used for NEC Storage D series (except D8 series):
            - Disk arrays and iSM server must connect to the same network.
            - If a firewall is used, the port 2730 (UDP) must be opened.
Q2-10 What should I note when the IP address of the management server is restricted by the disk array network
      settings?
    A Register actual IP addresses of all the NICs that can access the SVPs on the management server for
      Manager IP. Only specifying virtual addresses (floating addresses) that are provided by cluster is
      insufficient.
Q2-11 Is it possible to run iSM server on an application server?
    A Running iSM server on an application server is not recommended. Access via FC is a likely option if iSM
      server runs on an application server. FC connection, however, is not recommended. Read the Q&A “Which
      should I choose for monitoring of disk arrays from iSM server, via FC or via TCP/IP?” Note that there may be
      a conflict between application load and iSM server program load even if monitoring via TCP/IP is selected.
Q2-12 Are the configuration settings inherited when iSM server is upgraded?
    A Before upgrading iSM server, uninstall iSM server that has been installed, and then install a newer version
      of iSM server. The following files are not removed even if iSM server is uninstalled.
          - Environment definition file
          - Log files
          - Static information history file
          - Static information summarized file
          - Performance optimization log file
          - License-related files
      If the new version of iSM server is installed in the folder (directory) where the older version was installed, the
      settings are inherited.
      You can change the folder where iSM server is installed only on Windows. The folder where iSM server is
      installed is fixed in UNIX.
      If the new version of iSM server (Windows) is installed in a folder different from the folder the old version
      was installed, copy files remaining in the folder for the older version to the folder for the new version.
      To check where iSM server is installed, follow the procedure below.
        (1) Select Start, Programs (for Windows Server 2003, All Programs), NEC Storage Manager server
            and right-click Read Me to select Properties.
        (2) Check the folder for installation from Target.
           (Ex) C:\Program Files\NEC\iSMsvr\help\readme.txt
                C:\Program Files\NEC\iSMsvr is the folder where iSM server is installed.
Q2-13 Are there any notes on upgrading an iSM server?
    A Upgrade the iSM server and the iSM clients together to the same version.
      Follow the upgrade procedure below.
       For iSM client (Web GUI)
         1. Terminate all the iSM clients (Web GUI).
         2. Stop and then upgrade the iSM server.
         3. Restart the iSM server and then connect the iSM clients (Web GUI).
         4. Log in the iSM server. Then click the Run button to launch the installer or click the Save button to
            download and run the installer program on the installation window for the iSM clients (Win GUI). This
            operation upgrades the iSM clients.
            Notes
               - iSM clients need not be upgraded preliminarily.
                 After the upgrade of the iSM server, connect the clients with the iSM server for upgrade.
               - If any other optional functions such as replication control are used, upgrade them as well.


       For iSM client (Win GUI)
         1. Terminate all the iSM clients (Win GUI).
         2. Upgrade iSM clients (Win GUI). Use the installer contained in the NEC Storage Manager CD.
         3. Stop the iSM server and upgrade it. This upgrade can be performed while the iSM clients (Win GUI)
            are upgraded.
         4. Restart the iSM server and connect iSM clients (Win GUI).
            Notes
               - For an iSM server of Ver1.3 or earlier, be sure to upgrade the iSM server and the iSM clients (Win
                 GUI) together.
               - When the iSM server is Ver1.4 or later and the iSM server and the iSM clients (Win GUI) cannot
                 be upgraded together, upgrade the iSM clients (Win GUI) before the iSM server. The functions
                 supported by the version of the iSM server are available for the upgrade.
               - If any other optional functions such as replication control are used, upgrade them as well.
Q2-14 The message iSM10316 is not reported to syslog after upgrading NEC Storage Manager from V2.1/V2.2 to
      V3.1. Are there any other messages like this?
    A Appendix A “Message Output Destination List” in NEC Storage Software Messages Handbook lists
      messages.
      In V2.2 or earlier, some message destinations did not match the destinations described in the handbook. To
      tackle this problem, destinations have been corrected in V3.1 or later.
      The following are concerned messages:
         ■ No longer reported to syslog (reported to operation log)
               - iSM10313
               - iSM10314
               - iSM10315
               - iSM10316
               - iSM10318


         ■ Now reported to syslog (reported to operation log and syslog)
               - iSM10302
               - iSM10303
               - iSM10304
               - iSM10305
               - iSM10306
               - iSM10307
               - iSM10308
               - iSM10309
               - iSM10330


         ■ Change of error type (reported to operation log and syslog)
               - iSM10210 (Info→Notice)
Q2-15 Does the mail link function of NEC Storage Manager support POP before SMTP and SMTP authentication
      mail servers?
    A When you are using NEC Storage Manager Ver3.1 or later, POP before SMTP and SMTP authentications
      can be used for sending messages.
      Supported SMTP authentications are LOGIN authentication, PLAIN authentication, and CRAM-MD5
      authentication.
Q2-16 What should I note to install iSM server on nodes that constitute a cluster?
    A Note the following when you install iSM server on nodes that constitute a cluster.
          - The cluster should be set to have one-way standby configuration. Make sure two or more iSM servers
            do not monitor the same disk array at a time.
          - In using the iSM server for one-way standby, the following files should be shared among cluster
            nodes.
              - Statistical information history file
              - Thresholds management file
              - Statistical information summarized file
              - Performance optimization log file
          - It is strongly recommended to use TCP/IP for monitoring because monitoring via FC may cause the
            following problems.
              - Transfer of the shared disk ownership due to a failover may disable monitoring via FC if the iSM
                servers are using the shared disk as a control path.
              - An LD failure may disable monitoring via FC.
              - When accessing the FC path selected for the control path of iSM server is prohibited by access
                control settings, monitoring from iSM server via FC is disabled and cannot be cancelled.
              - Access conflict may occur because both business applications and iSM server use FC for access.
Q2-17 Why does the NEC Storage Manager management server have the FTP server settings? Do I need to use
      the FTP server?
    A If you are using iSM client (Web GUI), or iSM server and iSM client (Win GUI) are on one machine, you do
      not need to configure the settings.
      However, if you are using iSM client (Win GUI) Ver2.1 or later, the settings to transfer files by FTP between
      the monitoring server where iSM server runs and PCs where iSM client (Win GUI) runs must be configured.
      Note that it is not requisite to run FTP because FTP is not used for monitoring of disk arrays. If the following
      scenes where file transfer is used are not assumed, you do not need to configure the FTP settings.
          - Acquiring the configuration information in the Configuration Setting screen
          - Downloading the statistical information file on the performance monitoring screen
          - Showing the Busy Ratio Graph or forecasting relocation effectiveness on the performance
            optimization screen.
          - Collecting failure information on the main screen (iSM client)
Q2-18 Which port numbers should be open in an environment where a firewall is installed?
    A The following ports should be open in an environment where a firewall is installed.
      ■Between iSM client (Web GUI) and iSM server
       SOURCE                                                 DESTINATION
       iSM client (Web GUI)                                   iSM server
       ANY                                                    8020/TCP
                                                              8070/TCP


          * Ports 8020 and 8070 are used for access from iSM client (Web GUI) to iSM server. They can be
            changed by configuring the settings.

      ■Between iSM client (Win GUI) and iSM server
       Ver2.1 or later
       SOURCE                                                 DESTINATION
       iSM client                                             iSM server
       ANY                                                    8020/TCP
                                                              20/TCP
                                                              21/TCP
   * The port 8020 is used for access from iSM client (Win GUI) to iSM server. It can be changed by
     configuring the settings.
   * Ports 20 and 21 must be opened to use the file transfer functions in iSM client (Win GUI). They do not
     need to be opened if the file transfer function is not used. They can be changed by configuring the
     settings. To use the file transfer functions, all TCP ports on iSM client (Win GUI) must be opened.


Ver1.5 or earlier
SOURCE                                                DESTINATION
iSM client                                            iSM server
ANY                                                   8020/TCP


   * The port 8020 is used for access from iSM client (Win GUI) to iSM server. It can be changed by
     configuring the settings.



■Between iSM server and NEC Storage
Ver5.1 or later
SOURCE                                                DESTINATION
iSM server                                            NEC Storage
ANY                                                   2730/TCP
iSM server                                            iSM server
ANY                                                   2730/UDP


   * To monitor NEC Storage via TCP/IP, the port 2730/TCP on NEC Storage must be opened. 2730/TCP
     is a port used for access from iSM server to NEC Storage. It cannot be changed.
   * To configure the network settings of D1 series/D3 series/D4 series where no network settings have
     been configured, 2730/UDP must be opened. It cannot be changed.


Ver4.3 or earlier
SOURCE                                                DESTINATION
iSM server                                            NEC Storage
ANY                                                   2730/TCP


   * To monitor NEC Storage via TCP/IP, the port 2730/TCP on NEC Storage must be opened. 2730/TCP
     is a port used for access from iSM server to NEC Storage. It cannot be changed.



■Between iSM server and mail server

Ver3.1 or later
SOURCE                                                DESTINATION
iSM server                                            SMTP server
ANY                                                   25/TCP
iSM server                                            POP server
ANY                                                   110/TCP
          * Ports 25 and 110 can be changed by configuring the settings.
          * When the function to authenticate by the POP server (POP before SMTP) is not used, 110/TCP is not
            necessary.
          * When the mail link function is not used, 25/TCP and 110/TCP are not necessary.


       Ver2.2 or earlier
       SOURCE                                                   DESTINATION
       iSM server                                               SMTP server
       ANY                                                      25/TCP


          * When the mail link function is not used, 25/TCP is not necessary.
Q2-19 To upgrade iSM server (Windows) to Ver4.1 or later, which of the following should I choose in the screen to
      select configuration setting shown at the installation?
      - Set the required minimum with the wizard
      - Set all functions by dialog
      - Do it later
    A When an upgrade is performed, the operating environment of the old iSM server remains.
      If there is no change in the operating environment, select Do it later. If a change should be made on the
      operating environment, choose either Set the required minimum with the wizard or Set all functions by
      dialog depending on the nature of the change.
      See the following for information on what can be configured
          - Set the required minimum with the wizard
              - Disk array settings
              - User settings
              - Client settings *available from Ver5.1
              - Operation log settings (folder to store log files and file size)
              - File transfer function settings
          - Set all functions by dialog
              - Settings of all functions
       When Set the required minimum with the wizard or Set all functions by dialog is selected at the
       upgrade, the settings of the previous iSM operating environment are shown and they can be modified. If
       the upgrade is finished without any change on the settings, the previous settings take effect. Even if Do it
       later has been selected and the installation is complete, the settings can be modified by selecting
       Programs (for Windows Server 2003, All Programs) from the Start menu and then choosing either Setup
       Wizard or Environment Settings from iSM server.
Q2-20 How much disk capacity and memory amount do I need to use iSM server?
    A The following lists disk capacities and memory amounts required to use iSM server. For versions not listed
      below, see the Installation Guide of the corresponding version of NEC Storage Manager.


       Ver5.3.002 or later


         ■ Linux
           Disk capacity        : 78 MB or more
           Memory amount        : The amount required for OS memory + 25 MB or more
 See the following information to monitor the E series disk array.
 * The E series is supported in Ver5.3.004 or later.
    Disk capacity       : 100 MB or more
    Memory amount       : The amount required for OS memory + 31 MB or more


  ■ Windows
    Disk capacity       : 88 MB or more
    Memory amount       : The amount required for OS memory + 110 (370) MB or more


 See the following information to monitor the E series disk array.
 * The E series is supported in Ver5.3.004 or later
    Disk capacity       : 110 MB or more
    Memory amount       : The amount required for OS memory + 130 (475) MB or more


 *The numeric enclosed in parentheses is memory amount required on the 64 bit OS.


Ver5.2.003


  ■ Linux
    Disk capacity       : 78 MB or more
    Memory amount       : The amount required for OS memory + 25 MB or more


  ■ Windows
    Disk capacity       : 88 MB or more
    Memory amount       : The amount required for OS memory + 110 (367) MB or more
                        * The numeric enclosed in parentheses is memory amount required on the 64 bit
                          OS.


Ver5.1.002


  ■ Linux
    Disk capacity       : 75MB or more
    Memory amount       : The amount required for OS memory + 25 MB or more


  ■ Windows
    Disk capacity       : 86 MB or more
    Memory amount       : The amount required for OS memory + 110 (360) MB or more
                        * The numeric enclosed in parentheses is memory amount required on the 64 bit
                          OS.


Ver4.3.002/Ver4.3.301


  ■ Linux
    Disk capacity       : 41 MB or more
               Memory amount        : The amount required for OS memory + 25 MB or more


           ■ Windows
               Disk capacity        : 50 MB or more
               Memory amount        : The amount required for OS memory + 75 (315) MB or more
                                     * The numeric enclosed in parentheses is memory amount required on the 64 bit
                                       OS.
Q2-21 What are the specifications for node names and host names in NEC Storage Manager?
    A In Ver4.2.201 or earlier, a node name should be within 8 bytes and a host name should be within 63 bytes.
      Exceeding these limits of character string length results in:


           1 iSM Sever link function
               In order to set mail reporting in the iSM server link function, the host name should be set within 63
               bytes. In a system where the host name is set longer than the specifications, the following message is
               shown, and mail reporting may fail.
                      iSM06065:Communication error(mail server).~
           2 iSM server environment settings
               When the address of a disk array is specified by host name in iSM server environment settings, the
               address must be specified within 63 bytes. If a host name with 64 or more bytes is specified, the
               following message is reported and startup of iSM server fails.
                      iSM01110:Illegal configuration. File=iSMsvr.conf line=nn section=agent ~
           3 The host name shown in the iSMvollist command
               When properties of the Volume List is shown by specifying the –p option and the -ax option in the
               iSMvollist command, up to 8 characters are shown for the node name in Owner Host Name.


Q2-22 Are there any notes on iSM server when an existing disk array is replaced with a disk array from the NEC
      Storage D1 series or D3 series or D4 series?
    A Before uninstalling the older version of iSM server, remove the settings (IP address) of the disk array to be
      replaced by configuring the environment settings.
      If the IP address is not removed, the IP address becomes unavailable in the network settings of the NEC
      Storage D1 series/D3 series/D4 series disk array.
Q2-23 Are there any notes on installing iSM server on a Windows Server 2008 Hyper-V virtual machine?
    A Note the following.
       -       Make sure that disk arrays are monitored via TCP/IP.
       -       Disk arrays from the E series cannot be monitored.
Q2-24 Are there any notes on using an iSM server in a Windows machine where security software(*) is installed?
      (*) Software to prevent information leakage, to block unauthorized accesses, computer viruses, etc.
    A In addition to the folder where iSM server is installed, iSM server creates folders/files in the following
      location to save configurations and log files.
      (by default, <system drive>:\Program Files\NEC\iSMsvr
      (for the 64-bit version, <system drive>:\Program Files (x86)\NEC\iSMsvr))


           -    Folders to store logs as specified in the iSM server environment settings and working folders
           -    <system drive>:\Documents and Settings\<login user name>\Application Data
                  *     For windows, Windows Vista、Windows Server 2008 folders/files are created in the following
                        location.
                   <system drive>:\user\<login user name> \AppData\Roaming


      If security software restricts the creation of these folders and files, the iSM server will not work normally.
      Change the software settings to prevent the restriction.
Q3-1 iSM server is started automatically when the system starts up. What should I do to prevent iSM server from
     starting up automatically?
   A Follow the procedure below to prevent iSM server from automatically starting up.
      ■ Linux
        rm /etc/rc2.d/S93iSMsvr
        rm /etc/rc3.d/S93iSMsvr
        rm /etc/rc4.d/S93iSMsvr
        rm /etc/rc5.d/S93iSMsvr
      ■ Windows
        In Administrative Tools, specify NEC Storage Manager from Services and switch the startup type to
        Manual.


      To restore automatic startup, follow the procedure below.
      ■ Linux
        ln -s /etc/init.d/iSMsvr /etc/rc2.d/S93iSMsvr
        ln -s /etc/init.d/iSMsvr /etc/rc3.d/S93iSMsvr
        ln -s /etc/init.d/iSMsvr /etc/rc4.d/S93iSMsvr
        ln -s /etc/init.d/iSMsvr /etc/rc5.d/S93iSMsvr
      ■ Windows
        In Administrative Tools, specify NEC Storage Manager from Services and switch the startup type to
        Automatic.
Q3-2 Is it OK to monitor a single disk array by two or more iSM servers?
   A iSM can monitor two or more disk arrays at a time but a single disk array cannot be monitored by two or
     more iSMs. Monitoring a disk array by two or more iSMs causes dual reporting of a failure or conflict in
     performance statistical information, which results in operation problems.
Q3-3 Which iSM processes should be monitored for restart after an iSM server failure?
   A iSM server consists of multiple processes. For restart after a failure, monitor the following main process of
     iSM.
         - Windows                                           : iSMmaind.exe
         - Linux                                             : iSMmaind
     For other processes, the main process monitors. When a failure occurs, restart is tried. Restart is tried up to
     5 times per an hour. The sixth restart try either stops the server or closes the function of the process having
     the problem.
Q3-4 When the event link function is not used, what should I do to prevent the iSM06029 and iSM06040 message
     from being reported?
   A In Ver1.x of NEC Storage Manager, the dummy link definition file and the dummy header file must be
     prepared even if the event link function is not used. Without these files, the iSM06029 or iSM06040
     message is reported in syslog or operation log. See the following to create these files.
        1. Create /etc/iSMsvr/msgdrv.conf.
           Copy /etc/iSMsvr/msgdrv.sample(sample file) to /etc/iSMsvr/msgdrv.conf for creation(rename).
           Comment out (# at the top of the line) the link definition of the [LEVEL] section of msgdrv.conf.


                *** Beginning of an example of msgdrv.conf ***
                  [SERVER]
                  SMTP=123.123.123.123
                  HEADER=/etc/iSMsvr/mail.header
                  [LEVEL]
                  #ERR =shell(/opt/iSM/etc/err_shell) ,mail(iSM@nec.co.jp), mail(emergency@nec.co.jp)
                  #WARNING =shell(/opt/iSM/etc/warning_shell) ,mail(iSM2@nec.co.jp)
                  #NOTICE =shell(/opt/iSM/etc/notice_shell) ,mail(iSM3@nec.co.jp)
                  *** End of the example of msgdrv.conf ***


        2. Create the header file defined in HEADER of the [SERVER] section of msgdrv.conf. For the example
           msgdrv.conf in the previous step, 1, copy /etc/iSMsvr/mail.sample(sample file) to
           /etc/iSMsvr/mail.header for creation (rename).


      (Note)
            - Specify a dummy address in the SMTP server name described in SMTP. A machine having that IP
              address does not need to exist.
            - The header file must start with “FROM:” No other descriptions are needed.
            - If there is no link definition file or header file, a warning message is displayed for your attention. If you
              do not use the event link function and can ignore the warning messages, you do not need to create
              dummy link definition file and the dummy header file.
            - No message is reported in NEC Storage Manager versions other Ver1.x.
Q3-5 Is remote operation through terminal service client or remote desktop possible?
   A Remote operation is possible for iSM server with some exceptions.
     The following functions may not work successfully on a terminal service client or remote desktop. To use
     these functions, directly log in to the server having the functions.

      Notes on NEC Storage Manager
            - Configuration setting commands such as iSMview or volume display commands cannot be executed
              on a command prompt on a terminal service client or remote desktop. The function to show the
              Volume List at a glance cannot be used.
              Failure to run commands or to show disk or volume information may occur.
            - Do not select Log Collection of iSM server or Difficulty Information Gather in Storage Manager
              Volume List on a terminal service client or remote desktop.
              Collecting some disk array information such as device log or disk or volume information may fail.
Q3-6 What should I do to send a test message to the mail address defined in the event link function?
   A Temporarily define the mail association for messages reported under normal circumstances to check
     messages are sent successfully.
     For example, define the association for INFO-level messages. The INFO-level messages are reported when
     an iSM client is connected to an iSM server, by which the link test is achieved.
Q4-1 What should I do for the message “Error occurred at the time of deleting environment variable.” shown when
     installation of iSM server in Windows fails?
     What should I do for the message “Storage Manager Server installer was interrupted.” shown when the
     quick installation for NEC Storage Manager Setup, which is supported from V5.1, is selected.
   A This problem occurs when 1024 or a greater value is already set to the system environment path
     (Ver5.3.002 or earlier).
     Follow the steps below for the installation.


      (1)     Right-click My Computer, and then click Properties on the shortcut menu. In the System
           Properties dialog box, click the Advanced tab, and then click Environment variables.
     (2)   Check if there are any unused paths in System Variables.
           If there are any unused paths, remove them. Install iSM Sever again when the system variables path
           is within 1023 bytes.
           If you cannot reduce the system variables path to 1023 or smaller, continue performing (2).
     (3)   Click Path under System variables and then click Edit.
     (4)   Copy the value in Variable value in the Edit System Variable box to a text file for backup.
     (5)   Delete the value in Variable value and close the dialog boxes.
     (6)   Reinstall iSM server.
           You are asked whether or not to restart Windows after iSM server is installed. Do not restart Windows
           at this point but restart it in (10).
     (7)   Right-click My Computer, and then click Properties on the shortcut menu. In the System
           Properties dialog box, click the Advanced tab, and then click Environment variables.
     (8)   Click Path under System variables and then click Edit.
     (9)   Append what you have saved in step (4) to the path information configured in Variable value and
           close the dialog box.
     (10) Restart Windows.


     Restrictions on effective size of system variables path may make the path partly ineffective because of iSM
     server installation. Run the PATH command from a command prompt to check path is fully effective.
     If the path is partly ineffective, uninstall iSM server and install it on a different server.
Q4-2 What should I do for the message “Failed in getting systempath of environment variable.” shown while iSM
     server in Windows is uninstalled?
   A This problem occurs when 1024 or a greater value is already set to the system environment path.
     Uninstallation completes when you click OK but the iSM server path information remains in Path under
     System variables. Follow the steps below to remove the iSM server path information (Ver5.3.002 or
     earlier).


     (1)   Right-click My Computer, and then click Properties on the shortcut menu. In the System
           Properties dialog box, click the Advanced tab, and then click Environment variables.
     (2)   Click Path under System variables and then click Edit.
     (3)   Remove the following, which is set to the variable, and then close the dialog box.
           %iSMrd%\sbin;%iSMrd%\lib;
Q4-3 What should I do when disk arrays cannot be monitored via TCP/IP?
   A First of all, check the environment settings of iSM server are correctly configured.
     If the settings are correctly configured, check the network connection by using the ping command, etc.
     SVPs are redundant. The same IP address is assigned to them by default. However, different IP addresses
     should be set to avoid invalid dual IP address.
     Also check the port (2730), which iSM uses, is not blocked by a firewall.
     If any other iSM server is started and monitoring the same NEC Storage SVPs, monitoring may be disabled.
     Check the SVPs are not monitored by any other iSM servers.
     If you do not find any problem in above mentioned, a hardware failure is conceivable.
     Obtain the material showing the network configuration of the management server and SVP and collect
     failure information on the iSM server.
Q4-4 What should I do when disk arrays cannot be monitored via FC?
   A First of all, check the environment settings (iSM server) are correctly configured. If the settings are correctly
     configured, check the disk arrays are correctly recognized by the OS. If accessing the disk arrays from the
     management server where iSM server is installed is prohibited by the access control, the OS of the
     management server cannot recognize the disk arrays. Consequently, iSM server cannot monitor the disk
      arrays through FC. Or if RV being synchronized is the only volume allocated on the management server
      where iSM server is installed, the OS of the management server cannot recognize the RV. This also does
      not allow iSM server to monitor disk arrays via FC.
      If the disk arrays are successfully recognized, collect the failure information on the iSM server.
 Q4-5 Though rarely, monitoring disk arrays via TCP/IP stops. What should I do?
    A Redundancy of SVPs switches the TCP/IP path to the standby path when a failure occurs in the TCP/IP
      path.
      Stop of monitoring may be caused by erroneous monitoring settings, which prevents use of the standby
      path.
      Check the settings. Refer to Q4-3 as well.
 Q4-6 What information should I collect when a trouble occurs on iSM server and the cause is unknown?
    A For Linux, execute the iSMgather command. For Windows, execute Log Collection from Server Menu.
       The cause is examined based on this information.
       In iSM Ver3.1 or later, this information can be collected from iSM client through the file transfer function.
 Q4-7 Nothing was reported in the operation logs because iSM server could not be started. What should I do?
    A For Linux, see syslog. For Windows, see event log. There may be an error in the environment settings.
 Q4-8 Mail link does not work. What are conceivable causes?
    A The following are conceivable. See operation log messages and mail server error logs as well to find the
      cause.
          - Error in the SMTP server specification
          - Failure of mail forwarding due to SMTP server transfer restriction
          - Error in the recipient’s e-mail address
          - Error in the sender’s e-mail address
          - Error in the specified action level
 Q4-9 Shell script (batch file) link does not work. What are conceivable causes?
    A The following are conceivable. See operation log messages as well to find the cause.
          - Error in the SMTP server specification
          - Not an absolute path but a relative path has been specified.
          - Error in the information in the shell script (batch file)
          - Error in the link target message (Ver4.1 or later)
          - Error in the link target message level (Ver4.1 or later)
          - Error in the specified action level (Ver3.4 or earlier)
          - Error in shell script (batch file) permissions
          - No environment variables have been set.
      The environment where NEC Storage Manager was started is used for the environment where shell starts
      (such as environment variables). Settings such as environment variables are different when started from the
      system at OS startup and when started by a user. Required environment variables must be configured at the
      top of shell script (batch file).
Q4-10 Nothing is described in the message sent by the mail link. What should I do?
    A It is quite likely that the descriptor “$MSG”, which is converted to an actual message, is missing in the mail
      template file (mail header file for Ver3.4 or earlier) used for sending messages. Add “$MSG”
Q4-11 Iometer, which is provided by Intel for the Windows environment, does not work when iSM server is
      installed. What should I do?
    A Iometer reserves a fixed port number for a socket. This problem occurs when there is a conflict of socket
      port between Iometer and iSM server started up earlier. You can start Iometer when NEC Storage Manager
      is stopped by service. You can run Iometer and NEC Storage Manager together by resuming
      StorageManager after starting Iometer.
Q4-12 What should I do when the iSM01408 error is shown after iSMsvr is executed.
    A The error is reported when there is no permission for iSM server. Check the following.
          - To start iSM server, the root authority is required. Start iSM server as super user.


Q4-13 A file named iSMgather.tar.Z is not created after collecting failure information (running iSMgather) in the
      environment where Red Hat Enterprise Linux Version 2.1 is used for OS. What should I do?
    A In the Red Hat Enterprise Linux Version 2.1 environment, the compress command used for information
      collection at the time of NEC Storage Manager failure is sometimes not installed depending on the way the
      OS is installed. Make sure to install the RPM package of ncompress, which is contained in the Red Hat
      Enterprise Linux Version 2.1 CD, in advance. This is also the same for collection of information at a client
      failure.
Q4-14 What causes automatic restart of iSM server?
    A The following are conceivable.
          - Disconnecting the FC cable while disk arrays are monitored by iSM server (Windows) via FC
            connection can cause a communication error in the OS. When such communication failure is detected,
            iSM server automatically restarts.
            Monitoring of disk arrays can be continued even after iSM server is automatically restarted.
Q4-15 The following message is reported when the command to encrypt a password (iSMcipherpw) is executed.
      Incorrectly built binary which accesses errno or h_errno directly.
      Needs to be fixed.
      The encrypted value is reported as well. Has the encryption been completed successfully?
    A This message is reported when the command for encrypting a password in V3.3 to V4.1 (Linux version) is
      executed in the RHEL AS/ES 3.0 OS. Note that the encryption is completed successfully. You can continue
      using the encrypted value.
      If you do not want the above message to be reported, set the value "2.4.1" to the environment variable
      LD_ASSUME_KERNEL, and then run the command.

       [Example of execution (for sh)]
            # LD_ASSUME_KERNEL=2.4.1;export LD_ASSUME_KERNEL
            #iSMcipherpw the password value
            Accepted password is the password value.
            Return value is the password value.
            #unset LD_ASSUME_KERNEL
Q4-16 CPUs of a process for iSM server in Windows are highly loaded. What causes the high CPU load?
    A In an environment where an antivirus software program is installed, files are always checked because iSM
      server trace files are reported. This results in highly loaded CPUs, and may impact the system operation.
Q4-17 When any option other than Smaller - 100%(default)(S) is selected on the Display dialog box, which is
      opened by selecting Control Panel and Design, on Windows Server 2008 R2 or Windows7, display is
      distorted or mouse operation is disturbed. What should I do?
    A This problem may be experienced when Ver6.1 is used and a size other than Smaller - 100%(default)(S) is
      configured. Choose the default settings Smaller - 100%(default)(S).
 Q5-1 How do I migrate iSM server?
    A Follow the steps below to migrate iSM server.
      The environment to be migrated is iSM server that monitors disk arrays through IPs.
      The following steps explain how to migrate iSM server from the source (management node A) to the target
      (management node B) while the way disk arrays are monitored remains the same.
      <Work to be done on the target (management node B)> and <Work to be done on the source (management
      node A)> are described according to the steps.

      Note that there are some differences between UNIX (including Linux) and Windows.
<Work to be done on the target (management node B)>
 (1) Check the OS of the management node B.
    Check iSM server supports the OS on the management node B, the target.
    For information on OSes iSM server supports, see NEC StorageManager Installation Guide.


 (2) Build the environment of the management node B.
    Perform the following:
        - Apply the OS patch(es).
        - Build the network environment (such as cabling).


 (3) Configure the ESMPRO link (only for Windows version).
    Install ESMPRO if it should be associated and work together. It is not necessary to install ESMPRO if
    it is not associated.


 (4) Build the ftp server environment.
    This is not required when iSM client (Web GUI) is used.
    If the following is performed on iSM client (Win GUI) Ver. 2.1 or later, build the ftp server environment.
    It is not necessary to build the ftp server environment if the following is not performed.
        - Selecting Log Collection on the main screen.
        - Selecting Configuration Information Saving on the Configuration Setting menu
        - Selecting Download statistical information files on the performance optimization screen.
        - Selecting Busy Ratio Graph or Replacement Effect Prediction on the performance
          optimization screen.
    In the Windows version, if iSM server and iSM client (Win GUI) are used on the same machine, it is
    not necessary to build this environment because the ftp service is not used.


 (5) Check the network environment that iSM server uses.
    If a firewall is used, configure the settings to allow packets from/to iSM server to pass through the
    firewall. The following lists default ports iSM server uses.
      (a) Between iSM client (Web GUI) and iSM server
            - 8020/TCP
            - 8070/TCP
      (b) Between iSM client (Win GUI) and iSM server
            - 8020/TCP
            - 20/TCP *only when the ftp server environment is built in step (4).
            - 21/TCP *only when the ftp server environment is built in step (4).
      (c) Between iSM server and NEC Storage
            - 2730/TCP
      (d) Between iSM server and the mail server (only when the mail link function is used)
            - 25/TCP
            - 110/TCP *only when the function to authenticate by the POP server is used


 (6) Configure system parameters (only for UNIX).
    Make sure to check parameters required to operate iSM server in NEC StorageManager Installation
    Guide and configure them as necessary.
    Failure to set appropriate values to system parameters can impact iSM server behavior and cause
    problems such as failure to start up iSM server.


<Work to be done on the source (management node A)>
 (7) Check and configure the disk array network settings.
    Check that the management server settings (settings of the iSM server that monitors disk arrays) have
    been configured in disk arrays.
    From the Configuration Setting menu, select Management Setting, Network, and click Set
    Management Socket. If the Accept management packets from the following IP Address(es)
    check box is selected in the Set Management Socket dialog box and the IP address of the
    management node A is set, change to Accept management packets from any IP address.
    If Accept management packets from any IP address has already been selected, no change is
    necessary.
        * For a disk array with two SVPs, check and configure both SVPs.
          This can be done by switching the number shown in service processor number.


 (8) Stop iSM server.
        - For UNIX:
          Stop iSM server by using iSMsvr stop –e.
          When iSM server stops, the message, “iSM01004: NEC Storage Manager has terminated
          emergency” is reported in syslog. Check to see the message is shown in syslog.
        - For Windows:
          Select NEC Storage Manager from services to stop iSM server.
          When iSM server stops, the message “iSM01003: NEC Storage Manager has terminated
          normally” is shown in event logs. Check to see the message is shown in event logs.


 (9) Check files to be backed up (only for Windows)
    Backing up the environment setting file and related files and restoring them in the management node
    B allows for inheriting the operation environment of iSM server.
    Folders where the files are restored need to be the same as the installation folder in the management
    node A. Follow the steps below to check the installation folder and take notes of the information about
    installation folder.
        - From the Start menu, select Programs.
          (For Windows Server 2003, click All Programs, Storage Manager Server and right-click Read
          Me to select Properties.
        - Check the folder for installation in Target.
          (Ex) C:\Program Files\NEC\iSMsvr\help\readme.txt
          In this case, C:\Program Files\NEC\iSMsvr is the folder for installation.
    Start up the environment settings (by selecting Programs on the Start menu (on Windows Server
    2003, select All Programs, Storage Manager Server and Setup Utility) to check the following. Take
    notes as necessary.
      (a) On the State Monitoring tab, a folder other than the default value (folder for installation
          \iSMsvr\etc\log) is set in Log File Folder for operation log information.
      (b) On the Performance Monitoring tab, a folder other than the default value (folder for
          installation\iSMsvr\etc\mon) is set in Log File Folder for statistical information.
      (c) On the Performance Optimization tab, a folder other than the default value (folder for
          installation\iSMsvr\etc\optlog) is set in Log File Folder.
      (d) On the Event Link tab, a batch file or execution file is set in the list of links.
     For information on the environment settings, see NEC Storage Manager Installation Guide.


(10) Uninstall iSM server
     Uninstall iSM server. For details of the uninstallation, see NEC Storage Manager Installation Guide.
     Files required for the iSM server operation such as the those for the environment settings are not
     removed


(11) Back up iSM server environment settings and related files.
         - For UNIX
          Back up all the files in /etc/iSMsvr and in /opt/iSMsvr.
          Check and back up the following files for environment setting file (/etc/iSMsvr/iSMsvr.conf) and
          link definition file(/etc/iSMsvr/msgdrv.conf).
          (a) Environment definition file
             - The file_directory parameter in the [log] section
             - The monitor_file_directory parameter in the [performance] section
             - The optlog_directory parameter in the [optimizer] section
          (b) Link definition file
             - A shell file or execution file is set in the SHELL parameter of [LINKxxx].
          Back up files, shell files or execution files in the directories shown above.
          For information on environment definition and link definition files, see NEC Storage Manager
          Installation Guide.


         - For Windows
          Back up all the files checked in step (9).


<Work to be done on the target (management node B)>
(12) Install iSM server.
     Install iSM server. For information on how to install, see NEC Storage Manager Installation Guide.
     For Windows, specify the path name of the same installation folder as the management node A that
     has been checked in (9).
     As you see the message for restarting Windows during the installation, select No, I will restart my
     computer later.


(13) Restore the iSM server environment settings and related files.
     Restore the files backed up in step (11) in the same directory/folder as the management node A.


(14) Check and reconfigure the iSM server environment settings.
     Check that directories and folders specified in the iSM server environment settings are correct.
     If the ftp server environment has been build as described in step (4), see NEC Storage Manager
     Installation Guide and configure the following settings in iSM server.
         - For UNIX
          Modify the [file_transfer] section in the environment definition file (/etc/iSMsvr/iSMsvr.conf).
         - For Windows
          From the Start menu, select Programs (for Windows Server 2003, click All Programs, Storage
          Manager Server and Setup Utility to modify the information in the File Transfer tab.
     Make sure that the directories/folders for operation logs and the like have enough free space.
    If there is any change in the mail server used for sending messages for the event link function, the
    mail information must be modified. Change the information in /etc/iSMsvr/msgdrv.conf for UNIX and in
    Mail Setup on the Event Link tab of Setup Utility for Windows.
(15) Start up iSM server.
        - For UNIX
          Execute the iSMsvr start command or restart the OS.
        - For Windows
          Restart the OS.
    Check that the message “iSM01002: NEC Storage Manager is ready” is shown in syslog or event log,
    and then access the management node B by using the iSM client to check disk arrays are monitored.


(16) Check and configure the disk array network settings.
    If Accept management packets from any IP address is selected in Configuration Setting in step
    (7), select Accept management packets from the following IP Address(es) and configure the IP
    address of the management node B.
        * For a disk array with two SVPs, check and configure both SVPs.
          This can be done by switching the number shown in service processor number.
    Note Configure not the floating address of the management node B but the actual address of the NIC
         (if there are multiple NICs, all of their addresses).


<Work to be done on the source (management node A)>
(17) Refresh the network environment used by iSM server.
    If a firewall is used, disable ports used by iSM server. The following lists ports used by iSM server by
    default.
      (a) Between iSM client (Web GUI) and iSM server
            - 8020/TCP
            - 8070/TCP
      (b) Between iSM client (Win GUI) and iSM server
            - 8020/TCP
            - 20/TCP *only when the ftp server environment has been built in step (4).
            - 21/TCP *only when the ftp server environment has been built in step (4).
      (c) Between iSM server and NEC Storage
            - 2730/TCP
            - 2730/UDP *Only when the initial settings have been configured for Storage D series (except
              D8 series) by using the initialization wizard.
      (d) Between iSM server and the mail server (only when the mail link function is used)
            - 25/TCP
            - 110/TCP *Only when the function to authenticate by the POP server is used
Storage Management

iSM Client (Web GUI)
1. Installation
                   Q1-1 How much disk space do I need for using the iSM Client?
                   Q1-2 How much memory do I need for using the iSM Client?
                   Q1-3 What software is required for using the iSM Client?
                   Q1-4 Are there any problems with different versions of JRE that have been installed in a machine
                        where the iSM Client is used?
                   Q1-5 Does any setting need to be made on the web browser for using the iSM Client?
                   Q1-6 When should I install the iSM Client (Win GUI) to use the iSM Client (Web GUI)?
                   Q1-7 Can I apply the settings of iSM Client (Web GUI) to a machine in which the iSM Client (Win GUI)
                        has been used?
                   Q1-8 Are there any notes on upgrading iSM Client?
                   Q1-9 I connected to the iSM server using the iSM Client (Web GUI), and then downloaded the installer
                        of the iSM Client (Win GUI) and executed it.
                        The installation completed, but the shortcut icon was not created on the desktop. Why it was not
                        created?
                  Q1-10 Is the shortcut icon for starting iSM Client automatically created?
                  Q1-11 Are there any notes on using the iSM Client in a machine where JRE 6 update 10 or later is
                        installed?


2. Operation
                   Q2-1 Which user privilege do I need for using the iSM Client?
                   Q2-2 When the iSM Client started, the Java icon stayed on the web browser for a while and then the
                        connection window appeared. Why the connection window did not appear right after the iSM
                        Client started?
                   Q2-3 When I started the iSM Client, the Warning Security window appeared. What should I do?
                   Q2-4 When I started the iSM Client, the Windows Security Alert window showing that Internet Explorer
                        functions were blocked appeared. What should I do?
                   Q2-5 Have messages shown on the message field in the iSM Client been saved?
                   Q2-6 Where is the file including saved messages located?
                   Q2-7 Which format does the file including saved messages have?
                   Q2-8 Can I view the file including saved message?
                          How much is the maximum size of the file to which messages shown on the message field in the
                   Q2-9
                          iSM Client are reported?
                  Q2-10 To where and how much logs does the iSM Client report?
                  Q2-11 I want to know the meanings of the messages shown on the message field in the iSM Client.
                  Q2-12 Why I could not change a nickname or control monitoring (could not select the item on menus)?
                        What should I do to use perform NEC Storage DynamicDataReplication, NEC Storage
                        RemoteDataReplication, NEC Storage PerformanceMonitor , NEC Storage
                  Q2-13
                        PerformanceOptimizer, NEC Storage DynamicSnapVolume, NEC Storage VolumeProtect
                        function in the iSM Client?
                  Q2-14 Can I use the iSM Client remotely using the terminal service client or the remote desktop?
                  Q2-15 I have used the iSM Client in a machine where JRE 1.4.2 is installed. When I moved the cursor to
                        an entry field with a spin button using a shortcut key, I could not make any entry. Why did it
                        happen?
                  Q2-16 When I used the iSM client in a machine where JRE 5.0 is installed, the keyboard did not work on
                        some windows (a focus disappeared). Why did it happen?
              Q2-17 I have used the iSM client through Internet Explorer 7 (or 8).
                    When I attempted to view the help menu of the iSM Client by pressing the F1 key, the help menu
                    of Internet Explorer appeared. Why did it happen?
              Q2-18 The lines connecting items did not appear in an iSM Client tree. Why they did not appear?
              Q2-19 While a window (or dialog) was shown in the iSM Client, another dialog appeared. However, I
                    could not manipulate the second dialog. What should I do?
              Q2-20 Repeating the same operation in the iSM Client displayed more than one same dialog. Why did it
                    happen?
              Q2-21 I could not specify a name for the replication port. Why I could not specify the name?
              Q2-22 Can I connect to the iSM server from a web browser, via the proxy server?
              Q2-23 On the Connected Host list window, "-" appeared as the logical disk status. Why did it happen?
              Q2-24 Port and Cache Segment are indicated only for some resource disk arrays displayed in the
                    Configuration display area.
              Q2-25 Under which condition tabs are shown in the Configuration display area?
              Q2-26 When Port is selected in the Configuration display area, which kinds of port are shown in the
                    Information list display area for a disk array for which NEC Storage VirtualStoragePartitioning has
                    been purchased?
              Q2-27 In a partition port list under the Partition tab, ports that were not assigned at the partition setting
                    were shown. Why did it happen?
              Q2-28 Controllers and enclosures were indicated for each partition under the Partition tab, though they
                    were not assigned at the partition setting. Why they were indicated?
              Q2-29 I have used VirtualStoragePartitioning.
                    When I select a cache segment under the Partition tab, which kind of logical disk is shown in the
                    Information list display area?
              Q2-30 Why does the disk-array monitoring temporarily stop?
              Q2-31 I could not create a storage user, or edit or delete the created storage users shown on the User
                    setting window. Why I could not do these operations?
              Q2-32 I have used the iSM Client on Windows Vista (or later) or Windows Server 2008 (or later).
                    After I executed CSV Output of Information List with a folder under C:\Program Files specified
                    as the CSV-file output destination, the CSV file were not created under the folder. Why did it
                    happen?
              Q2-33 Are there any notes on using the iSM Client in a machine where security software(*) is installed?
                    (*) Software to prevent information leakage, to block unauthorized accesses or computer viruses,
                    etc.


3. Troubleshooting
               Q3-1 The Replication/Performance Monitoring/Performance Optimization/Snapshot/Volume Protect
                    Management window did not appear. What should I do?
               Q3-2 Connection from a client failed. What is the possible cause?
               Q3-3 I have used the iSM Client in which JRE 6 has been installed. I could not change the name of a
                    folder that I have created using the folder creation button on the storage folder selection window
                    for a file. Why did it happen?
               Q3-4 When I attempted to delete the connected host information, the "Failed in deleting host
                    information(17)." dialog appeared. Why did it appear?
               Q3-5 When I changed the desktop theme between the Windows Classics, Windows XP, and Windows
                    Vista styles while the iSM Client (Web GUI) is active, an iSM Client (Web GUI) window did not
                    work normally. Why did it happen?
               Q3-6 When the iSM server is connected, nothing appeared on the web browser window and Done was
                    only displayed in the status bar.
                    How can I solve this problem?
                Q3-7 When I run installation of the iSM Client (Win GUI) through the iSM Client (Web GUI), the dialog
                     "Error occurred during download(197). Please make sure the connection is not via a proxy
                     server." appeared. What should I do for this?
                Q3-8 I have not used the access control function for operation. When I collected the host information
                     on the server to which storage logical disks have been assigned and registered the information
                     with the iSM server, "-" appeared as Logical Disk Status in the list of hosts connected to the iSM
                     Client. Why did it happen?
                Q3-9 I have used iSM Client (Web GUI) V5.1.
                     On the iSM Client menu, I found that the background color behind separator lines is different from
                     colors behind other areas. Can I leave it as is?
               Q3-10 Though I changed the order of columns in the Information list display area, the order returned to
                     the original after a while. Why did it happen?
               Q3-11 When I attempted to start the iSM Client, the message [00000] appeared and the start failed. Why
                     did it fail?
               Q3-12 When I attempted to start the iSM Client, the message [00008-04] appeared and the start failed.
                     Why did it fail?
               Q3-13 Some button did not appear on the Storage Folder Selection window for a file. Why they did not
                     appear?
               Q3-14 When I clicked Run on the iSM Client (Win GUI) download window after connecting to the iSM
                     server, nothing started. Why did it happen?
               Q3-15 When I attempted to restart OS that has recognized an iSCSI device, the error message of event
                     ID 1, event ID 5, event ID 70, or event ID 113 appeared in the event log. What should I do?
               Q3-16 When I used the iSM Client in a machine where JRE 6 update 10 or later has been installed, a
                     window was suddenly frozen and no longer worked. Tell me about the cause and what I should
                     do.
               Q3-17 When I used the iSM Client, the following message appeared. Tell me about the action I should
                     take.
                       [01086-02] Failed in acquring information (Time-out)


4. Migration
                Q4-1 Tell me how to change the IP address of a machine in which the iSM Client is running.
                Q4-2 Tell me how to transfer the iSM Client to another machine.
                Q4-3 Which files will be deleted and will not be deleted from the installation folder when the iSM Client
                     is uninstalled?
                Q4-4 When upgrading a machine using the iSM Client to Windows Vista, do I need to perform any
                     operations in the iSM Client?


                Q1-1 How much disk space do I need for using the iSM Client?
                   A Because the iSM Client (Win GUI) needs to be installed for using the iSM Client (Web GUI), a
                     disk having an enough size to install the iSM Client (Win GUI) is required.
                Q1-2 How much memory do I need for using the iSM Client?
                   A It depends on the version as shown below.
                        * Operating a window other than the main requires a memory size enough to operate
                          both the window and the main window.
                          A value in parentheses is the memory size required for operating the window on a
                          64-bit OS.


                      Ver 6.1
                                                    23 (23) MB or    Failure Information gathering    5 (10) MB or
                      Main window
                                                        more         window                               more
      Configuration Setting                                                           8 (13) MB or
                                    1 (2) MB or more Snapshot window
      window                                                                              more
                                     13 (14) MB or     Data Retention Management      7 (12) MB or
      Replication window
                                         more          window                             more
      Performance Monitoring         14 (15) MB or                                    6 (7) MB or
                                                       Partition Setting window
      window                             more                                            more
      Performance Optimization       16 (32) MB or     Cache Partitioning Setting     3 (5) MB or
      window                             more          window                            more
                                     11 (12) MB or
      iSCSI Setting window                                           -                     -
                                         more


      Ver 5.2
                                    90 (140) MB or Failure Information Gathering 10 (31) MB or
      Main window
                                         more      window                            more
      Configuration Setting         26 (46) MB or                                    12 (29) MB or
                                                  Snapshot window
      window                             more                                            more
                                    24 (52) MB or Data Retention Management 11 (28) MB or
      Replication window
                                         more     window                        more
      Performance Monitoring        15 (35) MB or                                    7 (15) MB or
                                                  Partition Setting window
      window                             more                                            more
      Performance                   16 (32) MB or Cache Partitioning Setting          5 (8) MB or
      Optimization window                more     window                                 more


      Ver5.1
                                     73 (140) MB or    Performance Optimization     16 (32) MB or
      Main window
                                          more         window                           more
      Configuration Setting          25 (45) MB or     Failure Information          10 (31) MB or
      window                             more          Gathering window                 more
                                     24 (52) MB or                                  12 (29) MB or
      Replication window                               Snapshot window
                                         more                                           more
      Performance Monitoring         15 (33) MB or     Data Retention               11 (21) MB or
      window                             more          Management window                more
Q1-3 What software is required for using the iSM Client?
   A The following software is required:
     [Ver 6.1]
     ■ Web browser
        - Microsoft Internet Explorer Version 6 to 8
         *      The Version 7 and later are supported by Windows Vista and Windows Server
                2008.
         *      Only the Version 8 is supported by Windows 7 and Windows Server 2008 R2.
     ■ JRE (Java Runtime Environment)
         One of the following JREs (32-bit version) is required:
             - 5.0 Update 8 to 16
             - 6 Update 3 to 7, 10 to 13
     *   Be sure to install JRE 6 Update 11 or later for using Internet Explorer Version 8.
         Other versions of JRE are not supported by the IE Version 8.
     The following table shows JREs supported by each OS:


                                          JRE 1.4.2 (32                         JRE 6 (32 bit)
                                                           JRE 5.0 (32 bit)
                                          bit)                                  *6 Update
OS                                                         *5.0 Update
                                          *1.4.2_12 to                          3 to 7,
                                                           8 to 16
                                          1.4.2_16                              10 to 13
Windows 2000 Professional                        N                 S                    S
Windows 2000 Server                              N                 S                    S
Windows 2000 Advanced Server                     N                 S                    S
Windows XP Professional Edition                  N                 S                    S
Windows XP Professional x64 Edition              N                 S                    S
                                                                   S
Windows Vista Business                           N             (Update                  S
                                                                         (*1)
                                                            11 or later)
                                                                                       S
Windows 7
                                                 N                 N               (Update
Ultimate/Enterprise/Professional
                                                                                13 or later) (*3)
Windows Server 2003, Standard
                                                 N                 S                    S
Edition
Windows Server 2003 R2, Standard
                                                 N                 S                    S
Edition
Windows Server 2003, Standard x64
                                                 N                 S                    S
Edition
Windows Server 2003 R2, Standard
                                                 N                 S                    S
x64 Edition
Windows Server 2003, Enterprise
                                                 N                 S                    S
Edition
Windows Server 2003 R2, Enterprise
                                                 N                 S                    S
Edition
Windows Server 2003, Enterprise x64
                                                 N                 S                    S
Edition
Windows Server 2003 R2, Enterprise
                                                 N                 S                    S
x64 Edition
                                                                                       S
Windows Server 2008 Standard                     N                 N               (Update
                                                                                 4 or later) (*2)
                                                                                       S
Windows Server 2008 R2 Standard                  N                 N               (Update
                                                                                13 or later) (*3)
                                                                                       S
Windows Server 2008 Enterprise                   N                 N               (Update
                                                                                 4 or later) (*2)
Windows Server 2008 R2 Enterprise                N                 N                    S
                                                                                       (Update
                                                                                    13 or later) (*3)


     Combinations for which "S" is shown are only supported. Other combinations are not
*
     applicable.
*1: Windows Vista supports JRE 6 and JRE 5.0 Update 11 and later.
*2: Windows Server 2008 supports JRE 6 Update 4 and later.
*3: Windows 7 and Windows Server 2008 R2 support JRE 6 update 13.



[Ver 5.3]
■ Web browser
    - Microsoft Internet Explorer Version 6 or 7
■JRE (Java Runtime Environment)
     One of the following JREs (32-bit version) is required:
        - 1.4.2_12 to 1.4.2_16
        - 5.0 Update 8 to 14
        - 6 Update 3 to 7
     The following table shows JREs supported by each OS:


                                       JRE 1.4.2 (32 bit) JRE 5.0 (32 bit)         JRE 6 (32 bit)
OS                                     *1.4.2_12 to       *5.0 Update              *6 Update
                                       1.4.2_16           8 to 14                  3 to 7
Windows 2000 Professional                      S                      S                    S
Windows 2000 Server                            S                      S                    S
Windows 2000 Advanced Server                   S                      S                    S
Windows XP Professional Edition                S                      S                    S
Windows XP Professional x64
                                               N                      S                    S
Edition
                                                                      S
Windows Vista Business                         N                  (Update                  S
                                                               11 or later) (*1)
Windows Server 2003, Standard
                                               S                      S                    S
Edition
Windows Server 2003 R2,
                                               S                      S                    S
Standard Edition
Windows Server 2003, Standard
                                               N                      S                    S
x64 Edition
Windows Server 2003 R2,
                                               N                      S                    S
Standard x64 Edition
Windows Server 2003, Enterprise
                                               S                      S                    S
Edition
Windows Server 2003 R2,
                                               S                      S                    S
Enterprise Edition
Windows Server 2003, Enterprise
                                               N                    S                 S
x64 Edition
Windows Server 2003 R2,
                                               N                    S                 S
Enterprise x64 Edition
                                                                                     S
Windows Server 2008 Standard                   N                    N            (Update
                                                                               4 or later) (*2)
                                                                                     S
Windows Server 2008 Enterprise                 N                    N            (Update
                                                                               4 or later) (*2)


      Combinations for which "S" is shown are only supported. Other combinations are not
*
      applicable.
*1: Windows Vista supports JRE 6 and JRE 5.0 Update 11 and later.
*2: Windows Server 2008 supports JRE 6 Update 4 and later.



[Ver 5.2]
■ Web browser
    - Microsoft Internet Explorer Version 6 or 7
■ JRE (Java Runtime Environment)
     One of the following JREs (32-bit version) is required:
        - 1.4.2_12 to 1.4.2_14
        - 5.0 Update8 to 12
        - 6 Update3 (*1)
     The following table shows JREs supported by each OS:


                                       JRE 1.4.2 (32 bit) JRE 5.0 (32 bit)    JRE 6 (32 bit)
OS                                     *1.4.2_12 to       *5.0 Update         *6 Update
                                       1.4.2_14           8 to 12             3
Windows 2000 Professional                      S                    S                 S
Windows 2000 Server                            S                    S                 S
Windows 2000 Advanced Server                   S                    S                 S
Windows XP Professional Edition                S                    S                 S
Windows XP Professional x64
                                               N                    S                 S
Edition
                                                                   S
Windows Vista Business                         N                (Update               S
                                                               11, 12) (*2)
Windows Server 2003, Standard
                                               S                    S                 S
Edition
Windows Server 2003 R2,
                                               S                    S                 S
Standard Edition
Windows Server 2003, Standard                  N                    S                 S
x64 Edition
Windows Server 2003 R2,
                                               N                    S                 S
Standard x64 Edition
Windows Server 2003, Enterprise
                                               S                    S                 S
Edition
Windows Server 2003 R2,
                                               S                    S                 S
Enterprise Edition
Windows Server 2003, Enterprise
                                               N                    S                 S
x64 Edition
Windows Server 2003 R2,
                                               N                    S                 S
Enterprise x64 Edition


      Combinations for which "S" is shown are only supported. Other combinations are not
*
      applicable.
*1: To use JRE 6, apply a support program to NEC Storage Manager (server). Apply the
    support program ISMS-ISM-05200009 (for D1/D3) or ISMS-ISM-05200012 (for D8).


*2: Windows Vista supports JRE 6 and JRE 5.0 Update 11 and later.



[Ver 5.1]
■ Web browser
    - Microsoft Internet Explorer Version 6 or 7
■JRE (Java Runtime Environment)
     One of the following JREs (32-bit version) is required:
        - 1.4.2_12 to 1.4.2_13
        - 5.0 Update 8 to 13
     The following table shows JREs supported by each OS:


                                                                           JRE 5.0 (32 bit)
                                                     JRE 1.4.2 (32 bit)
OS                                                                          *5.0 Update
                                                   *1.4.2_12 to 1.4.2_13
                                                                               8 to 13
Windows 2000 Professional                                   S                     S
Windows 2000 Server                                         S                     S
Windows 2000 Advanced Server                                S                     S
Windows XP Professional Edition                             S                     S
Windows XP Professional x64 Edition                         N                     S
                                                                                 S
Windows Vista Business                                      N                 (Update
                                                                            11 to 13) (*1)
Windows Server 2003, Standard Edition                       S                     S
Windows Server 2003 R2, Standard Edition                    S                     S
Windows Server 2003, Standard x64 Edition                   N                     S
       Windows Server 2003 R2, Standard x64
                                                               N                       S
       Edition
       Windows Server 2003, Enterprise Edition                 S                       S
       Windows Server 2003 R2, Enterprise Edition              S                       S
       Windows Server 2003, Enterprise x64
                                                               N                       S
       Edition
       Windows Server 2003 R2, Enterprise x64
                                                               N                       S
       Edition


           Combinations for which "S" is shown are only supported. Other combinations are not
       *
           applicable.
       *1: Windows Vista supports JRE 5.0 Update 11 to 12.
Q1-4 Are there any problems with different versions of JRE that have been installed in a machine
     where the iSM Client is used?
   A When different versions of JRE have been installed, the latest version of JRE is enabled. No
     problem will occur if the enabled JRE is supported by the iSM Client.
     If not, reconfigure the environment to enable the JRE supported by the iSM Client or use another
     machine for iSM Client operation.
Q1-5 Does any setting need to be made on the web browser for using the iSM Client?
   A       Make the following settings on the web browser before using the iSM Client:
            ■ Follow the procedure below to add the iSM server to connect to Trusted sites:
               (1) On the Control Panel, click Internet Option and then the Security tab.
               (2) Click Trusted sites and then click Sites.
                     * When using Internet Explorer 7 or 8 on Windows Vista or later or Windows
                       Server 2008 or later, clear the Enabled Protected Mode check box.
               (3) In the Add this website to the zone box, type the URL of the iSM server to
                    connect (ex. http://[ IP address (host name) of the iSM server to connect]) and
                    then click Add.
                     * Clear the Require server verification (https:) for all sites in this zone check
                       box.
               (4) Click OK and close the window.
            ■ Follow the procedure below to specify a security level for Trusted sites:
               (1) On the Control Panel, click Internet Option and then the Security tab.
               (2) Click Trusted sites and then click Custom Level.
               (3) Click ActiveX Controls and Plug-ins, and under Run ActiveX Controls and
                   plugins, click Enable.
               (4) Click OK and close the window.
Q1-6 When should I install the iSM Client (Win GUI) to use the iSM Client (Web GUI)?
   A You do not need to install the iSM Client (Win GUI) preliminarily.
     After you connect to the iSM server from an web browser, a message informing you that the iSM
     Client (Win GUI) has not been installed in your machine will appear, or the iSM Client (Win GUI)
     installation window will appear if an old version of iSM Client (Win GUI) has been installed. On the
     window, click Execute to launch the installer, or click Save to download the installation program
     to the PC and then execute the installer.
     You can resume using the iSM Client (Web GUI) after the installation.
Q1-7 Can I apply the settings of iSM Client (Web GUI) to a machine in which the iSM Client (Win GUI)
     has been used?
    A The iSM Client (Web GUI) and the iSM Client (Win GUI) cannot share the settings. Make settings
      individually for them.
 Q1-8 Are there any notes on upgrading iSM Client?
    A Upgrade the iSM Server before upgrading the iSM Client (Web GUI), following the
      procedure below.
        1. Terminate all iSM Clients (Web GUI).
        2. Stop and then upgrade the iSM Server.
        3. Restart the iSM Server and then connect the iSM Client (Web GUI).
        4. Log in the iSM Server. Then click the Run button to launch the installer or click the
           Save button to download and run the installer program on the installation window for
           the iSM Client (Win GUI). This operation upgrades the iSM Client.


       [Notes]
         - The iSM Client need not be upgraded preliminarily.
           After upgrading the iSM Server, connect the iSM Client to the iSM Server for upgrade.
 Q1-9 I connected to the iSM server using the iSM Client (Web GUI), and then downloaded the installer
      of the iSM Client (Win GUI) and executed it.
      The installation completed, but the shortcut icon was not created on the desktop. Why it was not
      created?
    A When the iSM Client (Win GUI) is installed using the installer that was downloaded from the iSM
      Client (Web GUI), the shortcut icon for starting iSM Client is not created on the start menu and
      the desktop.
      Start the web browser and then connect to the iSM server to launch the iSM Client (Web GUI).
Q1-10 Is the shortcut icon for starting iSM Client automatically created?
    A The shortcut icon for starting the iSM Client (Web GUI) is not automatically created on the start
      menu and the desktop.
      Bookmark the URL of the iSM server to be connected manually using a browser function.
Q1-11 Are there any notes on using the iSM Client in a machine where JRE 6 update 10 or later is
      installed?
    A To use JRE 6 update 10 or later, disable next-generation Java Plug-in after installing the JRE.
      Check again if next-generation Java Plug-in is disabled after reinstalling or upgrading JRE.

      To disable next-generation Java Plug-in, select the Java icon under Control Panel and do the
      following under the control panel of Java:
      Click the Advanced tab, click Java Plug-in and clear the Enable the next-generation Java
      Plug-in check box.
 Q2-1 Which user privilege do I need for using the iSM Client?
    A Only a system administrator can operate the iSM Client.
 Q2-2 When the iSM Client started, the Java icon stayed on the web browser for a while and then the
      connection window appeared. Why the connection window did not appear right after the iSM
      Client started?
    A While the Java icon is shown, the files necessary for iSM Client operations are downloaded from
      the iSM server. This process is necessary for starting the iSM Client. Wait until the connection
      window appears.
      Do not perform the following while the Java icon is shown:
          - Deleting Java temporary files (by clicking Control Panel, Java, and then clicking the
            Basic tab and then Delete Files under Java Control Panel.
          - Moving to another page
             To perform one of the operations above, restart the web browser or open another
              web browser window.
 Q2-3 When I started the iSM Client, the Warning Security window appeared. What should I do?
    A Confirm that the issuer shown on the Warning Security window is NEC Corporation and click the
      Run button.
 Q2-4 When I started the iSM Client, the Windows Security Alert window showing that Internet Explorer
      functions were blocked appeared. What should I do?
    A The Windows Security Alert window may appear when the firewall is enabled.
      Cancel the firewall blocking on the window for which the alert window appeared or preliminarily
      cancel the firewall blocking for Internet Explorer on the firewall setting window.
 Q2-5 Have messages shown on the message display area in the iSM Client been saved?
    A To save the messages in a file, select Save Messages to a Log File check box on the
      Environment Setting that can be accessed from the log-in window (default is selected).
 Q2-6 Where is the file including saved messages located?
    A The file is stored in the following folder:
           <System drive>:\Documents and Settings\<Login user name>\Application
           Data\NEC\iSMClient\<Destination IP address>_<Port number>\LOG
             * On Windows Vista or later or Windows Server 2008 or later, <System
               drive>:\User\<Login user name>\AppData\Roaming\NEC\iSMClient\<Destination
               IP address>_<Port number>\LOG (with hidden attribute)
 Q2-7 Which format does the file including saved messages have?
    A Text format.
 Q2-8 Can I view the file including saved message?
    A You can view the file by using an editor.
 Q2-9 How much is the maximum size of the file to which messages shown on the message display
      area in the iSM Client are reported?
    A The upper limit of one log file (iSM.log) is 1MB. When the size of the messages reported to the file
      exceeds 1MB, the file name is changed to OLDiSM.log and a new iSM.log file is created. The
      OLDiSM.log and the iSM.log files are used alternately so that the file size reaches 2MB at the
      maximum.
Q2-10 To where and how much logs does the iSM Client report?
    A Not only the file for saving messages but the log file for internal traces is reported.
       [Reported to]
           <System drive>:\Documents and Settings\<Login user name>\Application
           Data\NEC\iSMClient\<Destination IP address>_<Port number>\TMP
             * On Windows Vista or later or Windows Server 2008 or later, <System
               drive>:\User\<Login user name>\AppData\Roaming\NEC\iSMClient\<Destination
               IP address>_<Port number>\TMP (with hidden attribute)
       [Log size]
           The maximum is approximately 20MB (it may be smaller depending on the functions
           used).
           The log file reported by the iSM Client is overwritten as necessary, keeping within the
           maximum size. The user need not adjust the file size.
Q2-11 I want to know the meanings of the messages shown on the message display area in the iSM
      Client.
    A Refer to the message list in the iSM Client Help or IS010 Messages Handbook that comes with
      iSM.
Q2-12 Why I could not change a nickname or control monitoring (could not select the item on menus)?
    A The user level of the user who logged in is under 3. Log in again as a user on a user level 3 or
      more.
      When you log in as a partition user, you cannot make settings related with the whole system such
      as monitoring control and nickname changes, even if you are on the user level 3. To make such
      settings, log in as a storage user (on user level 3).
Q2-13 What should I do to use NEC Storage DynamicDataReplication, NEC Storage
      RemoteDataReplication, NEC Storage PerformanceMonitor , NEC Storage
      PerformanceOptimizer, NEC Storage DynamicSnapVolume, NEC Storage VolumeProtect in the
      iSM Client?
    A If you cannot use those functions in spite of having purchased a product such as NEC Storage
      DynamicDataReplication, NEC Storage RemoteDataReplication, NEC Storage
      PerformanceMonitor , NEC Storage PerformanceOptimizer, NEC Storage DynamicSnapVolume,
      NEC Storage VolumeProtect, and having canceled the lock for the product, check the following:
         - To perform copies for Replication, set thresholds for Performance Monitoring, or
           perform the Snapshot or the Data Retention Management setting, a user on a user
           level 2 or more must be specified when the iSM Client starts.
Q2-14 Can I use the iSM Client remotely using the terminal service client or the remote desktop?
    A [Ver 5.3 or later]
          Can be used remotely using the terminal service client or the remote desktop.
       [Ver 5.2 or earlier]
          Cannot be used using the terminal service client or the remote desktop.
          Start the iSM Client directly from a machine that can be connected to the iSM server.
Q2-15 I have used the iSM Client in a machine where JRE 1.4.2 is installed. When I moved the cursor to
      an entry field with a spin button using a shortcut key, I could not make any entry. Why did it
      happen?
    A The problem you asked may happen when JRE 1.4.2 is used. Continue to press the TAB key to
      reactivate the entry function.
Q2-16 When I used the iSM Client in a machine where JRE 5.0 is installed, the keyboard did not work on
      some windows (a focus disappeared). Why did it happen?
    A When JRE 5.0 Update 14 or later is used, this problem you asked may happen on some windows
      accessed from the iSM Client main window.
      Upgrading JRE to the version 6 can prevent this problem.
      If it is difficult to upgrade JRE, use the mouse for operations on the windows on which the
      problem may happen.
Q2-17 I have used the iSM Client through Internet Explorer 7 (or 8).
      When I attempted to view the help menu of the iSM Client by pressing the F1 key, the help menu
      of Internet Explorer appeared. Why did it happen?
    A The specification of Internet Explorer causes this action. Use the shortcut key shown on the menu
      bar or the mouse to view the help menu.
Q2-18 The lines connecting items did not appear in an iSM Client tree. Why they did not appear?
    A Depending on the combination of JRE and OS that you use, lines that connect items in a tree
      may not appear in the Configuration display area on the main window, etc. This does not affect
      the system operation.
Q2-19 While a window (or dialog) was shown in the iSM Client, another dialog appeared. However, I
      could not manipulate the second dialog
      . What should I do?
    A If another window appears while a particular window or dialog (*) is shown, you can operate only
      the window or dialog that appeared first, though the second dialog appears in front of the first
      window or dialog.
        (*) The "particular" windows and dialogs are:
              - "Choose Details" window
             - "CSV Output of Information List" window
             - "The diskarray list that TimeLimt licenses will be expired or have expired" window
             - [01625] (iSM Client (Win GUI) installation) dialog
             - "Save" dialog accessed from the "Log Collection" window
Q2-20 Repeating the same operation in the iSM Client displayed more than one same dialog. Why did it
      happen?
    A In the iSM Client (V5.1/V5.2), repeating the same operation on the main window may display
      more than one same dialog. This does not affect the iSM Client operations. Check the message
      on the dialog and close the dialog.
Q2-21 I could not specify a name for the replication port. Why I could not specify the name?
    A A user can specify a name only for the host port. A replication port name cannot be specified.
Q2-22 Can I connect to the iSM server from a web browser, via the proxy server?
    A Specify not to use the proxy server for connection to the iSM server.
      If it is required to pass through the proxy server because of the network configuration, change the
      setting as follows:
         ■ Follow the procedure below to change the web browser destination port number in the
           iSM server environment setting.
           (1) In the iSM server environment setting, change the port number to which a web
               browser is connected to 443.
                 - In the UNIX version, change the port number specified for web_port_no
                   (default is 8070) to 443 under the web section in the environment definition file.
                 - In the Windows version, change the port number for the Web GUI of the iSM
                   Client that permits connection (default is 8070) to 443 on the Server/Client
                   window under the environment setting.
           (2) Restart the iSM server.
           (3) When connecting from a web browser to the iSM server, specify the port number
               443 for the URL.

      The port number 443 is also used for HTTPS. To perform operations that use the HTTPS port
      number 443, use a machine different from the one for iSM operations.

         * When JRE 1.4.2_12 is used in the iSM Client, connection via the proxy server is not made
           normally due to JRE.
           Upgrade JRE to 1.4.2_13 or later or JRE 5.0 or later that are supported by the iSM Client.
           The JRE versions supported by NEC Storage Manager when it is shipped may be upgraded.


           JRE problems:
              URL for reference [English]
           http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6226610
Q2-23 On the Connected Host list window, "-" appeared as the logical disk status. Why did it happen?
    A "-" appears when the relation between the connected host and the logical disk created on
      the disk array you are operating is not clear.
       The relation is recognized as unclear when:


        - The logical disk created on the disk array you are operating is not assigned
         (including when the access control has not started).
          [Action to take]
              Create an LD set for the connected host and assign a logical disk to display a logical
              disk status value.


        - The information about the connected host does not include HBA information (WWNN and
          WWPN), or includes incorrect HBA information (WWNN and WWPN).
          [Action to take]
              Register correct HBA information (WWNN and WWPN) as the host information with
              the iSM server to display a logical disk status value.
              To obtain the host information including the HBA information, run the collecting host
              information function on the host to which you connect.
Q2-24 Port and Cache Segment are indicated only for some resource disk arrays displayed in the
      Configuration display area.
     A Port and Cache Segment are indicated only for disk arrays for which NEC Storage
       VirtualStoragePartitioning has been purchased.
Q2-25 Under which condition tabs are shown in the Configuration display area?
     A When a disk array for which NEC Storage VirtualStoragePartitioning has been purchased is
       monitored, tabs are shown in the Configuration display area.
       [When a storage user logged in]
           The Diskarray and Partition tabs are shown.
           Under the Diskarray tab, all the resources of the device are shown as in the versions
           not supporting NEC Storage VirtualStoragePartitioning.
           Under the Partition tab, the specified partition information is shown for disk arrays for
           which NEC Storage VirtualStoragePartitioning has been purchased.
       [When a partition user logged in]
           Only the Partition tab is shown.
           Only the information about the partitions to be managed by the user who logged in is
           shown.


       When NEC Storage VirtualStoragePartitioning has not been purchased for any disk arrays,
       all the resources of the device are shown without tabs.
Q2-26 When Port is selected in the Configuration display area, which kinds of port are shown in the
      Information list display area for a disk array for which NEC Storage VirtualStoragePartitioning has
      been purchased?
     A Only host ports are shown. Replication ports are not.
Q2-27 In a partition port list under the Partition tab, ports that were not assigned at the partition setting
      were shown. Why did it happen?
     A Under the Partition tab, resources that were not assigned at the partition setting but are shared
       in the whole disk array are shown. A port set to WWN mode is shown in the list of each partition
       because the port is shared in the whole disk array.
Q2-28 Controllers and enclosures were indicated for each partition under the Partition tab, though they
      were not assigned at the partition setting. Why they were indicated?
     A Under the Partition tab, resources that were not assigned at the partition setting but are shared
       in the whole disk array are shown. Controller components and enclosure components are
       indicated for each partition because these components are shared in the whole disk array.
Q2-29 I have used VirtualStoragePartitioning.
      When I select a cache segment under the Partition tab, which kind of logical disk is shown in the
      Information list display area?
     A Logical disks that use the cache segment you selected (that belong to the partition to which the
      cache segment you selected is assigned) are shown.
      For the default segment used by multiple partitions, logical disks that belong to one of the
      partitions and that are managed by the user who logged in are shown.
Q2-30 Why does the disk-array monitoring temporarily stop?
    A Monitoring the whole disk array temporarily stops during one of the following operations.
       While the operation is ongoing, you cannot use the iSM Client to refer to the latest
       information or to make settings.
         - When making Configuration Setting or Quick Configuration for a disk array
         - When setting a partition (VSPAR) (activating the partition setting wizard)
         - When starting the cache partitioning setting
         - When a partition user makes partition Configuration Setting
Q2-31 I could not create a storage user, or edit or delete the created storage users shown on the User
      Setting window. Why I could not do these operations?
    A Storage users can be created, edited, and deleted only in the iSM server. On the User Setting
      window, partition users can be created, edited, and deleted but storage users can only be viewed.
Q2-32 I have used the iSM Client on Windows Vista (or later) or Windows Server 2008 (or later).
      After I executed CSV Output of Information List with a folder under C:\Program Files specified
      as the CSV-file output destination, the CSV file were not created under the folder. Why did it
      happen?
    A Windows Vista and later or Windows Server 2008 and later support the User Account Control
      (UAC) function. Due to this function, writing into <System drive>:\Program Files or <System
      drive>:\Windows is not allowed even for a user who logged in OS using an administrator account
      and executed the iSM Client.
      When CSV Output of Information List is executed with a folder under one of the above folders
      specified as the output destination, the OS automatically changes the output destination (*) and
      the process ends normally.
      When output to a folder under the above folder is required, right-click an icon or a menu item to
      start a web browser, click Run as administrator, and then run the web browser and the iSM
      Client. Using this way allows you to write into the above folders.


       (*)The output destination folders will be changed to:
           - When <System drive>:\Program Files is specified
             <System drive>:\User\ <Login user name> \AppData\Local\VirtualStore\Program
              Files
           - When <System drive>:\Windows is specified
             <System drive>:\User\ <Login user name> \AppData\Local\VirtualStore\Windows
Q2-33 Are there any notes on using the iSM Client in a machine where security software(*) is installed?
      (*) Software to prevent information leakage, to block unauthorized accesses or computer viruses,
      etc.
    A The iSM Client (Web GUI) creates a folder and a file under the following folders for storing
      setting files and log files:
        ■ <System drive>:\Documents and Settings\<Login user name>\Application Data
              *   On Windows Vista or later or Windows Server 2008 or later
                  <System drive>:\User\<Login user name> \AppData\Roaming
        ■ iSM Client (Win GUI) installation folder
              *   The default installation folder is:
                  <System drive>:\Program Files\NEC\iSMClient
      If security software restricts the creation of these folders and files, the iSM Client will not work
      normally. Change the software setting to prevent the restriction.
Q3-1 The Replication/Performance Monitoring/Performance Optimization/Snapshot/Volume Protect
     Management window did not appear. What should I do?
   A Have you purchased the product?
     Access the corresponding Disk Array Subsystem detail information window from the iSM Client
     main window to check the purchased products.
Q3-2 Connection from a client failed. What is the possible cause?
   A The following may have caused the failure. Check them as well as the shown dialog message
     and take an appropriate action.
      [Cause related to incorrect setting]
        - Incorrect user name
        - Incorrect password
        - The URL includes an incorrect IP address of iSM server or an incorrect host name.
        - The URL includes an incorrect the web browser destination port number.
        - The destination iSM server is not specified as a trusted site, or Run ActiveX Controls
          and plugins is not enabled in the security setting.
          [Action to take]
              Correct the incorrect item and connect to the iSM server again.


      [Cause related to the iSM server status]
        - The iSM server has not completely started.
        - The iSM server has not started.
        - The iSM server is terminating.
        - [Permitted Connection Type of Storage Manager Client] is not set to Web GUI in the
          iSM server environment setting.
          [Action to take]
              Check if the iSM server has started and the iSM server settings are correct and
              connect the iSM server again.


      [Cause related to the network environment]
        - LAN is not used to connect the server running the iSM Server and the server (PC)
          running the iSM Client.
          [Action to take]
              Connect the server running the iSM Server and the server (PC) running the iSM
              Client using LAN and make connection again.


      [Cause related to user setting]
        - Another client is creating, editing, or deleting a partition user (on the User setting
          window).
        - Another client is adding or deleting a partition user for a partition (on the partition
          setting wizard).
          [Action to take]
              You may not connect to the iSM server from the iSM Client temporarily while the
              above partition user setting is ongoing. Wait for a while and then make connection
              again.
      [Other cause]
          - A non-administrative OS user has started the iSM Client.
           [Action to take]
               Start the iSM Client as an administrative OS user.


          - (Only on Windows Vista) If a value has been changed in the environment variable
            "USERPROFILE" or "PUBLIC", the iSM Client may not be used. To check values in
            these environment variables, start the command prompt and execute "SET
            USERPROFILE" or "SET PUBLIC".
Q3-3 I have used the iSM Client in which JRE 6 has been installed. I could not change the name of a
     folder that I have created using the folder creation button on the storage folder selection window
     for a file. Why did it happen?
   A The problem you asked may occur when JRE 6 update 7 or earlier is used.
     If this is the case, use a created folder or do one of the following:
      -   Create a folder having the default name by using the folder creation button and change the
          folder name on Windows Explorer after the file output is complete.
      -   Create a folder having the default name by using the folder creation button and close the
          window. Then reopen the selection window and change the folder name.
Q3-4 When I attempted to delete the connected host information, the "Failed in deleting host
     information(17)." dialog appeared. Why did it appear?
   A Another client may have deleted the host information at the same time. The host information has
     already been deleted if the client succeeded the deletion. Update the list window to check the
     latest information.
Q3-5 When I changed the desktop theme between the Windows Classics, Windows XP, and
     Windows Vista styles while the iSM Client (Web GUI) is active, an iSM Client (Web GUI) window
     did not work normally. Why did it happen?
   A It occurs due to the specification of Java Applet used by the iSM Client (Web GUI).
     Be sure to restart the web browser (iSM Client (Web GUI)) after changing the desktop theme.
Q3-6 When the iSM server is connected, nothing appeared on the web browser window and Done was
     only displayed in the status bar.
     How can I solve this problem?
   A The possible causes are the following:
          - JRE has not been installed.
           Check if JRE has been installed in the machine. If JRE has not been installed, install it
           following the installation guide.
          - Security settings have not been made for the web browser.
           Specify the URL of the connected iSM server as Trusted sites on the web browser.
           Also click ActiveX Controls and Plug-ins and then set Run ActiveX Controls
           plugins to Enable on the security setting window for trusted sites.
           For more information, see the installation guide.
          - Heavy load on network
           When the iSM Client (Web GUI) starts, it downloads the files necessary for operation
           from the iSM server. The problem may occur if it takes time to download due to the
           network status. If it occurs, wait for several minutes until the download is complete.
Q3-7 When I run installation of the iSM Client (Win GUI) through the iSM Client (Web GUI), the dialog
     "Error occurred during download(197). Please make sure the connection is not via a proxy
     server." appeared. What should I do for this?
    A When the web browser uses the proxy server, bypass the proxy server to connect to the
      iSM server.
      To bypass the proxy server, specify both the host name and the IP address of the server to
      be connected as proxy exception for the web browser and JRE.
      Follow the procedure below to change the setting.
        1) On Control Panel, click Internet Options, click the Connections tab, and click LAN
           Settings to open the local area network setting window.
        2) If Use a proxy server for your LAN is selected, click Advanced to open the proxy
           setting window.
        3) Check if both the host name and the IP address of the server to be connected have
           been set in Don't Use Proxy For These Addresses correctly. If necessary, correct or
           add the host name and the IP address.
        4) Check the JRE proxy setting by following the procedure below.
            - JRE 1.4.2
             On Control Panel, click Java Plug-in, click the Proxy tab and check if Use browser
             settings is selected.
             If it is selected, no additional setting is required.
             If it is not selected and you cannot enable the setting, add both the host name and
             the IP address of the server to be connected to No Proxy Host.
            - JRE 6 or 5.0
             On Control Panel, click Java. On Network Settings, check if Use browser
             settings is selected.
             If it is selected, no additional setting is required.
             If it is not selected and you cannot enable the setting, click Advanced and add both
             the host name and the IP address of the server to be connected to Exceptions.
        5) After updating or adding the setting, terminate all the active web browsers. Then restart
           the web browser to reconnect to the iSM server.
 Q3-8 I have not used the AccessControl function for operation. When I collected the host information
      on the server to which storage logical disks have been assigned and registered the information
      with the iSM server, "-" appeared as Logical Disk Status in the list of hosts connected to the iSM
      Client. Why did it happen?
    A Logical Disk Status in the connected-host information shows the status of the logical disk
      explicitly related with the connected host (application server) (by using an LD set).
      Accordingly, Logical Disk Status appears in an environment where the AccessControl license
      has been canceled and LD sets have been set correctly.
 Q3-9 I have used iSM Client (Web GUI) V5.1.
      On the iSM Client menu, I found that the background color behind separator lines is different from
      colors behind other areas. Can I leave it as is?
    A This occurs when the iSM Client (Web GUI) V5.1 is used in a certain update version of JRE5.0.
      (Its occurrence in JRE 5.0 update 12 has been confirmed.)
      The system operation will not be affected if you leave it as is.
Q3-10 Though I changed the order of columns in the Information list display area, the order returned to
      the original after a while. Why did it happen?
    A If the order of columns is only changed on the Information list display area, the order will be kept
      temporarily and it may return to the original depending on the timing of a window update.
      To hold a changed order, click View on the menu and click Record Screen Information.
Q3-11 When I attempted to start the iSM Client, the message [00000] appeared and the start failed. Why
      did it fail?
    A You can start only one iSM Client to connect to one destination (multiple iSM Clients can be
      activated if they are connected to different destinations).
      Note that even if more than one user use the same machine with remote desktop, etc., only one
      iSM Client can be activated in the machine to connect to one destination.
Q3-12 When I attempted to start the iSM Client, the message [00008-04] appeared and the start failed.
      Why did it fail?
    A Check the machine environment according to the following possible causes:
       ■   A non-administrative user logged in OS.
           The administrative privilege (Administrators group) is required for logging in OS and starting
           the iSM Client.
       ■   (Internet Explorer 7 to 8) The protected mode is enabled.
           When the protected mode is enabled in Internet Explorer 7 to 8 (web browser), starting the
           iSM Client fails.
           Perform the following to disable the protected mode:
           (1) On Control Panel, click Internet Options and click the Security tab.
               *   Alternatively, on the Internet Explorer tool bar, click Tools, Internet Options, and
                   click the Security tab.
           (2) Clear the Enabled Protected Mode check box for the zone (trusted sites) in which the
               URL of the iSM server to be connected is specified.
           (3) Terminate all the active web browsers and restart the iSM Client (Web GUI).
       ■   The security policy for JRE has been changed.
           Installing other products may change the security policy for JRE, resulting in affecting the
           start of the iSM Client.
           For more information about actions to take, see the installation guide that comes with iSM or
           manual ("Client Start/Stop" in IS001/IS004).
       ■   The iSM Server and the iSM Client are running on the same machine (OS: Windows
           Server 2008 or later) where JRE 6 Update 10 to 13 has been installed. Also the loopback
           address ("localhost" or "127.0.0.1") is specified as the URL of the iSM server to be
           connected.
           In an environment as described above, the JRE specification may prevent the iSM Client
           from starting. Perform one of the following to solve the problem:
           -   Specify the IP address assigned to the machine you use as the URL of the iSM server
               to be connected.
           -   Right-click the icon or the menu item of Internet Explorer and click Run as
               administrator to start Internet Explorer.
               Alternatively, right-click the Internet Explorer shortcut icon, click Properties, click the
               Shortcut tab, click Advanced, and select the Run as administrator check box. Then
               start Internet Explorer.
Q3-13 Some button did not appear on the Storage Folder Selection window for a file. Why they did not
      appear?
    A When your machine is running on Windows Server 2008 R2 or Windows 7, this problem may
      occur due to Java behaviors.
      Use right-click menus, etc. instead of using those buttons.
Q3-14 When I clicked Run on the iSM Client (Win GUI) download window after connecting to the iSM
      server, nothing started. Why did it happen?
    A When your machine is running on Windows Vista or Windows Server 2008, this problem may
      occur due to Java behaviors. Perform one of the following to solve the problem:
       -   Right-click the Internet Explorer icon and click Run as administrator to start Internet
           Explorer.
           Alternatively, right-click the Internet Explorer shortcut icon, click Properties, click the
           Shortcut tab, click Advanced, and select the Run as administrator check box. Then start
           Internet Explorer.
       -   On the iSM Client (Win GUI) download window, click Save to download the iSM Client to
           any folder in the local machine. Then run the iSM Client program manually.
Q3-15 When I attempted to restart OS that has recognized an iSCSI device, the error message of event
      ID 1, event ID 5, event ID 70, or event ID 113 appeared in the event log. What should I do?
    A In a machine that connects to a target iSCSI device using iSCSI Software Initiator, one of the
      above error events may be logged periodically or when the machine is started. The system
      operation will not be affected if you ignore the message.
      For more information, see the Microsoft online support page:
      http://support.microsoft.com/kb/976072
Q3-16 When I used the iSM Client in a machine where JRE 6 update 10 or later has been installed, a
      window was suddenly frozen and no longer worked. Tell me about the cause and what I should
      do.
    A When JRE 6 update 10 or later is used and next-generation Java Plug-in is enabled, this
      problem may occur due to JRE behaviors.
      If this is the case, close the web browser and then reconnect to the iSM serer to resume the
      operation.
      To prevent this problem from occurring in JRE 6 update 10 or later, disable next-generation
      Java Plug-in after installing JRE.

      The procedure to disable next-generation Java Plug-in is the following:
      On Control Panel, click the Java icon. Then on the Java Control Panel, click the Advanced tab,
      click Java Plug-in, and clear the Enable the next-generation Java Plug-in check box.
Q3-17 When I used the iSM Client, the following message appeared. Tell me about the action I should
      take.
        [01086-02] Failed in acquiring information (Time-out)
    A When a heavy load is imposed on a machine running the iSM Server, a machine running the iSM
      Client, or the network between these machines, the [01086-02] message may appear.
      If a time-out error occurs in an iSM Client though it has no load problems and the information has
      been updated, restart the web browser (iSM Client).
 Q4-1 Tell me how to change the IP address of a machine in which the iSM Client is running.
    A Terminate the iSM Client before starting to change the IP address.
      No further actions are required for the iSM Client.
      When a firewall is installed between the iSM server and the iSM client, make settings to allow the
      changed IP address to pass through the firewall.
 Q4-2 Tell me how to transfer the iSM Client to another machine.
    A Transfer the iSM Client environment setting information from the current machine to a new
      machine by following the procedure below.
       (1) Terminate the iSM Client.


       (2) Backup the iSM Client environment setting information stored in the current machine.
           The information is stored in the following folder:
               <System drive>:\Documents and Settings\<Login user name>\Application
               Data\NEC\iSMClient\
                 * On Windows Vista or later or Windows Server 2008 or later, <System
                   drive>:\User\<Login user name>\AppData\Roaming\NEC\iSMClient (with
                   hidden attribute)
           Backup all the files stored in the folder above.


       (3) Restore the iSM Client environment setting information in the new machine.
                            Copy the old-machine environment information backed up in (2) to the folder having the
                            same name as the old machine in the new machine. The "login user name" part in the
                            folder name depends on the new-machine user.


                        (4) Check the iSM Client operations in the new machine.
                  Q4-3 Which files will be deleted and will not be deleted from the installation folder when the iSM Client
                       is uninstalled?
                     A Executable files, help files, shortcut icons on desktop, and start menu items will be deleted.
                       Setting files will not be deleted because they will be taken over at re-installation.
                       Delete the setting files manually only when you will not re-install the iSM Client or need not apply
                       the setting files to a new environment.
                  Q4-4 When upgrading a machine using the iSM Client to Windows Vista, do I need to perform any
                       operations in the iSM Client?
                     A While no operations are required for the iSM Client (Web GUI), some operations need to be
                       performed in the iSM Client (Win GUI).
                       For more information, see the iSM Client (Win GUI) FAQ.



Storage Management

iSM Client (Win GUI)
1. Installation
  Q1-1 Which user privilege do I need for installing the iSM Client?
  Q1-2 How much disk space do I need for using the iSM Client?
  Q1-3 How much memory do I need for using the iSM Client?
  Q1-4 When the iSM Client is upgraded, can the new version take over the environment settings?
  Q1-5 After re-installation of the iSM Client, other shortcut icons than default did not appear on the desktop. What
       should I do?
  Q1-6 In which folder the iSM Client will be installed?
  Q1-7 I connected to the iSM server using the iSM Client (Web GUI), and then downloaded the installer of the iSM
       Client (Win GUI) and executed it.
       The installation completed, but the shortcut icon was not created on the desktop. Why it was not created?
  Q1-8 Are there any notes on upgrading the iSM Client?


2. Operation
  Q2-1 Have messages shown on the message field in the iSM Client been saved?
  Q2-2 Where is the file including saved messages located?
  Q2-3 Which format does the file including saved messages have?
  Q2-4 Can I view the file including saved message?
  Q2-5 How much is the maximum size of the file to which messages shown on the message field in the iSM Client are
       reported?
  Q2-6 To where and how much logs does the iSM Client report?
  Q2-7 I want to know the meanings of the messages shown on the message field in the iSM Client.
  Q2-8 Why I could not change a nickname or control monitoring (could not select the item on menus)?
  Q2-9 What should I do to use perform NEC Storage DynamicDataReplication, NEC Storage RemoteDataReplication,
       NEC Storage PerformanceMonitor , NEC Storage PerformanceOptimizer, NEC Storage DynamicSnapVolume,
       NEC Storage VolumeProtect function in the iSM Client?
 Q2-10 Can I use the iSM Client remotely using the terminal service client or the remote desktop?
 Q2-11 When I started the iSM Client on Windows Vista or later or Windows Server 2008 or later, the "User Account
       Control" dialog appeared. What should I do?
 Q2-12 When I attempted to specify a port name, I could not specify a name for a replication port. Why did it happen?
 Q2-13 Are there any notes on using the iSM Client in a machine where security software(*) is installed?
       (*) Software to prevent information leakage, to block unauthorized accesses or computer viruses, etc.


3. Troubleshooting
  Q3-1 The Replication/Performance Monitoring/Performance Optimization/Snapshot/Volume Protect Magement
       window did not appear. What should I do?
  Q3-2 Connection from a client failed. What is the possible cause?
  Q3-3 Which user privilege is required for using the iSM Client?
  Q3-4 When I attempted to start the iSM Client, the iSM Client terminated with the error message "00006 Failed in
       acquiring the Client's IP address." The OS was Windows Server 2003 (without SP) and LAN cables were not
       connected. What caused the error?
  Q3-5 When I attempted to start the iSM Client, the message [00000] (or [00007-00]) appeared and the start failed.
       Why did it happen?
  Q3-6 I could not set the FTP service on Windows Vista SP1 in which the iSM Server was running for using file transfer
       in the iSM Client. What should I do?


4. Migration
  Q4-1 Tell me how to change the IP address of a PC in which the iSM Client is running.
  Q4-2 Tell me how to transfer the iSM Client to another PC.
  Q4-3 Which files will be deleted and will not be deleted from the installation folder when the iSM Client is uninstalled?
  Q4-4 When upgrading OS in a machine using the iSM Client to Windows Vista or later or Windows Server 2008 or
       later, do I need to perform any operations in the iSM Client?


  Q1-1 Which user privilege do I need for installing the iSM Client?
     A The necessary user privilege depends on the version.
           [Ver2.1 or later]
               Install as a system administrator.
           [Ver1.4/Ver1.5]
               Users are not restricted for installation on Windows 98.
               On Windows NT 4.0, Windows 2000, or Windows XP, install as a system
               administrator.
           [Ver1.3]
               Users are not restricted for installation on Windows 98.
               On Windows NT 4.0 or Windows 2000, install as a system administrator.
  Q1-2 How much disk space do I need for using the iSM Client?
     A It depends on the version as shown below.
                                                             Required disk size
        Version of NEC Storage Manager               For only basic         For basic +
                                                       functions        extended functions
        Ver 5.1 or later                                   51MB (51MB) or more
        Ver 4.3                                            38MB (38MB) or more
                                                            37MB (37MB) or more
                                                     * On Ver4.1 or later, the setup-type
        Ver 4.2/Ver 4.1
                                                     selection process is omitted and all
                                                      functions (conventional basic and
                                                      advanced) are installed.
                                               21MB (21MB) or       37MB (37MB) or
     Ver3.4/Ver3.3
                                                   more                 more
                                               21MB (21MB) or       34MB (34MB) or
     Ver3.2
                                                   more                 more
                                               19MB (19MB) or       31MB (31MB) or
     Ver3.1
                                                   more                 more
                                               14MB (14MB) or       25MB (25MB) or
     Ver2.2
                                                   more                 more
     Ver2.1                                      13MB or more        23MB or more
     Ver1.5/Ver1.4                               10MB or more        18MB or more
                                                                      8MB or more
     Ver1.3                                      6MB or more          (including for
                                                                     operation logs)
     * The values in parentheses are the disk sizes required for running the iSM Client
     on a 64-bit OS.
Q1-3 How much memory do I need for using the iSM Client?
   A It depends on the version as shown below.
       * Operating a window other than the main requires a memory size enough to
         operate both the window and the main window.
         A value in parentheses is the memory size required for operating the window
         on a 64-bit OS.


     Ver 6.1 or later
                                 21 (31) MB Performance                    16 (32) MB
     Main window
                                    or more Optimization window               or more
     Configuration Setting       6 (6) MB or Failure Information            5 (10) MB
     window                            more Gathering window                  or more
                                 13 (14) MB                                 8 (13) MB
     Replication window                     Snapshot window
                                    or more                                   or more
     Performance                 14 (15) MB Data Retention                  7 (12) MB
     Monitoring window              or more Management window                 or more
     Ver 5.2
                                 30 (70) MB Performance                    16 (32) MB
     Main window
                                    or more Optimization window               or more
     Configuration Setting       26 (46) MB Failure Information            10 (31) MB
     window                         or more Gathering window                  or more
                                 24 (52) MB                                12 (29) MB
     Replication window                     Snapshot window
                                    or more                                   or more
     Performance                 15 (35) MB Data Retention                 11 (28) MB
     Monitoring window              or more Management window                 or more
     Ver 5.1
                                 30 (70) MB Performance                    10 (31) MB
     Main window
                                    or more Optimization window               or more
Configuration Setting   25 (45) MB Failure Information    10 (31) MB
window                     or more Gathering window          or more
                        24 (52) MB                        12 (29) MB
Replication window                 Snapshot window
                           or more                           or more
Performance             15 (33) MB Data Retention         11 (21) MB
Monitoring window          or more Management window         or more
Ver 4.3
                        24 (70) MB Failure Information    10 (31) MB
Main window
                           or more Gathering window          or more
Configuration Setting   13 (42) MB                         8 (29) MB
                                   Snapshot window
window                     or more                           or more
                        22 (52) MB Data Retention          7 (21) MB
Replication window
                           or more Management window         or more
Performance             10 (32) MB Performance Analysis   10 (42) MB
Monitoring window          or more Support tool              or more
Performance              8 (32) MB
Optimization window        or more
Ver 4.2
                        23 (70) MB Performance             8 (15) MB
Main window
                           or more Optimization window       or more
Configuration Setting   13 (42) MB Failure Information    10 (28) MB
window                     or more Gathering window          or more
                        22 (51) MB                         8 (29) MB
Replication window                 Snapshot window
                           or more                           or more
Performance             10 (17) MB Performance Analysis   10 (20) MB
Monitoring window          or more Support tool              or more
Ver 4.1
                        23 (70) MB Performance             8 (15) MB
Main window
                           or more Optimization window       or more
Configuration Setting   13 (42) MB Failure Information    10 (28) MB
window                     or more Gathering window          or more
                        22 (48) MB                         8 (29) MB
Replication window                 Snapshot window
                           or more                           or more
Performance             10 (17) MB Performance Analysis   10 (20) MB
Monitoring window          or more Support tool              or more
Ver 3.3/3.4
                        21 (41) MB Performance             7 (15) MB
Main window
                           or more Optimization window       or more
Configuration Setting   13 (22) MB Failure Information    10 (16) MB
window                     or more Gathering window          or more
                        22 (29) MB                         7 (15) MB
Replication window                 Snapshot window
                           or more                           or more
Performance              9 (17) MB Performance Analysis    9 (18) MB
Monitoring window          or more Support tool              or more
Ver 3.2
                           21 (41) MB Performance                 7 (15) MB
Main window
                              or more Optimization window           or more
Configuration Setting      13 (22) MB Failure Information         9 (16) MB
window                        or more Gathering window              or more
                           22 (29) MB                             7 (15) MB
Replication window                    Snapshot window
                              or more                               or more
Performance                 9 (17) MB Performance Analysis        9 (18) MB
Monitoring window             or more Support tool                  or more
Ver 3.1
                           21 (41) MB Performance                 7 (15) MB
Main window
                              or more Optimization window           or more
Configuration Setting      13 (23) MB Failure Information        10 (17) MB
window                        or more Gathering window              or more
                           16 (29) MB Performance Analysis        9 (18) MB
Replication window
                              or more Support tool                  or more
Performance                 9 (17) MB
Monitoring window             or more
Ver 2.2
                           20 (37) MB Performance                 9 (16) MB
Main window
                              or more Monitoring window             or more
Configuration Setting      12 (22) MB Performance                 7 (15) MB
window                        or more Optimization window           or more
                           17 (25) MB Performance Analysis        8 (16) MB
Replication window
                              or more Support tool                  or more
Ver 2.1.022
                           20 (37) MB Performance                 9 (16) MB
Main window
                              or more Monitoring window             or more
Configuration Setting       7 (17) MB Performance                 7 (15) MB
window                        or more Optimization window           or more
                           16 (24) MB Performance Analysis        8(16) MB
Replication window
                              or more Support tool                 or more
Ver 2.1.006
                                        Performance
Main window             19 MB or more                         13 MB or more
                                        Monitoring window
Configuration Setting                   Performance
                         7 MB or more                          6 MB or more
window                                  Optimization window
Replication window      14 MB or more
Ver 1.5
                                        Performance
Main window             16 MB or more                         13 MB or more
                                        Monitoring window
Configuration Setting                   Performance
                         6 MB or more                          6 MB or more
window                                  Optimization window
      Replication window         9 MB or more
      Ver 1.4
                                                 Performance
      Main window               16 MB or more                             13 MB or more
                                                 Monitoring window
      Configuration Setting                      Performance
                                 6 MB or more                               7 MB or more
      window                                     Optimization window
      Replication window         9 MB or more
      Ver 1.3
      Main window               12 MB or more Replication window            9 MB or more
      Configuration Setting                      Performance
                                 6 MB or more                             13 MB or more
      window                                     Monitoring window
Q1-4 When the iSM Client is upgraded, can the new version take over the environment
     settings?
   A The iSM Client upgrade procedure is; uninstall the iSM Client and then install the new
     version of iSM Client.
     However, the environment setting files, the log files, etc. are not deleted by the
     uninstallation. To apply the old-version settings to the new version, install the
     new-version program into the folder where the old version has been installed.
            * V5.1 or later can be overwritten with the new version (uninstalling the old
              version is not required).
              Overwriting the old version installs the new version into the same folder as the
              old version, applying the old environment settings to the new version.
      When you want to install the iSM Client into a different folder from the one where the
      old version has been installed, follow the procedure below to apply the old
      environment settings to the new version.
       1. Uninstall the old version of iSM Client, and then install the new version.
       2. Copy all the folders and files under the folder where the old version has been
          installed (the default is; <System drive>:\Program Files\NEC\iSMClient) to the
          folder where the new version has been installed.
          Do not make environment settings in the new version before copying those files.
       3. Start the iSM Client, check the settings the new version has taken over on the
          Environment Setting window, and correct them if necessary.
        * When the "Confirm the installer's information Record" dialog appears during
          uninstallation of Ver 4.2 or later, select Yes. Then folders and files are
          automatically copied as described in the step 2 above (manual copy is not
          required).
Q1-5 After re-installation of the iSM Client, other shortcut icons than default did not appear
     on the desktop. What should I do?
   A Recreate the shortcut icons by following the procedure below.
     The recreation is not required for Ver 4.2 or later because it restores shortcut
     icons after re-installation.
       1. By using Explorer, open the folder where the iSM Client has been installed to
          display iSMCL.EXE.
       2. Right-click the iSMCL.EXE icon, then click Create Shortcut.
       3. Right-click the shortcut icon created in the folder and click Properties to
          display the Properties window.
       4. Select the Shortcut tab on the Properties window.
       5. Type an en space and the name of the folder in which the information on the
          target is stored after the double quote closing the iSMCL.EXE file name
          shown in Target.
          Example: "C:\Program Files\NEC\iSMClient\iSMCL.exe" SG1
          The folder that contains the target information is located under the folder in
          which the iSM Client has been installed. Access iSMmain.ini (IP of the target)
          or iSMstat.ini (name of the target) to check the folder name to specify.
       6. Select the General tab.
       7. Type the shortcut name in the field on the right of the icon as follows:
               iSM Client <Target name>
          The target name consists of the "[SERVER]" section in iSMstat.ini and the
          "NAME" parameter.
          Example: The target name is "SG1" (NAME=SG1).
             iSM Client SG1
       8. Click OK and close the Properties window.
       9. To place an icon on the desktop, copy or move an icon created in the steps
          above to the folder "\Documents and Settings\All Users\Desktop" in the
          system drive.
      10. To create a menu item, copy or move an icon created in the steps 1 to 8
          above to "\Documents and Settings\All Users\Start Menu\Programs\iSM
          Client" (default) in the system drive.


      The iSM Client help (topic "Start and Stop") also describes the above procedure.
Q1-6 In which folder the iSM Client will be installed?
   A The following are the default folders in which the iSM Client will be installed. You
     can install the iSM Client in another folder.
          32-bit OS: [System drive]:\Program Files\NEC\iSMClient
          64-bit OS: [System drive]:\Program Files (x86)\NEC\iSMClient


      If the iSM Client V4.2 or later had been installed and the installation information
      was saved when the iSM Client was uninstalled, the folder that contains the
      saved information will be shown as default.
Q1-7 I connected to the iSM server using the iSM Client (Web GUI), and then downloaded
     the installer of the iSM Client (Win GUI) and executed it.
     The installation completed, but the shortcut icon was not created on the desktop. Why
     it was not created?
   A When the iSM Client (Win GUI) is installed using the installer that was downloaded
     from the iSM Client (Web GUI), the shortcut icon for starting iSM Client is not created
     on the start menu and the desktop. Start the web browser and then connect to the iSM
     server to launch the iSM Client (Web GUI).
     If a previous version of the iSM Client (Win GUI) has been installed, the iSM Client
     (Win GUI) start shortcut will be created on the start menu and the desktop. However,
     you cannot start the iSM Client (Web GUI) from this shortcut icon. Delete the icon if not
     necessary.
Q1-8 Are there any notes on upgrading the iSM Client?
   A Upgrade iSM Client (Win GUI) and the iSM Server together to the same version.
     Follow the upgrade procedure below.
       1. Terminate all the iSM Clients (Win GUI).
      2. Uninstall the iSM Client (Win GUI) and then install a new version of the iSM
         Client (Win GUI). Use the installer stored in the CD of NEC Storage Manager.
               * V5.1 or later can be overwritten with the new version (uninstalling the old
                 version is not required).
      3. Stop the iSM Server and upgrade it. This upgrade can be performed while the
         iSM Client (Win GUI) is upgraded.
      4. Restart the iSM Server and connect the iSM Client (Win GUI).


     [Notes]
       - To use the iSM Client (Web GUI) or use the iSM Client (Web GUI) after
         upgrading iSM Client (Win GUI), follow not the above procedure but the
         procedure described in the iSM Client (Web GUI) FAQ.
       - When changing the folder in which the iSM Client (Win GUI) will be installed,
         you need to transfer the environment setting information. See Q1-4.
       - For the iSM Server Ver1.3 or earlier, be sure to upgrade the iSM Server and
         the iSM Client (Win GUI) together.
       - When the iSM Server is Ver1.4 or later and the iSM Server and the iSM Client
         (Win GUI) cannot be upgraded together, upgrade the iSM Client (Win GUI)
         before the iSM Server. The functions supported by the version of the iSM
         Server are available for the upgrade.
Q2-1 Have messages shown on the message display area in the iSM Client been saved?
   A To save messages in a file, select the Save Messages to a Log File check box on the
     Environment Setting window (default is selected).
Q2-2 Where is the file including saved messages located?
   A The file is stored in the \LOG folder under the folder in which the iSM Client has been
     installed.
Q2-3 Which format does the file including saved messages have?
   A Text format.
Q2-4 Can I view the file including saved message?
   A You can view the file by using an editor.
Q2-5 How much is the maximum size of the file to which messages shown on the message
     display area in the iSM Client are reported?
   A The upper limit of one log file (iSM.log) is 1MB. When the size of the messages
     reported to the file exceeds 1MB, the file name is changed to OLDiSM.log and a new
     iSM.log file is created. The OLDiSM.log and the iSM.log files are used alternately so
     that the file size reaches 2MB at the maximum.
Q2-6 To where and how much logs does the iSM Client report?
   A Not only the file for saving messages but the log file for internal traces is reported.
     [Reported to]
         \TMP folder under the folder in which the iSM Client has been installed (fixed).
         When multiple connection targets have been created, the log file is reported
         under each target (\SGn folder).
     [Log size]
         The maximum is approximately 20MB (it may be smaller depending on the
         functions used).
         The log file reported by the iSM Client is overwritten as necessary, keeping
         within the maximum size. The user need not adjust the file size.
Q2-7 I want to know the meanings of the messages shown on the message display area in
     the iSM Client.
    A Refer to the message list in the iSM Client Help or IS010 Messages Handbook that
      comes with iSM.
 Q2-8 Why I could not change a nickname or control monitoring (could not select the item on
      menus)?
    A The user level of the user who logged in is under 3. Log in again as a user on a user
      level 3 or more.
 Q2-9 What should I do to use perform NEC Storage DynamicDataReplication, NEC Storage
      RemoteDataReplication, NEC Storage PerformanceMonitor, NEC Storage
      PerformanceOptimizer, NEC Storage DynamicSnapVolume, NEC Storage
      VolumeProtect function in the iSM Client?
    A If you cannot use those functions in spite of having purchased a product such as NEC
      Storage DynamicDataReplication, NEC Storage RemoteDataReplication, NEC
      Storage PerformanceMonitor, NEC Storage PerformanceOptimizer, NEC Storage
      DynamicSnapVolume, NEC Storage VolumeProtect, and having canceled the lock for
      the product, check the following:
       1. To perform copies for Replication, set thresholds for Performance Monitoring,
          or perform the Snapshot or the Data Retention Management setting, a user
          on a user level 2 or more must be specified when the iSM Client starts.
       2. To use Replication, Performance Monitoring, Performance Optimization, or
          Snapshot, select "basic+extended" when installing the iSM Client. The iSM
          Client tool bar on which icons of Replication, Performance Monitoring,
          Performance Optimization, and Snapshot do not appear shows that only
          "basic function" has been installed. In such a case, uninstall the iSM Client
          and then reinstall it selecting "basic+extended". (Ver4.1 or later prompts you
          to install all the functions (conventional basic+extended) without the
          setup-type selection process.)
Q2-10 Can I use the iSM Client remotely using the terminal service client or the remote
      desktop?
    A [Ver 5.3 or later]
            Can be used remotely using the terminal service client or the remote desktop.
       [Ver 5.2 or earlier]
            Cannot be used using the terminal service client or the remote desktop.
            Install the iSM Client in a PC that can be connected to the iSM server.
Q2-11 When I started the iSM Client on Windows Vista or later or Windows Server 2008 or
      later, the "User Account Control" dialog appeared. What should I do?
    A When the iSM Client starts on Windows Vista or later or Windows Server 2008 or later,
      the "User Account Control" dialog appears. Select the Continue button (on Ver5.1 or
      later) or the Permit button (on Ver4.3.301) to start the iSM Client.
Q2-12 When I attempted to specify a port name, I could not specify a name for a replication
      port. Why did it happen?
    A You can specify names only for host ports. You cannot specify names for replication
      ports.
Q2-13 Are there any notes on using the iSM Client in a machine where security software(*) is
      installed?
      (*) Software to prevent information leakage, to block unauthorized accesses or
      computer viruses, etc.
    A The iSM Client (Win GUI) creates a folder and a file under the following folders for
      storing setting files and log files:
        ■ <System drive>:\Documents and Settings\<Login user name>\Application Data
             * On Windows Vista or later or Windows Server 2008 or later
               <System drive>:\User\<Login user name> \AppData\Roaming
       ■ iSM Client (Win GUI) installation folder
            * The default installation folder is:
               <System drive>:\Program Files\NEC\iSMClient


      If security software restricts the creation of these folders and files, the iSM Client will
      not work normally. Change the software setting to prevent the restriction.
Q3-1 The Replication/Performance Monitoring/Performance Optimization/Snapshot/Data
     Retention Management window did not appear. What should I do?
   A Have you purchased the product?
     Access the corresponding disk array detail information window from the iSM Client
     main window to check the purchased products.
Q3-2 Connection from a client failed. What is the possible cause?
   A The following may have caused the failure. Check them as well as the shown dialog
     message and take an appropriate action.
      [Cause related to incorrect setting]
      - Incorrect user name
      - Incorrect password
      - Incorrect IP address of the server or incorrect DNS name that has
        been specified in the environment setting
      - Incorrect port number of the server that has been specified in the
        environment setting
        [Action to take]
          Correct the incorrect item and connect to the iSM server again.


      [Cause related to the iSM server status]
      - The iSM server has not completely started.
      - The iSM server has not started.
      - The iSM server is terminating.
      - [Permitted Connection Type of Storage Manager Client] is not set to
        Win GUI in the iSM server environment setting.
        [Action to take]
          Check if the iSM server has started and the iSM server settings are correct
          and connect the iSM server again.


      [Cause related to the network environment]
      ■ Environment where the iSM Server and the iSM Client are running
        on different servers
         - LAN is not used to connect the server running the iSM Server and
           the server (PC) running the iSM Client.
          [Action to take]
                 Connect the server running the iSM Server and the server
                 (PC) running the iSM Client using LAN and make
                 connection again.


      ■ Environment where the iSM Server and the iSM Client are running
        on the same server
         - The IP address of the server has been specified in the
           environment setting, and a LAN cable is not connected to the
           server or all the devices to which the server is connected are
           inactive (powered off, etc.).(*)
             (*) A Windows machine cannot match the specified IP address
                 with the server (due to OS spec) if an LAN cable is not
                 connected to the server or all the devices to which the
                 server is connected are inactive (powered off, etc.).
          [Action to take]
                 Specify the loop-back address as the IP address of the
                 server in the environment setting.
                 Refresh the environment setting and make connection
                 again.
Q3-3 Which user privilege is required for using the iSM Client?
   A The required user privilege depends on the version.
         [Ver 2.1 or later]
             System administrator
         [Ver 1.4/Ver 1.5]
             Users are not restricted for use on Windows 98 or Windows NT 4.0.
             On Windows 2000 or Windows XP, only a system administrator can use
             the iSM Client.
         [Ver 1.3]
             Users are not restricted for use on Windows 98 or Windows NT 4.0.
             On Windows 2000, only a system administrator can use the iSM Client.
Q3-4 When I attempted to start the iSM Client, the iSM Client terminated with the error
     message "00006 Failed in acquiring the Client's IP address". The OS was Windows
     Server 2003 (without SP) and LAN cables were not connected. What caused the error?
   A This is a known OS error that occurs when the OS is Windows Server 2003 (without
     SP) and the machine is not connected to LAN.
     To remove this error, perform one of the following:
        - Connect the machine to LAN.
        - Apply Windows Server 2003 SP1 to the machine.
Q3-5 When I attempted to start the iSM Client, the message [00000] (or [00007-00])
     appeared and the start failed. Why did it happen?
   A You can start only one iSM Client to connect to one destination (multiple iSM Clients
     can be activated if they are connected to different destinations).
     Note that even if more than one user use the same machine with remote desktop, etc.,
     only one iSM Client can be activated in the machine to connect to one destination.
Q3-6 I could not set the FTP service on Windows Vista SP1 in which the iSM Server was
     running so that I could not use file transfer in the iSM Client. What should I do?
   A      The following error may occur on Windows Vista SP1:
          [Symptom]
              When a user click the default ftp site and click Properties to configure the
              FTP route directory for IIS, etc.,
              Microsoft Management Console has stopped working
              appears and the management console stops.
          If this symptom occurs, solve it by taking the following procedure given by
          Microsoft Corporation:


          Procedure
           ======
          Perform the following to create the management console for (IIS) 6.0:


          1. Click Start, type mmc.exe in the Start Search box, and then click Allow to
             start Microsoft Management Console.
          2. Click File and Add/Remove Snap-in to open the Add/Remove window.
          3. On the Add/Remove window, select Internet Information Service (IIS) 6.0
             Manager on the Available snap-ins list and click Add.
          4. On the Selected snap-ins list, select Internet Information Service (IIS) 6.0
             Manager and click Edit Extensions.
          5. On the Extension for Internet Information Services (IIS) 6.0 Manager window,
             click Enable only selected extensions and clear the ASP.NET
             Management Extension check box.
          6. Click OK to close the Extension for Internet Information Services (IIS) 6.0
             Manager window.
          7. Click OK to close the Add/Remove window.
          8. Click File, click Save As, type IIS 6.0 FTP Service Manager.msc in the File
             name box and click Save.
          9. Click Start, Control Panel, and then click Taskbar and Start Menu
             properties.
          10. Click the Start Menu tab and click Customize.
          11. On System administrative tools, click Display on the All Programs menu,
              click OK to close the Customize window on Start Menu.
          12. Click OK to close Taskbar and Start Menu properties.


          After the above process is complete, click Start, All Programs, Administrative
          Tools, and IIS 6.0 FTP Service Manager.msc and configure the FTP service in
          the activated IIS 6.0 Manager.


Q4-1 Tell me how to change the IP address of a PC in which the iSM Client is running.
   A Terminate the iSM Client before starting to change the IP address.
     No further actions are required for the iSM Client.
     When a firewall is installed between the iSM server and the iSM client, make settings
     to allow the changed IP address to pass through the firewall.
Q4-2 Tell me how to transfer the iSM Client to another PC.
   A Transfer the iSM Client environment setting information, menu icons and desktop
     icons from the old PC to the new PC by following one of the procedures below.
     See the procedure for the iSM Client version installed in your old PC.
     NEC Storage Manager User's Manual Part II also describes how to restore menu
     icons and desktop icons.


     [For V3.1 or later]
       (1) Terminate the activated iSM Client.
 (2) Move the iSM Client desktop icons stored in the old PC to any folder.
     The desktop icons are stored in the following folder:
        <System drive>:\Documents and Settings\All Users\Desktop
          * On Windows Vista or later or Windows Server 2008 or later, <System
            drive>:\Users\Public\Public Desktop (with hidden attribute)


 (3) Move the iSM Client menu icons stored in the old PC to any folder.
     The menu icons are stored in the following folder:
        <System drive>:\Documents and Settings\All Users\Start
        Menu\Programs\[iSM Client]
          * On Windows Vista or later or Windows Server 2008 or later, <System
            drive>:\ProgramData\Microsoft \Windows\Start Menu\Programs\[iSM
            Client] (with hidden attribute)
          * The [iSM Client] part will be the program folder name specified during
            installation (default: iSM Client).


 (4) Move the iSM Client environment setting information stored in the old PC.
     Move the setting files (*.ini) in the folder where the iSM Client has been installed
     to any folder.
     When multiple connection targets have been created, the folder [SGn] (n is a
     number) has been created in the installation folder.
     Move also the folder and all the files stored in the folder.


 (5) Move the log files stored in the old PC.
     Move the log files that have been created in the following folder to any folder:
        <iSM Client installation folder>\LOG\iSM.LOG,OLDiSM.LOG


 (6) Uninstall the iSM Client in the old PC if necessary.


 (7) Install the iSM Client in the new PC.
     It is recommended to install the iSM Client in the path/folder having the same
     name as the old PC so that you can use the desktop icons and menu icons that
     are moved in steps (2) and (3) also in the new PC.


 (8) Restore the old PC log files.
     Copy the old PC log files moved in step (5) to the following folder in the new PC:
        <iSM Client installation folder>\LOG
          * Create the LOG folder in a PC in which the iSM Client just has been
            installed and that has no LOG folder.


 (9) Restore the iSM Client environment setting information on the old PC.
     Copy the old PC environment setting information moved in step (4) to the iSM
     Client installation folder in the new PC.
     When prompted to confirm whether to overwrite files, choose to overwrite them.
     Also copy the [SGn] folder to the installation folder.


(10) Restore the iSM Client menu icons of the old PC.
     Copy the old PC menu icons moved in step (3) to the following folder in the new
     PC:
        <System drive>:\Documents and Settings\All Users\Start
        Menu\Programs\[iSM Client]
          * On Windows Vista or later or Windows Server 2008 or later, <System
            drive>:\ProgramData\Microsoft \Windows\Start Menu\Programs\[iSM
            Client] (with hidden attribute)
          * The [iSM Client] part will be the program folder name specified during
            installation (default: iSM Client).


     If the iSM Client installation path/folder name is different between the old and the
     new PCs, the icons will not be linked to the specified targets in the new PC.
     Follow the procedure below to set the targets again.
     1. Open the properties window of a menu icon.
     2. Click the Shortcut tab and correct the path of the iSM Client (iSMCL.exe) in
        the Target box according to the installation folder in the new PC.
          * Do not change double quotation marks and variables such as [SGn].
     3. Click OK to close the properties window.
     4. Repeat steps 1 to 3 for all the copied icons.


(11) Restore the iSM Client desktop icons of the old PC.
     Copy the old PC desktop icons moved in step (2) to the following folder in the
     new PC.
     When prompted to confirm whether to overwrite files, choose to overwrite them.
        <System drive>:\Documents and Settings\All Users\Desktop
          * On Windows Vista or later or Windows Server 2008 or later, <System
            drive>:\User\Public\Public desktop (with hidden attribute)


     If the iSM Client installation path/folder name is different between the old and the
     new PCs, the icons will not be linked to the specified targets in the new PC.
     Follow the procedure below to set the targets again.
     1. Open the properties window of a menu icon.
     2. Click the Shortcut tab and correct the path of the iSM Client (iSMCL.exe) in
        the Target box according to the installation folder in the new PC.
          * Do not change double quotation marks and variables such as [SGn].
     3. Click OK to close the properties window.
     4. Repeat steps 1 to 3 for all the copied icons.


[For V2.2 or earlier]
 (1) Terminate the activated iSM Client.


 (2) Move the iSM Client environment setting information stored in the old PC.
     Move the setting files (*.ini) in the folder where the iSM Client has been installed
     to any folder.


 (3) Move the log files stored in the old PC.
     Move the log files that have been created in the following folder to any folder:
              <iSM Client installation folder >\LOG\iSM.LOG,OLDiSM.LOG


       (4) Uninstall the iSM Client in the old PC if necessary.


       (5) Install the iSM Client in the new PC.


       (6) Restore the old PC log files.
           Copy the old PC log files moved in step (3) to the following folder in the new PC:
              <iSM Client installation folder>\LOG
                * Create the LOG folder in a PC in which the iSM Client just has been
                  installed and that has no LOG folder.


       (7) Restore the iSM Client environment setting information on the old PC.
           Copy the old PC environment setting information moved in step (2) to the iSM
           Client installation folder in the new PC.
           When prompted to confirm whether to overwrite files, choose to overwrite them.
Q4-3 Which files will be deleted and will not be deleted from the installation folder when the
     iSM Client is uninstalled?
   A Executable files, help files, shortcut icons on desktop, and start menu items will be
     deleted.
     Setting files will not be deleted because they will be taken over at re-installation.
     Delete the setting files manually only when you will not re-install the iSM Client or need
     not apply the setting files to a new environment.
Q4-4 When upgrading OS in a machine using the iSM Client to Windows Vista or later or
     Windows Server 2008 or later, do I need to perform any operations in the iSM Client?
   A When upgrading OS in a machine in which the iSM Client is used to Windows Vista or
     later or Windows Server 2008 or later, be sure to follow the procedure below to update
     the iSM Client. This update is required also when the updated iSM Client will have the
     same version as before the update.
      (1) Upgrade OS in a machine where the iSM Client has been installed to
          Windows Vista or later or Windows Server 2008 or later.
      (2) After upgrading OS to Windows Vista or later or Windows Server 2008 or
          later, uninstall the iSM Client.
      (3) Reinstall the iSM Client.
      (4) Open the properties window of the iSM Client shortcut created on the desktop
          or the properties window of iSMCL.exe stored in the folder where the iSM
          Client has been installed.
      (5) Click the Compatibility tab, select the Run this program as an
          administrator check box, and then click OK.
      (6) Use the iSM Client as usual.
Storage Management

NEC Storage Manager Volume List Command
1. Installation
      Q1-1 Can the iSM Volume List Command be used on a virtual machine using Windows Server 2008 Hyper-V?
      Q1-2 Are there any notes on using the iSM Volume List Command in a Windows machine where security
           software(*) is installed?
           (*) Software to prevent information leakage, to block unauthorized accesses or computer viruses, etc.
      Q1-3 Are there any notes on setting a Control Volume?


2. Troubleshooting
      Q2-1 The message "Failed in getting systempath of environment variable." appeared during uninstallation of the
           iSM Volume List Command for Windows. What should I do?
      Q2-2 Are there any notes on using the iSM Volume List Command in a Windows server in which the antivirus
           software "NOD32 Antivirus" (NOD32 Kernel Service) is running?



      Q1-1 Can the iSM Volume List Command be used on a virtual machine using Windows Server 2008 Hyper-V?
          A The iSM Volume List Command cannot be used on a virtual machine.
            If the command has been installed on a virtual machine, uninstall it.
      Q1-2 Are there any notes on using the iSM Volume List Command in a Windows machine where security
           software(*) is installed?
           (*) Software to prevent information leakage, to block unauthorized accesses or computer viruses, etc.
          A When the iSM Volume List Command is used, setting files and log files are stored under the following
            folder as well as under the folder where the iSM Volume List Command has been installed (default folder;
            <System drive>:\Program Files\NEC\iSMvol; for 64-vit version, <System drive>:\Program Files
            (x86)\NEC\iSMvol)):


                  Folder specified in the -export option of the iSMcc_hostinfo command
                  <System drive>:\windows\ismvol
                  <System drive>:\Program Files\Common Files
                  <System drive>:\Documents and Settings\<Login user name>\Application Data
                  * On Windows Vista or Windows Server 2008,
                   <System drive>:\User\<Login user name>\AppData\Roaming


                  If security software restricts the creation of these folders and files, the iSM server will not work
                  normally. Change the software setting to prevent the restriction.
      Q1-3 Are there any notes on setting a Control Volume?
          A Note the following when setting a Control Volume:
                     - On each disk array, assign one logical disk as Control Volume per server. (*1)
                     - Assign one logical disk to only one server.
                     - When registering a logical disk as Control Volume in the LD set of a server, it is recommended
                       to register the disk in the top of the LD set (LUN0). (*2)
                     - As a Control Volume, assign a logical disk with the MV or IV attribute or a logical disk with the
                       CV attribute that is designed for Control Volume.
                     - Allow a Control Volume only to issue control I/O to the disk array and do not allocate application
                       data to the Control Volume.
            *1: If multiple logical disks for Control Volume (CV) on the same disk array are assigned to one
                server, one of the logical disks will be applicable as a Control Volume.
                The following type of logical disk will be applied as a Control Volume:
                     - Logical disk for Control Volume (CV) to which drive letters or a mount point for the NTFS
                       folder name are assigned
                     - When drive letters or a mount point for the NTFS folder name are assigned to all the
                       logical disks for Control Volume (CV), the logical disk whose mount-point path name
                       comes earliest in alphabetical order.
                     - When a mount point is not assigned to all the logical disks for Control Volume (CV), the
                       logical disk that has been registered earliest in the LD set (having the smallest LUN
                       value)
            *2: If a server cannot recognize the logical disk LUN0 due to the spec of OS, the server may not
                recognize the subsequent logical disks (LUN1 and later). It is recommended to allocate a
                volume that will not be in NotReady or NotAvailable state during operation as Control Volume to
                LUN0.
Q2-1 The message "Failed in getting systempath of environment variable." appeared during uninstallation of the
     iSM Volume List Command for Windows. What should I do?
   A This symptom occurs when a value of 1024 bytes or more has already been specified in the system
     environment variable Path. Clicking OK completes the uninstallation, however, the path information for the
     iSM Volume List Command remains in the system environment variable Path. Delete the information by
     following the procedure below.


     (1) Right-click My Computer, click Properties. On the Advanced tab, click Environment Variables.
      (2) Select Path from the system environment variables and click Edit.
     (3) Delete the following specified in the variable and close the window.
               %iSMvol%\sbin;
Q2-2 Are there any notes on using the iSM Volume List Command in a Windows server in which the antivirus
     software "NOD32 Antivirus" (NOD32 Kernel Service) is running?
   A In a Windows machine in which the iSM Volume List Command is installed and the antivirus software
     "NOD32 Antivirus" (NOD32 Kernel Service) is running, the iSM Volume List Command may end
     abnormally due to the timing.
     It has already been confirmed that if this antivirus software scans files internally used by the iSM Volume
     List Command functions, an error will occur due to file conflicts. Perform the following (1) or (2) to prevent
     the antivirus software from scanning the files used by the iSM Volume List Command functions.
     (1)   Exclude the following folders and files that are used by the iSM Volume List Command functions
           from scanning:
           For how to exclude particular folders and files from scanning, see the NOD32 Antivirus's manual.
           -    Folders to be excluded from scanning
                -   The folder in which the iSM Volume List Command has been installed and its subfolders
                    (default: C:\Program Files\NEC\iSMvol
                    (On 64-bit OS: C:\Program Files (x86)\NEC\iSMvol\))
                -   ismvol folder under the system folder
                    (ex.: C:\windows\ismvol\)
                -   Folders under <System drive>\Program Files\Common Files\NEC\WebSAM\Framework\
                    (On 64-bit OS, folders under <System drive>\Program Files(x86)\Common
                    Files\NEC\WebSAM\Framework\)
           -    Files to be excluded from scanning
          -   Files specified by command parameters
(2)   Stop the following service temporarily while using an iSM Display Command function:
          NOD32 Kernel Service
Storage Management

Initialization wizard
1. Introduction
     Q1-1 Tell me about the initialization wizard.
     Q1-2 Which manual describes how to use the initialization wizard?


2. Installation
     Q2-1 Can I perform initialization again for a disk array that has ever been initialized?
     Q2-2 Can I perform initialization for multiple disk arrays at the same time by using the initialization wizard?
     Q2-3 Why do I need to connect to the management server using LAN for using the initialization wizard?


3. Operation
     Q3-1 Under how configuration can I use the initialization wizard file?
     Q3-2 Which types of RAID does the initialization wizard support?
     Q3-3 Can I configure multiple logical disks having different sizes and different RAID configurations to perform
          replication and snapshot?


4. Troubleshooting
     Q4-1 I could not find the disk array I wanted to configure. What should I do?
     Q4-2 After I configured the network, I could not perform monitoring using NEC Storage Manager. What should I
          do?
     Q4-3 When I configured a logical disk, an error occurred and I could not configure the disk. What should I do?


     Q1-1 Tell me about the initialization wizard.
         A Users who have purchased the NEC Storage D series (except D8 series) can perform disk-array
           initialization.
           The initialization includes the configurations of IP addresses, fiber channel ports and logical disks.
     Q1-2 Which manual describes how to use the initialization wizard?
         A For how to use the initialization wizard, see the Disk Array Unit User's Guide that corresponds to the version
           of NEC Storage Manager you use. For information about the version of disk array that corresponds to NEC
           StorageManager you use and how to obtain the disk array, see "Introduction" in Disk Array Unit User's
           Guide.
     Q2-1 Can I perform initialization again for a disk array that has ever been initialized?
         A [NEC StorageManager Ver 5.2 or later]
                  - Re-initialization can be performed by using the initialization wizard.
            [NEC StorageManager Ver 5.1]
                  - Re-initialization cannot be performed by using the initialization wizard. Use the Configuration Setting
                    to change the initialization setting.
     Q2-2 Can I perform initialization for multiple disk arrays at the same time by using the initialization wizard?
         A You can perform initialization for only one disk array by using the initialization wizard.
     Q2-3 Why do I need to connect to the management server using LAN for using the initialization wizard?
         A The disk-array initialization is performed from NEC Storage Manager through the management server
           connected to the disk array using LAN. The User Datagram Protocol (UDP) is used to search disk arrays that
           are connected to the network including the management server using LAN and for which no network address
           is set.
     Q3-1 Under how configuration can I use the initialization wizard file?
   A You can make settings in the same configuration as when the initialization wizard file was saved. Do not use
     the initialization wizard file to perform initialization settings in a different configuration because it may cause
     an error.
     Before using the initialization wizard file, change xxx in the file to the network setting and the license key you
     will use.
Q3-2 Which types of RAID does the initialization wizard support?
   A NEC Storage Manager Ver6.1 or later
          - All the RAID types supported by the disk array are supported.
      NEC Storage Manager Ver5.3 or earlier
          - The Basic Pool version supports RAID1 and the Dynamic Pool version supports RAID6 (4+PQ) and
            RAID6 (8+PQ).
Q3-3 Can I configure multiple logical disks having different sizes and different RAID configurations to perform
     replication and snapshot?
   A You can create multiple logical disks having the same size for a RAID type selected in the initialization
     wizard, however, you cannot add logical disks.
     Use the Configuration Setting to configure various logical disks for replication, snapshot, etc.
Q4-1 I could not find the disk array I wanted to configure. What should I do?
   A The disk array needs to be connected to the network where the management server is located.
     The initialization wizard searches disk arrays using the User Datagram Protocol (UDP) [using the port
     number 2730]. When a firewall is installed, configure the network that contains the management server and
     the disk array to allow search packets to pass through the firewall.
Q4-2 After I configured the network, I could not perform monitoring using NEC Storage Manager. What should I
     do?
   A See "Troubleshooting" in the user's guide that comes with the unit to reconfigure the network and restore
     monitoring using NEC Storage Manager.
Q4-3 When I configured a logical disk, an error occurred and I could not configure the disk. What should I do?
   A Check the following before configuring a logical disk:
      NEC Storage Manager Ver6.1 or later
        1. Check whether the RAID type and the number of PDs specified when the pool was newly created are
           correct.
          The number of PDs you can specify depends on the RAID type.
        2. Check whether the RAID and the PD type/capacity are matched correctly.
          The supported RAID type depends on the PD type (SATA/SAS).
        3. Check the number of specified logical disks.
        4. Check the specified logical disk capacity.
          When Selection host is selected, one logical disk of 0.2GB is created per Selection host, reducing
          the logical-disk size you can configure.
          When Selection host is not selected, you can configure one logical disk having the largest size among
          the sizes shown in the pull down menu of logical disk size.
          When Selection host1 or Selection host2 is selected, the size shown by default for each RAID type
          will be changed to the maximum size that can be configured by using one logical disk.
          As described above, the maximum logical-disk size that can be configured depends on whether
          Selection host is selected. Selection host is equivalent to “Creating an LD Set” in a device with
          iSCSI ports.
        5. Check Create Host Spare has been selected.
          When you bind a spare, there must be a PD with the same PD type and capacity as the pool.
      NEC Storage Manager Ver5.3 or earlier
        1. Check the number of installed physical disks.
  To use the initialization wizard, 2 physical disks are required for RAID1, 6 disks for RAID6 (4+PQ), and
  10 disks for RAID6 (8+PQ). Also the check button to configure a spare physical disk having the same
  size is selected by default. Select a RAID type that can be configured by using the installed physical
  disks.
2. Check the size of the specified logical disk.
  When Selection host is selected, one logical disk of 0.2GB is created per Selection host, reducing
  the logical-disk size you can configure.
  When Selection host is not selected, you can configure one logical disk having the largest size among
  the sizes shown in the pull down menu of logical disk size.
  When Selection host1 or Selection host2 is selected, the size shown by default for each RAID type
  will be changed to the maximum size that can be configured by using one logical disk.
  As described above, the maximum logical-disk size that can be configured depends on whether
  Selection host is selected.
3. Check the number of the specified logical disks.
  The number of configurable logical disks is limited depending on the combination of a selected
  RAID/PD type and a selected logical-disk size. Reduce logical disks before configuration if necessary.
Storage Management

Configuration Setting
1. Introduction
    Q1-1 What is the difference between Basic Pool and Dynamic Pool?
    Q1-2 Which disk format supports quick format?


2. Installation
    Q2-1 Which configuration setting should I use, CLI or GUI?
    Q2-2 What is the difference between Configuration Setting and Quick Configuration?


3. Operation
    Q3-1 How can I allow OS to recognize configured logical disks?
    Q3-2 Windows could not recognize 300 logical disks I created. Why did it happen?
    Q3-3 I configured a logical disk incorrectly. Do I have to wait until the format is complete to unbind the disk?
    Q3-4 When I performed Expanding Capacity on Windows 2000, Windows Server 2003, Windows Vista, Windows
         NT, HP-UX, Solaris or Linux, the size was not increased. Why it was not increased?
    Q3-5 Can I access a disk whose size is being expanded on Windows 2000, Windows Server 2003, Windows Vista,
         Windows NT, HP-UX, Solaris, or Linux?
    Q3-6 When I attempted to increase a pool size in the NEC Storage D series, NEC Storage 2800 series, S1400,
         S1500, S2400, or S2500, the logical disk size was not increased. Why it was not increased?
    Q3-7 When I used the initialization wizard of Configuration Setting and Logical Disk Quick Configuration functions
         to configure a logical disk and allocate the disk to a host, a small size of volume (0.2GB) was automatically
         created per host. What is this volume?
    Q3-8 Though I had enabled the write cache function in the cache setting for a logical disk, the hit rate of the cache
         was the same as when the write cache function was disabled. What caused it?
    Q3-9 When I configured a logical disk, the disk state entered "attn(unformatted)."
         Do I need to take any action for it?


4. Troubleshooting
    Q4-1 When I released all logical disks and restarted OS, the OS did not recognize the disk array. What should I do?
    Q4-2 I failed to unbind a spare disk. Why did it failed?
    Q4-3 Can I set ExpandLUN to ON on OS other than HP-UX?
    Q4-4 Whenever I attempt to start Configuration Setting, it ends with the message "Configuration Setting is
         executing from other client." What should I do?
    Q4-5 I could not activate Configuration Setting that has not been used by any other users. What should I do?
    Q4-6 I could not obtain the configuration information. Why could I not?
    Q4-7 When I attempted to unlock the license, an error message appeared and I failed to unlock the license. What
         may have caused the problem?
    Q4-8 An error occurred with the message "The duplication check of the IP Address of a Disk Array is failure."
         during network setting for a disk array. What is the possible cause?
    Q4-9 When I attempted to start Configuration Setting from the iSM Client (Web GUI), the message "[01286-00]
         Failed in displaying the configuration setting screen." appeared and I failed to start the Configuration Setting.
         What is the possible cause?
   Q4-10 When I selected Control Panel, Design, Display, and Smaller - 100%(default)(S) for the size of texts on
         windows and other items in Windows Server 2008 R2 or Windows 7, the window format became distorted or
         the mouse did not work. How can I solve this problem?
Q1-1 What is the difference between Basic Pool and Dynamic Pool?
   A A conglomerate of physical disks is called "pool" in the NEC Storage D series, NEC Storage S2800 series,
     S1400, S1500, S2400, S2500, and S4900. "Basic Pool" manages the area on a pool as a space sectioned by
     sequential addresses. "Dynamic Pool" manages the area on a pool as a virtual memory space, allowing users
     to add one or more physical disks and increase logical disks.
Q1-2 Which disk format supports quick format?
   A Logical disks to be allocated to a Windows host in a Basic Pool (*) can be quick-formatted.

     (*) Set the logical-disk format to WN or WG.
Q2-1 Which configuration setting should I use, CLI or GUI?
   A Use GUI. CLI is designed for disk-array experts such as maintenance staff, etc.
Q2-2 What is the difference between Configuration Setting and Quick Configuration (Easy Configuration v5.3 or
     earlier) ?
   A Quick configuration with the following functions provides simpler operability than the configuration setting.


            - Batch License Unlock
            - LD Binding (FC)                                  [V6.1 or later]
            - LD Binding (iSCSI)                               [V6.1 or later]
            - Easy Configuration                               [V5.3 or earlier]
      Use Configuration Setting to configure logical disks in consideration of physical-disk allocation.
Q3-1 How can I allow OS to recognize configured logical disks?
   A See the manual of the OS (restarting the system is required depending on the OS type).
Q3-2 Windows could not recognize 300 logical disks I created. Why did it happen?
   A It occurred because of the restriction on the OS and the driver. The number of logical disks that can be
     recognized by one port on Windows is up to 256.
Q3-3 I configured a logical disk incorrectly. Do I have to wait until the format is complete to unbind the disk?
   A You can unbind a logical disk before it is completely formatted. If you start unbinding a logical disk being
     formatted, the format will terminate, giving priority to unbinding the disk.
Q3-4 When I performed Expanding Capacity on Windows 2000, Windows Server 2003, Windows Vista, Windows
     NT, HP-UX, Solaris or Linux, the size was not increased. Why it was not increased?
   A Disk array supporting pools
            This problem is not experienced in a disk array supporting pools.
            Capacity can be increased right after you finished the procedure for expanding capacity.


      Disk array not supporting pools
            A disk size is not increased during Expanding Capacity.
            Wait until Expanding Capacity is complete, which can be checked on the Server/Client window.
Q3-5 Can I access a disk whose size is being expanded on Windows 2000, Windows Server 2003, Windows Vista,
     Windows NT, HP-UX, Solaris, or Linux?
   A Disk array supporting pools
            Yes. You can start using the capacity right after the procedure for expansion is finished.


      Disk array not supporting pools
            Yes. You can access a disk being expanded as a normal disk.
Q3-6 When I attempted to increase a pool size in the NEC Storage D series, NEC Storage 2800 series, S1400,
     S1500, S2400, or S2500, the logical disk size was not increased. Why it was not increased?
   A Performing Pool Expansion increases only a pool size, while a logical disk size is not increased automatically.
     To increase a logical disk size, specify a logical disk and add a necessary size to the disk. Also a new logical
     disk can be configured by using an area expanded by Pool Expansion.
Q3-7 When I used the initialization wizard of Configuration Setting and Logical Disk Quick Configuration functions
     to configure a logical disk and allocate the disk to a host, a small size of volume (0.2GB) was automatically
     created per host. What is this volume?
   A That is a Control Volume necessary for a host to control and operate disk arrays without affecting its
     operation.
     One Control Volume is assigned to and shared in each host.
Q3-8 Though I had enabled the write cache function in the cache setting for a logical disk, the hit rate of the cache
     was the same as when the write cache function was disabled. What caused it?
   A The write cache function is enabled only when the battery and the cache are in normal state. Check the
     battery and cache states.
Q3-9 When I configured a logical disk, the disk state entered "Attn.(unformatted)/attn(unformatted)."
     Do I need to take any action for it?
   A "Attn.(unformatted)/attn(unformatted)" shows the state in which a logical disk is waiting to be logically
     formatted.
     No actions need to be taken because the disk array unit logically formats disks in order. You cannot access a
     logical disk while it is formatted.
Q4-1 When I released all logical disks and restarted OS, the OS did not recognize the disk array. What should I do?
   A There are two ways of connecting an iSM server and a disk array, TCP/IP path and FC path. While OS
     recognizes a disk array including no logical disk when the TCP/IP path is used, OS does not recognize such
     disk array when the FC path is used. There are the following two solutions (1 and 2) for the S series. Only 2
     can be applied to the D series.
      1. Power off and on the disk array so that a virtual logical disk is created.
         Make OS recognize the logical disk and restart the iSM server.
         The virtual logical disk is shown as LDN0 and the size is as several MB. Unbind the virtual disk when
         reconfiguring logical disks.
         In the NEC Storage 2800 series, S1400, S1500, S2400, or S2500 in which a virtual logical disk is
         automatically created and released, you do not need to power off and on the disk array for allowing the
         OS to recognize the disk array.
      2. Connect the disk array and the iSM server using the TCP/IP path.
Q4-2 I failed to unbind a spare disk. Why did it failed?
   A Is the spare disk in Rebuilding state? A spare disk in Rebuilding state cannot be unbound.
Q4-3 Can I set ExpandLUN to ON on OS other than HP-UX?
   A Never do it. If setting ExpandLUN to ON when an iSM server is connected to a disk array using FC, you will
     no longer be able to change the configuration. In case you make the setting, contact a maintenance staff.
Q4-4 Whenever I attempt to start Configuration Setting, it ends with the message "Configuration Setting is
     executing from other client." What should I do?
   A The Configuration Setting has already been activated by another user. Activate Configuration Setting after the
     user finishes using it. When "It is currently under setting Failed to start." showing maintenance is ongoing
     appears, wait until the maintenance is finished.
Q4-5 I could not activate Configuration Setting that has not been used by any other users. What should I do?
   A It can be caused by one of the following:
      1. An error occurred in an access to the disk array while Configuration Setting is performed in an iSM client.
         Remove the cause of the access error, restart the iSM client, and activate Configuration Setting.
      2. The Configuration Setting window abnormally ended during Configuration Setting in an iSM client. Restart
         the iSM client and activate Configuration Setting.
Q4-6 I could not obtain the configuration information. Why could I not?
   A The configuration information file may have failed to be transferred. On Windows, check if file transfer has
     correctly been set in the iSM Server environment setting. On OS other than Windows, check if the
     file_transfer section has correctly been set in the iSM Server environment setting file.
Q4-7 When I attempted to unlock the license, an error message appeared and I failed to unlock the license. What
     may have caused the problem?
   A Check the following possible causes as well as the shown message dialog:


      [The entered license key is disabled]
             - An incorrect key may have been entered. Check the license key indicated in the license key
               sheet.


      [The license key has already been used]
             - The license key you entered may have been used for unlocking the license of another disk
               array having the same model number. Use the license key indicated in a license key sheet
               that has never been used to unlock a license.
             - There were multiple disk array units having the same model number, the license for one of the
               units was wrongly applied to another unit, and the license was unlocked. To restore an
               unlocked license, you need to contact a maintenance staff. If you have more than one disk
               array unit, check the unit name to apply a license to an appropriate unit.


      [The license to be unlocked does not suit to the disk array you want to apply a license]
             - You are about to unlock a license that cannot be upgraded from the parameter (size tier or
               number of connections) currently applied to the disk array. Check the parameter applied to the
               disk array unit and the upgrade license scope on product (ex. xxTB→xxTB) that is indicated in
               the license key sheet.


      [The disk array is not supported by the license to be applied]
             - The disk array series to be unlocked is not supported by the license. Check the disk array unit
               to be unlocked against the license key sheet indicating the supported disk array series.


      [The disk array does not support functions of the license to be applied]
             - Check if the disk array unit whose license will be unlocked is correct.


      [The license key cannot be converted]
             - An error occurs when the license key is decoded and converted because the version of NEC
               Storage Manager is old. Check the NEC Storage Manager version and the model number of
               the license.
Q4-8 An error occurred with the message "The duplication check of the IP Address of a Disk Array is failure." during
     network setting for a disk array. What is the possible cause?
   A The possible causes are:
         - Another server/device having the same IP address as the disk array is located on the network.
         - The network setting of the server in which the iSM Server has been installed is flawed.
         - The specified address is incorrect (such as 0.0.0.0).
Q4-9 When I attempted to start Configuration Setting from the iSM Client (Web GUI), the message "[01286-00]
     Failed in displaying the configuration setting screen." appeared and I failed to start the Configuration Setting.
     What is the possible cause?
   A The version of the installed JRE (Java Runtime Environment) may not be supported by NEC
     StorageManager.
     See NEC StorageManager Installation Guide and upgrade JRE to a supported version.
Q4-10 When any option other than Smaller - 100%(default)(S) is selected on the Display dialog box, which is
      opened by selecting Control Panel and Design, on Windows Server 2008 R2 or Windows7, display is
      distorted or mouse operation is disturbed. What should I do?
    A This problem may be experienced when Ver6.1 is used and a size other than Smaller - 100%(default)(S) is
      configured. Choose the default settings Smaller - 100%(default)(S).
Storage Management

State Monitoring
1. Introduction
Q1-1 What functions does state monitoring provide?
Q1-2 How is a failure on a disk array notified?


2. Installation
Q2-1 Is there any ideal value for state monitoring interval? What should be considered to configure the interval?


3. Operation
Q3-1 Why are two messages (for example, iSM07102 and iSM07152) reported when a resource failure occurs?
Q3-2 When a failure occurs on a disk array, how can it be checked on a client?
Q3-3 If a failure occurs on a disk array, where can I find the message for it?
Q3-4 Is it possible to physically locate a disk array cabinet from iSM client?
Q3-5 What messages are reported for physical disk failures?


4. Troubleshooting
Q4-1 A controller resource has a failure but the disk array icon does not change. What should I do?
Q4-2 When a resource has a failure, is the information for the resource accurate?


Q1-1 What functions does state monitoring provide?
   A With state monitoring, logical disks as well as state of devices such as physical disks that constitute a disk array,
     controllers, and power supply are monitored. If a failure occurs, it is reported via a message or icon on the iSM
     main window.
Q1-2 How is a failure on a disk array notified?
   A A failure on a disk array is notified through an icon on the iSM main window or a message. If iSM client (Web GUI)
     is monitoring a D series disk array, a failure in a physical disk, controller component or enclosure component is
     shown with a visual image as well.
     A reported message can be sent by email to any designated destinations.
Q2-1 Is there any ideal value for state monitoring interval? What should be considered to configure the interval?
   A Longer state monitoring intervals result in longer time lag from the moment of failure occurrence to its detection.
     Shorter state monitoring intervals result in larger overhead because target devices are checked more frequently.
     In general, use the default interval (15 seconds) but note that a preferable value for interval depends on the
     number of managed devices and LAN capacity.
Q3-1 Why are two message (for example, iSM07102 and iSM07152) reported when a resource failure occurs?
   A Messages to be reported depend on how a failure in a target disk array is notified (*).
      (*)Via fault report mechanism or NEC Storage Manager


      Two IDs exist for a message to show the status of a disk array component. For reporting via NEC Storage
      Manager, the number assigned to a message ID is greater by 50.


      The messages noting a physical disk failure (iSM07102 and iSM07152) are related as follows:
        - iSM07102:when reporting is not via NEC Storage Manager (for example, notified only via fault report
          mechanism)
        - iSM07152:when reporting is via NEC Storage Manager
      Information and the reporting timing are the same for both messages.


      The disk array must be configured to select which message to be reported.
      For the following disk arrays, the number assigned to a message ID is greater by 50.
      - S1100/S1200/S1300/S2100/S2200/S2300
Q3-2 When a failure occurs on a disk array, how can it be checked on a client?
   A The failure can be checked on the iSM main window of a client. The iSM main window shows configuration
     information in the tree view form divided into “disk array layer”, “component layer”, and “individual component
     layer.” One of “Critical fault”, “Fault”, “Attention”, “Offline” and “Ready (Maintenance)” is shown depending on the
     severity. If a failure occurs in a resource in a disk array, the icon corresponding to the resource changes. By
     clicking the disk array icon, you can identify the failing resource.

     If iSM client (Web GUI) is monitoring a D series disk array, physical disk controller and enclosure components are
     shown with visual images as well. A physical location having a failure is shown with an icon. For a failing
     component that does not have material substance (such as temperature), color representing the entire device
     changes.
Q3-3 If a failure occurs on a disk array, where can I find the message for it?
   A If a failure occurs in a disk array, a message is reported in operation logs of NEC Storage Manager. The message
     is also reported in event logs in a Windows system and system logs (syslog) in a UNIX system.
Q3-4 Is it possible to physically locate a disk array cabinet from iSM client?
   A You can configure to flash the service LED of a disk array cabinet through the main window only when the device
     is a D series disk array and monitored by iSM client (Web GUI). With this configuration, the cabinet can be
     identified.
     To operate the service LED, select Operation, State monitor, and Cabinet Service LED from the main window
     or click the button next to the cabinet image shown on the main window.
     Note that you can only control to flash or to stop flashing the service LED from the main window. Display of LED
     status is not supported.
Q3-5 What messages are reported for physical disk failures?
   A Messages related to physical disk failures are:
      1.    Messages notifying a physical disk failure
      2.    Messages notifying data being reconstructed
      3.    Messages notifying data reconstruction has been completed
      4.    Messages notifying recovery of physical disk (such as replacement of failed disk)


      The message to be reported depends on whether the physical disk failure should be taken care immediately or
      taken care in scheduled maintenance.


      1     For a physical disk failure
           - If immediate maintenance/troubleshooting is necessary:
            iSM07102 or iSM07152 is reported.
           - If it should be fixed in scheduled maintenance:
            iSM07402 or iSM07452 is reported.


      2     For data being reconstructed
           - If the data is being reconstructed due to a failure that needs immediate maintenance/troubleshooting:
            iSM07104 or iSM07154 is reported.
           - If the data is being reconstructed in scheduled maintenance:
            iSM07404 or iSM07454 is reported.


      3     For data that has been reconstructed
          - If the data has been reconstructed due to a failure that needed immediate maintenance/troubleshooting:
            iSM07109 or iSM07159 is reported.
          - If the data has been reconstructed in scheduled maintenance:
            iSM07409 or iSM07459 is reported.


            *    Depending on the timing of detection, a message for 4 may be reported.


      4     For physical disk recovery
            iSM07101 or iSM07151 is reported.


      iSM07151, iSM07152, iSM07154, iSM07159, iSM07452, iSM07454, and iSM07459 are reported for failures
      notified through NEC Storage Manager. See Q3-1 as well.


      For details of messages, see iSM07000 and on in 2.2 “Message List” of Manual NEC Storage Software
      Messages Handbook.
Q4-1 A controller resource has a failure but the disk array icon does not change. What should I do?
   A When a resource of controller or enclosure has a failure, “Ready (maintenance)” is shown for the status of Disk
     array and Component layers. By configuring the Display Maintenance State check box from environment
     settings of the iSM main window, you can choose whether or not to distinguish the icon representing this status
     from the icon representing Ready.
     To show the environment settings:
      iSM client (Web GUI)
           Click Option on the Connection window to open the dialog box for settings.
      iSM client (Win GUI)
           From the File, select Environment Settings to open the dialog box for environment settings.
Q4-2 When a resource has a failure, is the information for the resource accurate?
   A If a resource has a failure, information on the resource cannot be collected, which can result in failure to show the
     latest information.
      Example: If a failure due to removal of a host director occurs while the link status shown in the properties of the
               host director of a disk array supporting iSCSI is Link Up (port connected), the actual link status of the
               port is Link Down (port disconnected) but the link status shown in the properties of the host director
               remains to be Link Up (port connected).


      If the resource status is attention due to a reason such as reduce (i.e. degenerated mode) of component, latest
      information about the resource may not be shown.
Storage Management

Host Agent
1. Introduction
 Q1-1 What is iSM host agent service (service name:NEC Storage Manager Host Agent), which is installed on the
      Windows platform?
 Q1-2 What are supported OSes?


2. Installation
 Q2-1 Are there any patches or software programs that should be installed to use the host collection function (the
      iSMcc_hostinfo command) or the iSM host agent service?
 Q2-2 When VMware ESX is used, is it possible to collect host information and configure the access control by using the
      host information?


3. Operation
 Q3-1 What should I do when the message iSM11771 or iSM11776 is reported in event logs on a Windows server?
 Q3-2 What should I do when the host name is not fully displayed in the connection host?
 Q3-3 iSM11770 was reported in event logs (application) of the backup server when a nondisruptive backup using the
      VSS function was used.
 Q3-4 Are there any files that should be backed up before migrating the server enviornment or reinstalling the OS?
 Q3-5 The message iSM11773 or iSM11930 is reported in event logs (application) in the environment where
      ControlCommand/iSM Volume List Command is installed on VMware or the guset OS (Windows) of Hyper V.


4. Troubleshooting
 Q4-1 What should I do when the host IP address is not obtained successfully?
 Q4-2 The error message “iSMhoststore:103 Specified Disk Array does not exist” is reported when I specified the disk
      array name by using the -arrayname option of the command to store host information (iSMhoststore), and storing
      the host information failed. What should I do?
 Q4-3 The message iSM11718 or iSM11788 was reported when I collected host information by using iSM host agent
      service or the command to collect host information (iSMcc_hostinfo), and could not collect the HBA information.
      What should I do?
 Q4-4 I ran the command to collect host information (iSMcc_hostinfo) to create a host information file in a Linux server
      environment but the warning message iSM11718 or iSM11773 was reported, which resulted in failure of
      acquisition of host bus adapater (HBA) WWPN information (Host WWNN/WWPN). What should I do?


 Q1-1 What is iSM host agent service (service name: NEC Storage Manager Host Agent), which is installed on
      the Windows platform?
     A The iSM host agent service is a Windows service that can be used by installing the Volume List command
       or ControlCommand. This service can run independently on an application server (Windows) where iSM
       server is not installed.
       This service works together with the host information collection command (iSMcc_hostinfo) when the
       service is started or a logical disk of NEC Storage assigned to the application server is recognized, and
       collects the host name, OS identification information and host adapter (HBA) information of the installation
       server where the Volume List command or ControlCommand is installed to register the information with a
       disk array.
       iSM server obtains this information registered with the disk array to use it as the host information. The host
       information is registered only with the D series disk arrays that support the host information display.
 Q1-2 What are supported OSes?
     A The iSM host agent is listed in Storage Manager Volume List (iSMvollist). As for the support matrix of
     Storage Manager Volume List (iSMvollist), see the NEC Storage Manager Installation Guide.
Q2-1 Are there any patches or software programs that should be installed to use the host information collection
     function (the iSMcc_hostinfo command) or the iSM host agent service?
   A For Linux
       No. However, for use in the IA64 server environment, the following OS packages for 32 bit emulator or
       32 bit compatibility library must be already installed to allow 32 bit software programs to run.
            ia32el-XXXX.ia64.rpm
            glibc-XXXX.i686.rpm
            libtermcap-XXXX.i386.rpm
            bash-XXXX.i386.rpm
            e2fsprogs-XXXX.i386.rpm
                  (*) XXXX denotes package version


       These packages are contained in the following OS media. The packages should be installed in the order
       shown above because there is dependency among them.
            32-bit Compatibility Layer Common Binaries CD
            Extras CD
      For Windows
       SP1 or later must be installed if any of the following OSes is used.
           - Microsoft Windows Server 2003, Standard Edition (SP1, SP2)
           - Microsoft Windows Server 2003, Enterprise Edition (SP1, SP2)
           - Microsoft Windows Server 2003, Enterprise Edition for Itanium-based Systems (SP1, SP2)
Q2-2 When VMware ESX is used, is it possible to collect host information and configure the access control by
     using the host information?
   A VMware ESX allows for collecting host information by running the command to collect host information
     (iSMcc_hostinfo) on the service console, and configuring the access control based on the host information.
     However, VMware ESXi does not allow for collecting host information by running the command to collect
     host information (iSMcc_hostinfo) because it does not have the service console. VMware ESX4.0 does not
     allow for running the command to collect host information (iSMcc_hostinfo) provided in Ver6.1 or earlier.
     Because of these, the access control must be configured manually in VMware ESXi and VMware ESX4.0
     (when the command to collect host information is Ver6.1 or earlier) (*1).


      Follow the steps below to collect host information and configure the access control with VMware ESX. For
      information on configuring the access control, see Configuration Setting Tool User’s Manual (GUI). For
      information on collecting and registering host information, see Manual, NEC Storage Manager User’s
      Manual.
      1.    Log in the service console.
      2.    Install ControlCommand or the Volume List Command on the service control.
      3.    Run the command to collect host information (iSMcc_hostinfo) to collect host information and to
            report it as a host information file.
      4.    Transfer the host information file reported in step 3 to the management server where iSM server is
            running.
      5.    Run the command to store host information (iSMhoststore) to store the host information in a disk
            array.
      6.    Create an LD set by using the access control on the Configuration Setting screen of iSM client (Web
            GUI). Use the host information stored in step 5 to configure the settings to link LD set and path
            information. And then allocate logical disks to the LD set.
(*1) Collecting the VMware ESX host information (host name, HBA information, etc) by using CVI
     Perl Toolkit allows for creating a host information file based on the VMware ESX host information
     by a text editor or the like.


     Example
     I.     Install VI Perl Toolkit on a Windows server connected to VMware ESX over a network.
            Download VI Perl Toolkit from VMware’s web page.
     II.    Create a script
            Example of script:
     Script name:hostinfo.pl
     ------------------------------------------------
     #!/usr/bin/perl -w
     use strict;
     use warnings;
     use Math::BigInt;
     use VMware::VIRuntime;
     use VMware::VILib;
     Opts::parse();
     Opts::validate();
     Util::connect();
     (my $sec, my $min, my $hour, my $mday, my $mon, my $year, my $wday, my $yday, my
     $isdst) = localtime(time);
     my $yyyymmdd = sprintf("%04d-%02d-%02d", $year+1900, $mon+1, $mday);
     my $hhmmss = sprintf("%02d:%02d:%02d", $hour, $min, $sec);
     print "<websamexport>" . "\n";
     my $host_views = Vim::find_entity_views(view_type => 'HostSystem');
     foreach my $host_view (@$host_views) {
            my $hostname = $host_view->name;
            print "\t". "<class name=\"iSM_NodeInfo\">" . "\n";
            print "\t\t". "<property name=\"OwnerHostName\" " . "value=\"$hostname\"" .
            "></property>" . "\n";
            print "\t\t". "<property name=\"HostInfoDate\" " . "value=\"$yyyymmdd $hhmmss\"" .
            "></property>" . "\n";
            print "\t\t". "<property name=\"OSType\" " . "value=\"36\"" . "></property>" . "\n";
            my $consolevnics = $host_view->config->network->consoleVnic;
            foreach my $consolevnic (@$consolevnics) {
                    my $ipaddress = $consolevnic->spec->ip->ipAddress;
                    print "\t\t". "<property name=\"IPAddress\" " . "value=\"$ipaddress\"" .
                    "></property>" . "\n";
            }
            print "\t\t". "<property name=\"AddressType\" " . "value=\"1\"" . "></property>" . "\n";
            print "\t\t". "<property name=\"SystemName\" " . "value=\"$hostname\"" . "></property>" .
            "\n";
            print "\t\t". "<property name=\"PCDBVersion\" " . "value=\"1.0\"" . "></property>" . "\n";
            print "\t". "</class>" . "\n";
       my $hbas = $host_view->config->storageDevice->hostBusAdapter;
       foreach my $hba (@$hbas) {
               if ($hba->isa("HostFibreChannelHba")) {
                         my $BigVal = Math::BigInt->new($hba->nodeWorldWideName);
                         my $wwnn = $BigVal->as_hex();
                         $wwnn = substr($wwnn, 2);
                         $wwnn = uc $wwnn;
                         $wwnn = "0000000000000000" . $wwnn;
                         $wwnn = substr($wwnn, ((length $wwnn) -16));
                         print "\t". "<class name=\"iSM_HBAInfo\">" . "\n";
                         print "\t\t". "<property name=\"WWNN\" " . "value=\"$wwnn\"" .
                         "></property>" . "\n";
                         print "\t\t". "<property name=\"SystemName\" " . "value=\"$hostname\"" .
                         "></property>" . "\n";
                         print "\t\t". "<property name=\"PCDBVersion\" " . "value=\"1.0\"" .
                         "></property>" . "\n";
                         print "\t". "</class>" . "\n";
                         $BigVal = Math::BigInt->new($hba->portWorldWideName);
                         my $wwpn = $BigVal->as_hex();
                         $wwpn = substr($wwpn, 2);
                         $wwpn = uc $wwpn;
                         $wwpn = "0000000000000000" . $wwpn;
                         $wwpn = substr($wwpn, ((length $wwpn) -16));
                         print "\t". "<class name=\"iSM_FCPortInfo\">" . "\n";
                         print "\t\t". "<property name=\"WWNN\" " . "value=\"$wwnn\"" .
                         "></property>" . "\n";
                         print "\t\t". "<property name=\"WWPN\" " . "value=\"$wwpn\"" .
                         "></property>" . "\n";
                         print "\t\t". "<property name=\"SystemName\" " . "value=\"$hostname\"" .
                         "></property>" . "\n";
                         print "\t\t". "<property name=\"PCDBVersion\" " . "value=\"1.0\"" .
                         "></property>" . "\n";
                         print "\t". "</class>" . "\n";
               }
       }
}
print "</websamexport>" . "\n";
Util::disconnect();
------------------------------------------------
III.   Open the command prompt of VI Perl Toolkit.
       From the Start menu, select Programs, VMware, VMware VI Perl Toolkit, and
       Command Prompt to start Command Prompt.
IV.    Execute the script.
       >perl hostinfo.pl -server (IP address of VMware ESX)
       Enter username: root
                      Enter password:
                V.    Create a host information file by copying the image of the host information file, which is
                      reported in the standard output, to a text editor.

                You can configure the access control by performing steps 4 to 6 after creating the host
                information file.
                For information on creating a host information file, see “Sample host information file (when
                described to the minimum)” in “Host Information File” of Manual, NEC Storage Manager User’s
                Manual.
Q3-1 What should I do when the message iSM11771 or iSM11776 is reported in event logs on a Windows
     server?
   A Source               : iSMcc_hostinfo
     Event ID             : 11771
     Type                 : Information
     Message              : iSM11771: Target device does not exist. (code=---)


            => The message tells nothing was performed because the target disk array device did not exist
               when the iSM host agent service was executed or the command to collect host information
               (iSMcc_hostinfo) was executed on the command line. You do not need to take any action for this
               message.


     Source               : iSMcc_hostinfo
     Event ID             : 11776
     Type                 : Warning
                              iSM11776: Hostname in Host Information is truncated.(Disk Array= Host=)
     Message              :
                              (code=---)


            => The message tells the 33rd and the following characters of the host name registered as the host
               information have been truncated when the iSM host agent service was executed or the
               command to collect host information (iSMcc_hostinfo) was executed on the command line
               because the host name was longer than 32 characters. This message is reported for a host
               name longer than 32 characters when the host information was registered for the first time.
               You do not need to take any particular action for this message but the host name may overlap
               with a registered host name.
               If you want to rename the host name you registered that has more than 32 characters, change
               the host name in the host information file (OwnerHostName properties of the iSM_NodeInfo
               table) reported by using the –export option of the iSMcc_hostinfo command, and then re-register
               the host information by using that host information file.
               Make sure the re-registered host information is not overwritten and registered by the original
               host name in your operation hereafter.
Q3-2 What should I do when the host name is not fully displayed in the connection host?
   A Up to 32 characters can be registered for a host name with a disk array. A host name longer than 32
     characters is not shown fully.
     To rename a host name in the registered host information, change the host name in the host information
     file reported by using the –export option of the iSMcc_hostinfo command (OwnerHostName properties of
     the iSM_NodeInfo table), and then re-register the host information by using that host information file (by
     running the command to store host information, iSMhoststore).
     Make sure the re-registered host information is not overwritten and registered by the original host name in
     your operation hereafter.
Q3-3 iSM11770 was reported in event logs (application) of the backup server when a nondisrputive backup using
     the VSS function was performed.
   A The following message may be reported in event logs (application) due to the iSM host agent service in
     ControlCommand Ver5.1 or later. The message does not affect VSS backup.

          Event type                 : Information
          Event source               : iSMcc_hostinfo
          Event ID                   : 11770
          Message                    : iSM11770: Host Information was exported successfully.

     If it is not necessary to automatically collect and register host information by the iSM host agent service for
     your operation, you can stop it.
     If you do not want the iSM host agent service to be automatically restarted with system restart, click Start
     and All Programs, and select NEC Storage Manager Host Agent in Administrative Tools. Change the
     startup type from automatic to manual.
Q3-4 Are there any files that should be backed up before migrating the server environment or reinstalling the
     OS?
   A When the host information is collected for the first time, the host agent generates an ID to identify
     application server and saves it in a file. Because of this, back up the following files and restore them in the
     target environment.


      ■Windows
          %CommonProgramFiles%\NEC\WebSAM\Framework\.WebSAMUMFID
          (Example:C:\Program Files\Common Files\NEC\WebSAM\Framework\.WebSAMUMFID)


          For 64-bit OS
          %CommonProgramFiles(x86)%\NEC\WebSAM\Framework\.WebSAMUMFID
          (Example:C:\Program Files(x86)\Common Files\NEC\WebSAM\Framework\.WebSAMUMFID)


      ■Linux
          /var/opt/WebSAM/Framework/.WebSAMUMFID


      If the files mentioned above are not backed up and restored, a new ID for application server identification
      is created when host information is collected/registered, which can result in one host having host
      information registered more than once. If this occurs, check details of the host information and collection
      dates on iSM client (Web GUI) and remove unnecessary host information.
Q3-5 The message iSM11773 or iSM11930 is reported in event logs (application) in the environment where
     ControlCommand/Volume List Command is installed on VMware or the guest OS (Windows) of Hyper-V.
   A When ControlCommand/Volume List Command is installed on a Windows environment and the system is
     restarted or logical disks are allocated, the iSM host agent service automatically collects HBA information.
     You may see one of the following messages on a guest OS because the HBA information is not
     recognized in such OS.


      Event type               : Warning
      Event source             : iSMcc_hostinfo
      Event ID                 : 11773
      Message                  : iSM11773: Information collection was skipped. (Host WWNN/WWPN)
                              (code=<ccc...c>-<ddd...d>-<ddd...d>-<ddd...d>)


     Event type               : Warning
     Event source             : iSMcc_hostinfo
     Event ID                 : 11930
     Message                  : iSM11930: Host Information was exported without Host WWNN/WWPN.
                              (code=<ccc...c>-<ddd...d>-<ddd...d>-<ddd...d>)
        *   ccc...c … process number, ddd...d … details


     These messages do not affect the operation. However, when the Windows environment is used as a
     guest OS, stop the iSM host agent service to prevent unnecessary events from being reported. To prevent
     the iSM host agent service from being automatically started with system restart, click Start and All
     Programs, and select NEC Storage Manager Host Agent in Administrative Tools. Change the startup
     type from automatic to manual.
Q4-1 What should I do when the host IP address is not obtained successfully?
   A In a circumstance where multiple application server IP addresses are registered such as clustered server
     configuration, the server IP address collected by the command to collect host information
     (iSMcc_hostinfo) or the iSM host agent service is the IP address returned by the OS on a priority basis.


     If the IP address registered as the host information is not what you intended, it can be changed by
     registering another IP address by following the procedures below. For details about command functions
     and host information file, see NEC Storage Manager User’s Manual.


      1. If the application server is Windows, stop the iSM host agent service and change the startup type
         from automatic to manual.
      2. Create a host information file by using the -export option of the command to collect host information
         (iSMcc_hostinfo).
      3. Edit the reported host information file by using a text editor or the like to modify the IP address (where
         “IPAddress” is). Describe the value of the IP address you want to register as the host information.
      4. Send the updated host information to the server on which iSM server is running and register it by
         using the command to register host information (iSMhoststore).
     Check that the intended IP address is shown in the Connected Host list screen in iSM client (Web GUI).


     If multiple network adapters are installed on a Windows application server and multiple connections are
     configured, you can collect the intended IP address by changing the connection priority. Note that the
     change of the priority may impact applications being used. Before you change the priority, make sure it
     will not impact the system.


     How to change the connection priority
      1. In Control Panel, select Network Connections.
      2. On the Advanced menu, click Advanced Settings.
      3. On the Adapters and Bindings tab, select the IP address connection to which you want to assign
         top priority, and move it to the top by using the arrow button.
      4. Click OK to close Advanced Settings.
     Restart the iSM host agent service and check the intended IP address is displayed in the Connected Host
     list screen of iSM client (Web GUI) after three minutes.
Q4-2 The error message, “iSMhoststore:103 Specified Disk Array does not exist” is reported when I specified the
     disk array name by using the -arrayname option of the command to store host information (iSMhoststore),
     and storing the host information failed. What should I do?
   A Correct the host information file by one of the following ways and then re-execute the command to store
     host information.
          - Remove the iSM_ArrayInfo table description except for the description corresponding to the disk
            array specified by the –arrayname. In this case, information on “ports on disk array” is not registered.
          - Add the iSM_ArrayInfo table and the SM_FCConnectionInfo table descriptions that correspond to the
            disk array specified by the –arrayname option.
Q4-3 The message iSM11718 or iSM11788 was reported when I collected host information by using iSM host
     agent service or the command to collect host information (iSMcc_hostinfo), and could not collect the HBA
     information. What should I do?
   A See the host agent FAQ Q1-2 for introduction and Q2-1 for installation to check whether the server satisfies
     the operating requirements of host agent (OS, required patches, additional components, etc.).
     If the FC cable connection has been changed, restart the server and collect the host information.
Q4-4 I ran the command to collect host information (iSMcc_hostinfo) to create a host information file in a Linux
     server environment but the warning message iSM11718 or iSM11773 was reported, which resulted in
     failure of acquisition of host bus adapter (HBA) WWPN information (Host WWNN/WWPN). What should I
     do?
   A Example of reported warning message (for iSM11718)
          iSM11718: Failed to get information. (Host WWNN/WWPN)


      Example of reported warning message (for iSM11773)
          iSM11773: Information collection was skipped. (Host WWNN/WWPN)


      Refer to the user’s guide attached to the HBA to check the WWPN value of the HBA.
      Manually entering the WWPN value of the HBA that has been confirmed in the settings of Linking an LD
      set and Path in the access control configuration allows for allocating logical disks to a host.


      However, a host information file containing the WWPN information of the HBA is necessary in the
      following cases.
      -   When the host information is used to configure the link settings of LD set and path for the access
          control of the configuration settings.
      -   When the host information is used for quick configuration of logical disks in configuration settings.
      -   When you want to display and confirm the information on HBA List or Disk array Port in Connected
          host detail information screen.


      In these cases, add the WWPN information of the HBA you have confirmed by using a text editor or the
      like to the host information file to store the host information.
      For details about host information files, see NEC Storage D series manual, NEC Storage Sortwqare NEC
      Storage Manager User’s Manual (UNIX) or NEC Storage Sortwqare NEC Storage Manager User’s
      Manual (Windows).
Storage Control

DynamicDataReplication, RemoteDataReplication
1. Introduction
     Q1 How can I use the data replication function?


2. Operation
     Q2 How can I check copy progress during replicate?
     Q3 On the replication management window in iSM client, can I see only the list of volumes paired on the volume
        list window?
     Q4 What does "Outside iSM Management" on the iSM client replication management window represent?
     Q5 Can I perform separate during replicate?
     Q6 When Windows Server 2003 or Windows Server 2008 was launched, a message informing that volumes
        paired by the replication function have duplicated disk signatures appeared as an event log. Why did it occur?
     Q7 Why is operation in which MV and RV are in Separate (separate operation) recommended?
        Are there any notes on operating MV and RV in Replicate and Synchronous mode (replicate operation)?


3. Troubleshooting
     Q8 A disk array I want to operate does not appear on the replication management window in iSM client. How can I
        see it?
     Q9 When I attempted to open the replication window in iSM client, the error "02048" occurred.
    Q10 When I opened the connection window by selecting volumes (MV/BV, RV/BV) related to snapshot on the
        replication management window in NEC Storage Manager Ver4.1or later, snapshot volumes (SV and LV) did
        not appear on the connection screen. What should I do?
    Q11 I mistakenly terminated ongoing ATgroup replication by using the task manager on the replication
        management window in iSM client. Then the following statuses have remained as below:

          - ATgroup Sync State: Replicate

          - Configured pairs Sync State: Has not changed because synchronization has stopped in the middle of pair
        operation.

        What should I do?


     Q1 How can I use the data replication function?
      A You can create a volume (logical disk) replica by using the data replication function. Activate the replication
        management function in iSM client and define a pair of a source volume and a destination volume. With the
        replication management function, you can create or restore a replication volume or manage the copy status of
        pairs through GUI on a screen. On the application server, you can use ReplicationControl as well as the task
        control function to unmount a volume, establish a static point, and then create a replica for backup or restore a
        volume using a replica.
     Q2 How can I check copy progress during replicate?


      A In iSM client, select a volume to check and display the connection window through a menu. In
        ReplicationControl, use the iSMrc_query command to check the replication status.
     Q3 On the replication management window in iSM client, can I see only the list of volumes paired on the volume
        list window?
      A Yes.
         On the iSM client replication management window, select IV display or non-display through the IV Display
    menu.

Q4 What does "Outside iSM Management" on the iSM client replication management window represent?
 A It represents a disk array which is not connected to the iSM server. You cannot configure a disk array that is
   not managed by iSM.
Q5 Can I perform separate during replicate?
 A Yes.
    When separate is performed during replicate, difference in MV that has been made until separate is
    requested is reflected to RV. There are two types of separate. With general separate, RV cannot be used
    from when separate is requested until the separate is complete (while difference in MV is reflected). With
    Separate (immediate), RV to which difference in MV is reflected can be used right after separate is requested.
    Separate (immediate) is supported by DynamicDataReplication Ver2 or later.
Q6 When Windows Server 2003 or Windows Server 2008 was launched, a message informing that volumes
   paired by the replication function have duplicated disk signatures appeared as an event log. Why did it occur?
 A After a volume was copied by replicate or restore, the signature of the copy destination volume may not have
   been restored to the original that had been used before the copy and the paired volumes (MV and RV) may
   have the same signature.
   If OS is restarted under this circumstance, a message informing that MV and RV have duplicated disk
   signatures will appear as an event log and the signature will be forcibly rewritten.
   The reason why the signature of a copy destination volume is not restored to the original after replicate/restore
   on Windows Server 2003 or Windows Server 2008 is that the disk format of the volume is GPT (GUID partition
   table).
   The data replication function rewrites the signature of RV to the original that had been used before copy when
   volumes (use type is "WN") in the MBR (master boot record) format supported by Windows are separated, so
   that the signatures of MV and RV will not be identical. However, the data replication function does not rewrite
   the signature of paired volumes (use type is "WG") in the GPT (GUID partition table) format.
   Note that when MV and RV in the GPT (GUID partition table) format are assigned to the same server or more
   than one RV paired with the same MV are assigned to the same server, signature duplication occurs and the
   disk becomes disabled.

   To prevent such problem, check the disk format and if the format is GPT, change (format) it to MBR.
Q7 Why is operation in which MV and RV are in Separate (separate operation) recommended?
   Are there any notes on operating MV and RV in Replicate and Synchronous mode (replicate operation)?
 A The separate operation has the following advantages:
       - Previous backup data in which consistency and static points are kept can be stored in RV.
       - Even if inconsistency is made in MV data due to an operation error or logical failure, etc., the backup
         data of RV will be protected.
       - RV can be used for purpose other than backup (ex. secondary use).
       - A low-cost large-capacity disk (SATA) or a disk of the RAID type (RAID5 or RAID6) with high capacity
         efficiency can be used as RV.
       - The size of cache assigned to RV by the CachePartitioning function can be set to the minimum.


    Note the following for replication operation:
       - Because update in MV is constantly reflected to RV, static points are not kept in the backup data of RV.
       - If inconsistency is made in MV data due to an operation error or a logical failure, the data cannot be
         restored from RV (using tape, etc. is required).
       - If a cache failure, etc. occurs, data may not be restored from RV because it is difficult to ensure data
         integrity (restoration using tape, etc. is required).
       - To secure performance of operations using MV, RV and MV need to have the same configuration
         (physical disks, RAID type). The size of cache assigned to RV by the CachePartitioning function needs to
         be equal to the size assigned to MV.




 Q8 A disk array I want to operate does not appear on the replication management window in iSM client. How can I
    see it?
  A Have you purchased data replication products? From the main window, access the Disk Array Subsystem
    detail information window to check the products you have purchased.
 Q9 When I attempted to open the replication window in iSM client, the error "02048" occurred.
  A If the error "02048" appears in the dialog box when you open the replication window in iSM client, check the
    following:

    To use the replication function, you need to purchase DynamicDataReplication or RemoteDataReplication and
    unlock the license. See License on the Disk Array Subsystem detail information window in iSM client to check
    if the license has been unlocked. If the license has not been unlocked, do one of the following:


     (a) When NEC Storage S2100, S2200, S3100, or S4100 is used
         Contact your maintenance staff to request unlocking.
     (b) When NEC Storage 2000 series, 2800 series, 3000 series or 4000 series excluding NEC Storage D1
         series, D3 series, D4 series, D8 series, S1400, S1500, and series indicated in (a) above is used
         Use the iSM unlock function to unlock the license.
Q10 When I opened the connection window by selecting volumes (MV/BV, RV/BV) related to snapshot on the
    replication management window in NEC Storage Manager Ver4.1or later, snapshot volumes (SV and LV) did
    not appear on the connection screen. What should I do?
  A If a processing request is issued for a disk array that is about to become failed status due to termination of a
    remote disk array or a link failure, processing may be delayed in the disk array depending on the timing of the
    request issue and the processing request may time out.
    In such case, remote volumes are not displayed on the connection window because it assumes that volumes
    whose information has not been obtained due to an error do not exist.
    If this symptom occurs, check the disk-array operation status and remove the failure that has caused the error.
    Then reconnect NEC Storage Manager for restoration.
Q11 I mistakenly terminated ongoing ATgroup replication by using the task manager on the replication
    management window in iSM client. Then the following statuses have remained as below:
       - ATgroup Sync State: Replicate
       - Configured pairs Sync State: Has not changed because synchronization has stopped in the middle of pair
    operation.
    What should I do?
  A Perform replication for this ATgroup again to replicate the remaining pairs.
Storage Control

DynamicSnapVolume
1. Introduction
    Q1-1 What kind of function the snapshot is?
    Q1-2 For what a replication volume created by the snapshot function is used?
    Q1-3 What is the difference from the data replication function?
    Q1-4 Can I use the snapshot function together with the data replication function?


2. Installation
    Q2-1 Which storage devices do support the snapshot function?
    Q2-2 How many snapshot generations can I create?
    Q2-3 What is the condition for creating a snapshot volume?
    Q2-4 What can I do with the snapshot reserve area?
    Q2-5 What kind of volume a control volume is?
    Q2-6 Is there any other software necessary for installing NEC Storage DynamicSnapVolume?


3. Operation
    Q3-1 Are there any notes on using snapshot?
    Q3-2 Are there any notes on using snapshot in iSM client?
    Q3-3 Are there any notes on creating/deleting a snapshot?
    Q3-4 The size of used snapshot was 0.0GB after snapshot creation. Is this correct?
    Q3-5 Though I clicked Cancel during Snapshot Deletion, a snapshot was deleted. Why did it happen?
    Q3-6 How can I check that a snapshot has been deleted or restoration has been completed?
    Q3-7 What may happen if the snapshot reserve area (SRA) is insufficient?
    Q3-8 Where can I monitor the use of the snapshot reserve area (SRA)?
    Q3-9 How can I return an icon changed when a snapshot was released to the original (normal)?
   Q3-10 What kind of function is the threshold monitoring function for snapshot used capacity?
   Q3-11 After I created a snapshot of a volume used on Windows Server, snapshot difference was generated while no
         data was written. Why did it happen?
   Q3-12 What will happen if I attemt to create a snapshot cyclically while an oldest-generation SV is being linked?


4. Troubleshooting
    Q4-1 A disk array I want to operate does not appear on the snapshot management screen in iSM client. How can I
         see it?
    Q4-2 When I attempted to open the snapshot management screen in iSM client, the error "08000" occurred.
    Q4-3 How can I handle a master volume failure?
    Q4-4 A time-out occurred on the snapshot management screen. What should I do?


    Q1-1 What kind of function the snapshot is?
       A The snapshot function provides a low-cost non-disruptive backup solution that creates a volume (logical disk)
         replica at some point (snapshot) and manages the difference made in the volume.
         With the snapshot management function, you can replicate or restore a volume, or manage the statuses of a
         source volume and a destination volume through GUI on a screen. On the application server, you can use
         SnapControl as well as the task control function to create a replication volume for backup or restore a
         replication volume.
    Q1-2 For what a replication volume created by the snapshot function is used?
   A A replication volume can be used as backup data and data can be backed up from a replication volume to a
     magnetic tape. When a replication volume is a database, it can be used for search separately from a master
     volume. Also a test environment can be built up by using a replication database that provides the same or
     similar data for production environment.
Q1-3 What is the difference from the data replication function?
   A The major difference between the data replication function and the snapshot function is the following:
         - Data replication
          Replication volumes are physically independent, providing higher performance and reliability than
          snapshot when the replication volume is used.
          This function suits for operation using replication volumes where high performance and reliability are
          required and for backup operation.


         - Snapshot
          Replication by using snapshot requires only difference data capacity, achieving lower capacity cost than
          when data replication is used.
          This function suits for operation where storage capacity cost needs to be reduced.
Q1-4 Can I use the snapshot function together with the data replication function?
   A The snapshot function and the data replication function can be used together for operations such as the
     following:
      <Creating replica>
              - Stores replicated data in a replication volume for long period of time (ex. for one day) using data
                replication and backs up data periodically from the backup server to an external media.
              - Uses snapshot to create snapshots on a short term cycle (ex. one hour).


      <Advantage of using these functions together>
              - Creating snapshots on a short term cycle to maintain the latest image minimizes impact of a logical
                failure (restoration from snapshot by using Restore).
              - Using data replication to create replicas on a long term cycle allows for quick recovery from a
                physical failure (restoration from replica by using Restore)
              - Using physically-independent replication volumes of data replication for backup to a tape reduces
                impact of backup on master volumes.
Q2-1 Which storage devices do support the snapshot function?
   A The following NEC Storage series support the snapshot function:
         - NEC Storage D8-30
         - NEC Storage D8-20
         - NEC Storage D8-10
         - NEC Storage D4-30
         - NEC Storage D3-10i
         - NEC Storage D3-10
         - NEC Storage D1-10
         - NEC Storage S4900
         - NEC Storage S2900
         - NEC Storage S2800
         - NEC Storage S2500
         - NEC Storage S2400
         - NEC Storage S1500
         - NEC Storage S1400
Q2-2 How many snapshot generations can I create?
   A Up to 16 generations can be created per master volume.
Q2-3 What is the condition for creating a snapshot volume?
   A Snapshot volumes can be created only on a dynamic pool.
     Master volumes can be created on any type of pool and RAID.
Q2-4 What is the snapshot reserve area?
   A Update difference data required for maintaining snapshots are stored in the snapshot reserve area.
     Sufficient capacity is required for using snapshot.
     If capacity is insufficient, snapshot will not work. Monitor capacity to keep it sufficient. You can configure the
     threshold monitoring function of NEC Storage Manager to set a threshold for capacity use and to receive/see
     a mail or a log (syslog/event log) message when the use exceeds the threshold. You can monitor the capacity
     use also on an iSM client window.
Q2-5 What kind of volume a control volume is?
   A When a server uses a snapshot volume by using NEC Storage SnapControl, a volume constantly connected
     to the server is required for allowing the server to control the disk array. This volume is called control volume.
     One control volume is required per server that uses (mounts) snapshot and needs to be configured when the
     system is installed.
     Set a volume that will not be used for data replication or snapshot as a control volume.
     Do not store task data in a control volume. It should be exclusively used for the purpose mentioned above.
Q2-6 Is there any other software necessary for installing NEC Storage DynamicSnapVolume?
   A The following software is required for installing NEC Storage DynamicSnapVolume:
         - NEC Storage BaseProduct
         - NEC Storage AccessControl
         - NEC Storage SnapControl


     It is recommended to purchase the following product to handle I/O path failures that may occur on a
     application server:
         - NEC Storage PathManager
Q3-1 Are there any notes on using snapshot?
   A Note the following:
         - Purchasing products
          Purchase products required for using snapshot. You can check purchased products on the Disk Array
          Subsystem detail information window of NEC Storage Manager.
         - Access Control function
          Be sure to enable the Access Control function.
          When the Access Control function is disabled, all volumes in the storage can be accessed by the server.
          Because of this, when the server starts, it takes time to recognize volumes (ex. snapshot volumes) that
          cannot be accessed by the server, which may cause delay in the server start.
         - Configuring Access Control
          Configure Access Control so that the application server and the backup server can only see the volumes
          they want to access, and so that a base volume and the link volume linked with the base volume cannot
          be accessed by the same server.
         - Monitoring snapshot reserve area (SRA)
          If the snapshot reserve area is insufficient, snapshot will not work. Monitor the area to keep it sufficient.
          You can configure the threshold monitoring function to set a threshold for area use and to notify an
          administrator of crossing a threshold by using a mail, a log (syslog/event log) message, or display on an
          iSM client window.
Q3-2 Are there any notes on using snapshot in iSM client?
   A Check volume operation on the application server.
     Before performing snapshot, be sure to unmount volumes and then check that the data on the cache memory
     in the server has been updated by the volumes.
     While a link is set for a base volume, the base volume cannot be accessed. Do not access a base volume
     during link setting.
Q3-3 Are there any notes on creating/deleting a snapshot?
   A It may take time to delete a snapshot depending on the disk-array performance, the generation to be deleted,
     or the amount of difference.
     If snapshot creation or cyclical creation is performed before an old snapshot to be updated is deleted, the old
     snapshot will be deleted and then a new snapshot will be created, which may result in long processing time
     taken for snapshot creation and static-point establishment (including time when the task stops).
     Because of this, for backup scripts, etc., it is recommended to delete old snapshots beforehand by following
     the operation procedures described in a manual or a guidebook.
     Also when the snapshot management window is used, it is recommended to delete old snapshots before
     snapshot creation or cyclical creation.
     Especially for SnapControl that operates in cooperation with NEC Storage Manager or the snapshot
     management window operation, if snapshot creation or cyclic creation is performed before old snapshots are
     deleted, the creation may time out. Even if a time-out occurs, processing will continue on the iSM server and a
     message corresponding to operation will appear on the iSM server operation log window and in the message
     display area on the iSM client main window. When a time-out occurs, stop your operation and wait for the
     following message showing that snapshot creation is complete:

       iSM18001: Snapshot has been created...

     Messages appear in iSM client while it is connected to an iSM server. If a snapshot is created with iSM client
     not connected to an iSM server or iSM client is disconnected from an iSM server during snapshot creation,
     check the messages on the iSM server operation log window.
     A script created by ReplicationNavigator Suite has followed a recommended procedure and no special
     consideration is required for the script.

            (For your Snapshots are deleted approximately at the following speed (but it may vary depending on
           reference) the amount of difference):
                                   Series                      Snapshot deleting speed
                                  D series                        Approx. 500 MB/S
                                  S series                        Approx. 600 MB/S

Q3-4 The size of used snapshot was 0.0 GB after snapshot creation. Is this correct?
   A The size of used snapshot is 0 right after snapshot creation because difference made by base-volume update
     is recorded with a snapshot.
Q3-5 Though I clicked Cancel during Snapshot Deletion, a snapshot was deleted. Why did it happen?
   A [Ver3.3 or later]
          Clicking Cancel can stop processing, but cannot stop deleting a snapshot once it starts to get deleted.


     [Ver3.2]
          The dialog displayed during Snapshot Deletion prompts you to wait for deletion to be completed. When
          you click Cancel, the processing proceeds to the next step before the deletion is complete. If you do not
          need to wait for deletion to be completed, you can cancel the waiting and move to the next process.
          To consecutively delete snapshots configured on the same base volume, wait for the deletion of a
          previous snapshot to be completed.
Q3-6 How can I check that a snapshot has been deleted or restoration has been completed?
    A Check status changes in the Information list display area on the snapshot management window. You can also
      check restore progress by seeing changes in difference made by the restore.
 Q3-7 What may happen if the snapshot reserve area (SRA) is insufficient?
    A If the snapshot reserve area (SRA) that stores update difference for a base volume, snapshots will not work
      and will be discarded. Then the oldest generation snapshots of the updated base volume will be automatically
      deleted regardless of whether the snapshots have been protected or link settings.
      To prevent such problem, use the threshold monitoring function to monitor the use of SRA. You can configure
      the function to notify an administrator of crossing a threshold by using a mail, a log (syslog/event log)
      message, or display on an iSM client window.
      An administrator needs to expand SRA or delete unnecessary snapshots to prevent the area from being
      insufficient.
 Q3-8 Where can I monitor the use of the snapshot reserve area (SRA)?
    A You can configure the threshold monitoring function of NEC Storage Manager to set a threshold for the area
      use and to notify an administrator of crossing a threshold by using a mail or log (syslog/event log) message.
      You can also check the use on an iSM client window.
 Q3-9 How can I return an icon changed when a snapshot was released to the original (normal)?
    A Create a new snapshot to restore the original (normal) icon.
Q3-10 What kind of function is the threshold monitoring function for snapshot used capacity?
    A This function monitors snapshot used capacity and alarms an administrator before capacity becomes
      insufficient due to the snapshot used capacity. By using NEC Storage Manager, you can set a threshold for
      the use and configure the setting to notify an administrator of crossing a threshold by using a mail or log
      (syslog/event log) message. You can also monitor the use on an iSM client window.
Q3-11 After I created a snapshot of a volume used on Windows Server, snapshot difference was generated while no
      data was written. Why did it happen?
    A To access snapshot data, the corresponding snapshot volume needs to be linked to a link volume. When a
      snapshot volume on Windows Server is linked, the disk signature is moved and restored by the storage
      control. This control makes snapshot difference.
Q3-12 What will happen if I attempt to create a snapshot cyclically while an oldest-generation SV is being linked?
    A Note that when snapshots have been created for all SVs and an oldest-generation SV is linked to LV, cyclic
      creation using SnapControl acts differently from cyclic creation using iSM client.
          - Snapshot creation fails in cyclic creation using SnapControl.
          - In snapshot cyclic creation using iSM, a snapshot is created for SV which is the oldest among not-linked
            SVs.
            Cyclic creation using SnapControl operated in cooperation with NEC Storage Manager acts the same as
            creation using iSM.
 Q4-1 A disk array I want to operate does not appear on the snapshot management window in iSM client. How can I
      see it?
    A Have you purchased the snapshot product (DynamicSnapVolume)? From the main window, access to the
      Disk Array Subsystem detail information window to check the products you have purchased.
 Q4-2 When I attempted to open the snapshot management window in iSM client, the error "08000" occurred.
    A If the error "08000" appears in the dialog box when you open the snapshot management window in iSM client,
      check the following:

      To use the snapshot function, you need to purchase DynamicSnapVolume and unlock the license. See
      Product Status on the Disk Array Subsystem detail information window in iSM client to check if the license
      has been unlocked. If the license has not been unlocked, use the license unlock function of iSM.
 Q4-3 How can I handle a master volume failure?
    A Use NEC Storage SnapControl to restore the master volume. The action you should to take depends on the
      failure details:
         ■ An operation error by a user, an abnormal end of application, etc. has disabled data.
         [Action to take] Restore created snapshots to BV to restore the master volume (BV).
       ■ Data files of BV or volumes of BV cannot be accessed.
         [Action to take] Restore the master volume (BV) by using a backup such as a tape.


     For more details about the restoration procedure, see "Measures for Errors" in Snapshot User's Manual
     (Installation and Operation).
Q4-4 A time-out occurred on the snapshot management window. What should I do?
   A When snapshot creation or cyclic creation is performed on the snapshot management window (including the
     snapshot management window of another iSM client connected to the same server) or using SnapControl
     (when it is operated in cooperation with NEC Storage Manager), a time-out may occur.


     For notes on creating a snapshot, see Q3-3.


     Even if a time-out occurs due to snapshot creation or cyclic creation, processing will continue in the iSM
     server and a message corresponding to operation will appear on the iSM server operation log window or in
     the message display area on the iSM client main window. When a time-out occurs, stop your operation and
     wait for a message to be displayed.
     If the time-out is not due to snapshot creation or cyclic creation, check the server status, perform Refresh,
     and start your operation again.
Storage Management

PerformanceMonitor
1. Installation
    Q1-1 I installed iSM client, but the Performance Monitoring window does not appear. What should I do?
    Q1-2 How long is the logging interval for statistic information?
    Q1-3 Are there any notes on using the NEC Storage Performance Report Viewer?
    Q1-4 I purchased NEC Storage PerformanceMonitor. How can I configure it?
    Q1-5 How can I enable the function to automatically collect statistic information?
    Q1-6 How can I enable the function to set the keep period of statistic information and automatically delete files
         whose keep period has passed?
    Q1-7 The accumulation of statistic information did not start automatically. What is the possible cause?


2. Operation
    Q2-1 How can I set a threshold for statistic information?
    Q2-2 Right after the Performance Monitoring window is activated, a line does not appear on a time-series graph
         though the numeric table shows values. What should I do?
    Q2-3 A disk array shown on the iSM client main window does not appear on the Performance Monitoring window.
         What should I do?
    Q2-4 What is the difference between the direct secondary summarizing and the secondary summarizing in NEC
         Storage PerformanceMonitor?
    Q2-5 In what environment can I edit the NEC Storage PerformanceMonitor statistic information?
    Q2-6 How does NEC Storage PerformanceMonitor save statistic information?
    Q2-7 How can I start accumulating statistic information?
    Q2-8 "-" (hyphen) is displayed for the READ hit ratio/WRITE hit ratio/BUSY ratio on the Performance Monitoring
         window.
    Q2-9 Are there any notes on changing a statistic information storage folder?
   Q2-10 I specified one month as the keep period in the statistic information setting. With this setting, what
         time-stamps do the files to be deleted exactly have?
   Q2-11 Can I execute the performance analysis supporting tool directly for a statistic information history file stored in
         the storage folder I specified in the NEC Storage Manager environment setting?


3. Troubleshooting
    Q3-1 Though a disk array is monitored on the iSM client main window, the Performance Monitoring window shows
         that monitoring the disk array performance has been stopped. What should I do?
    Q3-2 When I added LD/PD to monitoring targets on the Performance Monitoring window, the following dialog
         appeared and I failed to add them. What should I do?
         03405 Error because of too many monitoring objects. Return to the status before the processing.
    Q3-3 When I upgraded PerformanceMonitor from Ver3.4 (or earlier) to Ver4.1 (or later), the output interval for
         statistic information was changed. What should I do?
    Q3-4 Since I configured the environment setting to automatically accumulate statistic information and restarted iSM
         server, statistic information has not been accumulated.
    Q3-5 Though I upgraded iSM server from Ver3.4 (or earlier) to Ver4.1 (or later) and set the keep period for statistic
         information, the statistic information reported by the old (Ver3.4 or earlier) iSM server was not deleted
         automatically.
    Q3-6 When I converted a statistic information history file by using the CSV conversion command (iSMprfext
         command), "iSMprfext:011" was reported showing that the number of recorded CSV files is over 65536. How
         can I estimate the number of CSV files that can be recorded so that I will be able to adjust the number of files
         to convert.
Q3-7 When any option other than Smaller - 100%(default)(S) is selected on the Display dialog box, which is
     opened by selecting Control Panel and Design, on Windows Server 2008 R2 or Windows7, display is
     distorted or mouse operation is disturbed. What should I do?


Q1-1 I installed iSM client, but the Performance Monitoring window does not appear. What should I do?
   A If you installed iSM client Ver3.4 or earlier, you may have selected an incorrect setup type during the
     installation. To use the Performance Monitoring window, you need to select basic+extended function on the
     setup-type selection window. Uninstall iSM client and reinstall it by selecting the correct option.
Q1-2 How long is the logging interval for statistic information?
   A You can specify the logging interval for statistic information in the performance section
     "monitor_interval" in the environment definition file on the UNIX version, or by using the iSM server
     environment setting on the Windows version.
      [Ver1.4 or later]
              - A specifiable value is 1 to 60 (minutes) and the default is 5 (minutes).
      [Ver1.3]
              - A specifiable value is 5 to 60 (minutes) and the default is 5 (minutes).
Q1-3 Are there any notes on using the NEC Storage Performance Report Viewer?
   A The NEC Storage Performance Report Viewer uses Microsoft Excel macros that can be executed in the
     following environment:
      [Ver2.1 or later]
              - Microsoft Office is installed.
      [Ver1.5 or earlier]
              - Microsoft Excel is installed and macros are enabled.
Q1-4 I purchased NEC Storage PerformanceMonitor. How can I configure it?
   A When you purchased NEC Storage PerformanceMonitor after installing NEC Storage, take the following
     procedure to configure the PerformanceMonitor:
     When the iSM client you use is Ver3.4 or earlier, start from 1. For Ver4.1 or later, start from 2.
        1. If you installed iSM client with 2.basic+extended function selected, proceed to 2. If you selected
           1.basic function, uninstall iSM client and reinstall it by selecting 2.basic+extended function.
        2. Configure PerformanceMonitor information on iSM server.
           The configuration procedure depends on OS of the server in which iSM server is installed, UNIX or
           Windows. Follow the procedure described in the manual for the OS.
           Be sure to configure the following:
            (a) Storage location     : Specify a disk having free space.
            (b) Output interval      : Specify one of the following values depending on the condition:
                   - When the research period is limited.
                     Specify 1 minute (when performance data will be collected only for a short period of time
                     such as 1 hour).
                   - When the research target cannot be limited and performance data needs to be collected
                     for a long period of time.
                     Specify 5 minutes.

        3. Unlock the license of PerformanceMonitor.
            (a) A maintenance staff should unlock the license for NEC Storage S1100, S1200, S2100,
                S2200, S3100, or S4100. Contact your maintenance staff.
            (b) When you use a system other than those indicated in (a), use the NEC Storage Manager
                license unlock function.
        4. Restart the iSM server.
        5. Connect to the iSM server, check that PerformanceMonitor is enabled on the disk-array properties
           window and use the PerformanceMonitor functions.
Q1-5 How can I enable the function to automatically collect statistic information?
   A The function allows you to periodically and automatically collect statistic information.
     Enable the function by making the following setting:


      ■ When iSM server is running on Windows
            On the iSM server environment setting window, select the Performance Monitoring tab, and
            click Automatic in Auto Archive Execution.
            Specify a collection start time in Time under the Performance Monitoring tab.


      ■ When iSM server is running on an OS other than Windows
            Specify auto_archive_execution at the performance section in the iSM server environment
            definition file (iSMsvr.conf).
            Specify a collection start time using auto_execution_time in the performance section.
            The default is 00:00.
Q1-6 How can I enable the function to set the keep period of statistic information and automatically delete files
     whose keep period has expired?
   A This function allows you to set a period for retaining statistic information files (keep period) and
     periodically delete unnecessary information files. The statistic information files which have been
     retained for beyond the days, months, or years specified as the keep period will be deleted. You can set
     a keep period on a file-type basis.
     To automatically delete statistic information, configure the following:


      ■ When iSM server is running on Windows
           On the iSM server environment setting window, select the Performance Monitoring tab. In
           Setting of Preservation Period, select the check box of the type of statistic information you want
           to automatically delete and specify a period in the text box.
                                                                   Statistic information history files will be
           History File                                       …
                                                                   deleted.
           Primary Summarized File                            … Primary summarized files will be deleted.
                                                                   Secondary summarized files will be
           Secondary Summarized File                          …
                                                                   deleted.


           Specify a keeping start time in Time under the Performance Monitoring tab.


      ■ When iSM server is running on an OS other than Windows
           Specify auto_deletion_execution at the performance section in the iSM server environment
           definition file (iSMsvr.conf). Specify a period for the statistic information type you want to
           automatically delete.
                                                                   Statistic information history files will be
           history_file                                       …
                                                                   deleted.
           primary_summarized_file                            … Primary summarized files will be deleted.
                                                                   Secondary summarized files will be
           secondary_summarized_file                          …
                                                                   deleted.
           Specify a keep period in the format of <Number><Unit>:
           <Unit>
           It represents a unit of date and one of the following can be specified (not case-sensitive):
            d … day
            m … month
            y … year
           <Number>
           Specifiable numbers depends on the unit.
            d … 1 to 366
            m …1 to 24
            y … 1 to 2


           Example: To set one month for a keep period, specify 1m.


         Specify a keeping start time using auto_execution_time in the performance section. The default is
         00:00.
Q1-7 The accumulation of statistic information did not start automatically. What is the possible cause?
   A Check the following three conditions:
      - The license of PerformanceMonitor has been applied.
         When the license of PerformanceMonitor is not applied to the disk array, statistic information is not
         accumulated because the performance monitoring function is disabled.
         See the following window in iSM client to check if the license is applied:
             License tab on the Disk Array Subsystem detail information window
      - The performance monitoring function has not stopped due to a failure.
         The message iSM08120 displayed on the operation log represents that the performance monitoring
         function and the accumulation of statistic information have stopped.
         Identify the cause of the failure by seeing other related messages and remove the failure.
      - The environment definition file has been configured appropriately.
         To start accumulating statistic information automatically, the following settings need to be made:
         [Ver4.1 or later]
         ■ When iSM server is running on Windows
             On the iSM server environment setting window, select the Performance Monitoring tab, click
             Output in Continue to Output when Storage Manager Server Restarts, and select the
             Output all the Disk Array Subsystems when it starts first time check box.
         ■ When iSM server is running on an OS other than Windows
             Check the performance section in /etc/iSMsvr/iSMsvr.conf includes the following:
             --------------------------------------
             auto_start_monitor = yes
             --------------------------------------
         [Ver3.4 or earlier]
         ■ When iSM server is running on Windows
             On the iSM server environment setting window, select the Performance Monitoring tab, and
             click Output in Output PSL when iSM Server Starts.
         ■ When iSM server is running on an OS other than Windows
             Check the performance section in /etc/iSMsvr/iSMsvr.conf includes the following:
             ---------------------------------------
             auto_start_monitor
             ---------------------------------------


         <<Notes on Ver.4.3 or earlier>>
         For disk arrays that meet the following conditions, the accumulation of statistic information will not
         start automatically after iSM server is restarted:
         - Disk arrays that were not monitored when iSM server was started for the first time (*1)
             (*1) Including disk arrays for which the license of PerformanceMonitor has not been unlocked


Q2-1 How can I set a threshold for statistic information?
A Threshold is an index value used for detecting overload automatically. The appropriate threshold depends on
  the operation. Set a threshold suitable for your operation. The following ((1)→(2)→(3)) is the recommended
  setting procedure:
  (1) Set an initial threshold.
     As an initial threshold, set a value representing 90% of the maximum hardware performance. Set
     thresholds for IOPSs and transfer rates of an entire device and ports. No initial value setting is
     required for other items. If a threshold is crossed, the system will be highly-loaded and the response
     performance will be degraded, though processing will be normally performed.


     [Initial thresholds for disk arrays and ports]
        Disk Array                                          Threshold
                                    Entire disk array                                Port
                           IOPS          Transfer rate (MB/S)        IOPS        Transfer rate (MB/S)
                                        1G        2G       4G                  1G           2G       4G
           D1-10          65,000       330        600      600       15,000     80          160      320
           D3-10          75,000       800        800      800       16,000     80          160      320
          D3-10i          55,000       280            -      -       14,000    100           -        -
           D8-10          110,000     1,000      1,000    1,000      16,000     80          160      320
           D8-20          110,000     1,000      1,000    1,000      16,000     80          160      320
           D8-30          130,000     1,000      1,000    1,000      16,000     80          160      320
           S1100          27,000       160            -      -       13,500     80           -        -
           S1200          27,000       160        270        -       13,500     80          135       -
           S1300          45,000       160        270        -       22,500     80          135       -
           S1400          65,000       330        330        -       16,000     80          160       -
           S1500          70,000       330        330      330       16,000     80          160      320
           S2100          54,000       320            -      -       24,000     80           -        -
           S2200          54,000       340        500        -       24,000     85          150       -
           S2300          76,000       340        500        -       38,000     85          150       -
           S2400          80,000       330        600        -       16,000     80          160       -
           S2500          90,000       330        600      600       16,000     80          160      320
           S2800          100,000      700        700        -       16,000     80          160       -
           S2900          110,000      800        800      800       16,000     80          160      320
           S3100          70,000       900       1,800       -       13,000     80          160       -
           S3300          140,000     2,000      2,000       -       14,000     80          160       -
           S4100          160,000     1,800      1,800       -       13,000     80          160       -
           S4300          320,000     2,000      2,000       -       14,000     80          160       -
           S4900          640,000     6,000      6,000    7,000      14,000     80          160      320
           * "1G", "2G", and "4G" are transfer rate settings for ports.
           * For D8 series, values in "IOPS" and "Transfer rate (MB/S)" of "Entire disk array" are
             thresholds for one node (xN for N nodes).
(2) Monitor performance status.
   To set appropriate thresholds, monitor the system performance using NEC Storage
   PerformanceMonitor for one to three months during system evaluation period or system installation.
   Log performance data during the monitoring period.


(3) Set thresholds suitable for operation.
   Based on the performance data logged by NEC Storage PerformanceMonitor and the performance
   data (number and time of online processing, etc.) on the application host, set thresholds with which
   system requirements can be met. The following table shows items for which a threshold should be
   set and information that should be taken into account when the threshold is set.
   NEC Storage PerformanceMonitor detects "crossing of threshold" when an IOPS, a transfer rate, an
   average response time, an average transfer length, or a BUSY ratio crosses the threshold, or a
   READ hit ratio or a WRITE hit ratio falls below the threshold.




   [Items for which threshold should be set and information that should be taken into account]
                        Entire disk          Port             Cache         Logical disk     Physical disk
                          array                              segment
         IOPS               (1)               (1)               (2)              (2)              (5)
     Transfer rate          (1)               (1)               (2)              (2)              (5)
        Average
                            (1)               (1)               (2)              (2)              (5)
     response time
       Average
                            (3)               (3)               (3)              (3)              (5)
    transfer length
     READ hit ratio         (4)                -                (4)              (4)               -
    WRITE hit ratio         (4)                -                (4)              (4)               -
      BUSY ratio             -                 -                 -                -               (5)
((number): Threshold can be set -: Threshold cannot be set)


       (1) For IOPS/transfer rate/average response time of entire disk array and port, specify a value
           that meets the system requirements based on the performance data logged by NEC Storage
           PerformanceMonitor.


       (2) Whether system requirements are met can be adequately checked by setting and checking
           thresholds for IOPS/transfer rate/average response time of the entire disk array and ports.
           There is no need to set threshold for all cache segments and logical disks. When I/O loads
           need to be limited because a main DB for task is located in the disk array, etc., setting
           thresholds for the cache segment and the logical disk that contain the DB allows for
           detection of errors.


       (3) The average transfer length for entire disk array, port, cache segment, or logical disk
           represents an average transfer length of I/O from the application server. An average
           transfer length is a reference value and setting a threshold for it is not required in general.
           However, in a system where an average transfer length is stable, setting a threshold
           allows for detection of a long average transfer length and a high load.
(4) READ hit ratio/WRITE hit ratio are reference values and setting threshold for them is not
    required in general. In an operation that needs to maintain a certain level of READ hit
    ratio/WRITE hit ratio for a special reason, setting thresholds allows for detection of errors.


(5) Due to increase in task data or operation-type change, loads may be concentrated on a
    certain physical disk. When I/O loads need to be limited because a main DB for task is
    located in the disk array, etc., setting a threshold for the physical disk based on the
    performance data logged by NEC Storage PerformanceMonitor allows for detection of
    overloads.
Q2-2 Right after the Performance Monitoring window is activated, a line does not appear on a time-series graph
     though the numeric table shows values. What should I do?
   A A line appears on a time-series table when there are two points connecting the line. A line appears after the
     window is refreshed.
Q2-3 A disk array shown on the iSM client main window does not appear on the Performance Monitoring window.
     What should I do?
   A The Performance Monitoring window shows only disk arrays supported by PerformanceMonitor. From the iSM
     client main window, access the properties window of the disk array to check License.
Q2-4 What is the difference between the direct secondary summarizing and the secondary summarizing in NEC
     Storage PerformanceMonitor?
   A Summarizing statistic information in NEC Storage PerformanceMonitor averages the statistic information.
     Averaging information degrades the information accuracy. The accuracy of a "secondary summarized" file is
     lower than the accuracy of a "directly secondary summarized" file. Use "direct secondary summarizing" for
     higher information accuracy.
     The difference is:
         - Direct secondary summarizing
          Creates a secondary summarized file directly from a statistic information history file, bypassing a
          primary summarized file.
         - Secondary summarizing
          Summarizes a primary summarized file and creates a secondary summarized file, resulting in
          averaging twice.
Q2-5 In what environment can I edit the NEC Storage PerformanceMonitor statistic information?
   A NEC Storage PerformanceMonitor uses the analysis supporting function to summarize, extract, and
     edit statistic information files.
      [Ver2.1 or later]
              - You can use the function also in a client. Download a statistic information file by using the
                performance monitoring client and use the performance analysis supporting tool to operate the
                file.
      [Ver1.5 or earlier]
              - You can use the function only on a machine where iSM server has been installed.
Q2-6 How does NEC Storage PerformanceMonitor save statistic information?
   A The statistic information is stored in the installation folder. Estimate the capacity based on the number of
     disk-array components, the period to accumulate statistic information, and the logging interval.
      [Ver4.3 or later]
          For more information, see the Appendix E in the manual NEC Storage Software Performance
          Monitoring User's Manual.
      [Ver4.2 or earlier]
          For more information, see the Appendix D in the manual NEC Storage Software Performance
          Monitoring User's Manual.
Q2-7 How can I start accumulating statistic information?
   A There are two ways to start accumulating statistic information.
     In either way, check that the message iSM08020 or iSM08035 is reported on the operation log after
     accumulation starts.
     After the message is reported and the specified logging interval is elapsed, a statistic information
     history file is created in the statistic information storage folder.


      - To start accumulating statistic information automatically when   iSM server is launched (*1)
         (*1) Ver1.3 or earlier does not support this way.
         [Ver4.1 or later]
         ■ When iSM server is running on Windows
             On the iSM server environment setting window, select the Performance Monitoring tab, click
             Output in Continue to Output when Storage Manager Server Restarts, and select the
             Output all the Disk Array Subsystems when it starts first time checkbox, and save the
             setting. Then restart the iSM server.


         ■ When iSM server is running on an OS other than Windows
             Type the following in the performance section in /etc/iSMsvr/iSMsvr.conf and restart the iSM
             server.
             ---------------------------------------
             auto_start_monitor = yes
             ---------------------------------------
         [Ver3.4 or earlier]
         ■ When iSM server is running on Windows
             On the iSM server environment setting window, select the Performance Monitoring tab, click
             Output in Output PSL when iSM Server Starts, and save the setting. Then restart the iSM
             server.
         ■ When iSM server is running on an OS other than Windows
             Type the following in the performance section in /etc/iSMsvr/iSMsvr.conf and restart iSM
             server.
             ---------------------------------------
             auto_start_monitor
             ---------------------------------------


      - To start accumulating statistic information manually
         [Using iSM client]
         You can start accumulating statistic information on the Performance Monitoring window in iSM
         client. For more information, see the following section in NEC Storage Software Performance
         Monitoring User's Manual:
             (2) Operations on the real-time display screen in 3.3.1 Accumulating Statistic Information


         [Using the iSMprflog command]
         You can start accumulating statistic information by executing the iSMprflog command in an
         environment where iSM server is running.
         For more information, see the following section in NEC Storage Software Performance Monitoring
         User's Manual:
             (1) Operations by using the iSMprflog command in 3.3.1 Accumulating Statistic Information


Q2-8 "-" (hyphen) is displayed for the READ hit ratio/WRITE hit ratio/BUSY ratio on the Performance Monitoring
     window.
   A The READ hit ratio/WRITE hit ratio/BUSY ratio do not appear on the Performance Monitoring window in
     Ver1.5 or earlier of iSM server because the version does not support the function to obtain information on
     those ratios.
     To display the information on the ratios, upgrade iSM server to Ver2.1 or later.
Q2-9 Are there any notes on changing a statistic information storage folder?
    A Follow the procedure below to change a folder to store statistic information files.
         1. Quit iSM server.
         2. Change a statistic information storage folder on the environment setting window.
         3. Move all the folders and files in the old storage folder to the new storage folder.
         4. Restart iSM server.
       To download performance data using PerformanceNavigator, on the PerformanceNavigator menu,
       select Operation, Download Data, Set Up..., and select Edit.... Then in Directory under Remote
       Server, specify a new directory to store statistic information files.
Q2-10 I specified one month as the keep period in the statistic information setting. With this setting, what time-stamps
      do the files to be deleted exactly have?
    A The keep period "one month" means until the same day of the previous month as this month. Files
      having the time-stamps including the same day of the previous month as this month are not deleted.
      For example, if "00:00" is specified as the processing start time and "one month" is specified as the
      keep period for statistic information history files in iSM server Ver4.1, the following files will be deleted
      depending on the processing start date:


          The current date is 2/28
                                   -->   Files having time-stamps including 1/27 and earlier are to be deleted.
          00:00
          The current date is 2/29       Files having time-stamps including 1/28 and earlier are to be deleted
                                   -->
          00:00                          (in a leap year).
          The current date is 3/01
                                   -->   Files having time-stamps including 1/31 and earlier are to be deleted.
          00:00
          The current date is 3/02
                                   -->   Files having time-stamps including 2/01 and earlier are to be deleted.
          00:00


          The current date is 3/28
                                   -->   Files having time-stamps including 2/27 and earlier are to be deleted.
          00:00
          The current date is 3/29       Files having time-stamps including 2/27 (2/28) and earlier are to be
                                   -->
          00:00                          deleted.
          The current date is 3/30       Files having time-stamps including 2/27 (2/28) and earlier are to be
                                   -->
          00:00                          deleted.
          The current date is 3/31       Files having time-stamps including 2/27 (2/28) and earlier are to be
                                   -->
          00:00                          deleted.
          The current date is 4/01       Files having time-stamps including 2/28 (2/29) and earlier are to be
                                   -->
          00:00                          deleted.
          The current date is 4/02
                                   -->   Files having time-stamps including 3/01 and earlier are to be deleted.
          00:00


          * The parenthesized time-stamps are applied in a leap year.
          As indicated above, with "one month" specified as the keep period, statistic information files for up to
          32 days are retained.
Q2-11 Can I execute the performance analysis supporting tool directly for a statistic information history file stored in
      the storage folder I specified in the NEC Storage Manager environment setting?
    A It may cause a problem. The iSM server may use statistic information history files stored in the statistic
      information storage folder. If you execute the performance analysis supporting tool directly for the file, a file
      access conflict may occur and affect the functions to accumulate or automatically summarize the statistic
      information. To prevent this problem, copy statistic information history files to another location and then
      execute the performance analysis supporting tool for the copied statistic information history files.
Q3-1 Though a disk array is monitored on the iSM client main window, the Performance Monitoring window shows
     that monitoring the disk array performance has been stopped. What should I do?
   A [Ver1.4 or later]
          Restarting to monitor the disk array can also restart the performance monitoring for the disk array.
          Follow the procedure below to restart disk-array monitoring.
             1. On the Start/Stop Monitoring window accessed from the main window, select a disk array you want
                to operate and stop and click Stop.
             2. Make sure that Start has been activated and then click the Start.
          From the time when performance monitoring is restarted to the time when collecting performance data is
          completed, the performance data on the disk array is not displayed.


Q3-2 When I added LD/PD to monitoring targets on the Performance Monitoring window, the following dialog
     appeared and I failed to add them. What should I do?
     03405 Error because of too many monitoring objects. Return to the status before the processing.
   A This dialog represents a status where so many logical disks and physical disks are monitored in iSM server
     that a new monitoring can no longer be registered.
     This error occurs because the number of components to be monitored in a certain period of time is limited to
     prevent the overhead that comes with performance data collection from affecting I/O to/from the application
     host.
     Stopping logging statistic information may allow for addition to the monitoring target. On Ver2.1 or later, the
     number of components that can be currently monitored is displayed.
Q3-3 When I upgraded PerformanceMonitor from Ver3.4 (or earlier) to Ver4.1 (or later), the output interval for
     statistic information was changed. What should I do?
   A Since Ver4.1, the default automatic adjustment of logging interval setting has been changed from
     automatic to manual in the iSM server environment setting in PerformanceMonitor.
     When you do not want the output interval to be adjusted automatically after upgrading PerformanceMonitor to
     Ver4.1 or later, change the automatic adjustment of logging interval setting to manual in the iSM server
     environment setting and then restart iSM server. (However, it is recommended to set automatic adjustment
     of logging interval to automatic because correct statistic information may not be reported unless an
     appropriate value is set for logging interval.)
Q3-4 Since I configured the environment setting to automatically accumulate statistic information and restarted iSM
     server, statistic information has not been accumulated.
   A For a disk array for which monitoring has failed due to an error that occurred when iSM server restarted, etc.,
     statistic information accumulation may not start automatically when monitoring restarts. In such case, after
     monitoring starts, start accumulation manually (by using the iSMprflog command and operating the real-time
     display window in iSM client).

     When accumulation starts automatically along with restart of iSM server, on the operation log, "iSM01002" is
     reported and then "iSM08020" or "iSM08035" is reported.
Q3-5 Though I upgraded iSM server from Ver3.4 (or earlier) to Ver4.1 (or later) and set the keep period for statistic
     information, the statistic information reported by the old (Ver3.4 or earlier) iSM server was not deleted
     automatically.
   A While the statistic information files created by iSM server of Ver4.1 or later are automatically summarized or
     deleted when the keep period expires, the statistic information files created by Ver3.4 or earlier are not
     summarized or deleted automatically. Summarize or delete those files manually if needed.
Q3-6 When I converted a statistic information history file by using the CSV conversion command (iSMprfext
     command), "iSMprfext:011" was reported showing that the number of recorded CSV files is over 65536. How
     can I estimate the number of CSV files that can be recorded so that I will be able to adjust the number of files
     to convert.
   A You cannot convert a statistic information history file to a CSV file by using the CSV conversion command
     when the conversion should increase recorded CSV files to more than 65536.
     In this case, use an option of the CSV conversion command to decrease resources to be converted or
     shorten the conversion time.
     See the following for how to estimate the number of CSV files that can be recorded:


     [Estimating the number of CSV files that can be recorded]
     The number of CSV files that can be recorded depends on the number of disk-array resources and the
     logging interval.


     With the following formula, you can estimate the approximate number of CSV files that you can record for a
     day by executing the CSV conversion command in the default format:


            Number of records to be reported = total of numbers of disk-array resources × (60 [min] × 24 [hours] ÷
            logging interval [min])


      Note: "Disk-array resources" in the above formula means resources used by your system among ones
            indicated in Table 1-3 to 1-10 in 1.5.3 "Supporting Statistic Information Analysis" in the manual NEC
            Storage Software Performance Monitoring User's Manual.
Q3-7 When any option other than Smaller - 100%(default)(S) is selected on the Display dialog box, which is
     opened by selecting Control Panel and Design, on Windows Server 2008 R2 or Windows7, display is
     distorted or mouse operation is disturbed. What should I do?
   A This problem may be experienced when Ver6.1 is used and a size other than Smaller - 100%(default)(S) is
     configured. Choose the default settings Smaller - 100%(default)(S).
Storage Management

PerformanceNavigator
1. Introduction
        Q1-1 What can we do with NEC Storage PerformanceNavigator?
        Q1-2 What storage devices does PerformanceNavigator support?
        Q1-3 What are supported OSes?
        Q1-4 How is PerformanceNavigator different from iSM Storage Performance Report Viewer?


2. Installation
        Q2-1 What should I do with the license that comes with NEC Storage PerformanceNavigator when it is
             purchased?
        Q2-2 What should I do when nothing is shown after installing and starting NEC Storage PerformanceNavigator?
        Q2-3 How do I register and apply the license key?
        Q2-4 Can I unregister the license key that has been applied to a disk array that was not intended?
        Q2-5 What user right do I need for installation?
        Q2-6 If the OS of the management server is Windows, can I install iSM server and NEC Storage
             PerformanceNavigator on the management server?
        Q2-7 Is it OK to install iSM client and NEC Storage PerformanceNavigator on one PC?
        Q2-8 Are there any requisite software programs to use NEC Storage PerformanceNavigator?
        Q2-9 Are there any related software programs to use NEC Storage PerformanceNavigator?
       Q2-10 Is there anything that should be in place to use the download function?
       Q2-11 When FTP is unavailable, is PerformanceNavigator unavailable?
       Q2-12 When iSMvollist is not installed, is PerformanceNavigator unavailable?
       Q2-13 How much disk capacity and memory amount do I need to use NEC Storage PerformanceNavigator?
       Q2-14 Are there any recommended threshold values for metrics?


3. Operation
        Q3-1 What types of performance data does PerformanceNavigator have, and how should I use them?
        Q3-2 Nothing is shown in a line graph (chart).
        Q3-3 If I try to show various types of information on a line graph (chart), some legends are not shown.
        Q3-4 If I try to show various types of information on a column graph (chart), some information for the horizontal
             axis is not shown.
        Q3-5 How can I emphasize certain information when various types of information are shown on a line graph
             (chart)?
        Q3-6 A time-series graph (chart) is shown with a break.
        Q3-7 On the Display tab of the Configure Settings dialog box, Stacked Area, 100 % Stacked, Stacked
             Column, and 100% Stacked Column are disabled.
        Q3-8 Elapsed Time is disabled in the Timeframe tab of the Configure Settings dialog box.
        Q3-9 I cannot set a day of the week on the Timeframe tab of the Configure Settings dialog box.
       Q3-10 How can I change the analysis timeframe of performance data for the interval information?
       Q3-11 What is median value?
       Q3-12 What is mode?
       Q3-13 The mode value, which I have set as a representative value for chart to be displayed, is not shown on the
             chart.
       Q3-14 Downloaded files were deleted when I selected Automatically import data on the Configure Download
             Data dialog box.
       Q3-15 Is it possible to perform a quick analysis if import of performance data is cancelled?
     Q3-16 Is it necessary to start up iSM server to use NEC Storage PerformanceNavigator?
     Q3-17 The Highlight check box on the Configure Graph dialog box is disabled.
     Q3-18 What types of log information are saved by NEC Storage PerformanceNavigator?
     Q3-19 No node is shown on the resource list (on the Resources tab) of the Configure Settings dialog box when
           performance data of the D8 series is analyzed.
     Q3-20 Are there any notes on using PerformanceNavigator on a machine where any software program for
           secuiryt (*) is installed?

           (*1) Software program used for data leakage prevention, unauthorized access prevention and so on.


4. Troubleshooting
      Q4-1 Performance data that has been downloaded is not shown on the Available Data on the Import Data
           dialog box.
      Q4-2 I cannot donwload performance data/volume lists. What are conceivable causes?
      Q4-3 Quick analysis ended in error and I cannot show graphs (charts).
      Q4-4 The license information is not taken over at reinstallation. What are conceivalbe causes?
      Q4-5 I cannot successfully import volume lists created by using the –ax option of the iSMvollist command
           provided in iSM Ver 3.4 or later.
      Q4-6 I cannot configure the FT service after I changed the OS of the server having performance data or volume
           lists to Windows Vista SP1. What should I do?
      Q4-7 What should I do for the dialog [00001] with the detail code 11 shown after import or upgrade of
           performance data?
      Q4-8 Time needed to import performance data has becom longer after changing the OS of the PC where
           PerformanceNavigator is installed to Windows Vista Business or Windows Server 2008. What are
           conceivable causes?
      Q4-9 Are there any notes on using NEC Storage PerformanceNavigator on a Windows machine where ESET
           NOD 32 Antivirus (NOD32 Kernel Service)が is running?
     Q4-10 When any option other than “Smaller – 100%(default)” is selected on the Display dialog box, which is
           opened by selecting Control Panel and Design, on Windows Server 2008 R2 or Windows7, dislpay is
           distorted or mouse operation is disturbed. What should I do?
  Q1-1 What can we do with NEC Storage PerformanceNavigator?
     A NEC Storage PerformanceNavigator allows for speedy and ensured analyses in various ways based on
       performance data accumulated by using NEC Storage PerformanceMonitor. PerformanceNavigator allows for
       effective use of such data, which can reduce workload of administrators significantly.
  Q1-2 What storage devices does PerformanceNavigator support?
     A The storage devices from the following series are supported.
          - NEC Storage D8 series
          - NEC Storage D4 series
          - NEC Storage D3 series
          - NEC Storage D1 series
          - NEC Storage S4000 series
          - NEC Storage S3000 series
          - NEC Storage S2800 series
          - NEC Storage S2000 series
          - NEC Storage S1000 series
  Q1-3 What are supported OSes?
     A As for the support matrix of NEC Storage PerformanceNavigator, see the NEC Storage PerformanceNavigator
       Installation Guide.
Q1-4 How is PerformanceNavigator different from iSM Storage Performance Report Viewer?
   A While iSM Storage Performance Report Viewer only shows performance data on the entire disk array in charts,
     NEC Storage PerformanceNavigator allows for analysis of any performance data that can be collected by NEC
     Storage PerformanceMonitor.
     PerformanceNavigator is also equipped with functions to change display, analyze with comparison, analyze
     related resources and so on, which are not in iSM Storage Performance Report Viewer.
Q2-1 What should I do with the license that comes with NEC Storage PerformanceNavigator when it is purchased?
   A Register the license key described on the license sheet with PerformanceNavigator to enable performance
     analysis using PerformanceNavigator.
     Keep the license sheet in a safe place.
Q2-2 What should I do when nothing is shown after installing and starting NEC Storage PerformanceNavigator?
   A You need to register the license. Use the Help menu to register the license.
     And then import the performance data. Select Apply License on the Help menu or Download Data/Import
     Data on the Operation menu according to your situation.
Q2-3 How do I register and apply the license key?
   A Follow the steps below to register and apply the license key.
         1 Select Register License on the Help menu to register the license.
         2 Select License list on the Help menu to check the license has been registered.
         3 -   When you are using PerformanceNavigator for the first time:
               Select Import Data on the Operation menu to import the performance data of the disk array to
               which you want to apply the license.
               Click OK on the license application warning dialog box, which is shown during the import.
               For details, see 3.4.2 “Importing Metrics” in the NEC Storage D series manual or NEC Storage S
               series manual, NEC Storage Software Performance Analysis User’s Manual.
           -   If you have ever used the trial version for analysis
               and the license has not been taken over at uninstallation:
               Choose the disk array to which you want to apply the license from Disk Array View dialog box and
               select Apply License on the Help menu.
         4 Select the disk array to which the license has been applied to check you can run quick analysis. And then
           you can start using PerformanceNavigator functions.
Q2-4 Can I unregister the license key that has been applied to a disk array that was not intended?
   A Reinstall PerformanceNavigator and start license registration from the beginning. When the inquiry “Do you
     want to take over the license information?” is shown during uninstallation, select No.
Q2-5 What user right do I need for installation?
   A Use the system administrator right to perform installation.
Q2-6 If the OS of the management server is Windows, can I install iSM server and NEC Storage
     PerformanceNavigator on the management server?
   A When the OS of the management server is Windows, you can install iSM server and NEC Storage
     PerformanceNavigator on the management server.
     However, if iSM server is used for accumulating performance data, performance data files cannot be directly
     imported from where performance data of iSM server is stored. Copy performance data files you want to
     analyze from where performance data of iSM server is stored to a local folder and then import them.
Q2-7 Is it OK to install iSM client and NEC Storage PerformanceNavigator on one PC?
   A Yes, you can install iSM client and NEC Storage PerformanceNavigator on one PC.
Q2-8 Are there any requisite software programs to use NEC Storage PerformanceNavigator?
   A The following software programs are required to use PerformanceNavigator.
         - NEC StorageManager (Ver1.4 or later)
         - NEC Storage PerformanceMonitor
 Q2-9 Are there any related software programs to use NEC Storage PerformanceNavigator?
    A The following software programs are related to use of PerformanceNavigator.
          - NEC Storage AccessControl
           This software program allows for narrowing down logical disks for logical disk analysis on an operation
           (LD set) basis (iSM Ver3.2 or later).
          - NEC Storage PerformanceOptimizer
           This software program allows for optimizing performance when a bottleneck is detected.
Q2-10 Is there anything that should be in place to use the download function?
    A The FTP service must be started on an iSM server machine to download performance data and on an
      application server to download volume lists.
      Start the FTP service on the following servers according to the data to be downloaded.
          - To download performance data                : Management server where iSM server is running
          - To download volume lists                    : Application server
      Follow the instructions of your FTP server (IIS FTP Publishing Service and other FTP daemons) to configure
      the environment of the FTP site.
Q2-11 When FTP is unavailable, is PerformanceNavigator unavailable?
    A PerformanceNavigator is available except for some of its functions even if FTP is not available. Functions that
      cannot be used are:
          - Function to download performance data
          - Function to download volume lists
      When FTP is not available, you can import performance data and volume lists to a machine where analysis
      takes place by using CD-R or the like.
Q2-12 When iSMvollist is not installed, is PerformanceNavigator unavailable?
    A PerformanceNavigator is available even if iSMvollist is not installed. However, if you are not importing volume
      lists created by running the iSMvollist command, the Host name/Path column (the Server/path column for
      PerformanceNavigator V2.2 or earlier,) of a logical disk list located on the Resources tab of the Configure
      Settings dialog box is not shown. Consequently, analysis by associating application server volumes and disk
      array logical disks cannot be performed.
Q2-13 How much disk capacity and memory amount do I need to use NEC Storage PerformanceNavigator?
    A The following describes the disk capacity and memory amount required to use NEC Storage
      PerformanceNavigator.
      For the latest information, see NEC Storage D Series Instalaltion Guide or NEC Storage S Series Installation
      Guide of NEC Storage PerformanceNavigator.
                         Disk capacity: 16 MB or more
                      Memory amount: Memory amount required for the OS + 45 (60) MB or more
                                     The figure enclosed by parentheses is the amount required for the 64-bit
                                     OS.
Q2-14 Are there any recommended threshold values for metrics?
    A Threshold values serve as an index to automatically detect overloading.
       Threshold values must be configured to fit your operation because they can vary according to how your
       system is used.
       When you configure threshold values, it is recommended to follow the steps below (in the order of (1), (2) and
       (3)).


        (1) Set initial threshold values
           Configure 90% of the maximum performance of the hardware as initial threshold values. The IOPS and
           transfer rate of the entire disk array device/port threshold values should be configured. Crossing a
           threshold value will lead to highly loaded state and will slow down response but processing will be
    performed successfully.
    If threshold values are already set by NEC Storage PerformanceMonitor, they are inherited for NEC
    Storage PerformanceNavigator threshold values, in which case you do not need to configure initial
    values.


 (2) Monitor performance
    Monitor your system performance by using NEC Storage PerformanceNavigator during the period the
    system is tested and evaluated or 1 to 3 months from operation of the system is started, to determine
    appropriate threshold values. Log performance data while performance is monitored.


 (3) Configure the threshold values to suit your operation.
    Use performance data logged by NEC Storage PerformanceMonitor as well as application server
    performance information (such as number of online transactions and time needed for processing) to
    configure the threshold values that satisfy system requirements. See the following considerations for
    items to which thresholds are configured.
    PerformanceNavigator detects “crossing of threshold” when IOPS, transfer rate, average response time,
    average transfer length, IO ratio, or busy ratio crosses its threshold, or hit ratio falls below the threshold.


Considerations for items to which thresholds are configured
                      Entire       Host      Disk        Replication Disk
                             Node                   Port
                     machine      director director         port     port
IOPS                     1        5        -         -        1         1         8
Transfer rate            1        5        -         -        1         1         8
Average response
                         1        5        -         -        1         1         8
time
Max response time        2        2        -         -        2         2         2
Average transfer
                         3        6        -         -        3         3         8
length
Cache hit ratio          4        4        -         -        -         4          -
IO ratio                 4        4        -         -        4         4         4
Busy ratio               -        -        7        7         7         7         7
Average queue
                         -        -        4         -        -         -          -
length
Max queue length         -        -        4         -        -         -          -
Average dirty
                         -        -        -         -        -         -          -
pages
Max dirty pages          -        -        -         -        -         -          -

                               Cache Logical           Physical
                      Cache                  RANK POOL
                              segment disk               disk
IOPS                     -        9            9     8        8        8
Transfer rate            -        9            9     8        8        8
Average response
                         -        9            9     8        8        8
time
Max response time          -        2        2        2       2         2
Average transfer
                           -        3        3        8       8         8
length
Cache hit ratio           4         4        4        -        -        -
IO ratio                   -        4        4        4       4         4
Busy ratio                 -        -        9        8       8         8
Average queue
                           -        -         -       -        -        -
length
Max queue length           -        -         -       -        -        -
Average dirty
                          4         4         -       -        -        -
pages
Max dirty pages           4         4         -       -        -        -
        A threshold value can be set unless – is shown.
        No threshold value can be set if – is shown.
*     Host director, disk director, and cache are supported in the D series as well as S4900 where storage
      control software version 0530 or later is applied.
*     Only D8 series nodes are supported.
*     Busy ratios of port, replication port and disk port are supported only in the D series.
*     Dirty page ratios of cache segment are supported only in the D8 series.


When threshold values are already configured by NEC Storage PerformanceMonitor, PerformanceNavigator
takes them over. If no threshold value has been configured by NEC Storage PerformanceMonitor or threshold
values cannot be configured by NEC Storage PerformanceMonitor, the values should be configured with the
following considerations taken into account.


    1 Configure values that satisfy system requirements based on the performance data logged by NEC
      Storage PerformanceMonitor for IOPS, transfer rate, and average response time of the entire device and
      ports.


    2 Configuring and checking a threshold value of average response time for each resource is adequate to
      satisfy system requirements. It is not necessary to set threshold values for maximum response time.
      Setting threshold values for maximum response time allows for detecting a failure in mission critical
      operations where a momentary decline of response can cause a problem.


    3 Average transfer lengths of the entire device, port, cache segment, logical disk and replication port are
      values representing average transfer length of input to and output from application servers or replication
      volumes. Average transfer lengths serve as a guide and you do not need to set threshold values for them
      in general. However, in a system where average transfer lengths are stable, setting threshold values for
      them allows for detecting a state where an average transfer length is long and the system is highly
      loaded.


    4 Cache hit ratio, IO ratio, average queue length, maximum queue length, average dirty pages ratios, and
      maximum dirty pages ratios serve as a guide and you do not need to set threshold values for them in
      general. If there is a particular reason to have operation where any of cache hit ratio, IO ratio, average
      queue length, maximum queue length, average dirty pages ratios, and maximum dirty pages ratios
      should be kept to a certain level, set threshold value(s) so that a problem can be detected.
5 IOPS, transfer rate, and average response time of a node are values representing IOPS, transfer rate,
  and average response time of input to and output from the node or other nodes. Configuring values that
  satisfy system requirements allows for detecting overload in input or output across nodes.


6 The average transfer length of a node is a value representing input to and output from the node or other
  nodes. The average transfer length serves as a guide and you do not need to set a threshold value for it
  in general. However, configuring the threshold value in a system where the average transfer length is
  stable allows for detecting a state where the average transfer length is large and the system is highly
  loaded.


7 Busy ratios of port, replication port, disk port, host director and disk director are ratios of actual data
  transfer against port bandwidth. Configuring threshold values for them allows for detecting a port or
  director bottleneck.


8 Configuring and checking thresholds of IOPS, transfer rate, and average response time for the entire
  device, ports and replication ports is adequate to satisfy system requirements. It is not necessary to
  configure these threshold values for all cache segments and logical disks. If it is necessary to set a limit
  of load for input and output due to reasons such as key databases for operation being installed, configure
  threshold values to the given cache segment and logical disk to detect a problem.


9 Certain physical disks may get highly loaded due to a reason such as growth of operation data or change
  of operation mode. If input/output load should have a certain limit (for example, because a key operation
  database is installed) configure threshold values for the physical disks based on performance data
  logged by NEC Storage PerformanceMonitor so that overloading can be detected.
 Q3-1 What types of performance data does PerformanceNavigator have, and how should I use them?
    A There are four types of performance data, which vary according to the length of time between data collections.
          - Interval                           ----   Performance data on a metric collection interval basis
          - Hourly summary                     ----   Performance data on an hourly basis
          - Daily summary                      ----   Performance data on a daily basis
          - Monthly summary                    ----   Performance data on a monthly basis


       Select a performance data type according to the interval between analyses.
          - Interval between analyses is within a day:                ----   Interval
          - Interval between analyses is from 1 day to 1 week:        ----   Hourly summary
          - Interval between analyses is from 1 week to few           ----   Daily summary
            months:
          - Interval between analyses is over few months:             ----   Monthly summary
 Q3-2 Nothing is shown in a line graph (chart).
    A When no line is drawn (for example, when a day of the week is specified for daily summary), you may think
      nothing is shown. If you select the Highlight check box, you will find the chart is plotted. Select the Highlight
      check box.
 Q3-3 If I try to show various types of information on a line graph (chart), some legends are not shown.
    A Point to the line you want to see to show a tooltip (legend information). Use the tooltip for associating the line with
      the information representing what the line signifies.
      If you are using PerformanceNavigator V1.2 or later, the performance data selected in the legend list is
      highlighted on the chart.
 Q3-4 If I try to show various types of information on a column graph (chart), some information for the horizontal axis is
      not shown.
    A Point to the column you want to see to show a tooltip (legend information). Use the tooltip for associating the
      column with the information representing what the column signifies.
      If you are using PerformanceNavigator V1.2 or later, the performance data selected in the legend list is
      highlighted on the chart.
 Q3-5 How can I emphasize certain information when various types of information are shown on a line graph (chart)?
    A You can change the color by clicking Change on the Appearance tab of the Configure Graph dialog box. Select
      the color for the information you want to emphasize.
 Q3-6 A time-series graph (chart) is shown with a break.
    A If there was any time period during which accumulation of performance data by iSM server was interrupted or
      during which a disk array was failing, the chart is shown with a break to tell the performance data lacks continuity.
 Q3-7 On the Display tab of the Configure Settings dialog box, Stacked Area, 100% Stacked Area, Stacked Column,
      and 100% Stacked Column are disabled.
    A Stacked Area, 100% Stacked Area, Stacked Column and 100% Stacked Column can be selected only when
      metrics is IO density, transfer rate, or average queue length.
 Q3-8 Elapsed Time is disabled in the Timeframe tab of the Configure Settings dialog box.
    A When Interval or Hourly Summary is selected for a data type, Elapsed Time is enabled if data of the following
      period is imported.
          - Interval: past 24 hours
          - Hourly Summary: past 31 days
 Q3-9 I cannot set a day of the week on the Timeframe tab of the Configure Settings dialog box.
    A You can specify a day of the week only when Hourly Summary or Daily Summary is selected.
Q3-10 How can I change the analysis timeframe of performance data for the interval information?
    A On the Timeframe tab of the Configure Settings dialog box, configure the Timeframe field in Period according
      to the steps shown below to modify the timeframe of analysis.
       You can also change the analysis timeframe by following the same steps on the Restrict Timeframe dialog box,
       which is displayed by selecting Restrict Timeframe and clicking Change on the Configure Quick Analysis
       dialog box.


       If the analysis timeframe of performance data extends over multiple months of the year and an analysis from
       certain time on the last day of a month to certain time of the same day should be performed, follow the steps
       below.
              1 Set the day you want to analyze for the end date.
              2 Set the day you want to analyze for the start date.
              3 Specify the time you want to start analysis for the start time.
              4 Specify the time you want to stop analysis for the end time.


       If analysis timeframe of performance data does not extend over multiple months of the year, or even if the
       timeframe extends over multiple months of the year but a day other than the last day of a month is specified, you
       can skip step 2.


       If metrics of the specified analysis timeframe is missing, data for either 24 hours from the start date and time or
       24 hours up to the end date and time is automatically configured.
Q3-11 What is median value?
    A Median value is the middle value when all data (i.e. a set of values) is sorted in the ascending order.
      Selecting this value allows for knowing a representative value with extremely large and small values eliminated.
Q3-12 What is mode?
    A Mode is the value that emerges most frequently.
      Selecting this value allows for knowing a representative value with large and small values that are less likely to
      emerge eliminated.
Q3-13 The mode value, which I have set as a representative value for the chart to be displayed, is not shown on the
      chart.
    A The mode value is the value that emerges most frequently. When data amount is small, the mode value may not
      become valid, and consequently it is not shown.
Q3-14 Downloaded files were deleted when I selected Automatically import data on the Configure Download Data
      dialog box.
    A Only for PerformanceNavigator V1.1
              When the Automatically import data check box is selected on the Server Settings dialog box (which is
              opened by clicking Edit on the Configure Download Data dialog box), files downloaded from a server are
              deleted.
              If you want to save downloaded files, click to clear the Automatically import data check box, and select
              Import Data on the Operation menu after download of files is complete.
       PerformanceNavigator V1.2 or later
              A confirmation message asking deletion of downloaded files is shown. If you want to keep the downloaded
              files, click Cancel.
Q3-15 Is it possible to perform a quick analysis if import of performance data is cancelled?
    A No. When import of performance data is cancelled, you cannot perform a quick analysis.
      Perform the import again and rerun the quick analysis after “Import finished” is displayed.
Q3-16 Is it necessary to start up iSM server to use NEC Storage PerformanceNavigator?
    A No, iSM server does not need to be started.
      PerformanceNavigator does not need to be connected to a certain server and it allows for offline analysis.
Q3-17 The Highlight check box on the Configure Graph dialog box is disabled.
    A Highlight is enabled only for line graphs (charts) and 2y axes graphs (charts).
Q3-18 What types of log information are saved by NEC Storage PerformanceNavigator?
    A PerformanceNavigator saves performance data, template information and volume information by logs. Capacity
      can be estimated by number of disk array resources, how long metrics are accumulated, logging interval and so
      on.
      For details, see Appendix E of NEC Storage D series manual or NEC Storage S series manual NEC Storage
      Software performance Analysis User’s Manual.
Q3-19 No node is shown on the resource list (on the Resources tab) of the Configure Settings dialog box when
      performance data of the D8 series is analyzed.
    A To analyze performance data of the D8 series, select Advanced on the Application Settings dialog box and
      restart PerformanceNavigator.
Q3-20 Are there any notes on using PerformanceNavigator on a machine where any software program for security (*1)
      is installed?

      (*1) Software program used for data leakage prevention, unauthorized access prevention, antivirus, and so on.
    A PerformanceNavigator creates folders or files in the following folders to store configuration files and log files.
         -    The installation folder (*2) and its subfolders of PerformanceNavigator.
         -    If the location where performance data is stored has been changed by selecting Data Location on the File
              menu: the new working folder and its subfolders
         -    <system drive>:\Documents and Settings\<login user name>\Application Data
              For Windows Server 2008:
              <system drive>:\user\<login user name>\AppData\Roaming
       (*2)   The following is the default installation folder of PerformanceNavigator.
              <system drive>:\Program Files\NEC\PerforNavi
                    For 64-bit version:
                    <system drive>:\Program Files(x86)\NEC\PerforNavi
       If creating these folders or files is restricted by any software program for security, PerformanceNavigator does
       not work successfully. Change the settings as necessary so the creation will not be restricted.
Q4-1 Performance data that has been downloaded is not shown on the Available Data on the Import Data dialog box.
    A Performance data that has been downloaded but is not listed falls into one of the following:
        1. Performance data is collected by iSM Ver.1.3 or earlier.

        2. Performance data is collected from a disk array where no license key has been applied.

        3. The name of the performance data history file does not comply with the naming convention.

        4. The performance data is collected by iSM whose version is not supported by
        PerformanceNavigator you are using.
       If 1. applies, the data cannot be listed on Available Data because analyzing such data is not
       supported by PerformanceNavigator.
       If 2. applies, register the license key of the disk array series from which you want to import data. And
       then try displaying the Import Data dialog box again.


       If 3. applies, rename the file according to following naming convention.
       For details, see 1.5.3.1 “Accumulating Statistics Information” of NEC Storage D series manual or NEC
       Storage S series manual, NEC Storage Software Performance Monitoring User’s Guide.
       File naming convention: yyyymmdd disk array name [#nnn] .psl
                                   yyyymmdd: The date (year, month and day) when accumulating
                                             performance data is started
                             Disk array name: The name of the disk array where performance data
                                              accumulation takes place.
                                          nnn: Serial number (from 2 through 999): if a file with the same
                                               name exists when accumulation of performance data is
                                               started, assign this serial file number.
       If 4. applies, the data cannot be listed on Available Data because PerformanceNavigator does not
       support the iSM used.
        [PerformanceNavigator and iSM correspondence]


          PerformanceNaviga
                            1.1           1.2      1.3     2.1        2.2    3.1      3.2     5.3      6.1
          tor version


                                 1.4      1.4      1.4     1.4    1.4        1.4      1.4     1.4      1.4
          iSM version
                                 ~ 3.3    ~ 3.3    ~ 3.4   ~ 4.2a ~ 4.3      ~ 5.1    ~ 5.2   ~ 5.3    ~ 6.1

        If you are using iSM that your PerformanceNavigator does not support, upgrade the
        PerformanceNavigator according to the list shown above.
Q4-2 I cannot download performance data/volume lists. What are conceivable causes?
   A Check your right to access the FTP environment.
     Users must have the right to access the FTP environment and the directory where performance data is
     located.
Q4-3 Quick analysis ended in error and I cannot show graphs (charts).
   A Import performance data again and retry the quick analysis.
Q4-4 The license information is not taken over at reinstallation. What are conceivable causes?
   A The following causes are conceivable:
        1 The installation folder has been changed.
        2 No was selected for Do you want to take over the license information? when installation was
          deleted.
      If any of the above applies, the license information cannot be taken over.
      Register the license key, which comes with the product you purchased, and apply it again.
Q4-5 I cannot successfully import volume lists created by using the –ax option of the iSMvollist command
     provided in iSM Ver.3.4 or later
   A If volume lists created by iSM Ver.3.4 or later should be imported by using PerformanceNavigator
     Ver1.1 or Ver1.2, use the -a option (Windows) or the –l option (UNIX) of iSMvollist.
Q4-6 I cannot configure the FTP service after I changed the OS of the server having performance data or
     volume lists to Windows Vista SP1. What should I do?
   A When Windows Vista SP1 is used, the following may be experienced:
      What you may experience
         When you right-click the default ftp site to configure the ftp root directory of IIS or for any other
         reasons, a message “
         Microsoft Management Console has stopped working” is shown and Management Console
         stops.




      Because the download function of PerformanceNavigator is achieved through the FTP function,
      the download function does not work properly if the server where the above mentioned is
      experienced is specified as the download source.
      If this problem is experienced, perform the following workaround instructions provided by
      Microsoft.


      Workaround
       ======
      Follow the steps below to create Management Console for Internet Information Service (IIS) 6.0.


      1. Click Start and type mmc.exe in the Start Search box, and then click Continue to start Run
         as administrator.
      2. On the File menu click Add/Remove Snap-in.
      3. Under Available snap-ins on the Add/Remove Snap-in window, click Internet Information
         Services (IIS) 6.0 Manager and click Add.
      4. Under Selected Snap-ins, select Internet Information Services (IIS) 6.0 Manager and then
         click Edit Extensions.
      5. On the Extension for Internet Information Services (IIS) 6.0 Manager window, select
         Enable only selected extensions and clear the ASP.NET Management Extension check
         box.
      6. Click OK and close the Extension for Internet Information Services (IIS) 6.0 Manager
         window.
      7. Click OK and close the Add/Remove Snap-in window.
      8. On the File menu, click Save As. Type “IIS 6.0 FTP Services Manager.msc” in the File name
         box and then click Save.
      9. Click Start, Control Panel to open Taskbar and Start Menu Properties.
      10
         On the Start Menu Programs tab, click Customize.
      .
      11 Select Display on the All Programs menu and Start menu in System administrative
      . tools, and the click OK to close the Customize Start Menu dialog box.
      12
         Click OK to close Taskbar and Start Menu Properties.
      .


      When all the steps mentioned above are completed, click Start, All Programs, System
      administrative tools, and IIS 6.0 FTP Services Manager.msc. Use the started IIS 6.0 Manager
      to configure the FTP service.


Q4-7 What should I do for the dialog [00001] with the detail code 11 shown after import or upgrade of
     performance data?
   A The detail code 11 is reported when accessing a target file is blocked by exclusive control.
     It is conceivable that:

      1.    Performance data files have been directly imported from where iSM server performance data is
            saved in an environment where PerformanceNavigator is installed on the machine that is used as
            the management server and iSM server is used for accumulating performance data.
            Copy the performance data files to be analyzed from where iSM server performance data is saved
            to a local folder and then import or update them.


      2.    The files to be imported are used by another program.
            Wait for the program to finish using the files or copy the files to a local folder, and then import or
            update them.
Q4-8 Time needed to import performance data has become longer after changing the OS of the PC where
     PerformanceNavigator is installed to Windows Vista Business or Windows Server 2008. What are
     conceivable causes?
   A If performance data to be imported is located in the driver where the OS is installed, import of the data in
     the Windows Vista Business or Windows Server 2008 OS environment may take time because the PC’s
     OS and other OSes compared.

     If this problem is experienced, you can shorten the time by storing performance data in a drive other
     than the drive where the OS is installed.
Q4-9 Are there any notes on using NEC Storage PerformanceNavigator on a Windows machine where ESET
     NOD 32 Antivirus (NOD32 Kernel Service) is running?
   A You may experience a problem such as failure to perform quick analysis when ESET NOD 32 Antivirus
     (NOD32 Kernel Service) is running on a Windows machine where PerformanceNavigator is installed.
     It is known that an error occurs due to file conflicts when this antivirus software package scans files
     that PerformanceNavigator uses internally. Choose either (1) or (2) described below to prevent
     scanning by the antivirus software package for files that PerformanceNavigator uses.
      (1)    Exclude the following folders that PerformanceNavigator uses from scanning target. For
             information on how to exclude folders from scanning target, see the manual of ESET NOD 32
             Antivirus.
             -   Folders to be excluded from scanning target
                 -    The PerformanceNavigator installation folder and its subfolders
                      (By default, C:\Program Files\NEC\PerforNavi
                      (for 64-bit OS, C:\Program Files (x86)\NEC\PerforNavi ))
                 -    When the data location has been changed by selecting Data Location on the File
                      menu, a new data location and its subfolders
       (2)   Stop the following service temporarily when you use PerformanceNavigator.
                 NOD32 Kernel Service
Q4-10 When any option other than “Smaller - 100%(default)” is selected on the Display dialog box, which is
      opened by selecting Control Panel and Design, on Windows Server 2008 R2 or Windows7, display is
      distorted or mouse operation is disturbed. What should I do?
    A This problem may be experienced when Ver6.1 is used and a size other than “Smaller - 100%(default)”
      is configured. Choose the default settings “Smaller - 100%(default).”
Storage Management

ReallocationControl
1. Introduction
       Q1 Tell me about ReallocationControl.
       Q2 Which software do I need for using ReallocationControl?


2. Operation
       Q3 When should I use the function to initialize a logical disk?


3. Troubleshooting
       Q4 Since I clicked Cancel during Get Disk Array Info, the system has not worked normally. What should I do?
       Q5 In a disk array of S4100 or S3100 series, how can I change a logical disk group to which Port mode has been
          set by Access Control?


       Q1 Tell me about ReallocationControl.
        A This is the software to maintain and manage logical disks, such as ensuring the security of disk arrays
          shared by multiple servers by using AccessControl, initializing stored logical disks (volumes) that cannot be
          accessed by servers to keep the disks secured when they are reused, and setting work disks to be used for
          the performance optimization function. Also, by locking the current storage configuration, you can guard and
          protect the currently active configuration from operations that can change the configuration. With
          ReallocationControl, a user can maintain and manage logical disks (reconfiguration, reallocation of files,
          storage, etc.) effectively, leading to reduction of man-hours for operation. ReallocationControl can also
          prevent data from being corrupted or system operation from being stopped by operation errors during
          configuration change, etc. You can easily operate ReallocationControl through GUI in iSM client.
       Q2 Which software do I need for using ReallocationControl?
        A The following software is necessary for using ReallocationControl:
           - NEC Storage Manager
           - NEC Storage AccessControl
       Q3 When should I use the function to initialize a logical disk?
        A You may reallocate a logical disk that has no longer been necessary for an application server to another
          application server. In such case, if these application servers use the same type of OS, the logical disk data
          that has been used in the previous server can also be viewed in the new server after reallocation. To prevent
          this problem, initialize the logical disk to keep it secured.
       Q4 Since I clicked Cancel during Get Disk Array Info, the system has not worked normally. What should I do?
        A Perform Get Disk Array Info again to make the disk array and the client have identical information.
       Q5 In a disk array of S4100 or S3100 series, how can I change a logical disk group to which Port mode has been
          set by Access Control?
        A In a disk array of S4100 or S3100 series, you cannot operate a logical disk whose access setting has been
          made to Port mode to control access from a port. To operate such kind of logical disk, cancel the access
          setting that has been made to Port mode to control access to the logical disk.
Storage Management

NEC Storage Manager Integration Base
1. Introduction
      Q1-1 Tell me about NEC Storage Manager Integration Base.


2. Installation
      Q2-1 Which software do I need for using NEC Storage Manager Integration Base?
      Q2-2 Are there any notes on using NEC Storage Manager Ver4.3 and NEC Storage Manager Integration Base
           Ver4.2 together?
      Q2-3 When upgrading Integration Base, can I apply the previous environment setting to the new version?


3. Troubleshooting
      Q3-1 Are there any notes on using NEC Storage Manager Integration Base in a Windows server in which the
           antivirus software"NOD32 Antivirus" (NOD32 Kernel Service) is running?


4. Move
      Q4-1 How can I move Integration Base to another node?


      Q1-1 Tell me about NEC Storage Manager Integration Base.
          A NEC Storage Manager Integration Base is infrastructure software to allow for integrated
            management and control of NEC Storage D/S series disk array units by related software,
            associating with NEC Storage Manager.
            Installing NEC Storage Manager Integration Base together with the following software provides
            various solutions for systems including NEC Storage D/S series:


                  - SigmaSystemCenter


      Q2-2 Which software do I need for using NEC Storage Manager Integration Base?
          A The following software is necessary for using NEC Storage Manager Integration Base:
                  - NEC Storage Manager
      Q2-3 Are there any notes on using NEC Storage Manager Ver4.3 and NEC Storage Manager Integration
           Base Ver4.2 together?
          A When using the storage system information preservation function in NEC Storage Manager
            Ver4.3, note the following regarding the software indicated below that associates with NEC
            Storage Manager Integration Base:


                  - SigmaSystemCenter


            Do not allocate a system volume to be used for the storage system information preservation
            function to an LD set.
            System volume is used for the storage system information preservation function. It is not
            necessary to allocate a system volume to an application server because the volume is not used
            directly by a task. In other words, the volume is supposed to be used in a device and should not
            be allocated to an LD set.
            To identify a system volume, check the volume purpose displayed in the State Monitor client of
            NEC Storage Manager. For a system volume, "System volume" is displayed as the purpose.
Q2-4 When upgrading Integration Base, can I apply the previous environment setting to the new
     version?
   A To upgrade Integration Base, uninstall the old version of Integration Base and install a new
     version of Integration Base. Uninstalling Integration Base does not delete the following files:
           - Environment setting files
           - Operation logs/server logs
       These files are taken over to the new version installed in the same installation folder as the
       previous version.
       If you have installed a new version of Integration Base in a different installation folder from the
       folder for the previous version, copy the files remaining in the previous installation folder to the
       new installation folder.
       The default installation folder for Integration Base is:
         System drive:\Program Files\NEC\iSMSM

       You can select any location to store an installation folder when installing Integration Base.
Q3-1 Are there any notes on using NEC Storage Manager Integration Base in a Windows server in
     which the antivirus software"NOD32 Antivirus" (NOD32 Kernel Service) is running?
   A
       In a machine in which NEC Storage Manager Integration Base is installed and the antivirus
       software "NOD32 Antivirus" (NOD32 Kernel Service) is running, NEC Storage Manager
       Integration Base may not work normally due to the timing.
       It has already been confirmed that if this antivirus software scans files internally used by NEC
       Storage Manager Integration Base, an error will occur due to file conflicts. Do the following to
       prevent the antivirus software from scanning the files used by NEC Storage Manager Integration
       Base:
       -      Exclude the following folders and files that are used by NEC Storage Manager Integration
              Base from scanning. For how to exclude particular folders and files from scanning, see the
              NOD32 Antivirus's manual.
              -     Folders to be excluded from scanning
                    -    The folder in which NEC Storage Manager Integration Base has been installed and
                         its subfolders
                         (default: C:\Program Files\NEC\iSMSM
                         (On 64-bit OS: C:\Program Files (x86)\NEC\iSMSM))

Q4-1 How can I move Integration Base to another node?
   A
        Follow the procedure below to move Integration Base.
        The procedure describes how to move Integration Base from a source node (management
        node A) to a destination node (management node B).
        Take each step of the procedure <on the destination node (management node B)> or <on the
        source node (management node A)> as follows:


        <On the destination node (management node B)>
        (1)       Check OS on the management node B.
                  Check that the OS on the destination node (management node B) is supported by
                  Integration Base.
                  For more information about OSes supported by Integration Base, see "Operating
                  Environment" in NEC Storage Manager Integration Base Installation Guide.


        (2)       Configure the environment of the management node B.
                  Do the following:
       -   Applying OS patches
       -   Configuring network environment (connecting cables, etc.)


<On the source node (management node A)>
(3)   Stop Integration Base.
      From the list displayed by selecting Services in Administrative Tools, select Integration
      Base to stop it.
      Check that the message "iSM51003: Integration Base has terminated normally" is
      reported in the event log.


(4)   Check files to backup.
      You can apply the Integration Base operating environment on the management node A to
      the management node B by backing up the environment setting files and operation
      logs/server logs and restoring them on the management node B.
      The restoration folder on the management node B needs to have the same path as the
      installation folder on the management node A. Check the installation folder on the
      management node A.
      The default installation folder for Integration Base is:
        System drive:\Program Files\NEC\iSMSM

      The installation folder above may have been changed when Integration Base was
      installed.
      Also check the environment setting files (which are stored in \conf\iSMSM.conf) using a
      text editor, etc. and make a note of the following information if necessary:
       -   A folder that is not the default (installation folder \etc\log) has been specified as the
           "location to store" operation logs/server logs.


(5)   Uninstall Integration Base.
      Uninstall Integration Base. For the uninstallation procedure, see NEC Storage Manager
      Integration Base Installation Guide.
      The files required for Integration Base operations such as environment setting files are not
      deleted by this uninstallation.


(6)   Backup all the files you checked in step (4).


<On the destination node (management node B)>
(7)   Install Integration Base.
      Install Integration Base. For the installation procedure, see NEC Storage Manager
      Integration Base Installation Guide.
      During installation, specify the installation folder having the same path as the installation
      folder on the management node A that is indicated in step (4).


(8)   Restore environment setting files and operation logs/server logs of Integration Base.
      Restore the files backed up in step (6) to the folder having the same path as the folder on
      the management node A.


(9)   Check and reconfigure the Integration Base environment setting.
     Confirm that the folders specified in the Integration Base environment setting are correct.
     Also check a folder to store operation logs/server logs has sufficient free space.


(10) Start Integration Base.
     From the list displayed by selecting Services in Administrative Tools, select Integration
     Base to start it.
     Check that the message "iSM51002: Integration Base is ready" is reported in the event log
     and the message "iSM52070:connected with iSM server ip=xx.xx.xx.xx port=xxxx" is
     reported in the operation log.
Storage Control

NEC Storage BaseProduct
1. Introduction
     Q1 What kind of product is NEC Storage BaseProduct?
     Q2 Which NEC Storage series support NEC Storage BaseProduct?
     Q3 How should I arrange NEC Storage BaseProduct?
     Q4 Why is NEC Storage BaseProduct is essential for using NEC Storage disk array units?
     Q5 How can I use a license sheet that came with NEC Storage BaseProduct?


     Q1 What kind of product is NEC Storage BaseProduct?
       A NEC Storage BaseProduct is software to be installed in a NEC Storage disk array unit and composed of
         storage control software that controls the basic functions of the disk array unit and NEC Storage Manager that
         monitors the status of the disk array unit and provides basic functions to configure the disk array setting.


         This product is essential for using a NEC Storage disk array unit.
     Q2 Which NEC Storage series support NEC Storage BaseProduct?
       A NEC Storage BaseProduct is supported by the following series:
         [NEC Storage D series]
           NEC Storage D8, D4,D3, D1
         [NEC Storage S series]
           NEC Storage S4900, S4300, S3300, S2900, S2800, S2500, S2400,
                       S2300, S2200, S1500, S1400,
                       S1300, S1200
     Q3 How should I arrange NEC Storage BaseProduct?
       A Arrange PP of NEC Storage BaseProduct suitable for NEC Storage disk array units you will use on a
         disk-array-unit basis.

     Q4 Why is NEC Storage BaseProduct essential for using NES Storage disk array units?
       A Because NEC Storage BaseProduct provides "storage control software" that controls the basic functions of a
         NEC Storage disk array unit. You can upgrade NEC Storage BaseProduct to make it support new HDDs and
         functions.
         To upgrade NEC Storage BaseProduct, apply for the PP Support Service beforehand.
     Q5 How can I use a license sheet that came with NEC Storage BaseProduct?
       A Use it as follows according to the disk array series you will install:
         [NEC Storage D4 series, D3 series, D1 series]
         If necessary conditions are met, a user can apply storage control software by using the license sheet.

         [Other series]
         To use the NEC Storage disk array series, the license of storage control software needs to be unlocked on
         each unit. Maintenance staff will unlock the license when configuring disk array units. Pass the license sheet
         to the staff.
Storage Control

ControlCommand
1. Introduction
   Q1-1 What kind of product is NEC Storage ControlCommand?


2. Installation
   Q2-1 Which software do I need for installing NEC Storage ControlCommand?
   Q2-2 Which NEC Storage products does ControlCommand support?
   Q2-3 How much disk capacity and memory amount are required for running NEC Storage ControlCommand?
   Q2-4 Tell me about the character string length specification for a node name/host name used in NEC Storage
        ControlCommand.
   Q2-5 I recreated a volume list after making the Windows initial setting by executing the SYSPREP tool on Windows.
        However, a ControlCommand command such as iSMrc_replicate or iSMrc_restore failed to be executed and
        abnormally ended.
        Checking the volume list, I found that a mount point volume name registered with the list was different from the
        name reported by the MOUNTVOL command. What should I do?
   Q2-6 Can I install NEC Storage ControlCommand on Windows Server 2008?
   Q2-7 Are there any notes on using ControlCommand in a Windows machine where security software (*) is installed?
        (*) Software to prevent information leakage, to block unauthorized accesses or computer viruses, etc.


3. Operation
   Q3-1 Can I use ControlCommand remotely using the terminal service client or the remote desktop?
   Q3-2 When I performed non-disruptive backup using the VSS function, a message was reported on the event log
        (application) in the backup server.
   Q3-3 After I edited a ControlCommand operation option configuration file on Windows Server 2008, I could not save
        the file. What should I do?
   Q3-4 When I attempted to execute a ControlCommand command on Windows Server 2008, the message "Access Is
        Denied" appeared and I could not execute the ControlCommand. What should I do?
   Q3-5 Up to how many NEC Storage LUNs can ControlCommand handle on a server?


4. Troubleshooting
   Q4-1 The message Failed in getting systempath of environment variable. appeared during uninstallation of
        ControlCommand for Windows. What should I do?
        This message appears for ControlCommandSet, ReplicationControl and SnapControl.
   Q4-2 On a Windows server, a ControlCommand failed and ended abnormally with the following error message. The
        volume information has been registered correctly with the volume list and I found no errors in the list. What
        should I do?
         Error message: example 1
          iSM13585: Volume list is missing or unexpected error occurred.
           error code=-2
          Error message: example 2
          iSM13555: Checking status has failed.
          (detail error code=49)
          Error message: example 3
          iSM13750: Volume list data does not exist.
          (code=1500-406f-0001-0000)
Q1-1 What kind of product is NEC Storage ControlCommand?
   A It is software to perform data replication, snapshot, data retention and power saving functions by executing
     commands on an application server.
     This software consists of the following five functions:
         - NEC Storage ReplicationControl
         - NEC Storage SnapControl
         - NEC Storage ReplicationControl/DisasterRecovery
         - NEC Storage ProtectControl
         - NEC Storage PowerControl
Q2-1 Which software do I need for installing NEC Storage ControlCommand?
   A The following software is required for installing NEC Storage ControlCommand:
         - NEC Storage BaseProduct
         - NEC Storage AccessControl


     [To use the data replication function]
         - NEC Storage DynamicDataReplication Ver2 or later or NEC Storage RemoteDataReplication Ver2 or
           later
     [To use functions for disaster recovery in data replication]
         - NEC Storage RemoteDataReplication Ver2 or later
         - NEC Storage RemoteDataReplication/DisasterRecovery
     [To use the snapshot function]
         - NEC Storage DynamicSnapVolume
     [To use the data retention function]
         - NEC Storage VolumeProtect
     [To use the power saving function]
         - NEC Storage StoragePowerConserver


     Arrange the software above and apply for the PP support service.
Q2-2 Which NEC Storage products does ControlCommand support?
   A The supported products depend on the function you will use. See FAQ of the function you want to use.
         - NEC Storage ReplicationControl
         - NEC Storage SnapControl
         - NEC Storage ReplicationControl/DisasterRecovery
         - NEC Storage ProtectControl
         - NEC Storage PowerControl
Q2-3 How much disk capacity and memory amount are required for running NEC Storage ControlCommand?
   A For information about disk capacity and memory amount required for running NEC Storage ControlCommand,
     see NEC Storage ControlCommand Installation Guide for D series or NEC Storage ControlCommand
     Installation Guide for S series.
Q2-4 Tell me about the character string length specification for a node name/host name used in NEC Storage
     ControlCommand.
   A Up to 8 bytes for a node name and up to 63 bytes for a host name.
     If a name has a length which is over the character string length spec above, the following symptom will occur:
         - When the iSMvollist command with the -p and -ax options is executed to display the property of a volume
           list, up to 8 characters of a node name is shown as Owner Host Name.
             This symptom will not occur on Windows.
Q2-5 I recreated a volume list after making the Windows initial setting by executing the SYSPREP tool on Windows.
     However, a ControlCommand command such as iSMrc_replicate or iSMrc_restore failed to be executed and
     abnormally ended.
     When checking the volume list, I found that a mount point volume name registered with the list was different
     from the name reported by the MOUNTVOL command. What should I do?
   A If you execute the Windows SYSPREP tool with a volume mounted on any NTFS folder, you may see a mount
     point volume name on Windows that had been used before execution of the SYSPREP command and you fail
     to create the volume list successfully.
     If it occurs, do the following to recreate a volume list:


        1. After configuring the Windows initial setting by using the Windows SYSPREP tool is completed, cancel all
           the mount points (drive letters and NTFS folder path names) of volumes registered with the volume list by
           using the MOUNTVOL command or Disk Management on Windows.
             [MOUNTVOL command to cancel a mount point]
                 MOUNTVOL (mount point)          /D
        2. Create the volume list temporarily, and check associations between logical disks, Windows physical
           disks and volumes (partitions), and mount point volume names of volumes.
        3. Use the MOUNTVOL command or Disk Management on Windows to set a NTFS folder mount point for
           each volume.
             [MOUNTVOL command to set a mount point]
                 MOUNTVOL (mount point)          (mount point volume name)
        4. Recreate the volume list.
           Then check new mount point volume names and mount points set for the volumes are correctly
           registered with the volume list.
Q2-6 Can I install NEC Storage ControlCommand on Windows Server 2008?
   A
       Windows Server 2008 is supported by ControlCommand Ver5.3 and later.
       However, note the following when installing ControlCommand on Windows Server 2008:

       The user account control (UAC) is enabled by default on Windows Server 2008.
       When UAC is enabled, install ControlCommand by following one of the procedures below.
             - Install ControlCommand with a local system administrator authority installed on the OS.
             - Activate an installer by right clicking the installation file (SETUP.EXE) icon and clicking Run as
               administrator, and install ControlCommand with a system administrator authority.


Q2-7 Are there any notes on using ControlCommand in a Windows machine where security software (*) is installed?
     (*) Software to prevent information leakage, to block unauthorized accesses or computer viruses, etc.
   A
       To store setting files and log files, ControlCommand creates a ControlCommand installation folder,
       (default: <System drive>:\Program Files\NEC\iSMrpl
       (On 64-bit Windows, <System drive>:\Program Files (x86)\NEC\iSMrpl))
       a Volume List Display command installation folder,
       (default: <System drive>:\Program Files\NEC\iSMvol
       (On 64-bit Windows, <System drive>:\Program Files (x86)\NEC\iSMvol))
       and folders and files in the following folders:


         -   Folder specified in the -export option of the iSMcc_hostinfo command
         -     Folder specified in the -export option of the iSMrc_signature command
         -     <System drive>:\windows\ismvol
         -     <System drive>:\windows
         -     <System drive>:\Program Files\Common Files
         -     <System drive>:\Documents and Settings\<login user name>\Application Data
                * On Windows Server 2008:
                <System drive>:\user\<login user name> \AppData\Roaming


               If security software restricts creation of these folders and files, ControlCommand will not work normally.
               Change the software setting to prevent the restriction.

Q3-1 Can I use ControlCommand remotely using the terminal service client or the remote desktop?
   A ControlCommand can be used on a remote desktop running on Windows Server 2003 or later but cannot be
     used on a terminal service client running on Windows 2000. When you use Windows 2000, log in a server
     where ControlCommand is installed.


       [Notes on ControlCommand (including iSMvollist)]
             - Note the following when using ControlCommand on a remote desktop.
               An incorrect operation may cause an abnormal end of unmount (iSMrc_umount command) or
               unexpected automatic mounting after unmount that may lead to data corruption.
                 - Do not use a volume accessed by another remote desktop when executing a ControlCommand
                   command.
                 - Do not use Explorer or other applications to access a volume used by the ControlCommand on
                   another terminal service.
             - To execute Difficulty Information Gather to collect the information on disk and volume status, etc.
               correctly, log in the server where ControlCommand is installed.
               On Windows Server 2003 or later, you can collect information by executing Difficulty Information
               Gather on a terminal service client or remote desktop.
Q3-2 When I performed non-disruptive backup using the VSS function, a message was reported on the event log
     (application) in the backup server.
   A The following message may be reported to the event log (application) depending on the NEC Storage Manager
     host agent service function supported by ControlCommand Ver5.1 or later. It has no impact on VSS backup.

              Event type                  : Information
              Event source                : iSMcc_hostinfo
              Event ID                    : 11770
              Description                 : iSM11770: Host Information was exported successfully.

       If you do not want the NEC Storage Manager host agent service to collect and register host information
       automatically, you can inactivate the NEC Storage Manager host agent service. To prevent the NEC Storage
       Manager host agent service from automatically starting when the system restarts, click Start, Programs, and
       select NEC Storage Manager Host Agent on the Administrative Tools service menu and then change the
       type of start up from Automatic to Manual.
Q3-3 After I edited a ControlCommand operation option configuration file on Windows Server 2008, I could not save
     the file. What should I do?
   A
        The user account control (UAC) is enabled by default on Windows Server 2008.
        When UAC is enabled, edit an operation option configuration file by following one of the procedures below.
              - Edit a file with a local system administrator authority installed on OS.
           - Launch a text editor by right-clicking the text editor start menu item or the execution file and clicking
             Run as administrator, and then edit a file as a system administrator.

Q3-4 When I attempted to execute a ControlCommand command on Windows Server 2008, the message "Access Is
     Denied" appeared and I could not execute the ControlCommand. What should I do?
   A
       The user account control (UAC) is enabled by default on Windows Server 2008.
       When UAC is enabled, perform a ControlCommand function by following one of the procedures below.
           - Perform a function with a local system administrator authority installed on the OS.
           - Launch a function as a system administrator(*).
           - Launch the command prompt as a system administrator(*) and execute a command on the prompt.


           * To launch a function or command as a system administrator, right-click a start menu item or an
             execution file icon and click Run as administrator.

Q3-5 Up to how many NEC Storage LUNs can ControlCommand handle on a server?
   A
       The maximum number of NEC Storage LUNs ControlCommand can handle on a server is:


       Windows                       Up to 256 LUNs
       Linux(Kernel2.4)              Up to 256 LUNs
       Linux(Kernel2.6)              Ver6.1 or earlier
                                            Up to 256 LUNs
                                     Ver6.2 or later
                                            Up to 18,278 LUNs

Q4-1 The message Failed in getting systempath of environment variable. appeared during uninstallation of
     ControlCommand for Windows. What should I do?
     This message appears for ControlCommandSet, ReplicationControl and SnapControl.
   A
       This symptom occurs when a value of 1024 bytes or more has already been specified in the system
       environment variable "Path". Clicking OK completes the uninstallation, however, the path information for
       ControlCommand remains in the system environment variable Path. Delete the information by following the
       procedure below.



         (1) Right-click My Computer, click Properties. On the Advanced tab, click Environment Variables.
         (2) Select Path from the system environment variables and click Edit.
         (3) Delete the following specified in the variable and close the window.
              %iSMvol%\sbin;%iSMrpl%\sbin;
             When V2.1.007 or earlier is used, delete the following:
              %iSMrpl%\sbin;

Q4-2 On a Windows server, a ControlCommand failed and ended abnormally with the following error message. The
     volume information has been registered correctly with the volume list and I found no errors in the list. What
     should I do?
      Error message: example 1
       iSM13585: Volume list is missing or unexpected error occurred.
        error code=-2
       Error message: example 2
       iSM13555: Checking status has failed.
       (detail error code=49)
       Error message: example 3
     iSM13750: Volume list data does not exist.
     (code=1500-406f-0001-0000)
A
    In a Windows machine in which ControlCommand is installed and the antivirus software "NOD32 Antivirus"
    (NOD32 Kernel Service) is running, this symptom may occur due to the timing.
    It has already been confirmed that if this antivirus software scans files internally used by ControlCommand
    commands, an error will occur due to file conflicts. Perform the following (1) or (2) to prevent the antivirus
    software from scanning the files used by ControlCommand commands.
      (1) Exclude the following folders and files that are used by ControlCommand commands from scanning:
          For how to exclude particular folders and files from scanning, see the NOD32 Antivirus's manual.
         -     Folders to be excluded from scanning
                 -   The folder in which ControlCommand has been installed and its subfolders (default:
                     C:\Program Files\NEC\iSMrpl (On 64-bit OS: C:\Program Files (x86)\NEC\iSMrpl\))
                 -   The folder in which the Volume List Command has been installed and its subfolders
                     (default: C:\Program Files\NEC\iSMvol (On 64-bit OS: C:\Program Files (x86)\NEC\iSMvol\))
                 -   ismvol folder in the system folder
                     (ex.:C:\windows\ismvol\)
                 -   Folders in <System drive>\Program Files\Common Files\NEC\WebSAM\Framework\ (On
                     64-bit OS, folders in <System drive>\Program Files(x86)\Common
                     Files\NEC\WebSAM\Framework\)
      (2) Stop the following service temporarily when executing a ControlCommand command:
           NOD32 Kernel Service
Storage Control

ReplicationControl
1. Introduction
    Q1-1 Tell me about the data replication function.
    Q1-2 What is the advantage of using the replication function?
    Q1-3 What will a replication volume created by the data replication function be used for?
    Q1-4 What is the effectiveness of installing the data replication function "ReplicationControl"?
    Q1-5 What is the advantage of using ReplicationControl for databases?
    Q1-6 If a HDD failure occurs during copy between MV/RV in Synchronous mode or transition (synchronization) from
         Separate to Replicate, does the Hot Spare function work?
    Q1-7 If an error occurs in MV while the data replication is performed, what should I do?


2. Installation
    Q2-1 What is volume type?
    Q2-2 Tell me about the volume types to be specified by -mvflg or -rvflg in the ReplicationControl command.
    Q2-3 Does a changed drive letter or mount point work normally on Windows?
    Q2-4 Are there any notes on changing the access right for files on MV?
    Q2-5 Which NEC Storage series support the data replication function?
    Q2-6 Which software is required for using the data replication function?
    Q2-7 Does the system need to be restarted after ReplicationControl is installed?
    Q2-8 How much disk capacity and memory capacity are required for running ReplicationControl?
    Q2-9 Are there any notes on applying quota management or file screening to Windows NTFS folders?
   Q2-10 Why is operation with MV and RV separated (separate operation) recommended?
         Are there any notes on operating MV and RV that are replicated in synchronous mode (replicate operation)?


3. Operation
    Q3-1 I changed an LD name. Does it have impact on replication operations?
    Q3-2 I changed a disk array configuration. Is there any way to make the OS recognize the change without system
         restart?
    Q3-3 Can I use volume management software such as LVM or VxVM?
    Q3-4 Are there any notes on starting or restarting a Windows system using RV?
    Q3-5 I changed a partition on Windows. Does it have any impact on operations?
    Q3-6 Is buffer flash (iSMrc_flush) or drive unmount (iSMrc_umount) necessary for operations on Windows?
    Q3-7 Where is the replication operation option configuration file stored on Windows?
         Can I apply the old version of replication operation option configuration file to upgraded ReplicationControl?
    Q3-8 How does ReplicationControl save log information?
    Q3-9 Can I serially configure a RemoteDataReplication pair and a DynamicDataReplication pair and replicate them
         at the same time?
   Q3-10 Can I operate a pair in a remote disk array connected by using RemoteDataReplication?


4. Troubleshooting
    Q4-1 A disk array volume cannot be recognized. What should I do?
    Q4-2 Some volumes are not displayed by executing the iSMvollist command. What should I do?
    Q4-3 Some volumes are not displayed by executing the iSMvollist command. What should I do?
    Q4-4 A replication operation command (such as iSMrc_replicate and iSMrc_separate) failed and abnormally ended.
         What should I do?
 Q4-5 On a Windows machine, the OS does not recognize volumes. What should I do?
 Q4-6 When I attempted to unmount a volume by executing the iSMrc_umount command, the error iSM13609
      appeared and the unmount failed. What should I do?
 Q4-7 I cannot execute the iSMrc_vollist command because it does not exist. What should I do?
 Q4-8 When I attempted to import a VxVM disk group, the following message appeared and I failed to import the
      group. What should I do?
      vxvm:vxdg: ERROR: Disk group xxxx: import failed: Disk write failure or
      vxvm:vxdg: ERROR: Disk group xxxx: import failed: No valid disk found containing disk group
 Q4-9 When I executed the iSMrc_mount command, the error iSM13574 appeared. What should I do?
Q4-10 The size of ReplicationControl logs has crossed the specified upper limit. What is the possible cause?
Q4-11 When I executed the iSMrc_signature command, the error iSM13615 or iSM13623 appeared. What should I
      do?
Q4-12 When I attempted to unmount RV by executing the iSMrc_umount command with the -offline option specified
      on Windows Server 2008 R2 with BitLocker enabled, the following message was reported on the event log.
      What should I do?
       <Message>
         Source: Microsoft-Windows-BitLocker-Driver
         ID: 24620
         Message: Encrypted volume check: Volume information on
      \?\Volume{e3eece92-b857-11de-ab2a-0019dbc2ceba} cannot be read.
                Error code: 0x80000010
         * The volume name may vary.


 Q1-1 Tell me about the data replication function.
    A It is the function to create a replica of a volume used for tasks (master volume) that allows for effective
      backup. The function to create a replica in the same disk array is called DDR (DynamicDataReplication), and
      the function to create a replica across different disk arrays is called RDR (RemoteDataReplication).
 Q1-2 What is the advantage of using the replication function?
    A To collectively manage huge amount of information accumulated by implemented tasks and to use the
      information effectively, you need to install a storage system having high performance, a large capacity and
      high reliability. The data replication function helps you to operate such kind of storage system effectively. The
      function can be used for:
          - High-speed backup
          - Backup in parallel with online tasks
          - Performing online tasks and search tasks simultaneously
          - Performing batch processing simultaneously
          - Creating test data for applications
 Q1-3 What will a replication volume created by the data replication function be used for?
    A A replication volume itself can serve as backup data and can also be used for backup from the replication
      volume to a magnetic tape. If a replication volume is a database replica, it can be used as a database for
      search operations separately from a master volume. Also a test environment can be configured by using
      replication volumes and the same task data as the data used in the production environment.
 Q1-4 What is the effectiveness of installing the data replication function "ReplicationControl"?
    A Replicas are created on disk arrays without burdening the application server. A replica can easily be created
      by connecting a replication volume to the master volume. Also a replication volume separated from the master
      volume can be used any time. These features bring you the following advantages:
          - When a replication volume is used as backup data, the period of operation stop caused by backup is
            substantially reduced and performance of access to a master volume is secured during task operation.
          - When a replication volume is used as test data, a test environment can easily be configured.
          - When a replication volume is used as a database replica, parallel processing of data update and data
          search allows for more effective system operation.


     In addition, higher system operability and maintainability such as following can be achieved:
         - Non-disruptive backup of Oracle databases by using the Oracle hot backup function (Begin Backup/End
           Backup)
         - Non-disruptive backup of Microsoft SQL Server databases by using ReplicationControl SQL Option
Q1-5 What is the advantage of using ReplicationControl for databases?
   A It allows for hot backup of Oracle databases and Microsoft SQL Server databases.
     In a Microsoft SQL Server database, snapshot-backed-up data can serve as a standby database that can be
     used for search operation, etc.
Q1-6 If a HDD failure occurs during copy between MV/RV in Synchronous mode or transition (synchronization) from
     Separate to Replicate, does the Hot Spare function work?
   A The Hot Spare function works normally regardless of the status of a logical volume. (While the DDR function is
     controlled on a logical-disk level, the function to transfer to Hot Spare after a HDD failure is controlled on a
     RAID level. Because of this difference of control level, the Hot Spare function is not affected by a HDD failure.)
Q1-7 If an error occurs in MV while the data replication is performed, what should I do?
   A As is the case with general disk drive errors, the procedure to restore data varies depending on the application
     of a platform, database system, etc. For the procedure of restoring a flat file on a platform, see the manuals for
     NEC Storage D series or manuals for NEC Storage S series such as NEC Storage Software Data Replication
     User's Manual.
     For the procedure to be taken when data replication is associated with an application in a cluster system or a
     database system, see the guidebooks such as NEC Storage Manager Data Replication System Setup Guide.
Q2-1 What is volume type?
   A To create a replication volume by using the data replication, you need to specify a pair of a source volume and
     a destination volume. The types of volume you will set are called volume type, and are categorized into the
     following three:
        ■ IV (Isolated Volume)
          Volume not paired with any other volumes
        ■ MV (Master Volume)
          Paired volume serving as a replication source volume
        ■ RV (Replication Volume)
          Paired volume serving as a replication destination volume
Q2-2 Tell me about the volume types to be specified by -mvflg or -rvflg in the ReplicationControl command.
   A A volume type specified in a command represents a parameter format specified for -mv or -rv.
     A special file (device file) name or a LD name is specified on UNIX, and a drive letter or a mount point is
     specified on Windows.
Q2-3 Does a changed drive letter or mount point work normally on Windows?
   A Use Disk Management to restore a drive letter that has been unexpectedly changed to the original. Recreate
     a volume list by executing the iSMvollist command to reflect information on the changed drive letter or mount
     point. If the drive letter or the mount point is used in a batch file, etc., correct the file.
Q2-4 Are there any notes on changing the access right for files on MV?
   A Performing replication transfers the information on access rights and users that have been specified for
     directories (folders) and files to RV as it is. Therefore user information should be the same on the server using
     MV and on the server using RV. Also a user who accesses directories and files on RV should be the same as
     for MV.
Q2-5 Which NEC Storage series support the data replication function?
   A The data replication function is supported by disk arrays of NEC Storage D1 series, D3 series, D4 series, D8
     series, S1400, S1500, 2000 series, 2800 series, 3000 series and 4000 series.
     The function to create replicas across different disk arrays (RDR) is supported only by NEC Storage D3
        series, D4 series, D8 series, S2400, S2500, 2800 series, 3000 series and 4000 series.
        Use FC (Fibre Channel) to connect an application server and disk arrays.
 Q2-6 Which software is required for using the data replication function?
    A      ■ Application server
             Install the data replication function "NEC Storage ReplicationControl" or "NEC Storage
             ControlCommand."
           ■ Management server
             Install NEC Storage Manager to manage disk arrays, pair a master volume and a replication volume,
             etc.
           ■ Disk array
             Products such as NEC Storage DynamicDataReplication, NEC Storage RemoteDataReplication, and
             NEC Storage AccessControl are offered. Purchase necessary products and unlock the licenses of the
             products.
           ■ Associated software
                - NEC Storage ReplicationControl SQL Option to allow for non-disruptive backup in Microsoft SQL
                  Server databases is offered.
 Q2-7 Does the system need to be restarted after ReplicationControl is installed?
    A If you want to use job scheduling software already installed in the system or Windows task scheduler after
      installing ReplicationControl, restart the system before using the software to make OS recognize the path
      names of the installed execution files.
 Q2-8 How much disk capacity and memory amount are required for running ReplicationControl?
    A For information about disk capacity and memory amount required for running ReplicationControl, see FAQ for
      ControlCommand. For the latest information, see NEC Storage ControlCommand Installation Guide for D
      series or NEC Storage ControlCommand Installation Guide for S series.
 Q2-9 Are there any notes on applying quota management or file screening to Windows NTFS folders?
    A When MV or RV that contains volumes or folders to which quota management or file screening has been
      applied is copied (replication or restoration), the applied configuration will also be applied to the copy
      destination. Because of this, make sure to configure the appropriate settings of the quota management or the
      file screening function if you want to restart operation on the MV or update the RV, etc. after restoration.
Q2-10 Why is operation with MV and RV separated (separate operation) recommended?
      Are there any notes on operating MV and RV that are replicated in synchronous mode (replicate operation)?
    A The separate operation has the following advantages:
           - RV can retain the consistent previous backup data in which static points are secured.
           - Even if data in MV becomes inconsistent due to an operation error or a logical failure, backup data in RV
             will be protected.
           - RV can be used for other purposes than backup, such as secondary use.
           - A low-cost large-capacity disk (SATA) or a RAID type (RAID5 or RAID6) with high capacity efficiency
             can be used as a disk for RV.
           - The number of caches allocated to RV by the CachePartitioning function can be minimized.


        Note the following on performing replicate operation.
           - Since updates in MV are constantly reflected to RV, backup data in RV has no secured static points.
           - If data in MV becomes inconsistent due to an operation error or logical failure, the MV cannot be
             restored by using RV (tape, etc. is required for restoring MV).
           - If a cache error, etc. occurs, RV may not be used for restoration because it is not clear whether the RV
             data has integrity or not (tape, etc. is required for restore).
           - To assure performance for tasks using MV, configure RV to have the same configuration (physical
          disks, RAID type) as MV. Also configure the CachePartitioning function to allocate the same number of
          caches as MV to RV.
Q3-1 I changed an LD name. Does it have impact on replication operations?
   A After an LD name is changed, use the iSMvollist command to recreate the volume list.
Q3-2 I changed a disk array configuration. Is there any way to make the OS recognize the change without system
     restart?
   A If you are using Linux, the only way to make the OS recognize the change is to restart the system.
     If you are using Windows 2000, Windows Server 2003, or Windows Server 2008, run the iSMrc_scan
     command provided by NEC Storage ReplicationControl, NEC Storage ReplicationControl, or NEC Storage
     Manager/ReplicationControl or open Computer Management and click Disk Management to scan the disk
     again. If this solution does not work, restart the system.




Q3-3 Are there any notes on starting or restarting a Windows system using RV?
   A RV in the following state will not be recognized after system restart:
         - RV is in NotReady state due to a pair in Replicate or Restore.
         - The access restriction for RV has been set to Read Only or NotReady.
      Separate all the pairs in Replicate or Restore and change the access restriction for RV to ReadWrite. Then
      restart the system or scan the disk to make the system recognize RV.
      In a Windows 2000 system where automatic mount is disabled (*) and devices are unmounted, be sure to
      execute the iSMrc_scan command after starting the system to have the system recognize RV again.
      There is no need to make any configuration changes for restarting a system using only MV.
      * When the iSMrc_umount command is executed under one of the following conditions:
         - offline is specified for unmounting
         - NOTREADY is specified for the UMOUNT_RVACC parameter in the [FILESYSTEMOPERATION]
           section in a replication operation option configuration file (iSMrpl.ini) for unmounting.
Q3-4 I changed a partition on Windows. Does it have any impact on operations?
   A After you change a partition, use the iSMvollist command to recreate the volume list.
Q3-5 Is buffer flash (iSMrc_flush) or drive unmount (iSMrc_umount) necessary for operations on Windows?
   A Reflect the data that applications and OS retain on the caches into a volume to synchronize states of the OS
     and the volume.
     If these states are not synchronized, the volume may not be used. To prevent it, perform buffer flash
     (iSMrc_flush) and drive unmount (iSMrc_umount) for MV before performing separation.
Q3-6 Where is the replication operation option configuration file stored on Windows?
     Can I apply the old version of replication operation option configuration file to upgraded ReplicationControl?
   A [Ver2.1.007 or earlier]
          When ReplicationControl is installed, a replication operation option configuration file (iSMrpl.ini file) is
          created under the system folder.
          Keep the replication operation option configuration file under the system folder.
          The replication operation option configuration file is deleted when ReplicationControl is uninstalled. To
          apply an old replication operation configuration file to updated ReplicationControl, back up the
          configuration file in another location before upgrade and overwrite the configuration file created in the
          upgraded machine with the backed-up file after upgrade. Alternatively, configure the newly-created
          configuration file after upgrade.


      [Ver2.1.007 or later]
          When ReplicationControl is installed, a replication operation option configuration file (iSMrpl.ini file) is
          created in the ismvol folder under the system holder.
          The system folder contains a shortcut to the iSMrpl.ini file. Keep the replication operation option
          configuration file in the ismvol folder under the system folder.
          You can also access the replication operation option configuration file by using a shortcut under the
          system folder. The replication operation option configuration file is not deleted when ReplicationControl
          is uninstalled. When ReplicationControl is upgraded, the old version of configuration file is taken over to
          the upgraded ReplicationControl.
Q3-7 How does ReplicationControl save log information?
   A ReplicationControl logs command trace and operation trace, and the logs are recorded with the event log
     (Windows) or syslog (UNIX). The command trace and the operation trace are log information
     ReplicationControl internally retain and by default, they can be as large as 5MB (1MB for command trace and
     4MB for operation trace) in the installation folder.
     You can change the setting whether to report logs and the maximum log size setting by using the replication
     operation option configuration file on Windows or by using an environment variable on UNIX.
     For more information, see Chapter 8 in NEC Storage Software ControlCommand Command Reference
     included in manuals for NEC Storage D series or Chapter 7 in NEC Storage Software ControlCommandSet
     Command Reference included in manuals for NEC Storage S series.
Q3-8 Can I serially configure a RemoteDataReplication pair and a DynamicDataReplication pair and replicate them
     at the same time?
   A Simultaneous replication for serially-configured pairs is supported by Ver3.1 or later of ReplicationControl.
     To enable the simultaneous replication for serially-configured pairs in ReplicationControl Ver3.1 to Ver3.3, the
     following software needs to be installed:
        - NEC Storage RemoteDataReplication Ver2 or later
        - NEC Storage RemoteDataReplication/DisasterRecovery
        - NEC Storage ReplicationControl/DisasterRecovery
     To enable the simultaneous replication for serially-configured pairs in ReplicationControl Ver3.4 or later, the
     following software needs to be installed:
        - NEC Storage RemoteDataReplication Ver2 or later
     To enable the simultaneous replication for serially-configured pairs in ReplicationControl Ver5.1 or later, the
     following software needs to be installed:
        - NEC Storage RemoteDataReplication
Q3-9 Can I operate a pair in a remote disk array connected by using RemoteDataReplication?
   A You can remotely operate a RemoteDataReplication pair which is connected to a volume accessible from the
     application server within one layer. The functions you can use for a remote pair are the functions which can be
     performed by executing the replication and information display commands (iSMrc_replicate, iSMrc_separate,
     iSMrc_restore, iSMrc_change, iSMrc_wait, iSMrc_query, iSMrc_sense). You cannot execute commands to
     display disk array information, pair setting and association with server information (iSMrc_arrayinfo,
     iSMrc_ldlist, iSMrc_pair, iSMvollist). Only a logical disk name can be used as a volume type that will be used
     for specifying a pair to be operated.
Q4-1 A disk array volume cannot be recognized. What should I do?
   A If the OS does not recognize a disk even after system restart, the AccessControl setting may be incorrect. The
     OS cannot recognize a volume if access to the volume is restricted by AccessControl. Check the
     AccessControl setting in NEC Storage Manager. If the setting disconnects the volume from the application
     server, reconfigure the setting.
Q4-2 Some volumes are not displayed by executing the iSMvollist command. What should I do?
   A The volume list may not have been created by executing the iSMvollist command or the volumes may not be
     recognized by the OS. Check if the volumes are correctly recognized by the OS and recreate the volume list.
Q4-3 Drive letters for some volumes are not displayed by executing the iSMvollist command. What should I do?
   A It will occur if a volume list is created by executing the iSMvollist command without any drive letters given.
     Before creating a volume list, perform separation, specify drive letters and check that the volumes are
     correctly recognized by OS.
Q4-4 A replication operation command (such as iSMrc_replicate and iSMrc_separate) failed and abnormally ended.
     What should I do?
   A See the displayed message and take the action described in a manual.
Q4-5 On a Windows machine, the OS does not recognize volumes. What should I do?
   A The OS does not recognize RV under one of the following conditions:
        - RV is in NotReady state due to a pair in Replicate or Restore.
        - The access restriction for RV has been set to Read Only or NotReady.
     Separate all the pairs in Replicate or Restore and change the access restriction for RV to ReadWrite. Then
     restart the system or scan the disk to make the system recognize RV.
     In a Windows 2000 system that unmounts devices with automatic mount disabled (*), be sure to execute the
     iSMrc_scan command after starting the system to have the system recognize RV again.
     * When the iSMrc_umount command is executed under one of the following conditions:
        - offline is specified for unmounting
        - NOTREADY is specified for the UMOUNT_RVACC parameter in the [FILESYSTEMOPERATION]
          section in a replication operation option configuration file (iSMrpl.ini) for unmounting.
Q4-6 When I attempted to unmount a volume by executing the iSMrc_umount command, the error iSM13609
     appeared and I failed to unmount the volume. What should I do?
   A When you attempt to unmount a volume while it is accessed by a Windows service or other applications, the
     following message appears and the iSMrc_umount command ends abnormally:
         iSM13609: Access of specified disk was refused.


     Before unmounting a volume by using the iSMrc_umount command, be sure to quit all the services and
     applications that may access the volume.
         Examples of services and applications that may access volumes
            - Explorer
            - Recycle bin
            - ESMPRO (ESMCommonService, ESMFSService, ESM Storage Service)
            - IIS (IIS Admin Service, World Wide Web Publishing Service)
            - FTP (FTP Publishing Service)
            - Distributed Link Tracking Service (Distributed Link Tracking Server and Distributed Link Tracking
              Client)
            - Monitoring software (for viruses or drives)
            - Backup software


     There is a utility that allows you to identify programs and services accessing volumes.
     For how to download and use the utility, access http://www.sysinternals.com/.


            - Process Explorer (GUI format)
            - Handle (command line format)


     If unmounting a volume fails with all the services and applications that may access the volumes stopped,
     check the following:


            - In a Windows 2000 environment, unmount may fail due to a bug of Windows 2000 Link Tracking
               Service.
          Microsoft has provided a program to fix this bug. Be sure to apply Windows 2000 SP3 or later or the fix
          program (W2K-030).


              - In a Windows Server 2008 environment, unmount may fail due to a bug of Windows Server 2008
                Server Service.
          Microsoft has provided a program to fix this bug. Be sure to apply the fix program (Microsoft Knowledge
          Base - 952790).
 Q4-7 I cannot execute the iSMrc_vollist command because it does not exist. What should I do?
    A The function of the iSMrc_vollist command supported by NEC Storage Manager/ReplicationControl in NEC
      Storage Manager Ver1.3.007 or earlier has been integrated into the function of the Volume List Display
      command iSMvollist. You can specify an option in the iSMvollist command in the same way as for
      iSMrc_vollist command. However, when you execute the iSMrc_vollist command as it has been used
      conventionally, create a symbolic link for "/opt/iSMvol/sbin/iSMvollist" or create an alias. An example of
      creating a symbolic link:
      ln -s /opt/iSMvol/sbin/iSMvollist /usr/sbin/iSMrc_vollist
 Q4-8 When I attempted to import a VxVM disk group, the following message appeared and I failed to import the
      group. What should I do?
      vxvm:vxdg: ERROR: Disk group xxxx: import failed: Disk write failure or
      vxvm:vxdg: ERROR: Disk group xxxx: import failed: No valid disk found containing disk group
    A If RV for which access restriction is set to RO (ReadOnly) exists in a disk group, you cannot import the disk
      group. Set RW (ReadWrite) for the access restriction for RV which you want to use as a disk group.
 Q4-9 When I executed the iSMrc_mount command, the error iSM13574 appeared. What should I do?
    A If execution of the iSMrc_mount command for RV on a backup server causes the error iSM13574, check the
      following:
         1. Check that the volume list on the backup server is the latest version. A volume list needs to be updated
            when a configuration is changed not only for a NEC Storage device but also for a partition.
         2. When a backup server is stopped and then restarted with MV and RV in Replicate/Restore, an error may
            occur because the backup server cannot recognize the RV. Separate MV and RV and then perform one
            of the following to make the backup server recognize RV:
               - Stop and restart the backup server.
               - Execute the iSMrc_scan command.
         3. When a backup server is stopped and then restarted with the access restriction for RV set to Read Only
            or NotReady, an error may occur because the backup server cannot recognize the RV.
            Change the access restriction for RV to Read/Write and perform one of the following to make the
            backup server recognize RV:
               - Stop and restart the backup server.
               - Execute the iSMrc_scan command.
           When you stop and restart a backup server in a Windows 2000 system with automatic mount disabled
           (*), be sure to execute the iSMrc_scan command after system restart to make the system to recognize
           RV.
       * When the iSMrc_umount command is executed under one of the following conditions:
               - offline is specified for unmounting
               - NOTREADY is specified for the UMOUNT_RVACC parameter in the [FILESYSTEMOPERATION]
                 section in a replication operation option configuration file (iSMrpl.ini) for unmounting.
Q4-10 The size of ReplicationControl logs has crossed the specified upper limit. What is the possible cause?
    A The ReplicationControl Ver3.3 or earlier checks the log size when starting the ReplicationControl command
      and changes the log when the size crosses the upper limit.
      Because of this, the log size may cross the upper limit while the command is executed though it was under the
      limit when the command was started.
      Especially when a large amount logs are reported at a time by a processing such as batch specification, the
      log size is more likely to cross the upper limit.
      To prevent data in the installation directory of ReplicationControl from exceeding the capacity because of logs
      over the upper limit, create a symbolic link.
      The ReplicationControl Ver3.4 or later checks if the log size has crossed the upper limit and change the log if
      necessary when logs are reported.
Q4-11 When I executed the iSMrc_signature command, the error iSM13615 or iSM13623 appeared. What should I
      do?
    A When the iSMrc_signature is executed multiple times, the error iSM13615 or iSM13623 may appear.
      If you have confirmed that this command was executed multiple times, execute this command again.
Q4-12 When I attempted to unmount RV by executing the iSMrc_umount command with the -offline option specified
      on Windows Server 2008 R2 with BitLocker enabled, the following message was reported on the event log.
      What should I do?
       <Message>
         Source: Microsoft-Windows-BitLocker-Driver
         ID: 24620
         Message: Encrypted volume check: Volume information on
      \?\Volume{e3eece92-b857-11de-ab2a-0019dbc2ceba} cannot be read.
                Error code: 0x80000010
         * The volume name may vary.
    A Ignore this event because this error message only informs BitLocker does not recognize the device you are
      about to operate, and it does not affect the system operation.
      See the following online support page provided by Microsoft:

      http://support.microsoft.com/kb/976733
Storage Control

SnapControl
1. Introduction
    Q1-1 Tell me about SnapControl.
    Q1-2 What is the advantage of using SnapControl?


2. Installation
    Q2-1 Which software is required for using the snapshot function?
    Q2-2 Are there any notes on using SnapControl and ReplicationControl together on the same server?
    Q2-3 What kinds of volumes are required for using the snapshot function?
    Q2-4 Tell me about the volume types to be specified by -bvflg or -svflg in the SnapControl command.
    Q2-5 Does a changed drive letter or mount point work normally on Windows?
    Q2-6 Are there any notes on changing the access right for files on BV?
    Q2-7 Tell me about storage series supporting the snapshot function.
    Q2-8 How much disk capacity and memory amount are required for running SnapControl?
    Q2-9 Are there any notes on applying quota management or file screening to Windows NTFS folders?
   Q2-10 Can I use a GPT (GUID partition table) disk?


3. Operation
    Q3-1 I changed an LD name. Does it have impact on snapshot operations?
    Q3-2 I changed a disk array configuration. Is there any way to make the OS recognize the change without restarting
         the system?
    Q3-3 Can I use volume management software such as LVM or VxVM?
    Q3-4 Are there any notes on starting or restarting a Windows system using LV?
    Q3-5 I changed a partition on Windows. Does it have any impact on operations?
    Q3-6 Is buffer flash (iSMrc_flush) or drive unmount (iSMrc_umount) necessary for operations on Windows?
    Q3-7 How does SnapControl save log information?


4. Troubleshooting
    Q4-1 A disk array volume is not recognized. What should I do?
    Q4-2 Some volumes are not displayed by executing the iSMvollist command. What should I do?
    Q4-3 When restoration to BV was performed through LV in an MSCS environment, mounting BV/LV on the backup
         server failed with the following error. What should I do?
         iSM13563: System call error (error code=170)
    Q4-4 I cannot mount LV on Windows. What should I do?
    Q4-5 When I attempted to unmount a volume by executing the iSMrc_umount command, the error iSM13609
         appeared and the unmount failed. What should I do?
    Q4-6 A timeout occurred when SnapControl and NEC Storage Manager operated together. What should I do?
    Q4-7 When I attempted to unmount RV by executing the iSMrc_umount command with the -offline option specified
         on Windows Server 2008 R2 in which BitLocker was enabled, the following message was reported on the
         event log. What should I do?
          <Message>
            Source: Microsoft-Windows-BitLocker-Driver
            ID: 24620
            Message: Encrypted volume check: Volume information on
         \?\Volume{e3eece92-b857-11de-ab2a-0019dbc2ceba} cannot be read.
                   Error code: 0x80000010
       * The volume name may vary.


Q1-1 Tell me about SnapControl.
   A SnapControl operates the snapshot function (DynamicSnapVolume) through the command line interface (CLI)
     on an application server connected to the NEC Storage D series/S series. It allows for association with
     backup software running on a backup server by using scripts, enabling unmanned backup operation.
Q1-2 What is the advantage of using SnapControl?
   A The biggest advantage of using SnapControl is high-speed and low-cost non-disruptive backup operation.
     As well as ReplicationControl, SnapControl can be used for the following:
         - High-speed backup
         - Backup in parallel with online tasks
         - Performing online tasks and search tasks simultaneously
         - Performing batch processing simultaneously
         - Creating test data for applications
Q2-1 Which software is required for using the snapshot function?
   A    ■ Application server
          Install NEC Storage ControlCommand (NEC Storage ControlCommandSet).
          Install NEC Storage SnapControl for a version that has not been integrated into ControlCommandSet.
        ■ Management server
          Install NEC Storage Manager to manage disk arrays and configure relationships between master
          volumes and replication volumes.
        ■ Disk array
          Products such as NEC Storage BaseProduct, NEC Storage DynamicSnapVolume, and NEC Storage
          AccessControl are offered. Purchase necessary products and unlock the licenses of the products.
Q2-2 Are there any notes on using SnapControl and ReplicationControl together on the same server?
   A ReplicationControl and SnapControl that have not been integrated into ControlCommand and will be installed
     on the same server need to have the same version.
Q2-3 What kinds of volumes are required for using the snapshot function?
   A The following kinds of volumes are required for the snapshot function:
        ■ BV (Base Volume)
          Replication source volume
        ■ SV (Snapshot Volume)
          Volume that saves a replica of BV at a particular moment on an instruction to create a snapshot
        ■ LV (Link Volume)
          Virtual volume used to access BV or SV
        ■ CV (Control Volume)
          Control volume for disk arrays that is required for a server to use LV
Q2-4 Tell me about the volume types to be specified by -bvflg or -svflg in the SnapControl command.
   A A volume type specified in a command represents a parameter format specified for -bv or -sv.
     A special file (device file) name or a LD name is specified on UNIX, and a drive letter or a mount point is
     specified on Windows.
Q2-5 Does a changed drive letter or mount point work normally on Windows?
   A Use Disk Management to restore a drive letter that has been unexpectedly changed to the original. Recreate
     a volume list by executing the iSMvollist command to reflect information on the changed drive letter or mount
     point. If the drive letter or mount point is used in a batch file, etc., correct the file.
Q2-6 Are there any notes on changing the access right for files on BV?
   A When a snapshot is created, the information on access rights and users that have been specified for
      directories (folders) and files is stored in SV as it is. Therefore user information on a server using BV should
      be the same as the server using SV through LV, and a user who accesses directories and files on SV also
      should be the same for BV.
 Q2-7 Tell me about storage series supporting the snapshot function.
    A The snapshot function is supported by the following storage series:
          - NEC Storage D8-30
          - NEC Storage D8-20
          - NEC Storage D8-10
          - NEC Storage D4-30
          - NEC Storage D3-10i
          - NEC Storage D3-10
          - NEC Storage D1-10
          - NEC Storage S4900
          - NEC Storage S2900
          - NEC Storage S2800
          - NEC Storage S2500
          - NEC Storage S2400
          - NEC Storage S1500
          - NEC Storage S1400
      Except for a device used exclusively for iSCSI (NEC Storage D3-10i), use FC (Fibre Channel) to connect a
      server and disk arrays.
 Q2-8 How much disk capacity and memory amount are required for running SnapControl?
    A For information about disk capacity and memory amount required for running SnapControl, see FAQ for
      ControlCommand. For the latest information, see NEC Storage ControlCommand Installation Guide for D
      Series or NEC Storage ControlCommand Installation Guide for S Series.
 Q2-9 Are there any notes on applying quota management or file screening to Windows NTFS folders?
    A When BV that contains volumes or folders to which a resource management function such as quota
      management (*1) or file screening (*2) is applied is used to create or restore a snapshot, the setting
      configured for BV will be reflected into SV at snapshot creation or the setting configured for SV will be
      reflected into BV via LV at snapshot restoration. Because of this, make sure to configure the appropriate
      settings of the quota management or the file screening function if you want to restart operation on BV or
      update SV via LV after restoration.

      (*1) Function to restrict and control the amount of use not to exceed the specified limit
      (*2) Function to prevent files having particular extensions from being saved
Q2-10 Can I use a GPT (GUID partition table) disk?
    A In the NEC Storage D series, Windows GPT disks are available when ControlCommand Ver 5.1 or later is
      used. Note the following when using GPT disks:
          - Use BV and LV (SV) separately on different servers.
          - When multiple LVs are configured for BV, use the LVs separately on different servers.
          - Set the format for using logical disks to WG.
            To perform snapshot functions for GPT disks, modify the option configuration file. For more information
          - about the option configuration file, see NEC Storage Software ControlCommand Command Reference
            included in manuals for NEC Storage D series or manuals for NEC Storage S series.
 Q3-1 I changed an LD name. Does it have impact on snapshot operations?
    A After an LD is changed, use the iSMvollist command to recreate the volume list.
 Q3-2 I changed a disk array configuration. Is there any way to make the OS recognize the change without restarting
      the system?
   A If you are using Linux, the only way to make the OS recognize the change is to restart the system.
     If you are using Windows 2000, Windows Server 2003, or Windows Server 2008, run the iSMrc_scan
     command provided by NEC Storage ControlCommand or open Computer Management and click Disk
     Management to scan the disk again. If this solution does not work, restart the system.




Q3-3 Are there any notes on starting or restarting a Windows system using LV?
   A A server using LV stops recognizing unlinked volumes (LV) when the system is restarted. Set links for LVs
     before restarting the system. Restart a server using only BV without making any changes.
Q3-4 I changed a partition on Windows. Does it have any impact on operations?
   A After you change a partition, use the iSMvollist command to recreate the volume list.
Q3-5 Is buffer flash (iSMrc_flush) or drive unmount (iSMrc_umount) necessary for operations on Windows?
   A Reflect the data that applications and OS retain on the caches into a volume to synchronize states of the OS
     and the volume.
     If these states are not synchronized, the volume may not be used. To prevent it, perform buffer flash
     (iSMrc_flush) and drive unmount (iSMrc_umount) when creating a snapshot.
Q3-6 How does SnapControl save log information?
   A SnapControl logs command trace and operation trace, and the logs are recorded with the event log
     (Windows) or syslog (UNIX). The command trace and the operation trace are log information SnapControl
     internally retain and by default, they can be as large as 5MB (1MB for command trace and 4MB for
     operation trace) in the installation folder.
     You can change the setting whether to report logs and the maximum log size setting by using the replication
     operation option configuration file on Windows or by using an environment variable on UNIX.
     For more information, see Chapter 8 in NEC Storage Software ControlCommand Command Reference
     included in manuals for NEC Storage D series or Chapter 7 in NEC Storage Software ControlCommandSet
     Command Reference included in manuals for NEC Storage S series.
Q4-1 A disk array volume is not recognized. What should I do?
   A If the OS does not recognize a disk after system restart, the AccessControl setting may be incorrect. The OS
     cannot recognize a volume if access to the volume is restricted by AccessControl. Check the AccessControl
     setting in NEC Storage Manager. If the setting disconnects the volume from the application server,
     reconfigure the setting.
Q4-2 Some volumes are not displayed by executing the iSMvollist command. What should I do?
   A The iSMvollist command may not have created the volume list or the volumes may not be recognized by the
     OS. Check if the volumes are correctly recognized by the OS and recreate the volume list.
Q4-3 When restoration to BV was performed through LV in an MSCS environment, mounting BV/LV on the backup
     server failed with the following error. What should I do?
     iSM13563: System call error (error code=170)
   A A shared disk (BV) to be restored is still controlled by MSCS and cannot be used by other servers.


     Take the following procedure to remount BV/LV:
       1. Set a shared disk (BV) to be restored to offline (on the application server).
          Configure this setting by using a MSCS management tool (GUI or CLI).
       2. Shut down the application server.
       3. Link BV and LV (on the backup server).
       4. Mount BV/LV (on the backup server).


     The steps you should take depends on the type of restoration as follows:
         - For logical restoration with no disk reconfiguration,
           perform steps 1 to 4.
        - For physical restoration with disk reconfiguration that follows restoration of MSCS,
          perform steps 1 to 4.
        - For physical restoration with disk reconfiguration that precedes restoration of MSCS,
          perform steps 2 to 4 (step 1 is not required).
Q4-4 I cannot mount LV on Windows. What should I do?
   A The OS may not have recognized LV because the server was restarted when LV was in Not Ready (cannot be
     referred/updated), such as when LV was not linked or LV was unmounted by the iSMrc_umount command,
     etc. If this is the case, make the OS recognize LV again by following the procedure described in 3.9 Start of
     Server Connected to SV (LV) in Snapshot User's Manual (Installation and Operation Guide for Windows).
Q4-5 When I attempted to unmount a volume by executing the iSMrc_umount command, the error iSM13609
     appeared and the unmount failed. What should I do?
   A When you attempt to unmount a volume accessed by a Windows service or other applications, the following
     message appears and the iSMrc_umount command ends abnormally:
         iSM13609: Access of specified disk was refused.


     Before unmounting a volume by using the iSMrc_umount command, be sure to quit all the services and
     applications that may access the volume.
         Examples of services and applications that may access volumes
            - Explorer
            - Recycle bin
            - ESMPRO (ESMCommonService, ESMFSService, ESM Storage Service)
            - IIS (IIS Admin Service, World Wide Web Publishing Service)
            - FTP (FTP Publishing Service)
            - Distributed Link Tracking Service (Distributed Link Tracking Server and Distributed Link Tracking
              Client)
            - Monitoring software (for viruses or drives)
            - Backup software


     There is a utility that allows you to identify programs and services accessing volumes.
     For how to download and use the utility, access http://www.sysinternals.com/.


            - Process Explorer (GUI format)
            - Handle (command line format)


     If unmounting a volume fails with all the services and applications that may access the volumes stopped,
     check the following:


            - In a Windows 2000 environment, unmount may fail due to a bug of Windows 2000 Link Tracking
              Service.
         Microsoft has provided a program to fix this bug. Be sure to apply Windows 2000 SP3 or later or the fix
         program (W2K-030).


            - In a Windows Server 2008 environment, unmount may fail due to a bug of Windows Server 2008
              Server Service.
         Microsoft has provided a program to fix this bug. Be sure to apply the fix program (Microsoft Knowledge
         BAse - 952790).
Q4-6 A timeout occurred when SnapControl and NEC Storage Manager operated together. What should I do?
   A A timeout may occur when SnapControl and NEC Storage Manager work together and a snapshot is created
     or cyclically created through the snapshot management window in SnapControl or in NEC Storage Manager.


     For notes on creating snapshots, see Q3-3 in the DynamicSnapVolume section.


     If a timeout occurs due to creation or cyclical creation of a snapshot, processing will continue on the iSM
     server and a message corresponding to operation will appear on the iSM server operation log window and in
     the message display area on the iSM client main window. When a timeout occurs, stop your operation and
     wait for a message to appear.
     If a timeout occurs due to other reason than creation or cyclical creation of a snapshot, check the server
     status and restart your operation.
Q4-7 When I attempted to unmount RV by executing the iSMrc_umount command with the -offline option specified
     on Windows Server 2008 R2 in which BitLocker was enabled, the following message was reported on the
     event log. What should I do?
      <Message>
        Source: Microsoft-Windows-BitLocker-Driver
        ID: 24620
        Message: Encrypted volume check: Volume information on
     \?\Volume{e3eece92-b857-11de-ab2a-0019dbc2ceba} cannot be read.
               Error code: 0x80000010
        * The volume name may vary.
   A Ignore this event because this error message only informs BitLocker does not recognize the device you are
     about to operate, and it does not affect the system operation.
     See the following online support page provided by Microsoft:

     http://support.microsoft.com/kb/976733
Storage Control

ReplicationControl/DisasterRecovery
1. Introduction
      Q1-1 What kind of is product ReplicationControl/DisasterRecovery?


2. Installation
      Q2-1 Which NEC Storage series support ReplicationControl/DisasterRecovery?
      Q2-2 Which software is required for installing ReplicationControl/DisasterRecovery?
      Q2-3 How much disk capacity and memory amount are required for running
           ReplicationControl/DisasterRecovery?
      Q2-4 Are there any notes on creating an ATgroup for NEC Storage S4900?


3. Operation
      Q3-1 How does ReplicationControl/DisasterRecovery save log information?
      Q3-2 Can I operate a pair or an ATgroup in a remote disk array connected by using
           RemoteDataReplication/DisasterRecovery?
      Q3-3 When I attempted to create an ATgroup, the following error message appeared on the replication batch
           setting window. What possibly caused the error?
             failure(link disk array name not specified)


      Q1-1 What kind of product is ReplicationControl/DisasterRecovery?
         A It operates RemoteDataReplication/DisasterRecovery through an application server.
      Q2-1 Which NEC Storage series support ReplicationControl/DisasterRecovery?
         A The following NEC Storage series support ReplicationControl/DisasterRecovery:
            NEC Storage S4900, S4300, S3300, S2900, and S2800
            NEC Storage D8 series
      Q2-2 Which software is required for installing ReplicationControl/DisasterRecovery?
         A The following software is required for installing ReplicationControl/DisasterRecovery:
                  - NEC Storage BaseProduct
                  - NEC Storage AccessControl (coming with NEC Storage BaseProduct)
                  - NEC Storage RemoteDataReplication
                  - NEC Storage RemoteDataReplication/DisasterRecovery
                  - NEC Storage ReplicationControl (coming with NEC Storage ControlCommand)
                    (NEC Storage ReplicationControl Ver3.1 or later, or
                    NEC Storage ControlCommandSet Ver4.1 or later (*))
                  - NEC Storage ReplicationControl/DisasterRecovery (coming with NEC Storage ControlCommand)
                    (NEC Storage ReplicationControl/DisasterRecovery Ver3.1 or later, or
                    NEC Storage ControlCommandSet Ver4.1 or later (*))


                      * The NEC Storage ControlCommandSet you will arrange contains the following functions:
                          - NEC Storage ReplicationControl
                          - NEC Storage ReplicationControl/DisasterRecovery


            As well as arranging these software products, apply for the PP and support service.
      Q2-3 How much disk capacity and memory amount are required for running
     ReplicationControl/DisasterRecovery?
   A For information about disk capacity and memory amount required for running
     ReplicationControl/DisasterRecovery, see FAQ for ControlCommand. For the latest information, see NEC
     Storage ControlCommand Installation Guide for D series or NEC Storage ControlCommand Installation
     Guide for S series.
Q2-4 Are there any notes on creating an ATgroup for NEC Storage S4900?
   A To create an ATgroup for NEC Storage S4900 that serves as a concentrator, check if the function to specify
     Link Disk Array Name is supported. If it is supported, specify a Link Disk Array Name.


     [Checking if the function of specifying Link Disk Array Name is supported]
       1. Select a disk array that will serve as a concentrator on the replication window and open the disk array
          properties window.
       2. If the function is supported, ON appears in Function to specify Destination Disk Array Name in
          Creating Atgroup.


     [Specifying Link Disk Array Name]
        - To create an ATgroup by using the replication batch setting of iSM client
           → See F.2 "Pair Setting File" in NEC Storage Software Configuration Setting Tool User's Manual
             (GUI) included in manuals for NEC Storage D series or manuals for NEC Storage S series.
        - To create an ATgroup by using the Replication Management of iSM client
           → See 4.1.3 "Creating an ATgroup" in Data Replication User's Manual (Disaster Recovery System
             Installation and Operation Guide) included in manuals for NEC Storage D series or manuals for
             NEC Storage S series.
        - To create an ATgroup by using the ReplicationControl/DisasterRecovery command
           → See 4.2.8 "Building an ATgroup (iSMrc_atg)" in Data Replication User's Manual (Disaster
             Recovery System Installation and Operation Guide) included in manuals for NEC Storage D
             series or manuals for NEC Storage S series.


        * The function to specify Link Disk Array Name is supported by NEC Storage Manager Ver4.2 or later.
Q3-1 How does ReplicationControl/DisasterRecovery save log information?
   A ReplicationControl/DisasterRecovery logs command trace and operation trace, and the logs are recorded
     with the event log (Windows) or syslog (UNIX).
     The command trace and the operation trace are log information ReplicationControl/DisasterRecovery
     internally retain and by default, they can be as large as 5MB (1MB for command trace and 4MB for operation
     trace) in the installation folder for ReplicationControl.
     The command trace and the operation trace are shared with ReplicationControl and you can change the
     setting whether to report logs and the maximum log size setting by using the replication operation option
     configuration file on Windows or by using an environment variable on UNIX.
     For more information, see Chapter 8 in NEC Storage Software ControlCommand Command Reference
     included in manuals for NEC Storage D series or Chapter 7 in NEC Storage Software ControlCommandSet
     Command Reference included in manuals for NEC Storage S series.
Q3-2 Can I operate a pair or an ATgroup in a remote disk array connected by using
     RemoteDataReplication/DisasterRecovery?
   A You can remotely operate a RemoteDataReplication pair which is connected to a volume accessible from
     the application server within one layer. The functions you can use for a remote pair are the functions which
     can be performed by executing the replication and information display commands (iSMrc_replicate,
     iSMrc_separate, iSMrc_restore, iSMrc_change, iSMrc_wait, iSMrc_query, iSMrc_sense). You cannot
     execute commands to display disk array information, pair setting and association with server information
     (iSMrc_arrayinfo, iSMrc_ldlist, iSMrc_pair, iSMvollist). Only a logical disk name can be used as a volume
     type that will be used for specifying a pair to be operated.

     An ATgroup can be operated only by the server that can access MV or RV of a pair that belongs to the
     ATgroup. Also the ATgroup configuration command (iSMrc_atg) can be executed only by the server that can
     access MV of a pair to be registered with the ATgroup.
Q3-3 When I attempted to create an ATgroup, the following error message appeared on the replication batch
     setting window. What possibly caused the error?
       failure(link disk array name not specified)
   A To create an ATgroup for a disk array device supporting the function to specify Link Disk Array Name,
     specify a Link Disk Array Name. Otherwise an error message will appear.


     [Checking if the function to specify Link Disk Array Name is supported]
       1. Select a disk array that will serve as a concentrator on the replication window and open the disk array
          properties window.
       2. If the function is supported, ON appears in Function to specify Destination Disk Array Name in
          Creating Atgroup.


     [Specifying Link Disk Array Name]
          See F.2 "Pair Setting File" in NEC Storage Software Configuration Setting Tool User's Manual (GUI)
          included in manuals for NEC Storage D series or manuals for NEC Storage S series.
Storage Control

ProtectControl
1. Introduction
   Q1-1 What funcitons does ProtectControl provide?
   Q1-2 What is the benefit of using ProtectControl?
   Q1-3 Can I use ProtectControl and the data replication function together?


2. Installation
   Q2-1 Are there any devices that must be in place to use the data retention function?
   Q2-2 Are there any software programs that are required to use the data retention function?
   Q2-3 Is Windows Server 2003 SP1 or later required to use the data retention function (Windows)?
   Q2-4 What volume is necessary to use the data retention function?
   Q2-5 What is the volume type specified by –volflg of the ProtectControl command?
   Q2-6 Can the operation in Windows be continued successfully after changing a drive letter or mount point?
   Q2-7 Can the operation in Linux be continued successfully after changing a mount point?
   Q2-8 How much disk capacity and memory amount do I need to use ProtectContro?


3. Operation
   Q3-1 Does changing an LD name impact the operation of the data retention function?
   Q3-2 The disk configuraiton has been changed. Is there any way to make the OS recognize the change without
        restarting the system?
   Q3-3 Can I use a volume management software program such as LVM or VxVM?
   Q3-4 Is unmount of protected volumes necessary?
   Q3-5 How does ProtectControl collect logs?
   Q3-6 Is the retention automatically released when the volume retention period expires?
   Q3-7 Can volumes for databases be protected?


4. Troubleshooting
   Q4-1 What should I do when volumes on a disk array are not recognized?
   Q4-2 What should I do when some volumes are not shown after running the iSMvollist command?
   Q4-3 What should I do if I set protection for a volume that I did not intend?


   Q1-1 What functions does ProtectControl provide?
      A ProtectControl is a function to operate the data retention function (VolumeProtect) by using a command line
        interface (CLI) on an application server connected to the NEC Storage series. ProtectControl prevents
        unauthorized data rewrite and data corruption and allows for storing data in a format that cannot be tampered
        for a long period of time.
   Q1-2 What is the benefit of using ProtectControl?
      A ProtectControl works with business operations to provide means to store data appropriately and control access.
   Q1-3 Can I use ProtectControl and the data reprlicaiton function together?
      A Yes. To use the data retention function and the data replication function together, NEC Storage
        ControlCommandSet Ver4.3 or later and the storage control fuction version 0430 or later are required.
   Q2-1 Are there any devices that must be in place to use the data retention function?
      A A disk array from the NEC Storage D series, S4900, S2900, S2500, or S1500 is requisite to use the data
        retention function. The archive server and the disk array must be connected by Fibre Channel (FC).
   Q2-2 Are there any software programs that are required to use the data retention function?
   A ■ On application server:
     Install NEC Stroage ControlCommand (NEC Storage ControlCommandSet).
     ■ On the management server:
     The management software program “NEC Storage Manager” must be installed to manage disk arrays and to
     create volumes.
     ■ On disk arrays:
     Products such as “NEC Storage BaseProduct”, “NEC Storage VolumeProtect”, and “NEC Storage
     AccessControl” are set on disk arrays. Corresponding products must be purchased to unlock licenses.
Q2-3 Is Windows Server 2003 SP1 or later required to use the data retention (Windows) function?
   A Yes. To use the data retention function, you need Windows Server 2003 SP1 or later.
Q2-4 What volume is necessary to use the data retention function?
   A The following volume is necessary to use the data retention function:
     ■Control Volume (CV)
     This is a control volume for disk arrays.
Q2-5 What is the volume type specified by -volflg of the ProtectControl command?
   A The volume type specified in the command identifies a parameter type specified for –vol. For example,
     specification of a special file (device file) name or an LD name in Linux or specification of a physical disk
     number or an LD name in Windows. For details, see Chapter 5 of NEC Storage Software ControlCommand
     Command Reference for NEC Storage D series manual or NEC Storage S series manual.
Q2-6 Can the operation in Windows be continued successfully after changing a drive letter or mount point?
   A If change of a drive letter is unintended, the original status can be restored by using Disk Management. A
     volume list must be re-created by using the iSMvollist command to reflect the changed drive letter or mount
     point information.
Q2-7 Can the operation in Linux be continued successfully after changing a mount point?
   A Yes. You do not need to update the volume list.
Q2-8 How much disk capacity and memory amount do I need to use ProtectControl?
   A See FAQ for ControlCommand to find the information about the disk capacity and memory amount required to
     use ProtectControl. For the latest information, see NEC Storage D Series Installation Guide or NEC Storage S
     Series Installation Guide for ControlCommand.
Q3-1 Does changing an LD name impact the operation of the data retention function?
   A When an LD name is changed, a volume list must be re-created by using the iSMvollist command.
Q3-2 The disk array configuration has been changed. Is there any way to make the OS recognize the change without
     restarting the system?
   A If you are using Linux, the only way to make the OS recognize the change is to restart the system.
     If you are using Windows, run the iSMrc_scan command provided by ProtectControl or open Computer
     Management and click Disk Management to scan the disk again. If this solution does not work, restart the
     system.
Q3-3 Can I use a volume management software program such as LVM or VxVM?
   A No, you cannot use LVM or VxVM on protected volumes.
Q3-4 Is unmount of protected volumes necessary?
   A To protect volumes (iSMpc_protect) or release volume protection (iSMpc_release), unmount the volumes.
Q3-5 How does ProtectControl collect logs?
   A How ProtectControl has operated is recorded as logs in command trace, operation trace, event logs (Windows)
     and syslog (Linux). Command trace and operation trace are log information that ProtectControl saves internally
     in the installation folder. By default the maximum size is 5 MB (1 MB for command trace and 4 MB for operation
     trace).
     Use the option setting file on Windows or environment variables on Linux to configure whether or not to report
     logs and the maximum log size.
     For details, Chapter 8 of NEC Storage D series manual, NEC Storage Software ControlCommand Command
     Reference or Chapter 7 of NEC Storage S series manual, NEC Storage Software ControlCommandSet
     Command Reference.
Q3-6 Is retention automatically released when the volume retention periold expires?
   A Retention is not automatically released even if the retention period has expired, by which data confidentiality is
     kept. To release the retention, run the iSMpc_release command.
Q3-7 Can volumes for databases be protected?
   A Yes. When you use a database on a protected volume, it should be used as read-only database.
Q4-1 What should I do when volumes on a disk array are not recognized?
   A If the OS does not recognize disks after the system is restarted, the AccessControl settings may be configured
     incorrectly. Volumes to which access is restricted by AccessControl are not recognized by the OS. Check the
     AccessControl settings by using NEC Storage Manager. If the application server in question is not connected,
     configure the settings correctly.
Q4-2 What should I do when some volumes are not shown after running the iSMvollist command?
   A A volume list created by the iSMvollist command may be not in place or the volumes are not recognized. Check
     the volumes are successfully recognized by the OS and re-create a volume list.
Q4-3 What should I do if I set protection for a volume that I did not intend?
   A If protection mode is normal, protection can be released by using the iSMpc_release command.
     For situations other than above, release the protection after the retention periods is over or contact
     maintenance staff.
Storage Control

PowerControl
1. Introduction
      Q1-1 What functions does PowerControl provide?
      Q1-2 What is the benefit of using PowerControl?
      Q1-3 Can I use PowerControl and the data repliation function together?


2. Installation
      Q2-1 Are there any dvices that must be in place to use the power saving function?
      Q2-2 Are there any software programs that are required to use the power saving function?
      Q2-3 What volume is necessary to use the power saving function?
      Q2-4 What is the volume type specified by –volflg of the PowerControl command?
      Q2-5 Can the operation in Windows be continued successfully after chaning a drive letter or mount point?
      Q2-6 Can I use the power saving function from the terminal service remote desktop?
      Q2-7 What are supported OSes?
      Q2-8 How much disk capacity and memory amount do I need to use PowerControl?


3. Operation
      Q3-1 Does changing an LD name impact the operation of the power saving function?
      Q3-2 The disk configuration has been changed. Is there any way to make the OS recognize the change without
           restarting the system?
      Q3-3 Can I use a volume management software program such as LVM or VxVM?
      Q3-4 What should I note in starting or restarting a system that uses the power saving function?
      Q3-5 Is unmount of volumes necessary?
      Q3-6 How does PowerControl collect logs?


4. Troubleshooting
      Q4-1 What should I do when volumes on a disk array are not recognized?
      Q4-2 What should I do when some volumes are not show after running the iSMvollist command?
      Q4-3 Running the iSMec_start command by specifying a volume failed while starting pool operation. What should
           I do?
      Q4-4 What should I do when created volumes cannot be accessed from a server?


      Q1-1 What functions does PowerControl provide?
         A PowerControl is a function to operate the power saving function (StoragePowerConserver) by using a
           command line interface (CLI) on an application server connected to the NEC Storage D series. It allows for
           power saving associating with operations running on the server.
      Q1-2 What is the benefit of using PowerControl?
         A PowerControl works together with business operations to provide means to check how each volume is used
           and allow for power-saving operation according to how volumes are used.
      Q1-3 Can I use PowerControl and the data replication function together?
         A Power-saving operation on volumes (MV or RV) of the data replication function is possible. However,
           power-saving operation on volumes (BV, SV or LV) of the snapshot function is not possible.
      Q2-1 Are there any devices that must be in place to use the power saving function?
         A A disk array from the NEC Storage D series is requisite to use the power saving function.
           Servers and the disk array must be connected by Fibre Channel (FC).
Q2-2 Are there any software programs that are required to use the power saving function?
   A    ■ On application servers:
               Install NEC Storage ControlCommand.
        ■ On the management server:
               The management software program “NEC Storage Manager” must be installed to manage disk
               arrays and to create volumes.
        ■ On disk arrays:
               Products such as “NEC Storage BaseProduct”, “NEC Storage PowerConserver”, and “NEC
               Storage AccessControl” are set on disk arrays. Corresponding products must be purchased to
               unlock licenses.
Q2-3 What volume is necessary to use the power saving function?
   A The following volume is necessary to use the power saving function.
        ■ CV (Control Volume)
               This is a control volume for disk arrays.
Q2-4 What is the volume type specified by -volflg of the ProtectControl command?
   A The volume type specified in the command identifies a parameter type specified for –vol. For example,
     specification of an LD name or a special file (device file) name in UNIX or specification of an LD name or a
     drive letter in Windows. For details, see Chapter 6 of the manual, NEC Storage Software ControlCommand
     Command Reference.
Q2-5 Can the operation in Windows be continued successfully after changing a drive letter or mount point?
   A If change of a drive letter is unintended, the original status can be restored by using Disk Management. A
     volume list must be re-created by using the iSMvollist command to reflect the changed drive letter or mount
     point information.
Q2-6 Can I use the power saving function from the terminal service/remote desktop?
   A No. If the power saving function is used from the terminal service/remote desk top, the connection to the
     terminal service/remote desktop may get disconnected or volume operation may fail.
Q2-7 What are supported OSes?
   A The Power Control is listed in NEC Storage ControlCommand. As for the support matrix of NEC Storage
     ControlCommand, see the NEC Storage ControlCommand Installation Guide.
Q2-8 How much disk capacity and memory amount do I need to use PowerControl?
   A See FAQ for ControlCommand to find the information about the capacity and memory amount required to
     use PowerControl. For the latest information, see Installation Guide of ControlCommand.
Q3-1 Does changing an LD name impact the operation of the power saving function?
   A When an LD name is changed, a volume list must be re-created by using the iSMvollist command.
Q3-2 The disk array configuration has been changed. Is there any way to make the OS recognize the change
     without restarting the system?
   A
        ■ For Windows
               Run the iSMrc_scan command provided by ControlCommand or open Computer Management
               and click Disk Management. If this solution does not work, restart the system.
        ■ For Linux
               The only way to make the OS recognize the change is to restart the system.
Q3-4 What should I note in starting or restarting a system that uses the power saving function?
   A If use of volumes is stopped, they are not recognized after system is started.
     Restart the system after the use of volumes is started. Or scan OS disks to make the system recognize
     volumes.
Q3-5 Is unmount of volumes necessary?
   A To stop use of volumes (the iSMec_stop operation), unmount the volumes.
Q3-6 How does PowerControl collect logs?
   A How PowerControl has operated is recorded as logs in command trace, operation trace, event logs
     (Windows), and syslog (UNIX). Command trace and operation trace are log information that PowerControl
     saves internally in the installation folder. By default the maximum size is 5 MB (1 MB fo command trace and
     4MB for operation trace).
     Use the option setting file on Windows or environment variables on Linux to configure whether or not to
     report logs and the maximum log size.
     For details, see Chapter 8 of the manual, NEC Storage Software ControlCommand Command Reference.
Q4-1 What should I do when volumes on a disk array are not recognized?
   A If the OS does not recognize disks after the system is restarted, the AccessControl settings may be
     configured incorrectly. Volumes to which access is restricted by AccessControl are not recognized by the
     OS. Check the AccessControl settings by using NEC Storage Manager. If the application server in question
     is not connected, configure the settings correctly.
Q4-2 What should I do when some volumes are not shown after running the iSMvollist command?
   A A volume list created by the iSMvollist command may be not in place or the volumes are not recognized.
     Check the volumes are successfully recognized by the OS and re-create a volume list.
Q4-3 Running the iSMec_start command by specifying a volume failed while starting pool operation. What should I
     do?
   A Specify a pool number and run the iSMec_start command again.
     For details, see Chapter 6 of the manual, NEC Storage Software ControlCommand Command Reference.
     If the failure to run the command persists even after specifying a pool number, contact maintenance staff.
Q4-4 What should I do when created volumes cannot be accessed from a server?
   A Follow the instruction below to check use of the created volumes has not been stopped.
        1. Select the target logical disk on the window showing a list of iSM client’s logical disks and open the
           detail information window.
        2. Check “NotAvailable” is shown for access mode on the detail information window of the logical disk.

     Follow the instruction below to cancel the stop of usage.
        1. Check power saving mode of the pool to which the logical disk belongs. If OFF is shown, switch the
           mode to ON.
        2. Run the iSMec_start command for the logical disk from the server (such as backup server) to which
           CV is connected to restore use of volumes.
                 iSMec_start -vol (logical disk name) -volflg ld
        3. If the detail information window of the logical disk is open, close it and then reopen it to check
           “ReadWrite” is shown for access mode.
        4. If power saving mode is set to ON in step 1, switch back to OFF.

     For details of operation, see NEC Storage Software Power Saving User’s Manual.
Storage Control

ReplicationControl SQL Option
1. Introduction
     Q1-1 What is ReplicationControl SQL Option?
     Q1-2 What is the benefit of using ReplicationControl SQL Option?
     Q1-3 What is snapshot backup?
     Q1-4 What is a metafile?


2. Installation
     Q2-1 What are supported OSes?
     Q2-2 What are requisite software programs for ReplicationControl SQL Option?
     Q2-3 Do requisite software programs need to be installed before installing ReplicationControl SQL Option?
     Q2-4 What user right do I need to use ReplicationControl SQL Option?
     Q2-5 Does ReplicationControl SQL Option support Microsoft SQL Server 2005? Are there any notes on using
          Microsoft SQL Server 2005?
     Q2-6 Does ReplicationControl SQL Option support Microsoft SQL Server 2008?
          Are there any notes on using Microsoft SQL Server 2008?
     Q2-7 I want to install either of the following fixes to protect SQL Server 2000 against the SQL Slamme worm. Do
          they impact operation and behavior of ReplicationControl SQL Option?
          -SQL Server 2000 SP2 and MS02-061
          -SQL Server 2000 SP3
     Q2-8 How much disk capacity and memory amount do I need to use ReplicationControl SQL Option?
     Q2-9 Can I perform a shapshot backup for a database where the data partitioning or database mirroring function of
          Microsoft SQL Server 2005 has been applied?
    Q2-10 Are there any notes on using ReplicationControl SQL Option on a machine where a software program for
          security (*) is installed?
          (*) Software prgoram to tackle issues such as information leakage, unauthorized access, antivirus, and so
          on.


3. Operation
     Q3-1 How is the business opeartion affected by snapshot backups?
     Q3-2 How does increase in the number of databases for snapshot backup affect?
     Q3-3 Where are metafiles saved?
     Q3-4 Is it possible to perform snapshot restoration if there is not metafile?
     Q3-5 Is it possible to perform snapshot restoration by using a metafile and a database file that were created on
          different occasions?
     Q3-6 When a copy database created on RV or SV through snapshot backup was used as a standby database on
          another Microsoft SQL Server, is it possible to perform restoration by using the database?
     Q3-7 Is it possible to obtain multiple backups from one master volume through a single snapshot backup?
     Q3-8 How is login information saved in ReplicationControl SQL Option?


4. Troubleshooting
     Q4-1 What should I do when the messate “Failed in getting system path of environment variable” is shown during
          uninstallation of ReplicationControl SQL Option?
     Q4-2 What should I do if I cannot use metafiles on a shared disk?
     Q4-3 What should I do when a snapshot backup fails?
     Q4-4 What should I do when a snapshot backup failed with Microsoft SQL Server error logs showing the error code
     844/845?
Q4-5 What should I do when accessing SQL Server fails after a database is detached?
Q4-6 The message “iSM13676: Failed to sql server connection.” noting accessing Microsoft SQL Server is not
     possible is reported when a snapshot backup is performed in a Microsoft Cluster Server (MSCS) or Microsoft
     Failover Cluster (MSFC) environment.
     The Microsoft SQL Server service is started and the user ID and password are correctly specified. What
     should I do?
Q4-7 Although there is no network problem, the message “iSM13689 Failed to snapshot execution. code=11”
     noting general network error is shown during a snapshot backup in Microsoft SQL Server 2005 or Microsoft
     SQL Server 2008. What should I do?



Q1-1 What is ReplicationControl SQL Option?
   A SQL Option is an optional product of ReplicationControl and SnapControl and works together with Microsoft
     SQL Server to achieve uninterrupted backup of SQL Server databases.
Q1-2 What is the benefit of using ReplicationControl SQL Option?
   A When SQL Option is installed, you can backup databases without stopping application servers or Microsoft
     SQL Server.
Q1-3 What is snapshot backup?
   A Snapshot backup is a backup performed without stopping any business applications that use Microsoft SQL
     Server. When the data replication function is used, MV and RV are separated from each other and a copy of
     databases is created in RV. When the snapshot function is used, a snapshot of BV is created in SV and a
     copy of databases is created in SV. In either case, performing a snapshot backup creates a metafile.
Q1-4 What is a metafile?
   A A metafile is a file to store file configuration of databases created on Microsoft SQL Server and state
     information about transaction logs. It is created when a snapshot backup is performed and information
     contained in it is used when a snapshot restoration is performed.
Q2-1 What are supported OSes?
   A As for the support matrix of NEC Storage ReplicationControl SQL Option Installation Guide, See the NEC
     Storage ReplicationControl SQL Option Installation Guide.
Q2-2 What are requisite software programs for ReplicationControl SQL Option
   A The following software programs are requisite.
     For Ver4.1/Ver5.3 or later (*1 and *2)
       - NEC StorageManager
       - NEC Storage AccessControl
       - NEC Storage ControlCommand (*3)
         The following functions are included.
                  NEC Storage ReplicationControl
                  NEC Storage SnapControl
       - NEC Storage DynamicDataReplication or NEC Storage RemoteDataReplication
         To use the data replication function:
       - NEC Storage DynamicSnapVolume
         To use the snapshot function:
       - Microsoft SQL Server
         One of the following is required.
                  Microsoft SQL Server 2000 Enterprise Edition (SP3 *4)
                  Microsoft SQL Server 2000 Enterprise Edition (SP4 *4)
                  Microsoft SQL Server 2000 Standard Edition (SP3 *4)
                  Microsoft SQL Server 2000 Standard Edition (SP4 *4)
                  Microsoft SQL Server 2005 Enterprise Edition
                  Microsoft SQL Server 2005 Enterprise Edition (SP1)
                  Microsoft SQL Server 2005 Enterprise Edition (SP2)
                  Microsoft SQL Server 2005 Enterprise Edition (SP3)
                  Microsoft SQL Server 2005 Standard Edition
                  Microsoft SQL Server 2005 Standard Edition (SP1)
                  Microsoft SQL Server 2005 Standard Edition (SP2)
                  Microsoft SQL Server 2005 Standard Edition (SP3)
                  Microsoft SQL Server 2008 Enterprise
                  Microsoft SQL Server 2008 Enterprise (SP1)
                  Microsoft SQL Server 2008 Standard
                  Microsoft SQL Server 2008 Standard (SP1)


              (*1) When you use Microsoft SQL Server 2005, use SQL Option Ver4.1 or later and NEC Storage
                   ControlCommandSet Ver4.2 or later.
              (*2) When you use Microsoft SQL Server 2008, use ReplicationControl SQL Option Ver5.3 or later
                   and NEC Storage ControlCommand Ver5.3 or later.
              (*3) For the NEC Storage D series, use Ver5.1 or later for NEC Storage ControlCommand.
                   To use ReplicationControl SQL Option Ver5.3, use Ver5.3 or later for NEC Storage
                   ControlCommand.
              (*4) To use the following OSes, SP4 must be applied to Microsoft SQL Server 2000.
                  Microsoft Windows Server 2003, Standard x64 Edition
                  Microsoft Windows Server 2003 R2, Standard x64 Edition
                  Microsoft Windows Server 2003, Enterprise x64 Edition
                  Microsoft Windows Server 2003 R2, Enterprise x64 Edition
Q2-3 Do requisite software programs need to be installed before installing ReplicationControl SQL Option?
   A ReplicationControl (*) or SnapControl (*) must be installed before ReplicationControl SQL Option is installed.
     Microsoft SQL Server can be installed after ReplicationControl SQL Option is installed.
     *ReplicationControl and SnapControl are contained in NEC Storage ControlCommandSet Ver 4.1 or later, or
     in NEC Storage ControlCommand Ver5.1 or later.
Q2-4 What user right do I need to use ReplicationControl SQL Option?
   A You must be a user who belongs to the Administrators group to use ReplicationControl SQL Option.
     An account to access Microsoft SQL Server must have the right to access all databases.
Q2-5 Does ReplicationControl SQL Option support Microsoft SQL Server 2005?
     Are there any notes on using Microsoft SQL Server 2005?
   A Microsoft SQL Server 2005 is supported.
     When you use Microsoft SQL Server 2005, ReplicationControl SQL Option must be Ver4.1 or later, NEC
     Storage ControlCommandSet must be Ver4.2 or later (*), and for the NEC Storage D series, NEC Storage
     ControlCommand must be Ver5.1 or later.
     The ReplicationControl SQL Option command (iSMsql_snapshotbkup, iSMsql_snapshotrst) may run slower
     than the time when Microsoft SQL Server 2000 is used.

     (*)   For the NEC Storage D series, use Ver5.1 or later for NEC Storage ControlCommand.
Q2-6 Does ReplicationControl SQL Option support Microsoft SQL Server 2008?
     Are there any notes on using Microsoft SQL Server 2008?
   A Microsoft SQL Server 2008 is supported.
     When you use Microsoft SQL Server 2008, ReplicationControl SQL Option must be Ver5.3 or later and NEC
     Storage ControlCommand must be Ver5.3 or later.

     When you use Microsoft SQL Server 2008, note the following:
         - When ReplicationControl SQL Option is Ver5.3, databases where the following functions supported in
           Microsoft SQL Server 2008 are applied are not supported.
              - Transparent encryption (database encryption)
              - FILESTREAM data (support for unstructured data)
              - Change tracking (saving history of changes in database)
          When a snapshot backup or snapshot restoration is attempted for these databases, a
          ReplicationControl SQL Option command can fail or even if it is successfully executed, data
          inconsistency can occur. Do not use ReplicationControl SQL Option commands.
          To use databases where any of the functions mentioned above is applied, use ReplicationControl SQL
          Option Ver6.1 or later.
         - The backup compress function of Microsoft SQL Server 2008 is not supported.
          The snapshot backup of ReplicationControl SQL Option is a function to create a backup of the master
          volume (MV or BV) as a copy of logical disks. It does not compress and back up files on disks.
          When you perform a backup, you can compress the backup by specifying the "COMPRESSION"
          option. You can apply transaction logs while backup compression remains transparent.
          Example of the command for backup compression of transaction logs.
                BACKUP LOG DataBaseName TO DISK = 'D:\Backup\log' WITH NO_TRUNCATE,
                COMPRESSION
          Example of the command for applying transaction logs that have been backed up and compressed
                RESTORE LOG DataBaseName FROM DISK = 'D:\Backup\log' WITH NORECOVERY
Q2-7 I want to install either of the following fixes to protect SQL Server 2000 against the SQL Slammer worm. Do
     they impact the operation and behavior of ReplicationControl SQL Option?
     -SQL Server 2000 SP2 and MS02-061
     -SQL Server 2000 SP3
   A The fixes mentioned above do not impact the operation or behavior of ReplicationControl SQL Option. The
     following versions are supported by ReplicationControl SQL Option.
     NEC StorageManager/ReplicationControl SQL Server 2000 Option Ver1.3
     NEC Storage ReplicationControl SQL Option Ver2.1 or later
     NEC Storage ReplicationControl SQL Option Ver4.1 or later
Q2-8 How much disk capacity and memory amount do I need to use ReplicationControl SQL Option?
   A See the following description to find disk capacity and memory amount needed to use ReplicationControl
     SQL Option. For the latest information, see ReplicationControl SQL Option Installation Guide.

     Ver5.3 or later
          Disk capacity:3 MB or more
          Memory amount:
               Windows 2000 Server                                            Memory amount required for OS +
                                                                              8 MB or more
               Windows 2000 Advanced Server                                   Memory amount required for OS +
                                                                              8 MB or more
               Windows Server 2003, Standard Edition                          Memory amount required for OS +
                                                                              10 MB or more
               Windows Server 2003 R2, Standard Edition                       Memory amount required for OS +
                                                                              10 MB or more
               Windows Server 2003, Enterprise Edition                        Memory amount required for OS +
                                                                              10 MB or more
               Windows Server 2003 R2, Enterprise Edition                    Memory amount required for OS +
                                                                             10 MB or more
               Windows Server 2003, Standard x64 Edition                     Memory amount required for OS +
                                                                             12 MB or more
               Windows Server 2003 R2, Standard x64 Edition                  Memory amount required for OS +
                                                                             12 MB or more
               Windows Server 2003, Enterprise x64 Edition                   Memory amount required for OS +
                                                                             12 MB or more
               Windows Server 2003 R2, Enterprise x64 Edition                Memory amount required for OS +
                                                                             12 MB or more
               Windows Server 2003, Enterprise Edition for Itanium-based     Memory amount required for OS +
               Systems                                                       30 MB or more
               Windows Server 2008 Standard (IA32)                           Memory amount required for OS +
                                                                             10 MB or more
               Windows Server 2008 Enterprise (IA32)                         Memory amount required for OS +
                                                                             10 MB or more
               Windows Server 2008 Standard (EM64T)                          Memory amount required for OS +
                                                                             12 MB or more
               Windows Server 2008 Enterprise (EM64T)                        Memory amount required for OS +
                                                                             12 MB or more
               Windows Server 2008 for Itanium-based Systems                 Memory amount required for OS +
                                                                             30 MB or more
     Ver4.1 or later
          Disk capacity:3MB or more
          Memory amount:
               Windows 2000 Server                                           Memory amount required for OS +
                                                                             8 MB or more
               Windows 2000 Advanced Server                                  Memory amount required for OS +
                                                                             8 MB or more
               Windows Server 2003, Standard Edition                         Memory amount required for OS +
                                                                             8 MB or more
               Windows Server 2003 R2, Standard Edition                      Memory amount required for OS +
                                                                             8 MB or more
               Windows Server 2003, Enterprise Edition                       Memory amount required for OS +
                                                                             8 MB or more
               Windows Server 2003 R2, Enterprise Edition                    Memory amount required for OS +
                                                                             8 MB or more
               Windows Server 2003, Standard x64 Edition                     Memory amount required for OS +
                                                                             10 MB or more
               Windows Server 2003 R2, Standard x64 Edition                  Memory amount required for OS +
                                                                             10 MB or more
               Windows Server 2003, Enterprise x64 Edition                   Memory amount required for OS +
                                                                             10 MB or more
               Windows Server 2003 R2, Enterprise x64 Edition                Memory amount required for OS +
                                                                             10 MB or more
               Windows Server 2003, Enterprise Edition for Itanium-based     Memory amount required for OS +
               Systems                                                       16 MB or more
Q2-9 Can I perform a snapshot backup for a database where the data partitioning or database mirroring function of
      Microsoft SQL Server 2005 has been applied?
    A You can perform a snapshot backup for a database where the data partitioning function has been applied.
      However, you cannot back up partitions individually. Specify pairs to include all data partitions (data files)
      constituting the database, and then perform a snapshot backup.

      You can backup a database where the database mirroring function has been applied from the principal
      database. Note that in an instance where a standby database of the mirror is located, you cannot perform a
      snapshot backup for other principal databases or databases where database mirroring has not been applied.
      When you create multiple databases, they should be configured without putting the mirror database in an
      instance where the principal database or database where database mirroring has not been applied.
      If you want to perform snapshot restoration of a database where the database mirroring function has been
      applied, cancel the mirroring settings of the database to be restored before performing the snapshot
      restoration.
Q2-10 Are there any notes on using ReplicationControl SQL Option on a machine where a software program for
      security (*) is installed?
      (*) Software program to tackle issues such as information leakage, unauthorized access, viruses, and so on.
    A In addition to the ReplicationControl SQL Option installation folder (by default, <system drive>:\Program
      Files\NEC\iSMsql
      (for 64-bit version, <system drive>:\Program Files (x86)\NEC\iSMsql)), ReplicationControl SQL Option
      creates folders and files in the following folders to save configuration files and log files.
         -    Folder specified by the -metafolder option of the iSMsqlhe_snapshotbkup command
         -    File specified by the –metafile option of the iSMsql_snapshotbkup command
         -    File specified by the -refile option of the iSMsql_snapshotrst command
         -    <system drive>:\Documents and Settings\<login user name>\Application Data
                   For Windows Server 2008:
                   <system drive>:\user\<log in user name> \AppData\Roaming


       If creation of any of the folder and files is restricted by the software program for security, ReplicationControl
       SQL Option does not work properly. Configure the settings as necessary so that the restriction does not take
       place.
 Q3-1 How is the business operation affected by snapshot backups?
    A While a database is frozen, updating the database is paused. When the database is unfrozen, the update is
      resumed.
      The period during which a database is frozen is short in the period for executing a command, and is
      dependent on the number of databases and the size of logical disks. If there are a few databases, the frozen
      period is short (few seconds).
      For information on the time a database is frozen, see the following messages in Microsoft SQL Server error
      logs.

       For SQL Server 2000:
             Database (database name): IO is frozen for snapshot
             Database (database name): IO is thawed
       For SQL Server 2005 or SQL Server 2008
             I/O is frozen on database (database name).
             I/O was resumed on database (database name).

      Referring to a database is not stopped by database freeze. However, while a command is running, response
      slows down by several tens of %.
 Q3-2 How does increase in the number of databases for snapshot backup affect?
   A Increase in the number of databases for snapshot backup results in longer time for command execution and
     database freeze.
Q3-3 Where are metafiles saved?
   A Metafiles can be created on any of a shared disk, MV, BV, and a local disk. It is recommended to save them
     in a shared disk to allow easy operation.
Q3-4 Is it possible to perform snapshot restoration if there is no metafile?
   A To perform snapshot restoration, the metafile created at a snapshot backup is necessary. When you perform
     a snapshot backup, make sure to save its metafile. If the metafile is overwritten in the next backup by
     mistake, the snapshot backup becomes data that cannot be restored.
Q3-5 Is it possible to perform snapshot restoration by using a metafile and a database file that were created on
     different occasions?
   A The metafile created by the snapshot backup command and the database file on RV must match. If you
     attempt to perform the restoration by using a metafile created on a different timing, conflict between the
     transaction logs sequence and the database file occurs, and the message noting roll forward to the latest
     state cannot be done is reported in Microsoft SQL Server when the transaction logs are applied.
Q3-6 When a copy database created on RV or SV through snapshot backup was used as a standby database on
     another Microsoft SQL Server, is it possible to perform restoration by using the database?
   A When copy database files created on RV or SV through snapshot backup are used (including read-only) in
     another Microsoft SQL Server, you cannot use the database for snapshot restoration. When you attempt to
     apply transaction logs in this circumstance, the message noting roll forward to the latest state cannot be done
     is reported in Microsoft SQL Server because conflict between the transaction logs sequence and the
     database file occurs.
Q3-7 Is it possible to obtain multiple backups form one master volume through a single snapshot backup?
   A Although you can have a configuration with one master volume (MV or BV) having multiple backup volumes
     (RV or SV), only one backup can be obtained from one master volume (MV or BV) in a single snapshot
     backup. You cannot obtain backups for multiple backup volumes (RV or SV) from one master volume (MV or
     BV) in a single backup.
Q3-8 How is log information saved in ReplicationControl SQL Option?
   A ReplicationControl SQL Option reports logs about how it has been operated in the command trace, the
     operation trace, and Windows event logs. The command trace and the operation trace are log information
     saved internally in ReplicationControl SQL Option, and by default they can be as large as 5 MB (1 MB for
     command trace and 4 MB for operation trace) in the ControlCommand (or ControlCommandSet) installation
     folder.
     The command trace and the operation trace share functions such as ReplicationControl and SnapControl.
     You can configure whether or not to report logs and the maximum log size by using the operation option
     setting file.
     For details, see Chapter 8 of NEC Storage Manager D Series manual, NEC Storage Software
     ControlCommand Command Reference or Chapter 7 of NEC Storage S Series manual, NEC Storage
     Software ControlCommandSet Command Reference.
Q4-1 What should I do when the message “Failed in getting system path of environment variable.” is shown during
     uninstallation of ReplicationControl SQL Option?
   A This problem is experienced when a value greater than 1024 bytes has been set in the system variable
     Path. You can finish the uninstallation by clicking OK. However, the path information of ReplicationControl
     SQL Option remains in the system variable Path. Follow the steps below to remove the information.


      (1)   Right-click My Computer and select Properties. On the Advanced tab, click Environment
            Variables.
      (2)   Under System variables, click Path and then click Edit.
      (3)   Remove the following, which is set to the variable, and then close the dialog box.
             %iSMsql%\sbin;
Q4-2 What should I do if I cannot use metafiles on a shared disk?
   A When metafiles are in a shared disk of other computers, the shared disk must be available through the name
     and password of the user who is running ReplicationControl SQL Option.
     If you are using a scheduling software program such as ESMPRO/JMSS, check the name and password of
     the user who runs ReplicationControl SQL Option.

     Even if the user name and password of the user who is running ReplicationControl SQL Option are available
     on the shared disk, sometimes the error message “13696” is reported and metafiles on the shared disk are
     unavailable.
     If this problem is experienced, the location of metafiles on the shared disk should be specified according to
     the format that conforms to UNC (universal naming convention) (\\Servername\Sharename\Path\File).
Q4-3 What should I do when a snapshot backup fails?
   A Check the reported error messages to determine what to be done.
     When the “13689” and “13690” error messages are reported with no other messages:
           An error has occurred in Microsoft SQL Server. See Microsoft SQL Server error logs to perform
           appropriate troubleshooting.
     When the error message “13682” is reported:
           ReplicationControl SQL Option and another backup may have contended for the VDI resources. If a
           Microsoft SQL Server database is backed up concurrently, you must find a way not to run backups at
           the same time. If backups are not performed concurrently, see Microsoft SQL Server error logs to
           perform appropriate troubleshooting.
Q4-4 What should I do when a snapshot backup failed with Microsoft SQL Server error logs showing the error code
     844/845?
   A When a snapshot backup is performed in a circumstance where SQL Server is highly loaded or a number of
     I/O requests are concentrated, the error code 844/845 may be found in Microsoft SQL Server error logs,
     which results in failure of the snapshot backup. Snapshot backups should be performed when operational
     load is low.
Q4-5 What should I do when accessing SQL Server fails after a database is detached?
   A When a SQL Server user detaches his/her own default database, the user cannot access SQL Server. Use
     the database by attaching it as another user such as Administrator, or configure the default database of the
     user who runs SQL Server Option (user accessing SQL Server) as database that is not detached such as
     master database in advance.
Q4-6 The message “iSM13676: Failed to sql server connection.” noting accessing Microsoft SQL Server is not
     possible is reported when a snapshot backup is performed in a Microsoft Cluster Server (MSCS) or Microsoft
     Failover Cluster (MSFC) environment.
     The Microsoft SQL Server service is started and the user ID and password are correctly specified. What
     should I do?
   A In the MSCS or MSFC environment, a virtual computer name must be specified as the name of the computer
     to be connected. Specify the virtual computer name of MSCS or MSFC for the server option to run
     ReplicationControl SQL Option.
Q4-7 Although there is no network problem, the message “iSM13689 Failed to snapshot execution. code=11”
     noting general network error is shown during a snapshot backup in Microsoft SQL Server 2005 or Microsoft
     SQL Server 2008. What should I do?
   A If this error occurs while there is no network problem, Microsoft SQL Server worker thread starvation may be
     experienced.
     Change the maximum number of worker threads to tackle this problem.
     (Ex) The following is an example of how to check how worker threads are used by using the SQLCMD utility.
          You can also use Query Editor in SQL Server Management Studio for checking.
            1. Access SQL Server by using dedicated administrator connection (DAC) from a command prompt
               immediately after “general network error” is reported in ReplicationControl SQL Option.
                   >sqlcmd -E -SADMIN:(SQLServer name)
      2. Run the following query to check how worker threads are used.
             >select sum(current_workers_count) as N'Current',
                 sum(active_workers_count) as N'Active'
              from sys.dm_os_schedulers
              where status='VISIBLE ONLINE'


              Current                   Active
                          -----------            -----------
                                256                    253
        When the query result shows almost the same values for the Active column and the Current
        column (difference in the values is within a single digit), it is quite likely worker thread starvation is
        experienced.
To change the maximum number of worker threads, see Books On Line of Microsoft SQL Server and/or 5.2
“Setting of Microsoft AQL Server” of NEC Storage D series manual or NEC Storage S series manual, NEC
Storage ReplicationControl SQL Option User’s Manual (IS006).
Storage Control

ReplicationControl FileSystem Option
1. Introduction
   Q1 What functions does Replication Control FileSystem Option provide? How do I use them?
   Q2 How much disk capacity and memory amount do I need to use ReplicationControl FileSystem Option (Linux)?


4. Operation (for all OSes)
   Q3 The default value of the –t option of the iSMrc_fsseparate command and iSMsc_fscreate command is 60
      seconds. Does it mean running the command always takes 60 seconds?
   Q4 Is the smallest value that can be set to the –t option of iSMrc_fsseparate command and iSMsc_fscreate
      command 1 second?
   Q5 Is replication by the iSMrc_fsreplicate command delta synchronization or full synchronization?
   Q6 Is completion of iSMrc_fsseparate/iSMrc_fsreplicate command execution listened? Or does it end without
      listning to completion?
   Q7 Are there any notes on using ReplicationControl File System Option together with JobCenter?


6. Operation (for Linux)
   Q8 How is log information saved in ReplicationControl FileSystem Option (Linux)?


7. Troubleshooting (for OSes)
   Q9 The following error message is reported when speration is performed by using iSMrc_fsseparate on an
      application server and then an attempt to mount the file system on the backup server is made.
        vxfs mount: /dev/vgsap01/lvol1 is corrupted. needs checking
      Why does mounting fail?


   Q1 What functions does ReplicationControl FileSystem Option provide? How do I use them?
     A ReplicationControl FileSystem Option is an optional product that performs data replication or snapshot after
       freezing file systems and synchronizing all the file system data when disk volumes are used as file systems.
       When file systems are used, you can create a copy volume and back it up without stopping business
       applications or unmounting file systems by using ReplicationControl FileSystem Option.
   Q2 How much disk capacity and memory amount do I need to use ReplicationControl FileSystem Option (Linux)?
     A See the following description. For the latest information, see FileSystem Option (Linux) Installation Guide.
       Linux
         Disk capacity:1 MB or more
         Memory amount:Memory amount required for the OS + 7 MB or more
   Q3 The default value of the -t option of the iSMrc_fsseparate command and iSMsc_fscreate command is 60
      seconds. Does it mean running the command always takes 60 seconds?
     A The value specified by the –t option is the maximum timeout duration at file system freeze.
       When separation or snapshot creation is complete, unfreeze takes place to complete the process.
       Consequently the option does not mean execution takes 60 seconds.
   Q4 Is the smallest value that can be set to the –t option of the iSMrc_fsseparate command and iSMsc_fscreate
      command 1 second?
     A The smallest value you can set is 1 second.
       Note if a value set to the option is too small, unfreeze takes place before MV/RV separation or BV/SV snapshot
       creation is complete, which does not allow the ReplicationControl FileSystem Option function to be executed
       and causes an error. Note that the value specified for the –t option is the maximum of timeout at freeze.
Q5 Is replication by the iSMrc_fsreplicate command delta synchronization or full synchronization?
 A By default, delta synchronization is performed. To perform full synchronization, specify -o cprange=full.
Q6 Is completion of the iSMrc_fsseparate/iSMrc_fsreplicate command execution listened? Or does it end without
   listening to completion?
 A By default completion is listened. If you do not want to listen to completion, specify the -o nowait option.
Q7 Are there any notes on using ReplicationControl FileSystem Option together with JobCenter?

 A If a disk to be used by ReplicationControl FileSystem Option is specified for the working directory of JobCenter,
   a timeout error occurs in unfreeze of FileSystem Option. For the JobCenter working directory, set a disk that is
   not used by ReplicationControl FileSystem Option.


     Example:Error message during separation
       # /opt/NECiSMfso/bin/iSMrc_fsseparate -m dg -t 60 -o wait tsdg2
          *** Separate Start
          *** Freeze Start
          Freezing /data/ts
          *** Freeze Success
          Separating MV: 2000003013840AB90006 RV: 2000003013840AB90014
          *** Unfreeze Start
          Error: ioctl VX_THAW /data/ts: Connection timed out
          Warning: Unfreeze Timeout !
          Warning: Separate is not correctly done.
          Warning: You must merge again and please retry
          Warning: to separate setting larger value of timeout.
       iSMrc_fsseparate: Unfreeze Failed
Q8 How is log information saved in ReplicationControl FileSystem Option (Linux)?
 A
     ReplicationControl FileSystem Option reports logs about how it has been operated in the command trace and
     syslog. The command trace is log information that ReplicationControl FileSystem Option saves internally.


     <Log information>
       - .hafss.log file in /tmp
          Capacity: Maximum 0.3 KB
               Note: Only the latest information remains. If a failure occurs, the hafss.log file must be collected
                     before you run a ReplicationControl FileSystem Option command the next time.
                     If the hafss.log file does not exist, collection is not necessary.


     - All the files in /opt/iSMfso/etc/trace (Linux)
           Capacity: Maximum 2.4 MB
                      -Data replication function                       :Up to six 0.2-MB files
                      -Snapshot function                               :Up to six 0.2-MB files
               Note: If there is no directory or files when a failure occurs, collection is not necessary.
     When a failure occurs, see Related Software for NEC Storage Information to be collected when a failure occurs
     (PDF).
Q9 The following error message is reported when separation is performed by using iSMrc_fsseparate on an
   application server and then an attempt to mount RV on the backup server is made.
     vxfs mount: /dev/vgsap01/lvol1 is corrupted. needs checking
   Why does mounting fail?
A When you run iSMrc_fsseparate, a volume can be separated with no file system inconsistency while the file
  system is mounted.
  However, data replication is performed while a flag indicating the source disk for copy is mounted on the
  management area of the file system is shown. Because of this, you must run the fsck command to remove the
  mount flag so that the flag will not be copied when an attempt to mount the disk on the destination is made.
Storage Control
VSS Provider
1. Introduction
      Q1-1 What type of software program is VSS Provider?


2. Installation
     Q2-1 Is it necessary to install ControlCommand on the backup server as well in a multi-servers configuration
           where the backup server is in another system?
     Q2-2 Is it necessary to install VSS Provider on the backup server as well in a multi-servers configuration where
          the backup server is in another system?
     Q2-3 Are there any environment variables that I need to configure?
     Q2-4 How can I obtain VSS Provider?
     Q2-5 Is file system backup supported?
     Q2-6 Can I use VSS Provider in a system where Storage PathManager is installed?
     Q2-7 How does VSS Provider work?


3. Operation
      Q3-1 The OS fails to recognize devices (Plug and Play).
      Q3-2 The following error message is reported in event logs when NetBackup is used for backups.
            Type: ERROR
            Event source: iSMvss
            Event ID: 13882
            Message: iSM13882: LD attribute is neither MV nor BV.(ldattr=4)
      Q3-3 A VWW warning message is reported in event logs (application).


       Q1-1 What type of software program is VSS Provider?
           A VSS Provider works together with the data replication function (DynamicDataReplication or
             RemoteDataReplication) or the snapshot function (DynamicSnapVolume) of the NEC Storage series to
             create a volume copy (shadow copy) that supports the Volume Shadow Copy Service (VSS) function of
             Windows Server.
             Exchange Server is the database product that supports VSS Provider.
       Q2-1 Is it necessary to install ControlCommand on the backup server as well in a multi-servers configuration
            where the backup server is in another system?
           A Yes, you need to install ControlCommand on the backup server as well. The backup server does not
             perform synchronization but imports LV or RV by the ControlCommand function.
       Q2-2 Is it necessary to install VSS Provider on the backup server as well in a multi-servers configuration
            where the backup server is in another system?
           A Yes, you need to install VSS Provider on the backup server as well.
       Q2-3 Are there any environment variables that I need to configure?
           A No, three is no environment variables that need to be configured to use VSS Provider.
       Q2-4 How can I obtain VSS Provider?
           A VSS Provider is shipped together with Replication Navigator Suite.
       Q2-5 Is file system backup supported?
           A Backup of the NTFS filesystems is supported.
       Q2-6 Can I use VSS Provider in a system where Storage PathManager is installed?
   A Yes.

       You need to configure the backup server as follows.
           - Set the event mode to Type1.
            PROMPT > spscmd -seteventmode 1
           - Set the failback mode to active.
            PROMPT > spscmd -setfbmode a
Q2-7 How does VSS Provider work?
   A It works as the "NEC VSS Provider" service.
     The "NEC VSS Provider" service is automatically started when it is used for the first time after the
     system is started. It does not stop automatically.
     The "Volume Shadow Copy" service must be stopped to stop the "NEC VSS Provider" manually.
     The "Volume Shadow Copy" service is automatically started when the VSS function is used and
     automatically stopped three minutes after the usage is finished.
Q3-1 The OS fails to recognize devices (Plug and Play).
   A
       If backups using the VSS function are repeated, unnecessary device entry information is accumulated,
       which can result in failure of the OS to recognize device (Plug and Play).
       Enter the following command from a command prompt to remove unnecessary device entry
       information from the registry.

            iSMvss_clear delete
Q3-2 The following error message is reported in event logs when NetBackup is used for backups.
     Type: ERROR
     Event source: iSMvss
     Event ID: 13882
     Message: iSM13882: LD attribute is neither MV nor BV.(ldattr=4)

   A This error does not affect the backup behavior.
     If you do not want this message to be reported, disable the Windows Open File Backup settings of
     NetBackup.
Q3-3 A VSS warning message is reported in event logs (application).
   A If there is any unformatted partition (including volumes that you do not intend to back up) in a server
     where a VSS backup is performed, the following warning (example) may be reported in event logs
     (application).
     Unformatted partitions include ExpressCluster partitions.


       Event type             : WARNING
       Event source           : VSS
       Event ID               : 12290

       Explanation            : Volume shadow copy service warning:

                                GetVolumeInformationW(\\?\Volume{941f0b7b-120c-11d9-b701-505054503030}\,
                                NULL,0,NULL,NULL,[0x00000000],,260)==0x00000057。hr=0x00000000


       This warning does not affect the backup behavior.
Storage Control

RemoteDataReplication/DisasterRecovery
1. Introduction
     Q1 What is NEC Storage RemoteDataReplication/DisasterRecovery?


2. Installation
     Q2 How should I determine whether to install NEC Storage RemoteDataReplication only or NEC Storage
        RemoteDataReplication and NEC Storage RemoteDataReplication/DisasterRecovery in a disaster recovery
        system using a remote data replication software product?
     Q3 What are supported NEC Storage products/series?
     Q4 Are there any software programs that are required to install NEC Storage
        RemoteDataReplication/DisasterRecovery?
     Q5 Are there any notes on installing NEC Storage RemoteDataReplication/DisasterRecovery?
     Q6 What is an atomic group (AT group)?
     Q7 How many atomic groups (AT groups) can I create on one disk array device?
     Q8 How many pairs can I register with one atomic group (AT group)?
     Q9 How should I arrange NEC StorageManager?
    Q10 Copies are constantly made by NEC Storage RemoteDataReplication/DisasterRecovery. Do I still need local
        backups?


     Q1 What is NEC Storage RemoteDataReplication/DisasterRecovery?
       A It is a product that provides basic functions to enhance NEC Storage RemoteDataReplication, a software
         program for remote data replication, and to achieve disaster recovery.
     Q2 How should I determine whether to install NEC Storage RemoteDataReplication only or NEC Storage
        RemoteDataReplication and NEC Storage RemoteDataReplication/DisasterRecovery in a disaster recovery
        system using a remote data replication software product?
       A When you build a disaster recovery system by using a remote data replication software product, in principle,
         install NEC Storage RemoteDataReplication and
         NEC Storage RemoteDataReplication/DisasterRecovery.
         When backups are performed by using a remote data replication product, the system may need only NEC
         Storage RemoteDataReplication in some cases.
     Q3 What are NEC Storage products/series?
       A The following NEC Storage products/series are supported.
             NEC Storage S4900, S4300, S3300, S2900, and S2800
             NEC Storage D8 series
     Q4 Are there any software programs that are required to install NEC Storage
        RemoteDataReplication/DisasterRecovery?
       A The following software programs are required to install NEC Storage
         RemoteDataReplication/DisasterRecovery.
           - NEC Storage NEC Storage BaseProduct (Ver3.1 or later)
           - NEC Storage AccessControl
           - NEC Storage RemoteDataReplication Ver2 or later
           - NEC Storage RemoteDataReplication/DisasterRecovery
           - NEC Storage ReplicationControl Ver3.1 or later
             or NEC Storage ControlCommandSet Ver4.1 or later (*)
             or NEC ControlCommand Ver5.1 or later (*)
           - NEC Storage ReplicationControl/DisasterRecovery Ver3.1 or later
        or NEC Storage ControlCommandSet Ver4.1 or later (*)
        or NEC Storage ControlCommand Ver5.1 or later (*)


        *If you use NEC Storage ControlCommandSet or NEC Storage ControlCommand, the following functions
        are included.
           - NEC Storage ReplicationControl
           - NEC Storage ReplicationControl/DisasterRecovery


    The following software program is required to perform local backups by using data replication.
       - NEC Storage DynamicDataReplication Ver2 or later


    In addition to having these programs in place, you need to have PP support service agreement(s) concluded.
 Q5 Are there any notes on installing NEC Storage RemoteDataReplication/DisasterRecovery?
  A When you install NEC Storage RemoteDataReplication/DisasterRecovery, you may need upgrade the disk
    array device’s FW. When you create atomic groups (AT group) you cannot create them in parallel at a time on
    the same disk array device. Make sure not to create them in parallel and operate from a single point.
 Q6 What is an atomic group (AT group)?
  A With functions supporting disaster recovery, pairs of volumes for which consistency must be ensured can be
    grouped. These groups are called atomic groups.
 Q7 How may atomic groups (AT groups) can I create on one disk array device?
  A If you are using NEC Storage S4300, S3300, S2900, or S2800, up to 64 atomic groups can be created in a disk
    array device.
    If you are using the NEC Storage D8 series or S4900, up to 256 groups can be created in a disk array device.
 Q8 How many pairs can I register with one atomic group (AT group)?
  A If you are using NEC Storage S4300, S3300, S2900, or S2800, up to 128 pairs can be registered with one
    atomic group (AT group).
    If you are using NEC Storage S4900, up to 8192 pairs can be registered with one atomic group (AT group).
    If you are using the NEC Storage D8 series, up to 1024 × number of nodes (1 through 4) pairs can be
    registered with one atomic group (AT group).
 Q9 How should I arrange NEC Storage Manager?
  A Install iSM server in each site to monitor NEC Storage in the site.
Q10 Copies are constantly made by NEC Storage RemoteDataReplication/DisasterRecovery. Do I still need local
    backups?
  A Yes. For recovery from disk failures or multiple failures, you need local backups as well.
Storage Control

AccessControl
1. Introduction
      Q1-1 What functions does AccessControl provide?
      Q1-2 What is an LD set?
      Q1-3 What is WWN (World Wide Name) used in the AccessControl settings?
      Q1-4 What should I do if I want to restrict accessible areas on a host basis in a SAN environment?



2. Operation
      Q2-1 What is a LUN (Logical Unit Number)?
      Q2-2 What is the function to “allocate logical disks”?
      Q2-3 Can I specify a logical disk LUN, the sequence by which application servers recognize logical disks, when
           allocating logical disks to an LD set?
      Q2-4 What is the link path mode function?
      Q2-5 What should I note in registering logical disks and path information with an LD set?
      Q2-6 Can I modify or delete an LD set any time?
      Q2-7 How can I find a WWPN of an application server?
      Q2-8 When does the information about a new or modified LD set take effect?
      Q2-9 How do I identify the application server of the linked path information (WWPN)?
     Q2-10 What should I do for the settings when a Host Bus Adaptor (HBA, sometimes referred to as FC controller) is
           replaced?
     Q2-11 What is the maximum number of LUNs that can be allocated to an LD set?
     Q2-12 I cannot assign any link volume (LV) to LUN0 of an LD set. What should I do?
     Q2-13 Is it possible to use Port mode and WWN mode of AccessControl together?
     Q2-14 When I create an LD set for VMware ESX Server, what platform should I set to the LD set?
     Q2-15 What characters can I use for named of initiators that can be used by NEC StorageManager?
     Q2-16 What should I do when an error message is shown for discovery performed in the OS to detect a disk
           array?
     Q2-17 What iSCSI security settings can I use in NEC Storage D series?



3. Troubleshooting
      Q3-1 What should I do if I cannot add any path on the Link Path window?
      Q3-2 On the Link Path window, a message telling the path has already been set to another LD set is shown and
           I cannot add the path. What should I do?
      Q3-3 When I clicked Get Disk Array and clicked Cancel, the dislpay and the settings on the window stopped
           working properly. What should I do?
      Q3-4 What should I do when a logical disk I added to an LD set is not recognized by the application server?
      Q3-5 What should I when linking path information fails though the license allows for more paths to be configured?



      Q1-1 What functions does AccessControl provide?
         A AccessControl is a function to set the permission to access from application servers to logical disks on a
           WWN (World Wide Name) basis or disk array’s port basis.
            ■ When AccessControl (WWN) is applied, the GUI of iSM client can be used to configure the
              AccessControl settings for WWN mode.
      [Disk arrays to which AccessControl (WWN) can be applied]
       - NEC Storage S1100, S2100, S3100 and S4100
       - NEC Storage S1200 and S2200
      ■ When AccessControl is applied, the GUI of iSM client can be used to configure the AccessControl
        settings for WWN mode or Port mode.
      [Disk arrays to which AccessControl can be applied]
       - NEC Storage D series
       - NEC Storage S1300, S1400, S1500, S2300, S2400, S2500, S2800, S2900, S3300, S4300, and S4900
Q1-2 What is an LD set?
   A An LD set is a virtual concept representing a group of logical disks created by NEC Storage Manager.
      - When AccessControl (WWN) is applied, an LD set becomes accessible from an application server by
        linking the path information (WWN (World Wide Name) of the application server) to the LD set.
      - When AccessControl is applied, an LD set becomes accessible from an application server by linking the
        path information (WWN (World Wide Name) of the application server or a disk array port whose mode is
        Port) to the LD set.
Q1-3 What is WWN (World Wide Name) used in the AccssControl settings?
   A WWN (World Wide Name) consists of WWNN (World Wide Node Name) and WWPN (World Wide Port
     Name) It is also allocated to HBA (sometimes called Host Bus Adaptor or FC controller) as unique
     identification code information. AccessControl uses WWPN of HBA WWN on application servers.
Q1-4 What should I do if I want to restrict accessible areas on a host basis in a SAN environment?
   A If you are using any of the following devices in a SAN environment where no switch or hub is used, you can
     do it by using the AccessControl function that is equipped with the device.
      - NEC Storage S1100, S2100, S3100, and S4100
      - NEC Storage S1200 and S2200
     If you are using any of the following devices, you need to purchase the AccessControl license whether or
     not switches or hubs are used.
      - NEC Storage D series
      - NEC Storage S1300, S1400, S1500, S2300, S2400, S2500, S2800, S2900, S3300, S4300, and S4900
Q2-1 What is a LUN (Logical Unit Number)?
   A This is a value to determine the sequence by which application servers recognize logical disks. Application
     servers recognize logical disks according to the sequence of logical disk LUNs (Logical Unit Number)
     specified on an LD set basis. A LUN can be configured by allocating logical disks.
Q2-2 What is the function to “allocate logical disks”?
   A This is a function to specify the sequence of presenting logical disks to application servers. A logical disk
     LUN (Logical Unit Number) can be configured on an LD set basis.
Q2-3 Can I specify a logical disk LUN, the sequence by which application servers recognize logical disks, when
     allocating logical disks to an LD set?
   A You can specify a LUN (Logical Unit Number) by using the New Setting (for Ver1.3, Batch Setting is shown)
     function. New Setting (for Ver1.3, Batch Setting is shown) cancels all the settings of logical disks allocated
     to an LD set, specifies a LUN newly and allocates logical disks to it.
Q2-4 What is the link path mode function?
   A This is a function to link a WWPN (World Wide Port Name), the path information of an application server
     and a port whose mode is Port to an LD set. This function allows the application server to access the logical
     disks allocated to the LD set. (You can use the GUI on NEC Storage AccessControl to link ports whose
     mode is Port to LD sets.)
Q2-5 What should I note in registering logical disks and path information with an LD set?
   A Because a piece of path information (WWPN or port number) can be registered with only one LD set, logical
     disks configured to your target path information should not belong to multiple LD sets. Make sure to group
      them in one LD set.
 Q2-6 Can I modify or delete an LD set any time?
    A When you modify or delete an LD set, access from the application servers to which the LD set is associated
      to logical disks may fail. You must be very careful when you operate an LD set while accessing logical disks
      from an application server. When you modify or delete an LD set, it is recommended to stop access from
      application servers to logical disks. When iSM server is connected to a disk array by FC, at least one logical
      disk must be recognized by the machine on which iSM server runs. If no logical disk is recognized, you
      cannot monitor the disk array from iSM server.
 Q2-7 How can I find a WWPN of an application server?
    A - If a Host Bus Adaptor (HBA, sometimes referred to as FC controller) has not been installed on the
        application server, you can find the WWPN of the HBA on its card sticker. Take note of the WWPN.
       - On Windows, you can use the driver utility or the BIOS screen to check the WWPNs.
       - On HP-UX, you can use the fcmsutil command.
       - On Solaris, some HBAs report their WWPN values to syslog when the OS is started.
       - Or, you can use the SG specification where WWPNs values are noted.
       - If you are using the NEC Storage D series, you can check WWPNs on the properties window of the
         connected host on the Performance Monitoring screen by using the host information. The registered
         WWPNs can be displayed by selecting your target host in the path info select field on the Link Path
         window.
 Q2-8 When does the information about a new or modified LD set take effect?
    A Unless an error message is shown, a request from iSM client is immediately set to the disk array and takes
      effect.
      However, logical disks must be recognized by the OS on the application server so that the application
      server can recognize the information.
 Q2-9 How do I identify the application server of the linked path information (WWPN)?
    A On each application server, check its WWPNs. Or you can see the information described in the SG
      specification.
      If you are using the NEC Storage D series, you can check the WWPN on the properties window of the
      connected host on the Performance Monitoring screen by using the host information.
Q2-10 What should I do for the settings when a Host Bus Adaptor (HBA, sometimes referred to as FC controller) is
      replaced?
    A Replace the WWPN (World Wide Port Name) of the old HBA by the WWPN of the new HBA on the Link
      Path window.
Q2-11 What is the maximum number of LUNs that can be allocated to an LD set?
    A The maximum number depends on whether AccessControl is set to on or off, the access mode and the disk
      array.


       The following table shows the maximum number of LDs as well as LUNs that can be set to one LD set.
       Specification of LDs that can be set to LD set


                                Access                                                   Max       Configurab
       Purchased license                                  Disk array
                                mode                                                     LDs       le LUN
                                                                                                   From
                                                          1000/2000 series                     512 0000h to
       AccessControl (WWN)
                                                                                                   01ffh
                                WWN
                                                                                                   From
                                                          3000/4000 series                     512 0000h to
                                                                                                   01ffh
                                                                                               From
                                                         1000/2000 series                 1024 0000h to
                               Port                                                            03ffh
                               (operated by
                               maintenance staff)                                              From
                                                         3000/4000 series                 4096 0000h to
                                                                                               0fffh
                                                                                           512 From
                                                         D1/D3/D4/D8 series                    0000h to
                                                                                               01ffh
                                                                                           512 From
                                                         100/1000/2000/2800 series             0000h to
                               WWN and Port
                                                                                               01ffh
                                                                                           512 From
                                                         3000/4000 series                      0000h to
                                                                                               01ffh
                                                                                          1024 From
                                                         D1/D3/D4 series                       0000h to
                                                                                               03ffh
       AccessControl
                                                                                          4096 From
                                                         D8 series                             0000h to
                                                                                               0fffh
                               Port of ACOS-4
                                                                                          1024 From
                               resource
                                                         2000 series                           0000h to
                               (operated by
                                                                                               03ffh
                               maintenance staff )
                                                                                          4096 From
                                                         S4100/S4300                           0000h to
                                                                                               0fffh
                                                                                          8192 From
                                                         S4900                                 0000h to
                                                                                               1fffh
       On a disk array where AccessControl is set to off, created LDs are recognized by all the hosts
       connected to the disk array.
       However, the number of LDs that can actually be used by an application server depends on the OS of
       the application server.
Q2-12 I cannot assign any link volume (LV) to LUN0 of an LD set. What should I do?
    A Link volumes are protected to prevent them from being assigned to LUN0.
      This is because if an LV is assigned to LUN0 and access mode of the LV is set to Not Ready or Not
      Available, logical disks of LUN1 and the following LUNs as well as logical disks of LUN0 are not recognized
      in some application servers. Assign logical disks other than LV to LUN0.
Q2-13 Is it possible to use Port mode and WWN mode of AccessControl together?
    A I you are using any of the following disk array devices, in principle, do not use Port mode and WWN mode
      together. Given system configuration design issues and complexity of operation, it is strongly recommended
      to use either Port mode or WWN mode on one disk array device.
       - NEC Storage D series
       - NEC Storage S1300, S1400, S1500, S2300, S2400, S2500, S2800, and S2900
Q2-14 When I create an LD set for VMware ESX Server, what platform should I set to the LD set?
    A Set “LX.”
Q2-15 What characters can I use for names of initiators that can be used by NEC Storage Manager?
    A     -     Characters you can use: alphanumeric characters, ‘:’ (colon), ‘-’ (hyphen), and ‘.’ (period).
          -     Maximum number of characters: up to 223 characters
        The number of characters you can use for initiator names that can be used in Windows software initiator
        are as follows (as of January 2009):
          -     Windows Server 2003 (Microsoft iSCSI Software Initiator 2.08): up to 221 characters
          -     Windows Server 2008 (contains Microsoft Software Initiator): up to 221 characters
Q2-16 What should I do when an error message is shown for discovery performed in the OS to detect a disk array?
    A The following message may be shown but it does not affect the operation of your system. Continue the
      settings.
          -     Windows Server 2003 (Microsoft iSCSI Software Initiator 2.08): Authorization Failure.
          -     Windows Server 2008 (contains Microsoft Software Initiator): Connection Failed
Q2-17 What iSCSI security settings can I use in the NEC Storage D series?
    A CHAP authentication and Mutual CHAP authentication.
 Q3-1 What should I do when I cannot add any path on the Link Path window?
    A It can be either the number of licenses has reached the maximum or the the number of paths has reached
      the limit of the disk array. Remove unnecessary LD sets or unnecessary paths and links, and then try
      adding the path.
 Q3-2 On the Link Path window, a message telling the path has been already set to another LD set is shown and I
      cannot add the path. What should I do?
    A You cannot register a WWPN or port number that is already linked to an LD set with another LD set. Check
      the path you are intending to register is correct.
 Q3-3 [When I clicked Get Disk Array and then clicked Cancel, the display and settings on the window stopped
      working propertly. What should I do?
    A Click Get Disk Array Info again so that the information in the disk array and the client information will be
      identical.
 Q3-4 What should I do when a logical disk I added to an LD set is not recognized by the application server?
    A On NEC Storage:
        - Check LUNs are configured in sequence from 0.
        On the application server:
        - If the application server is not recognizing the LD set, check the manual of the application server (OS).
          Depending on the type of the server, you may need to restart it.
 Q3-5 What should I do when linking path information fails though the license allows for more paths to be
      configured?
    A The number of paths you can set to an LD set depends on the NEC Storage Manager version.
        Maximum number of paths you can set
              Ver1.5 or later      :64
              Ver1.3 and 1.4       :4
              If you want to link paths more than the maximum, create multiple LD sets where the same logical disk
              assignment is configured and link paths to them.
Storage Control

PerformanceOptimizer
1. Introduction
     Q1-1 Are there any software programs that are required to use performance optimization?
     Q1-2 What is the logging interval of the statistical information in general?


2. Operation
     Q2-1 When do I use the FTP function?
     Q2-2 What is a work disk for optimization? How do I configure it?
     Q2-3 Do I need to stop business operations when I replace logical disks? Do I need to configure the settings of the
          application server after replacing logical disks?
     Q2-4 The disk array shown on iSM client is not shown on PerformanceOptimizer screen. What should I do?
     Q2-5 How are performance optimization logs saved by PerformanceOptimizer?


3. Troubleshooting
     Q3-1 A failure interrupted replace of a logical disk. Is it OK to just remove the cause of the failure and replace the
          logical disk again?
     Q3-2 If fault(over capacity) or fault(over quota) is experienced while replace of a virtual capacity logical disk is
          ongoing, does the replace complete?


     Q1-1 Are there any software programs that are required to use performance optimization?
         A The following software programs are required to use NEC Storage PerformanceOptimizer.
               - NEC StorageManager
               - NEC Storage PerformanceMonitor
               - NEC Storage ReallocationControl
               - NEC Storage AccessControl
                    NEC Storage PerformanceOptimizer for ACOS-4, which is for ACOS-4, contains NEC Storage
                    PerformanceMonitor, NEC Storage ReallocationControl and NEC Storage AccessControl.
     Q1-2 What is the logging interval of the statistical information in general?
         A The logging interval of the statistical information can be specified through the environment definition file in
           UNIX and the environment settings of iSM server in Windows.
           Ver2.1 or later
                  The value you can define is 1 through 60 minutes. The default is 5 minutes.
                  On UNIX, use “monitor_interval” in the performance section in the environment definition file for
                  specifying the logging interval. “optlog_interval” in the optimizer section is combined with the logging
                  interval of the performance monitoring in Ver2.1, and is no longer used.
           Ver1.5 or earlier
                  The value you can specify is either 30 or 60 minutes. The default is 30 minutes.
                  On UNIX, use “optlog_interval” in the optimizer section in the environment definition file.
     Q2-1 When do I use the FTP function?
         A The FTP function is used from Ver2.1 on to obtain the information required to display the Busy Ratio Graph
           or Graph Indicating Replacement Effect.
     Q2-2 What is a work disk for optimization? How do I configure it?
         A PerformanceOptimizer solves bottleneck problems by moving a logical disk on a highly loaded RANK/pool to
           a RANK/pool that is not highly loaded. A work disk for optimization is the destination where the logical disk is
           moved. It is concealed from all application servers and it is assured that no access to it is made. A work disk
     for optimization is configured by using the LD Administration function of the NEC Storage Manager (NEC
     Storage ReallocationControl). For details see the manual NEC Storage Software Reallocation Control User’s
     Manual.
Q2-3 Do I need to stop business operations when I replace logical disks? Do I need to reconfigure the settings of
     the application server after replacing logical disks?
   A You do not need to stop business operations to replace logical disks. No reconfiguration of the settings on
     the application server and on disk arrays is needed.
Q2-4 The disk array shown on iSM client is not shown on PerformanceOptimizer Screen. What should I do?
   A Only disks that can be optimized are shown on iSM client. Check the product state (license) of the disk array
     properties on iSM client.
Q2-5 How are performance optimization logs saved by PerformanceOptimizer?
   A Performance optimization logs are saved in the installation folder. The size can be estimated by the number
     of disk array components (RANK/pools, logical disks) and logging interval. Files are saved on a disk array
     basis at a maximum of two months.
     For details, see Appendix B of the manual NEC Storage Software Performance Optimization User’s Manual.
Q3-1 A failure interrupted replace of a logical disk. Is it OK to just remove the cause of the failure and replace the
     logical disk again?
   A When replace of a logical disk is interrupted, the state before replace is maintained for the source logical disk
     as well as for the work disk for optimization. Consequently, you do not need to modify the configuration of the
     application server and the disk array. Remove the cause and simply try the relocation again.
Q3-2 If fault(over capacity) or fault(over quota) is experienced while replace of a virtual capacity logical disk is
     ongoing, does the replace complete?
   A If the fault(over capacity) or the fault(over quota) is experienced in the source logical disk, the replace
     completes. However you need to check data integrity after removing the failure cause.
     Depending on the replace option, the fault(over capacity) or the fault(over quota) status may disappear, in
     which case you need to check the status by operation logs.
     If the fault(over capacity) or the fault(over quota) is experienced in the destination logical disk, the replace
     fails and the status before the replace is restored.

     You can manually resolve the failure status for the logical disk where the over capacity/over quota failure
     occurred after the relocation is complete. For details, see the manual NEC Storage Software Thin
     Provisioning User’s Manual.
Storage Control

Volume Protect
1. Introduction
   Q1-1 What is the data retention function?
   Q1-2 Can I use the data retention function and the data replication function together?


2. Installation
   Q2-1 How much does the data retention function cost?
   Q2-2 Which sotrage devices support the data retention function?
   Q2-3 Are there any other software programs that are required to install NEC Storage VolumeProtect?
   Q2-4 What is a control volume?


3. Operation
   Q3-1 Are there any notes on using the data retention function?
   Q3-2 How is the volume reinitialization function at the time of volume protection release different from the volume
        initialization function provided by the OS?
   Q3-3 Is there any way to check how a volume is protected?
   Q3-4 Is there any way to check the progress of volum reinitialization?
   Q3-5 Are there any notes on using the data retention function from iSM client?
   Q3-6 Is there any way to check the result of initialization of OS type/logical disk name?
   Q3-7 Both Release protection and initialize at the same time and Initialization of OS Type/Logical Disk Name
        check boxes were disabledwhen I tried to release protection. Why?
   Q3-8 The Initialization of OS Type/Logical Disk Name check box was disabled when I tried to release protection.
        Why?


4. Troubleshooting
   Q4-1 What should I do when initialization of a volume by using the volume reinitialization function fails because of a
        hardware error?
   Q4-2 What should I do if I cannot find my target disk array on the iSM client data retention management screen?
   Q4-3 The error “10000” is reported when I try to open the iSM data retention management screen.
   Q4-4 The error “10001” is reported when I try to open the iSM data retention management screen.


   Q1-1 What is the data retention function?
       A The data retention function is a function to prevent unauthorized data rewrite or data corruption due to a
         mistake in operation by configuring data access rights or data retention period on a volume basis. This is a
         software program that allows for saving data long period of time in a format that cannot be tampered.
         Driven by laws and regulations mandating storing business documents and emails in a format that cannot be
         tampered, importance of data protection is increasing. The data retention function provides basic functions to
         achieve management and operations according to data types; for example appropriate data storage and
         access management.
   Q1-2 Can I use the data retention function and the data replication function together?
       A Yes. You need NEC Storage Manager Ver4.3 or later and storage control software version 0430 or later to use
         the data retention function and data replication function together.
   Q2-1 How much does the data retention function cost?
       A The price of the data retention function depends on the disk array or the capacity of the disks. For details see
         Price List for your NEC Storage device.
   Q2-2 Which storage devices support the data retention function?
   A The data retention function is supported in the following NEC Storage devices.
         - NEC Storage D series
         - NEC Storage S4900
         - NEC Storage S2900
         - NEC Storage S2500
         - NEC Storage S1500
Q2-3 Are there any other software programs that are required to install NEC Storage VolumeProtect?
   A The following software programs are required to use NEC Storage VolumeProtect.
         - NEC Storage BaseProduct (contains NEC Storage Manager. With NEC Storage Manager Ver4.3 or later,
           you can use the data retention function on iSM client as well.)
         - NEC Storage AccessControl
         - NEC Storage ControlCommand


      It is recommended to purchase the following product to be prepared for I/O path failures of application servers.
         - NEC Storage PathManager
Q2-4 What is a control volume?
   A When you work on protected volumes from an application server by using NEC Storage ProtectControl, a
     volume used for constant connection to the server is necessary to control the disk array from the server. This
     volume is called control volume. One control volume must be configured for each application server on the disk
     array when the system is installed.
     Control volumes should be used exclusively and no data should be stored in them.
Q3-1 Are there any notes on using the data retention function?
   A Note the following:
         - Purchase of products
           Purchase products required to use the data retention function. You can check what products have been
           purchased on the main window of iSM client (disk array subsystem detail information screen).
         - AccessControl configuration
           Configure AccessControl appropriately to show only target volumes to the application server.
         - Supported file systems
           The data retention function supports the following file system in the Linux environment.
             - ext2
Q3-2 How is the volume reinitialization function at the time of volume protection release different from the volume
     initialization function provided by the OS?
   A The volume reinitialization function used at the time of volume protection release is a function provided by the
     NEC Storage disk array and totally clears the volume area to completely remove data stored there. The erased
     data cannot be restored. This allows you to achieve confidentiality.
Q3-3 Is there any way to check how a volume is protected?
   A You can use the following ways to check how a volume is protected:
        ■ Using GUI
           Check the properties of your target logical disk from the data retention management window (Logical
           Disk list) of iSM client.
        ■ Using a CLI
           Check how your target volume is protected by using the iSMrc_sense command provided by NEC
           Storage ProtectControl.
Q3-4 Is there any way to check the progress of volume reinitialization?
   A You can use the following ways to check the progress of volume reinitialization:
        ■ Using GUI
           Check the properties of your target logical disk from the main window (Logical Disk list) of iSM client.
        ■ Using a CLI
           Check how your target volume is protected by using the iSMrc_sense command provided by NEC
           Storage ProtectControl.
Q3-5 Are there any notes on using the data retention function from iSM client?
   A When you use the data retention function, make sure that your target volume has been unmounted from the
     host. Note if the access right is set to ReadOnly, you cannot mount your target volume on a Windows host.
Q3-6 Is there any way to check the result of initialization of OS type/logical disk name?
   A Use the Logical Disk list on the data retention management screen.
Q3-7 Both Release protection and initialize at the same time and Initialization of OS Type/Logical Disk Name
     check boxes were disabled when I tried to release protection. Why?
   A When your target volume is a replication volume (MV or RV), you cannot initialize it. Check the RPL Type
     column of the Logical Disk list on the data retention management screen
Q3-8 The Initialization of OS Type/Logical Disk Name check box was disabled when I tried to release protection.
     Why?
   A When your target volume is locked and its configuration cannot be modified, you cannot use the Initialization of
     OS Type/Logical Disk Name function. Check the Configuration Change column of the Logical Disk list on the
     main window. If you want to initialize OS type/logical disk name, unlock the volume before initialization.
Q4-1 What should I do when initialization of a volume by using the volume reinitialization function fails because of a
     hardware error?
   A If it has been confirmed that initialization of the volume by using a command or iSM GUI has failed, contact
     maintenance staff.
Q4-2 What should I do if I cannot find my target disk array on the iSM client data retention management screen?
   A Have you purchased the product having the data retention function (NEC Storage VolumeProtect)? On the
     main window of iSM client, display the details information window of the corresponding disk array to check what
     products have been purchased.
Q4-3 The error “10000” is reported when I try to open the iSM data retention management screen.
   A To use the data retention function, you need to purchase NEC Storage VolumeProtect and unlock its license.
     On the main window of iSM client, display the product status of the disk array details information window to
     check the license has been unlocked. If not, use iSM’s license unlocking function to unlock the license.
Q4-4 The error “10001” is reported when I try to open the iSM data retention management screen.
   A To use the data retention function on iSM client, iSM server and iSM client must be Ver4.3 or later. Check the
     version from the main window of iSM client.
Storage Control

StoragePowerConserver
1. Introduction
   Q1-1 What is the power saving function?
   Q1-2 How is the power saving function effective?
   Q1-3 Can I use the power saving function and the data replication function together?


2. Installation
   Q2-2 On which storage devices can I use the power saving function?
   Q2-3 Are there any other software programs that are required to install NEC Storage StoragePowerConserver?
   Q2-4 What is a control volume?


3. Operation
   Q3-1 Are there any notes on using the powe saving function?
   Q3-2 What is the eco mode?
   Q3-3 Is there any way to check how a volume is used?
   Q3-4 Is there any way to check the rotation state of a pool?
   Q3-5 Is there any way to check the rotation state of a physical disk?
   Q3-6 The rotation of the pool is stopped but some physical disks constituting the pool are still rotating. Is this OK?
   Q3-7 How long does it take to start rotating a pool?


4. Troubleshooting
   Q4-1 The pool is in reduced (degenerated) mode due to a physical disk failure. Is it possible to stop rotation of the
        pool under this circumstance?
   Q4-2 The pool that had not been rotating started to rotate though I did not do anything. Why?


   Q1-1 What is the power saving function?
       A The power saving function is a software program that manages usage on a volume basis and controls start and
         stop of physical disks that constitute a pool to which the volume belongs according to how the volume is used.
         While reduction of burden on the environment is increasingly important, the power saving function allows for
         starting and stopping physical disks that constitute a pool to which the volume belongs according to how the
         volume is used and provides fundamental functions that supports power saving operation associated with
         business practice.
   Q1-2 How is the power saving function effective?
       A The power saving function allows for reduction of power consumption by stopping physical disks that are not
         used all the time. Effectiveness depends on the number of physical disks to be stopped and how long they are
         stopped in a day.
         The more disks you stop and the longer they are stopped, the more effective the power saving you can expect.
   Q1-3 Can I use the power saving function and the data replication function together?
       A You can save power of volumes for the data replication function (MV or RV). However, you cannot save power
         of volumes for the snapshot function (BV, SV or LV).
   Q2-2 On which storage devices can I use the power saving function?
       A You can use the power saving function on the following NEC Storage devices:
             - NEC Storage D1-10
             - NEC Storage D3-10
             - NEC Storage D4-30
          - NEC Storage D8-10
Q2-3 Are there any other software programs that are required to install NEC Storage StoragePowerConserver?
   A The following software programs are required to use NEC Storage StoragePowerConserver.
          - NEC Storage BaseProduct
      -    NEC Storage AccessControl
      -    NEC Storage ControlCommand
      It is recommended to purchase the following product to be prepared for I/O path failures of application
      servers.
      -    NEC Storage PathManager
Q2-4 What is a control volume?
   A When you work on volumes from a server by using PowerControl, a volume used for constant connection to
     the server is necessary to control the disk array from the server. This volume is called control volume. One
     control volume must be configured for each application server on the disk array when the system is installed.
     Control volumes should be used exclusively and no data should be stored in them.
Q3-1 Are there any notes on using the power saving function?
   A Note the following:
          - Purchase of products
                Purchase products required to use the power saving function. You can check what products have
                been purchased on the disk array subsystem detail information screen of NEC Storage Manager.
          - AccessControl configuration
                Configure AccessControl appropriately to show only target volumes to the server.
          - Configuration of volumes
                The power saving function starts and stops physical disks on a pool basis. The following volumes
                should not be created on pools where you use the power saving function.
                  a) Volume that run constantly and used for business operation
                  b) Volumes used for the snapshot function
                  c) Control volume
                  d) System volume
          - Unbinding a volume
                Volumes not in use state shoud not be unbound. Before unbinding a volume, it should be restored to
                the in use state.
Q3-2 What is the eco mode?
   A The eco mode is an attribute configured on a pool basis. It specifies whether or not the power saving function
     should be used on volumes of the given pool. Configure the eco mode from iSM client.
     For details, see Chapter 4 of NEC Storage Software Power Saving User’s Manual.
Q3-3 Is there any way to check how a volume is used?
   A Use the iSMec_sense command provided by PowerControl to check how your target volume is used.
Q3-4 Is there any way to check the rotation state of a pool?
   A You can check the rotation state of a pool by:
          ■ Using GUI
                Check the properties of your target pool on the pool list of NEC Storage Manager.
          ■ Using a CLI
                Check the rotation state of your target pool by using the iSMec_sense command provided by
                PowerControl.
Q3-5 Is there any way to check the rotation state of a physical disk?
   A You can check how the rotation state of a physical disk by:
        ■ Using GUI
                Check the properties of your target physical disk on the physical disk list of NEC Storage Manager.
        ■ Visually checking the device directly
                Check the LED of your target physical disk. If the physical disk is not rotating, the LED flashes in
                amber.
Q3-6 The rotation of the pool is stopped but some physical disks constituting the pool are still rotating. Is this OK?
   A It is OK. Physical disks where the configuration information about storage devices is stored must rotate all the
     time. Because of this, they do not stop even if the pool is stopped. Physical disks that do not stop rotating are:
         - D1-10        0000h ~ 0003h, 0080h ~ 0083h
         - D3-10        0000h ~ 0003h, 0080h ~ 0083h
         - D8-1010      0000h ~ 0003h, 0080h ~ 0083h
         - D8-1020      0000h ~ 0003h, 0080h ~ 0083h, 0200h ~ 0203h, 0280h ~ 0283h
Q3-7 How long does it take to start rotating a pool?
   A It depends on the how many physical disks that pool has and how the disk array is loaded. In general, normal
     state is restored within two minutes.
Q4-1 The pool is in reduced (degenerated) mode due to a physical disk failure. Is it possible to stop rotation of the
     pool under this circumstance?
   A When the pool is failing, it does not stop rotating even if use of all volumes that belong to the pool is stopped.
     The rotation of the pool will be stopped after recovery from the failure.
Q4-2 The pool that had not been rotating started to rotate though I did not do anything. Why?
   A Check to see if any of physical disks constituting the pool is not failing. If any of the physical disks constituting
     the pool is failing, the device cancels the state where rotation of the pool is stopped to allow maintenance and
     recovery. The pool restores the state where rotation is stopped after recovery from the failure.
Storage Control

VirtualStoragePartitioning
1. Introduction
   Q1-1 What is the partitioning function?
   Q1-2 On what storage devices can I use the partitioning function?


2. Installation
   Q2-1 How much does the partitioning function cost?
   Q2-2 Are there any requisite software programs to install VirtualStoragePartitioning?
   Q2-3 Are there any other software programs that are required to install VirtualStoragePartitioning?
   Q2-4 Do I need to stop business operation to install VirtualStoragePartitioning?
   Q2-5 What should I do if I cannot see the partition information from iSM client though I installed
        VirtualStoragePartitioning (unlocked the license)?


3. Operation
   Q3-1 What is a partition user?
   Q3-2 What resources can I allocate to partitions by using the partitioning function?
   Q3-3 Are there any functions that partition users cannot use?
   Q3-4 Why are there ports that do not apper on the list of ports to be allocated to partitions (available ports)?


4. Troubleshooting
   Q4-1 What should I do when “Attn. (Invalid Configuration of Partition)” is shown for the partition status?
   Q4-2 I cannot create a new partition by using the partitioning wizard. Why?
   Q4-3 I failed to allocate users to a partition. Why?
   Q4-4 I deleted a partition but the cache segment allocated to it remains. Why?


   Q1-1 What is the partitioning function?
       A The partitioning function virtually partitions resources on a disk array (disks, cache memories, and ports) and
         allocate them on an operation basis to achieve stability among operations. You can expect the following
         benefits by installing this function:
            ■ Minimize performance impact
               Virtual allocation of resources on an operation basis can minimize interference among operations. You
               can also add a new operation without impacting ongoing operations.
            ■ Prevent erroneous operation
               You can configure users on a resource allocation basis. Users can work only on allocated resources and
               do not work on other operational resource by mistake. This can prevent erroneous operation among
               operations.
   Q1-2 On what storage devices can I use the partitioning function?
       A The following NEC Storage supports the partitioning function.
             - NEC Storage D8 series
   Q2-1 How much does the partitioning function cost?
       A The price of the partitioning function varies according to the number of nodes constituting a disk array. For
         details, see Price List for your NEC Storage device.
   Q2-2 Are there any requisite software programs to install VirtualStoragePartitioning?
       A The following software programs are required to install VirtualStoragePartitioning.
             - NEC Storage Manager (shipped with NEC Storage BaseProduct)
         - NEC Storage AccessControl (shipped with NEC Storage BaseProduct)
Q2-3 Are there any other software programs that are required to install VirtualStoragePartitioning?
   A It is recommended to purchase the following product when you install VirtualStoragePartitioning
         - NEC Storage PerformanceMonitor
         - NEC Storage PerformanceNavigator
             You need this software program to monitor and analyze the performance of virtual storage (Virtual
             Storage Partition:VSPAR) resources.
Q2-4 Do I need to stop business operation to install VirtualStoragePartitioning?
   A You can install VirtualStoragePartitioning without stopping your business operation. However, when you
     change access mode of ports that are already used from WWN to Port, you need to stop your operations to
     reconfigure AccessControl including re-creation of LD sets.
Q2-5 What should I do if I cannot see the partition information from iSM client though I installed
     VirtualStoragePartitioning (unlocked the license)?
   A You can see the partition information by disconnecting iSM client after VirtualStoragePartitioning is installed
     (unlocking the license) and reconnecting it to iSM server.
Q3-1 What is a partition user?
   A A partition user is a user who has authority for a particular partition. The partition user can see and operate the
     partition he/she is authorized to do so. This authority prevents users from mistakenly operating resources that
     they are not authorized to do so.
Q3-2 What resources can I allocate to partitions by using the partitioning function?
   A The following resources can be allocated to partitions.
      V5.3 or later
         - Pools
         - Logical disks
         - Cache segments (except for default segment)
         - Port-mode ports
      V5.2
         - Pools
         - Cache segments (except for default segment)
         - Port-mode ports
Q3-3 Are there any functions that partition users cannot use?
   A Partition users cannot use functions that require management of entire disk array such as performance
     monitoring, performance optimization and data retention functions. These functions must be operated by
     storage users.
Q3-4 Why are there ports that do not appear on the list of ports to be allocated to partitions (available ports)?
   A Ports whose mode is WWN are shared resources of the entire disk array. Because of this they are excluded
     from ports that can be allocated to a partition and do not appear on the list of ports to be allocated to partitions
     (available ports). Ports in WWN mode are not allocated to any partitions and are shared in the disk array.
Q4-1 What should I do when “Attn. (Invalid Configuration of Partition)” is shown for the partition status?
   A This status is experienced when the partition information becomes invalid due to reasons such as a failure in
     the course of partition configuration. This status, which does not allow you to configure other partitions, start
     up the AccessControl/Configuration Setting function and so on, must be fixed immediately. There are two
     ways to fix the problem.
        1. Reconfigure the partition whose configuration is invalid by using the partitioning wizard. Select the
           partition and click modify. When the wizard is complete the invalid problem is fixed.
        2. Delete the partition whose configuration is invalid.
Q4-2 I cannot create a new partition by using the partitioning wizard. Why?
   A     - If there is any partition whose status is “Attn. (Invalid Configuration of Partition)” on the window showing
           the partition information list, you cannot create a new partition. Fix the partition configuration problem first.
         - If there are 127 partitions, you cannot create a new partition. Check how many partitions exist.
Q4-3 I failed to allocate users to a partition. Why?
   A If a user to be allocated has logged in from iSM client to NEC Storage Manager, you cannot allocate the user to
     a partition. Check the login status of the user.
Q4-4 I deleted a partition but the cache segment allocated to it remains. Why?
   A Even if a partition is deleted, the cache segment allocated to it is not deleted automatically. You can remove
     cache segments from the Cache Segment Setting window. However, you cannot remove the default segment
     (segment ID=xxh-00h:xxh is a node number).
Storage Control

ThinProvisioning
1. Introduction
    Q1-1 What is the thin provisioning function?
    Q1-2 On what storage devices can I use the thin provisioning function?
    Q1-3 Under what circumstance can the thin provisioning function used effectively?


2. Installation
    Q2-1 How much does the thin provisioning function cost?
    Q2-2 Are there any requisite software programs to install NEC Storage ThinProvisioning?
    Q2-3 Are there any other software programs that are required to install NEC Storage ThinProvisioning?
    Q2-4 Do I need to stop business operation to install NEC Storage ThinProvisioning?
    Q2-5 What is virtual capacity?
    Q2-6 What is a virtual capacity logical disk?


3. Operation
    Q3-1 Can I defrag a virtual capacity logical disk allocated to an application server?
    Q3-2 Do I need particular settings on a server to use virtual capacity logical disks?
    Q3-3 I cannot create a virtual capacity pool that is larger than the maximum physical capacity.
    Q3-4 What is the actual capacity threshold of a virtual capacity pool?
    Q3-5 What are LD capacity quota and LD capacity threshold of a virtual capacity logical disk?
    Q3-6 Is there any way to check the actual capacity of a virtual capacity pool?
    Q3-7 Is there any way to check the actual used capacity of a virtual capacity logical disk?
    Q3-8 Is there any impact on business operation when capacity is allocated to a virutal capacity logical disk?
    Q3-9 I cannot create a virtual capacity logical disk on a pool that has already been created. Why?
   Q3-10 When I create a virtual capacity logical disk on Linux, all capacity is allocated to it. Why?
   Q3-11 Why is the actual used capacity not reduced even though I deleted a file from the volume?
   Q3-12 Can I create a new logical disk on a virtual capacity pool where actual used capacity is 100%?
   Q3-13 Are there any notes on using the thin provisioning function?


4. Troubleshooting
    Q4-1 I cannot turn off the alarm though I restored data after LD capacity quota had been exceeded/short of capacity
         had been experienced.
    Q4-2 What would happen if LD capacity quota is exceeded/short of capacity is experienced?


    Q1-1 What is the thin provisioning function?
        A It is a function to virtualize volume capacity and allocate capacity according to the amount of data written to the
          volume. With this function you can:
             ■ Increase disk array capacity without stopping your business operation.
                  If the data amount increases and the disk array runs out of capacity, you can add disk drives to increase
                  the disk array capacity without stopping your business operation.
             ■ Reduce initial installation costs.
                  You can start using a disk array with fewer disk drives than the conventional way of provisioning a disk
                  array. Consequently, you can reduce initial installation costs.
             ■ Use capacity effectively.
           You can use disk space efficiently by allocating free space to volumes used for other operation.
        ■ Reduce power consumption.
           Having fewer disk drives on a disk array reduces power consumption and emission of carbon dioxide
           (CO2).
Q1-2 On what storage devices can I use the thin provisioning function?
   A The following NEC Storage device supports the thin provisioning function.
         - NEC Storage D8-30
Q1-3 Under what circumstance can the thin provisioning function used effectively?
   A You can make most of the thin provisioning function in a system where files are not (or less likely to be)
     deleted. For example, database usage.
Q2-1 How much does the thin provisioning function cost?
   A The price of the thin provisioning function varies according to the number of nodes constituting a disk array.
     For details, see Price List for your NEC Storage device.
Q2-2 Are there any requisite software programs to install NEC Storage ThinProvisioning?
   A The following software programs are required to install NEC Storage ThinProvisioning.
         - NEC StorageManager (shipped with NEC Storage BaseProdeuct)
         - NEC Storage AccessControl (shipped with NEC Storage BaseProdeuct)
Q2-3 Are there any other software programs that are required to install NEC Storage ThinProvisioning?
   A It is recommended to purchase the following products when you install NEC Storage ThinProvisioning.
         - NEC Storage PerformanceMonitor
           You need this software program to monitor and analyze the capacity and performance of virtual capacity
           resources.
         - NEC Storage PerformanceOptimizer
           You can use this software program to shift from actual capacity logical disk operation to virtual capacity
           logical disk operation or move logical disks between pools without stopping your business operation.
         - NEC Storage ReallocationControl
           This software program is requisite to use PerformanceOptimizer.
Q2-4 Do I need to stop business operation to install NEC Storage ThinProvisioning?
   A You can install NEC Storage ThinProvisioning without stopping your business operation. However, if you want
     to switch actual capacity disks used in your business operation without using NEC Storage Performance
     Optimizer’s function to move LDs to switch from the actual logical disks to virtual logical disks, you need to
     stop running business operation.
Q2-5 What is virtual capacity?
   A Virtual capacity is capacity where no actual capacity is allocated but recognized by servers. Actual capacity is
     allocated when data is written.
Q2-6 What is a virtual capacity logical disk?
   A A virtual capacity logical disk is a logical disk that virtual capacity constitutes. You can create a virtual capacity
     logical disk only on a virtual capacity pool.
Q3-1 Can I defrag a virtual capacity logical disk allocated to an application server?
   A When you run defrag, files are moved and actual capacity may be allocated to a space where no capacity has
     been allocated. This will reduce disk usage efficiency. Do not defrag virtual capacity logical disks.
Q3-2 Do I need particular settings on a server to use virtual capacity logical disks?
   A No. However, monitor capacity so that it will not run out.
Q3-3 I cannot create a virtual capacity pool that is larger than the maximum physical capacity.
   A Configure the environment settings of NEC Storage Manager to allow a virtual capacity pool to exceed the
     maximum physical capacity.
Q3-4 What is the actual capacity threshold of a virtual capacity pool?
    A An actual capacity threshold is a value set to prevent short of free space. This value is used to monitor the
      used capacity of a virtual capacity pool and to notify users when a certain level is crossed. You can set two
      levels of an actual capacity threshold for a pool; actual capacity threshold and actual capacity threshold (pre).
 Q3-5 What are LD capacity quota and LD capacity threshold of a virtual capacity logical disk?
    A An LD capacity quota is a value to set an upper limit of allocation to prevent allocating actual capacity to a
      virtual capacity logical disk more than you intended.
      An LD capacity threshold is a value set to prevent allocating actual capacity beyond the LD capacity quota that
      has been set. This threshold is used to alert users when capacity is allocated more than a certain level so that
      the LD capacity quota will not be crossed.
 Q3-6 Is there any way to check the actual capacity of a virtual capacity pool?
    A You can check the actual capacity of a virtual capacity pool on the iSM client window showing the list of pools
      or the properties of the pool.
 Q3-7 Is there any way to check the actual used capacity of a virtual capacity logical disk?
    A You can check the actual used capacity of a virtual capacity logical disk on the iSM client window showing the
      list of logical disks or the properties of the logical disk.
 Q3-8 Is there any impact on business operation when capacity is allocated to a virtual capacity logical disk?
    A Capacity is allocated to a virtual capacity logical disk in an instant and does not impact your business
      operation.
 Q3-9 I cannot create a virtual capacity logical disk on a pool that has already been created. Why?
    A Virtual capacity logical disks can be created only on a virtual capacity pool. Check the attribute of the pool that
      has already been created.
Q3-10 When I create a virtual capacity logical disk on Linux, entire capacity is allocated to it. Why?
    A When ext3 is used as a file system on Linux, metadata is written by the unit that is smaller than the capacity to
      be allocated. Because of this, capacity is allocated across the disk. Do not use ext3 on Linux.
Q3-11 Why is the actual used capacity not reduced even though I deleted a file from the volume?
    A When a file is deleted from a file system, the management data of the file system (data recording the file
      location) is deleted but actual data remains on a disk. Because of this the actual used capacity is not freed up.
Q3-12 Can I create a new logical disk on a virtual capacity pool where actual used capacity is 100%?
    A No, you cannot create a logical disk on a virtual capacity pool where actual used capacity is 100%. To create a
      logical disk, actual used capacity must be reduced to 99% or less by adding a physical disk to the pool to
      increase the actual capacity or by removing unnecessary logical disks.
Q3-13 Are there any notes on using the thin provisioning function?
    A When an attempt to write data larger than the actual capacity of the pool or the LD capacity quota of the logical
      disk is made, the attempt may fail and the file may beocome invalid or get corrupted. Configure the LD
      capacity quota adequately according to your system operation. The actual capacity threshold (pre) /actual
      capacity threshold of pools as well as the LD capacity threshold of logical disks must be configured
      appropriately so that crossing of the actual capacity of a pool or the LD capacity quota of a logical disk will not
      occur in capacity monitoring.
 Q4-1 I cannot turn off the alarm though I restored data after LD capacity quota had been exceeded/short of capacity
      had been experienced.
    A See Chapter 5 of NEC Storage Software Thin Provisioning User’s manual for the NEC Storage D series to
      turn off the alarm.
 Q4-2 What would happen if LD capacity quota is exceeded/short of capacity is experienced?
    A If LD capacity quota has been exceeded or an attempt to write data larger than the actual capacity is made,
      writing data fails and the data may get corrupted. However, the application error does not occur instantly due
      to cache control of the OS or file system, and it may look as if data is being written beyond the LD capacity
      quota on the OS. If no action is taken, writing data fails at delay writing to the logical disk or file closing. In any
      case, check data integrity. Take a recovery action such as restoring data from backup as necessary.
Storage Control

PathManager for Windows
1. Installation
     Q1-1 How can I check that PathManager has been properly installed and normally running?
     Q1-2 Which OSes are supported?
     Q1-3 How much disk capacity and memory amount are required for running PathManager ?
     Q1-4 How long does it take to install PathManager?
     Q1-5 When I executed spscmd after installing PathManager, an error occurred.
     Q1-6 Only one path is displayed and any others are not. What should I do?
     Q1-7 Is Hyper-V supported?
     Q1-8 Is Windows Server 2008 R2 supported?
     Q1-9 When I attempted to install PathManager that came with NEC Storage E1-10 in a ft server in a Windows
          Server 2008 environment, the message "Setup is not compatible with this environment" appeared and the
          installation failed. What should I do?


2. Operation
     Q2-1 Is failback performed automatically?
     Q2-2 Can I disable automatic failback?
     Q2-3 Along with addition or deletion of a LUN, what should I perform for PathManager?
     Q2-4 After an NEC Storage device or HBA is replaced, is it required to reinstall PathManager?
     Q2-5 Is dynamic load balancing not supported by NEC Storage E1, and NEC Storage 100, 1000, and 2000 series?
     Q2-6 PathManager2.0 and later support the path patrol function. Is it available in PathManager1.1?
     Q2-7 Up to how many paths can PathManager manage/control?
     Q2-8 How does PathManager save log information?
     Q2-9 How can I upgrade PathManager?
    Q2-10 Although the Windows service list window shows that the Storage PathManager Configuration Checker
          service is set to Automatic, the service stops shortly after PathManager starts. Why does it happen?
    Q2-11 The PathManager log (spsevent.log) shows an event that seems to be an error. Does it represent any
          problem?
    Q2-12 The Warning event having the source name "spsdsm" and the Event ID 280 was recorded with the event log
          (system). Does it represent any problem?
    Q2-13 The Warning event having the source name "spsdsm" and the Event ID 278 was recorded with the event log
          (system).
    Q2-14 The active failback does not work in the NEC Storage E series.
    Q2-15 In the NEC Storage E series, executing spscmd -path does not switch an active path.
    Q2-16 In the NEC Storage E series, even when I execute spscmd -lbmode ::: 8 (or spscmd -lbmode ::: foa), active
          paths are not distributed (they do not become statically load balanced status).
    Q2-17 The Warning event having the source name "WinMgmt" and the Event ID 10 was recorded with the event log
          (application) although it was not after PathManager installation.
    Q2-18 Though I installed PathManager, PathManager does not appear in Add/Remove Programs. Has
          PathManager been installed normally?


     Q1-1 How can I check that PathManager has been properly installed and normally running?
         A Use the PathManager command. Execute spscmd -getlun from the command prompt to check that the
           expected number of path information items is displayed on a LUN basis. For more information about spscmd
           -getlun, see User's Manual.
     Q1-2 Which OSes are supported?
   A As for the support matrix of NEC Storage PathManager for Windows, see NEC Storage PathManager for
     Windows Installation Guide.
Q1-3 How much disk capacity and memory amount are required for running PathManager?
   A The following disk capacity and memory amount are required for running PathManager. For the latest
     information, see the installation guide for NEC Storage PathManager for Windows.
     [Windows Server 2003/2008]
                            Disk capacity: 33MB or more
                       Memory capacity: Memory required for OS + 10MB or more
Q1-4 How long does it take to install PathManager?
   A It takes several tens of minutes to install PathManager in one server.
     The time from installation to operation start depends on the system environment because connecting FC
     cables and starting servers are also needed. In general, it takes about one hour.
Q1-5 When I executed spscmd after installing PathManager, an error occurred.
   A When PathManager does not recognize paths at all, executing spscmd may fail with the following error:

     "CreateInstanceEnum failed"
     "ShowDiskDescriptors failed"

     If an error occurs, check the following:
         Has a correct HBA driver been installed? Has the correct procedure been taken for installing the HBA
     -
         driver?
           → Check the procedure for installing a HBA driver and reinstall the HBA driver corresponding to the
             installed OS and servers.
     - Have NEC Storage (AccessControl, Cross Call, etc.) and FC switches been configured correctly?
           → Check the NEC Storage and FC switch configurations.
     - Has a supported edition of PathManager been installed?
           → The supported editions of PathManager depend on the installed storage device.
             Check that the edition of PathManager you want to install is supported by the storage device to be
             connected to the PathManager.
Q1-6 Only one path is displayed and any others are not. What should I do?
   A Check the following:
     - Has FC cables been connected correctly?
           → Connect FC cables correctly.
     - Has a correct HBA driver been installed? Has the correct procedure been taken for installing the HBA
       driver?
           → Check the procedure for installing a HBA driver and reinstall a HBA driver corresponding to the
             installed OS and servers.
     - Have NEC Storage (AccessControl, Cross Call, etc.) and FC switches been configured correctly?
           → Check the NEC Storage and FC switch configurations.
Q1-7 Is Hyper-V supported?
   A An OS managed by Hyper-V can be connected to the NEC Storage D series.
     Operations on a guest OS built on Hyper-V are not supported.
Q1-8 Is Windows Server 2008 R2 supported?
   A The versions 4.1.2 and later are supported.
     The supported media are indicated on a medium label.
Q1-9 When I attempted to install PathManager that came with NEC Storage E1-10 in a ft server in a Windows
     Server 2008 environment, the message "Setup is not compatible with this environment" appeared and the
       installation failed. What should I do?
   A In the version 4.1.1, you cannot use Autorun in the setup CD to install PathManager. Start the following file
     directly for installation:

       (Drive to run setup CD):\W2K8\x64\setup.exe

       In the version 4.1.2 or later, Autorun in the setup CD is available for installation.
       The supported media are indicated on a medium label.
Q2-1 Is failback performed automatically?
   A In PathManager1.1, manual failback is set as default. PathManager2.0 or later performs failback
     automatically in the standby failback method when it acts according to the default setting.
Q2-2 Can I disable automatic failback?
   A No, you cannot.
Q2-3 Along with addition or deletion of a LUN, what should I perform for PathManager?
   A The required operation depends on the OS:
       [Windows Server 2003/2008]
              After you add or delete a LUN, start Disk Management and perform Rescan Disks.
              When rescanning is completed, the addition or deletion of the LUN is fixed.
       [Windows 2000]
              Restart the system.
Q2-4 After an NEC Storage device or HBA is replaced, is it required to reinstall PathManager?
   A Restart the system.
Q2-5 Is dynamic load balancing not supported by NEC Storage E1, and NEC Storage 100, 1000, and 2000 series?
   A The dynamic load balancing is not available in NEC Storage E1-10, S1100, S1200, S1300, S2100, S2200, or
     S2300 that do not support dynamic load balancing. It is available in other series.
Q2-6 PathManager2.0 and later support the path patrol function. Is it available in PathManager1.1?
   A PathManager1.1 does not support the path patrol function. It is recommended to use all paths constantly by
     using static load balancing.
Q2-7 Up to how many paths can PathManager manage/control?
   A PathManager can manage/control up to the following number of paths:
                           NEC Storage S/D series: 8 paths
                              NEC Storage E series: 4 paths
Q2-8 How does PathManager save log information?
   A The Windows-version PathManager logs activities in the PathManager log and event log (system). You can
     specify the size of OS-related event logs to be recorded through the event viewer. PathManager logs are log
     information PathManager internally retains and up to 10MB (5MB x 2) of PathManager logs will be saved.
     For more information, see 3.6 in the manual NEC Storage PathManager User's Manual (Windows version).
Q2-9 How can I upgrade PathManager?
   A
        To upgrade PathManager to 4.0 or later in a Windows Server 2003 environment, uninstall the
        PathManager you use currently and then install a new version of PathManager.
        When PathManager is upgraded, configurations of load balancing, etc. are not taken over. Take the
        following procedure to check and restore configurations:
        (1)   Execute the following commands to check the current configurations and take a note of them:
              >    spscmd -getwatcher (Health/Recovery check configuration)
              >    spscmd -getfbmode (Failback mode configuration)
              >    spscmd -geteventmode (Event mode configuration)
              >    spscmd -getlun -v (Load balancing configuration for each LUN and priority of each path)
       (2)   Install a new version of PathManager by following the procedure.
       (3)   Execute the following commands to restore configurations in order:
             >   spscmd -setwatcher (Health/Recovery check configuration)
             >   spscmd -setfbmode (Failback mode configuration)
             >   spscmd -seteventmode (Event mode configuration)
             >   spscmd -lbmode (Load balancing configuration)
             >   spscmd -priority (Priority of each path)


       For more details about spscmd, see NEC Storage PathManager User's Manual.

       The procedure for upgrading PathManager to the version 3.4 or earlier depends on the version of
       PathManager you currently use or the type of OS. For more information, see the installation guide.
Q2-10 Although the Windows service list window shows that the Storage PathManager Configuration Checker
      service is set to Automatic, the service stops shortly after PathManager starts. Why does it happen?
    A The Storage PathManager Configuration Checker service for Windows Server 2003 is a service to check the
      path configuration when PathManager starts. In the version 3.0 or 3.1, the service automatically stops when
      checking the path configuration is complete, which does not affect the system operation.
      In the version 3.2 or later, the Storage PathManager Configuration Checker service does not stop. In the
      Windows 2000 version, this symptom does not occur because the version does not have the Storage
      PathManager Configuration Checker service.
Q2-11 The PathManager log (spsevent.log) shows an event that seems to be an error. Does it represent any
      problem?
    A PathManager logs include events related to internal operations that developers should check. Not all logged
      events show errors.

      Events that a user should check will be logged in the event log (system). If no events are recorded with the
      event log (system) and normal path status is confirmed by executing spscmd –getlun, PathManager does not
      have any problem.
Q2-12 The Warning event having the source name "spsdsm" and the Event ID 280 was recorded with the event log
      (system). Does it represent any problem?
    A The event ID280 occurs when the device configuration has been changed due to a path failure or a
      maintenance operation.
      Execute spscmd -getlun through the command prompt to check that the expected number of path information
      items is displayed on a LUN basis.
      If the expected number of path information items is displayed, this warning event notifies you of the device
      configuration has been changed by a maintenance operation. To prevent events from being reported,
      execute spscmd -deletemissing.
      If the expected number of path information items is not displayed, this warning tells that some paths have not
      been recognized because of a path failure, etc.
Q2-13 The Warning event having the source name "spsdsm" and the Event ID 278 was recorded with the event log
      (system).
    A The event ID278 shows a non-redundant path.
      Some paths may have not been recognized because of a path failure, etc.
      Execute spscmd -getlun through the command prompt to check if paths have been recognized.
      See Q1-5 if executing spscmd -getlun results in an error or Q1-6 if only one path is displayed.
      If following the instructions in the answers for these questions does not solve the problem, a path failure may
      have occurred.
Q2-14 The active failback does not work in the NEC Storage E series.
    A With PathManager running on the NEC Storage E series, the active failback function does not work.
      Use the standby failback function instead. To remove a failure and restore a failed path to active, execute the
      following command through the command prompt:
          spscmd avail :::
Q2-15 In the NEC Storage E series, executing spscmd -path does not switch an active path.
    A It may occur when PathManager is used in the NEC Storage E series, when it is in a cluster environment or
      after failback from a path failure occurs.
      Execute the following commands through the command prompt in order:
            spscmd -notavail :::
            spscmd -avail :::
      Then reexecute spscmd -path to switch an active path.
Q2-16 In the NEC Storage E series, even when I execute spscmd -lbmode ::: 8 (or spscmd -lbmode ::: foa), active
      paths are not distributed (they do not become statically load balanced status).
    A It may occur when PathManager is used in the NEC Storage E series and it is in a cluster environment or
      after failback from a path failure occurs.
      Execute the following commands through the command prompt in order:
            spscmd -notavail :::
            spscmd -avail :::
      Then reexecute spscmd -lbmode ::: 8 (or spscmd -lbmode ::: foa) to make paths correctly become statically
      load balanced status.
Q2-17 The Warning event having the source name "WinMgmt" and the Event ID 10 was recorded with the event log
      (application) although it was not after PathManager installation.
    A The event ID10 of WinMmgt may be recorded not only after PathManager installation but also during system
      operation, such as when Configuration Checker is ongoing or when spscmd -getlun is executed. Also even
      after PathManager is uninstalled, the event may be recorded when a server starts. It happens due to the
      PathManager specification. Even if this event is recorded, it does not mean an abnormal operation and does
      not affect the system operation.
Q2-18 Though I installed PathManager, PathManager does not appear in Add/Remove Programs. Has
      PathManager been installed normally?
    A Windows has specification that shows PathManager in Add/Remove Programs only for the account of a
      user who has installed PathManager. Log in Windows using the account you used when installing
      PathManager.
Storage Control

PathManager for Linux
1. Installation
   Q1-1 Even after I install PathManager and restart OS, the dd device is not created. How can I solve this problem?
   Q1-2 How can I check that PathManager has been properly installed and normally running?
   Q1-3 Which OSes are supported?
   Q1-4 I do not have PathManager corresponding to the kernel version I use. Can I use PathManager supporting a
        kernel version close to the version I use?
   Q1-5 When I attempted to execute the patch command to change a startup script, an error message appeared and I
        failed to apply the patch. What should I do?
   Q1-6 Up to how many LUNs can I use?
   Q1-7 How much disk capacity can I use?
   Q1-8 How can I create a status setting file?
   Q1-9 How long does it take to install PathManager?
  Q1-10 Do I need to create a device file manually?
  Q1-11 Will existing data be assured after the Cross Call configuration is changed?
  Q1-12 Though I started PathManager, /etc/dualpathrc was not created. What should I do?
  Q1-13 As the size of /tmp/dd.log has increased, the size of free space in /tmp has decreased. What should I do?
  Q1-14 Tell me about the procedure for upgrading PathManager in an environment where ExpressCluster is running.
  Q1-15 A device of PathManager (ex. /dev/ddb) was mounted as unwritable. What should I do?
  Q1-16 Since I installed PathManager, ExpressCluster has not worked. What should I do?
  Q1-17 How much disk capacity and memory capacity are required for running PathManager?
  Q1-18 Does PathManager support a volume manager such as LVM or VxVM/VxFS?
  Q1-19 Can I use MD (Raid) in a PathManager device (/dev/dd*)?
  Q1-20 Can DMPs (dynamic multi paths) of PathManager and VxVM exist on the same OS?
  Q1-21 Does PathManager support VMWare?
  Q1-22 The status setting file for PathManager has been created correctly. However, IO through a dd device resulted
        in an I/O error.
        What is the possible cause?
  Q1-23 When I started OS, "sps: Error: Serial is NULL." was displayed in the system log and the device file of
        PathManager was not created. What should I do?
  Q1-24 Can I specify a label in /etc/fstab to mount a disk device?
  Q1-25 I cannot perform "Migration to a PathManager Environment" described in the installation guide because of no
        sg_scan command. What should I do?
  Q1-26 Which versions of PathManager and kernel are supported by NEC Storage E series?
  Q1-27 When I installed/upgraded PathManager in an Express5800/ft server series (320Fa/320Fb) environment, the
        FT lamp lit in green was turned off. What is the possible cause?


2. Operation
   Q2-1 Since I started the OS after changing hardware (NEC Storage, HBA, etc.), PathManager has been unstable.
        Tell me about the cause and how to solve the problem.
   Q2-2 Is failback performed automatically?
   Q2-3 Can I disable automatic failback?
   Q2-4 Along with addition, change, or deletion of a LUN, what should I perform for PathManager?
   Q2-5 Which series of NEC Storage support dynamic load balancing?
   Q2-6 Tell me about the least I/O size mode which is one of dynamic load balancing methods.
   Q2-7 Up to how many paths can PathManager manage/control?
 Q2-8 With the system log, how can I find logs reported by PathManager?
 Q2-9 Standby paths seem not to be monitored. How can I monitor them?
Q2-10 I will upgrade the glibc/FC driver along with kernel upgrade. Does this upgrade have impact on PathManager?
Q2-11 The ratio of CPU used by path patrol daemon is very high. How can I decrease it?
Q2-12 When the OS was restarted with some paths failing and then the failing paths recovered from the failures,
      PathManager does not recognize paths. How can I make PathManager recognize the paths?
Q2-13 I will upgrade PathManager along with kernel upgrade. By the upgrade, items configured in the previous
      version will be deleted?
Q2-14 In an environment where ExpressCluster is running, an error occurred in disk monitoring during path
      restoration (failback) and a cluster failover occurred. How can I prevent this problem?
Q2-15 When I started the OS, the message "Path Not Found" was displayed and I could not access the PathManager
      device (/dev/ddX). What is the possible cause?
Q2-16 After updating a certain RPM, do I need to perform any operation for PathManager?
Q2-17 When the OS is restarted with a non-redundant path, the message "The dd device of no redundant paths was
      detected." is not reported to ESMPRO. What is the possible cause?


 Q1-1 Even after I install PathManager and restart OS, the dd device is not created. How can I solve this problem?
    A Check the following:
          1. Has a supported HBA board been used?


          2. Has the serial number of NEC Storage been set?
             If the message "sps: Error: Serial is NULL." was output to the system log,
             serial number has not been set. Contact your maintenance staff.
             (This case is same as Q1-23.)


          3. Has the log "Unit Not Ready" been displayed in the system log?
           - When "sdx: Unit Not Ready" or an I/O error log is displayed in the system log, the NEC Storage LUN
             may be in Not Ready state. Use the GUI client of NEC Storage Manager to check the LUN state.
             ReplicationControl, SnapControl, or ProtectControl of ControlCommandSet may have changed the LUN
             state to Not Ready. Cancel the Not Ready state according to functions you use.


          4. Has the OS recognized NEC Storage?
           - Open the "/proc/scsi/scsi" file to check that "Vendor:NEC" and "Model:iStorage xxxx" are displayed.
             They are not displayed when NEC Storage has not been recognized by the OS.
             Check if FC cables are properly connected.

             (Example) HBA (Host:scsi2,scsi3) has recognized one NEC Storage disk (Lun:00).
             #cat /proc/scsi/scsi
             Host:scsi2 Channel:00 Id:00 Lun:00
                Vendor:NEC Model:iStorage 1000 Rev: 1400
                Type:Direct-Access ANSI SCSI revision:04
             Host:scsi3 Channel:00 Id:00 Lun:00
                Vendor:NEC Model:iStorage 1000 Rev: 1400
                Type:Direct-Access ANSI SCSI revision:04


          5. Does the PathManager you purchased meet the environment conditions for NEC Storage?
           - The Standard version is supported by the NEC Storage D8/D4/D3/D1 series, the S2XXX series or lower
             and the E series, and the Enterprise version is supported by all the NEC Storage series.
             For more information, see 2.1 "Operation Environment" in NEC Storage PathManager for Linux User's
            Manual.
            If you find that your PathManager does not meet your environment conditions, purchase PathManager
            of a version supported by the environment.


         6. Did you follow the procedures described in installation guide exactly when installing PathManager?
          - Execute the uname -r command to check the kernel version and if the kernel is supported by the
            installed PathManager.
          - Has the dependency (#depmod -a `uname -r`) been updated?
          - For restarting a 2.4 series kernel, has a created RAM disk been used?
            For more information, see Part I 1.2.1 "Installing RPM Files" in the Installation Guide.
Q1-2 How can I check that PathManager has been properly installed and normally running?
   A Use the rpm -qa | grep sps command to check if PathManager has been installed.
     The way of checking if PathManager is normally running varies depending on the OS you use, 2.6 series kernel
     or 2.4 series kernel. Take one of the following procedures.
     The following procedure is also available for checking PathManager operations after you upgrade
     PathManager to correspond to the upgraded kernel.

          - 2.6 series kernel
            Check that devices for the number of LUNs x paths have been recognized in "/proc/scsi/sps/devices"
            and the device information is displayed in "/proc/scsi/sps/ddx" (x=a to iv).


          - 2.4 series kernel
            Check that the disk-info: and path-info: lines for the number of LUNs x paths exist in
            "/proc/dualpath/devices" and the device information is displayed in "/proc/dualpath/ddx" (x=a to dx).


     Execute the uname -r command to check a kernel type. A result showing "2.6.~" represents 2.6 series kernel,
     or "2.4.~" represents 2.4 series kernel.
Q1-3 Which OSes are supported?
   A As for the support matrix of NEC Storage PathManager for Linux, see NEC Storage PathManager for Linux
     Installation Guide.
Q1-4 I do not have PathManager corresponding to the kernel version I use. Can I use PathManager supporting a
     kernel version close to the version I use?
   A Only PathManager that corresponds to the kernel version you use is enabled. Consider using a kernel whose
     version corresponds to your PathManager.
Q1-5 When I attempted to execute the patch command to change a startup script, an error message appeared and I
     failed to apply the patch. What should I do?
   A Change the startup script manually.
     Open the /etc/rc.d/rc.sysinit file by using an editor and put a script in it. Add the line group starting with a "+" of
     the patch file to the /etc/rc.d/rc.sysinit file.

     *    To use iSCSI connection, add the patch file also to the /etc/rc.d/init.d/iscsi file.
Q1-6 Up to how many LUNs can I use?
    A The maximum number of LUNs you can specify as volumes under PathManager in each kernel version is
      shown below.
      When ExpressCluster is used in a kernel that is not Kernel-2.6 series, up to 16 LUNs can be allocated as
      volumes under PathManager regardless of the kernel version.


       (Redhat)            Kernel-2.4.9-e series: [(128-n)/2]
                           Kernel-2.4.21-20.EL or earlier: [(256-n)/2]
                           Kernel-2.4.21-27.EL or later: [(256-n)/m]
                           Kernel-2.6.9-22.EL or earlier: [256/m]
                           Kernel-2.6.9-34.EL or later: [512/m]
       (MIRACLE)           Kernel-2.4.9-e.25.72ml or earlier: [(128-n)/2]
                           Kernel-2.4.9-e.25.78ml or later: [(128-n)/m]
                           Kernel-2.4.21 series: [(256-n)/m]
                           Kernel-2.6 series: [512/m]


                  n: Number of SCSI devices including HDDs built in the server except NEC Storage connected to the
                     server
               m: Number of redundant paths (2 to 32)
               [ ]: Rounded off to a whole number
 Q1-7 How much disk capacity can I use?
    A The (maximum) disk capacity that can be handled by a dd device depends on the OS.

       [ 8TB (terabyte)]
       (Red Hat)             Kernel-2.6.9-67.EL or later


       [ 2TB (terabyte)]
       (Red Hat)             Kernel-2.4 series
                             Kernel-2.6.9-55.0.12.EL or earlier


       (MIRACLE)             Kernel-2.4 series
                             Kernel-2.6 series
 Q1-8 How can I create a status setting file?
    A A status setting file (/etc/sps.conf for 2.6 series kernel and /etc/dualpathrc for 2.4 series kernel) is automatically
      created when PathManager is started. Users do not need to create the file under normal situations.
 Q1-9 How long does it take to install PathManager?
    A It takes only several minutes to install PathManager in general (it may be longer depending on the
      environment). After installation, the server needs to be restarted. Take the time to be taken for server restart
      into account when installing PathManager.
Q1-10 Do I need to create a device file manually?
    A You do not need to create a device file manually because it is automatically created when PathManager is
      installed.
Q1-11 Will existing data be assured after the Cross Call configuration is changed?
    A Changing the Cross Call configuration has no impact on existing data. You can use the data as usual.
Q1-12 Though I started PathManager, /etc/dualpathrc was not created. What should I do?
    A When PathManager 2.0.1 or earlier is used and the mount point is different between /etc and /tmp in the
      operation system, this symptom occurs due to a bug of PathManager.
      Apply the patch program of Issue No. 04016 stored in the update folder in the CD-ROM that comes with a
      PathManager product.

Q1-13 As the size of /tmp/dd.log has increased, the size of free space in /tmp has decreased. What should I do?
    A How to solve this problem is the same as Q1-12. Apply the patch program of Issue No. 04016.
Q1-14 Tell me about the procedure for upgrading PathManager in an environment where ExpressCluster is running.
    A An appendix of the installation guide describes in detail how to upgrade PathManager in an environment where
      ExpressCluster is running.
      The PathManager installation guide can be downloaded from the installation CD and Installation Guide on the
      NEC Storage web page.
Q1-15 A device of PathManager (ex. /dev/ddb) was mounted as unwritable. What should I do?
    A If ExpressCluster has been installed, this symptom may occur due to the configuration of ExpressCluster.
      For more information, see the manual of ExpressCluster.
Q1-16 Since I installed PathManager, ExpressCluster has not worked. What should I do?
    A Do you use 17 or more LUNs on OS of a 2.4-series kernel?
      When ExpressCluster is used, the number of LUNs you can use in PathManager is up to 16, which is also
      described in the manual of PathManager.
      Configure the number of LUNs to be 16 or less.
Q1-17 How much disk capacity and memory amount are required for running PathManager?
    A The following disk capacity and memory amount are required for running PathManager. For the latest
      information, see the installation guide for NEC Storage PathManager for Linux.
       (Kernel-2.6 series)
                Disk capacity: 5MB or more
          Memory capacity: Memory required for OS + 2MB or more
       (Kernel-2.4 series)
                Disk capacity: 1MB or more
          Memory capacity: Memory required for OS + 1MB or more
Q1-18 Does PathManager support a volume manager such as LVM or VxVM/VxFS?
    A The following are supported OSes. Other OSes are not supported by the PathManager.

       [VxVM]
                  Not supported


       [VxFS]
                  - RHEL3(IA32)
                    (Update2, Update4, Update5, Update5+Errata, Update6, Update7, Update8)
                  - RHEL3.9(IA32)


                  * The EM64T version is not supported.


       [LVM]
                  - RHEL4(IA32/EM64T/IA64)
                    (Update4)
                  - RHEL4.5(IA32/EM64T/IA64)
                  - RHEL4.5+Errata(IA32/EM64T/IA64)
                  - RHEL4.6(IA32/EM64T/IA64)
                 - RHEL4.7(IA32/EM64T)
                 - RHEL4.7+Errata(IA32/EM64T)
                 - RHEL4.8(IA32/EM64T)
                 - RHEL5.1(IA32/EM64T)
                 - RHEL5.2(IA32/EM64T)
                 - RHEL5.2+Errata(IA32/EM64T)
                 - RHEL5.3(IA32/EM64T)
                 - RHEL5.3+Errata(IA32/EM64T)
                 - SLES10 SP2(IA32/EM64T)
                 - SLES10 SP2+Errata(IA32/EM64T)


       To use LVM, the setting specific to PathManager needs to be made. For more information, see the
       manual/installation guide.
Q1-19 Can I use MD (Raid) in a PathManager device (/dev/dd*)?
    A Yes. When you configure MD in a PathManager device, note the following:
         1    To configure md in a PathManager device, specify "83(Linux)" for the partition ID of the PathManager
              device.
              (* Even if a PathManager device is specified in mdadm.conf when the partition ID is "fd" (Linux raid
              auto), md will be configured using the sd device with the result that md will not be started normally.)
         2    Modify mdadm.conf as follows:
              (Ex.)   To configure md by using PathManager devices (/dev/dda1, /dev/ddb1)
                      # vi mdadm.conf
                      DEVICE /dev/dda1 /dev/ddb1
                      ARRAY /dev/md0 devices=/dev/dda1,/dev/ddb1

                      (* If "UUID" is specified in the ARRAY line, md will not be started normally.)
Q1-20 Can I use both PathManager and DMP(dynamic multi paths) of VxVM concurrently?
    A Yes. PathManager supports the concurrent use with DMP on the following OSes.:
         -   RHEL5.2(IA32/EM64T)
Q1-21 Does PathManager support VMWare?
    A PathManager does not support VMware.
Q1-22 The status setting file for PathManager has been created correctly. However, IO through a dd device resulted in
      an I/O error.
      What is the possible cause?
    A A LUN of NEC Storage may be in Not Ready state. See the third answer in Q1-1.
Q1-23 When I started OS, "sps: Error: Serial is NULL." was displayed in the system log and the device file of
      PathManager was not created. What should I do?
    A "sps: Error: Serial is NULL." displayed in the system log when OS starts represents no serial No. specified for
      NEC Storage. It may be caused by an incorrect setting. Contact your maintenance staff.
      (* "sps: Error: Serial No is NULL." is displayed for a 2.4 series kernel.)
Q1-24 Can I specify a label in /etc/fstab to mount a disk device?
    A You cannot mount a disk device with a label specified.
      A label name to be specified for mounting a disk device needs to be unique. An environment where
      PathManager has been installed has at least two paths. If you attempt to mount a disk device by specifying a
      label, the environment will recognize the three same labels in total, two for /dev/sd* and one for /dev/dd* so that
      it will result in a mount error. In the first field of /etc/fstab, specify not a label but /dev/dd* for mounting.
Q1-25 I cannot perform "Migration to a PathManager Environment" described in the installation guide because of no
      sg_scan command. What should I do?
    A The sg_scan command is included in rpm "sg3_utils." sg3_utils may not be installed depending on the
      specification made during installation of the OS. In such a case, install the rpm contained in the installation CD
      of OS or the rpm "sg3_utils" downloaded from the web page of a distribution.
Q1-26 Which versions of PathManager and kernel support NEC Storage E series?
    A PathManager that comes with NEC Storage E series and PathManager Ver4.1 (Red Hat Enterprise Linux 5.1)
      and later support NEC Storage E series.
      PathManager Ver4.2 (Red Hat Enterprise Linux 5.3) or later can be used with ExpressCluster.
Q1-27 When I installed/upgraded PathManager in an Express5800/ft server series (320Fa/320Fb) environment, the
      FT lamp lit in green was turned off. What is the possible cause?
    A Is "sps: Warning: Attached /dev/dda only 1 path. " displayed in the system log?
      If the message is displayed, the FT lamp may not be lit because PathManager has recognized only one path.
      Perform the following:

             1. Stop I/O to/from NEC Storage. When NEC Storage is in use, stop I/O and unmount the corresponding
             device.
             2. Execute "/etc/rc.d/init.d/dd_daemon stop" to stop dd_daemon.
             3. Rename the /etc/sps.conf file by using any file name and save the file.
             4. Execute "mkdd -p."
                   (* After the execution, just in case, see /etc/sps.conf to check that two paths have been recognized
                   (two path-info lines) as described in Part II 3.3.3 "File Format (1.0)" in the manual of PathManager.
             5. Execute "/etc/rc.d/init.d/dd_daemon start" to start dd_daemon.
             6. Check that the FT lamp is lit in green.
 Q2-1 Since I started the OS after changing hardware (NEC Storage, HBA, etc.), PathManager has been unstable.
      Tell me about the cause and how to solve the problem.
    A Does the information in the status setting file match the hardware status?
      PathManager recognizes path information when it is started for the first time and saves the information in the
      status setting file. Unless a normal connection to NEC Storage and correct configurations are made when OS is
      started for the first time after PathManager installation, incorrect path information will remain.
      If it occurs, PathManager needs to recognize the path information again.
      To disable the status setting file, perform the following:

      (1) (For 2.4 series kernel)
          Stop path patrol daemon.
          # /etc/rc.d/init.d/dd_daemon stop
      (2) (For 2.6 series kernel)
          Rename /etc/sps.conf
          # mv /etc/sps.conf /etc/sps.conf.bak
          (For 2.4 series kernel)
          Rename /etc/dualpathrc
          # mv /etc/dualpathrc /etc/dualpathrc.bak
      (3) Restart OS.
 Q2-2 Is failback performed automatically?
    A Yes.
 Q2-3 Can I disable automatic failback?
    A No, you cannot disable automatic failback.
 Q2-4 Along with addition, change, or deletion of a LUN, what should I perform for PathManager?
    A After you add or change a LUN, perform the following:
       * If you use 2.6-series kernel OS, replace "/etc/dualpathrc" by "/etc/sps.conf" in below.


       1. Execute "/proc/scsi/scsi" to check that an added LUN is recognized by each HBA.
       2. Execute "/etc/rc.d/init.d/dd_daemon stop" to stop dd_daemon.
       3. Rename the /etc/dualpathrc file to any file name and save the file.
       4. Execute "mkdd".
       5. Execute "/etc/rc.d/init.d/dd_daemon start" to start dd_daemon.
       6. Make sure that the description of the device corresponding to the added LUN has been added to
          /etc/dualpathrc.


       After you delete a LUN, perform the following:
       1. Execute "/etc/rc.d/init.d/dd_daemon stop" to stop dd_daemon.
       2. Delete the information about the device corresponding to the deleted LUN from /etc/dualpathrc.
       3. Restart the system.
       4. Make sure that /etc/dualpathrc contains no description of the device corresponding to the deleted LUN.


 Q2-5 Which series of NEC Storage support dynamic load balancing?
    A The dynamic load balancing is supported by all the NEC Storage series except NEC Storage S1100, S1200,
      S1300, S2100, S2200, S2300, and E series.
 Q2-6 Tell me about the least I/O size mode which is one of dynamic load balancing methods.
    A The method is to detect a path whose total I/O size is less than other paths and issue I/O to that path. If some
      paths have same value, the earliest detected one is selected.
 Q2-7 Up to how many paths can PathManager manage/control?
    A The number of paths PathManager can manage/control is 2 in the function version 2.0.1 or earlier, and 2 to 32
      in the function version 2.0.2 or later. To check the function version of PathManager, execute
      "/proc/dualpath/version" in a 2.4 series kernel or "/proc/scsi/sps/version" in a 2.6 series kernel.
      If you use NEC Storage E series, the number of paths is 2.
      If you use NEC Storage D series (via iSCSI), the number of paths is 4.
 Q2-8 With the system log, how can I find logs reported by PathManager?
    A Search for the following character string to extract messages reported by PathManager:

       - For 2.6 series kernel: "sps:"
       - For 2.4 series kernel: "dualpath:"
 Q2-9 Standby paths seem not to be monitored. How can I monitor them?
    A The PathManager (the version of RPM module name is 2.0.0 or earlier) uses crond to monitor standby paths
      and send a signal (SIGUSR1) periodically to the monitoring daemon (dd_daemon).
      The new PathManager (the version og RPM module name is 2.0.1 or later) monitors active and standby paths.
      For more details about path monitoring, see 3.5 "Path Patrol Daemon" in the manual of PathManager.
Q2-10 I will upgrade the glibc/FC driver along with kernel upgrade. Does this upgrade have impact on PathManager?
    A It has no impact on PathManager because PathManager does not use glibc and is independent from the FC
      driver version.
Q2-11 The ratio of CPU used by the path patrol daemon is very high. How can I decrease it?
    A In NEC Storage PathManager 2.0d for Linux or earlier, the default interval for monitoring by path patrol daemon
      (CHK_IVAL) is 3 seconds. Because this interval is the minimum value for two LUNs, if NEC Storage is heavily
      loaded, CPU may also be heavily loaded. When a heavy load is put on NEC Storage, about 1 second is
      required for monitoring one path. A value for CHK_IVAL should be equal to or larger than the number of all the
      paths to be used.
      If a value less than the number of all the paths is set, the load of path patrol daemon will be constantly heavy
      depending on your system environment, which may affect the system operation.
      It is recommended to specify 60 seconds when the number of all paths is 60 or less.
Q2-12 When the OS was restarted with some paths failing and then the failing paths recovered from the failures,
      PathManager does not recognize paths. How can I make PathManager recognize the paths?
    A Because a 2.6-series kernel OS does not guarantee the order of recognizing paths, restarting the OS may
      change the path information. Once this occurs, even after failing paths recovered from the failures,
      PathManager cannot recognize paths and cannot perform failback because the path information to be
      recognized by OS has been changed. Not only PathManager devices but also the sd devices corresponding to
      the restored paths are not recognized by the OS. When it occurs, restart the OS after the failing paths
      recovered from the failures. In PathManager of the function version 3.0.5 or later, restarting OS is not required
      after restoration of failed paths. For more information, see Part II 4.2 "When the Fault Occurs" in the manual.
      To check a function version of PathManager, execute "/proc/scsi/sps/version".
Q2-13 I will upgrade PathManager along with kernel upgrade. Will items configured in the previous version be deleted
      by the upgrade?
    A The items configured in the previous version will be taken over.
      The PathManager settings are stored in the status setting file (2.6 series - /etc/sps.conf, 2.4 series -
      /etc/dualpathrc). This file will not be deleted by uninstallation of PathManager. Reinstalled PathManager will
      work according to the same configuration as the previous PathManager. It is recommended to save the status
      setting file as other name before new PathManager is installed to make sure the settings will be taken over.
Q2-14 In an environment where ExpressCluster is running, an error occurred in disk monitoring during path restoration
      (failback) and a cluster failover occurred. How can I prevent this problem?
    A Increase the number of retries for disk monitoring in ExpressCluster to prevent this problem.

Q2-15 When I started the OS, the message "Path Not Found" was displayed and I could not access the PathManager
      device (/dev/ddX). What is the possible cause?
    A See answers for Q1-1 and Q2-1.

Q2-16 After updating a certain RPM, do I need to perform any operation for PathManager?
    A After you update one of the following RPMs 1 to 5, perform the operation required along with the update:


       1.   initscripts
            The setting for automatic start of PathManager may be cleared and PathManager may not start.
            Check /etc/rc.d/rc.sysinit to see if the patch for automatic start of PathManager has been applied. If the
            setting to automatically start PathManager has been cleared, enable the setting again.
            To apply the patch, see also the answer for Q1-5.


       2.   iscsi-initiator-utils
            The setting for automatic start of PathManager may be cleared and PathManager may not start.
            Check /etc/rc.d/init.d/iscsi to see if the patch for automatic start of PathManager has been applied. If the
            setting to automatically start PathManager has been cleared, enable the setting again.
            To apply the patch, see also the answer for Q1-5.


       3.   diskdumputils
            When you have specified the PathManager device (/dev/dd*) as the destination to which diskdump will be
            reported, check /etc/sysconfig/diskdump to make sure the specification is correct. If the specification has
            been cleared, make it again.


       4.   kexec-tools (kdump for SLES10)
           When you have specified the PathManager device (/dev/dd*) as the destination to which kdump will be
           reported, check /etc/kdump.conf to make sure the specification is correct. If the specification has been
           cleared, make it again.


      5.   lvm2
           If you have configured LVM using the PathManager device (/dev/dd*), check /etc/lvm/lvm.conf to make
           sure the configuration is correct. If the configuration has been cleared, make it again.
Q2-17 When the OS was restarted with a non-redundant path, the message "The dd device of no redundant paths
      was detected." was not reported to ESMPRO. What is the possible cause?
    A In a SLES10 environment, this message is not reported depending on the version of ESMPRO.
      In such a case, stop the service (/etc/init.d/boot.klog) which uses /var/log/boot.msg. Then message reporting
      will work.
      (* If you have an application that accesses /var/log/boot.msg, do not take this procedure.)

      Perform the following:
         #insserv -r boot.crypto (Stop this first because it is dependent on boot.klog.)
         #insserv -r boot.klog
Backup

General backup
    Q1 Why do I need to back up data?
    Q2 What kind of advantage does disk backup have over tape backup?


Cluster

Express5800 series (Windows)
    Q3 Are there any notes on the procedure to replace the ExpressCluster FC drivers?
    Q4 Tell me about the notes on using NEC Storage Manager in an MSCS environment.


Groupware/Database

Groupware (Exchange, etc.)
    Q5 What should I take into account when using Exchange in terms of the number of users and responsiveness?


Database (Oracle/SQL, etc.)
    Q6 Tell me about non-disruptive backup in SQL/Oracle.


    Q1 Why do I need to back up data?

     A As the capacity of HDD is increased and data is collectively managed, high reliability on data storage is
       increasingly demanded. The most important thing in the information society is accumulated data itself. Data
       corruption due to an application error, a computer virus, or an operation error may lead to an irrecoverable loss
       in your business. To prevent it, data should be backed up.
    Q2 What kind of advantage does disk backup have over tape backup?

     A Tape backup has an advantage of using low cost and portable media, however it needs long backup time. With
       LTO, it takes about two hours to back up data of 100GB. On the contrary, it takes only about several tens of
       minutes to back up the same amount of data based on disks. NEC Storage features DynamicDataReplication
       that allows for disk backup. On a system that requires high reliability, you can separate data, which was backed
       up from a disk to a disk, from business tasks and then back up the data again to a tape.
    Q3 Are there any notes on the procedure to replace ExpressCluster FC drivers?

     A Replace FC drivers on a cluster system using ExpressCluster by following the procedure below.
          1. On each server in a cluster system, click Programs, Administrative Tools, and Services. Then change
             Startup Type for ActiveRecoveryManager related services from Automatic to Manual.
          2. Perform cluster shutdown (restart).
          3. Replace the FC driver on each server.
          4. Shut down the servers.
          5. Perform the following on each server:
             1) Start the server.
             2) Start Disk Administrator of the OS and check if the driver letter of each partition on the shared disk
                has been changed.
                If a drive letter has been changed, restore the original letter.
             3) Start the ExpressCluster Disk Administrator to check that the shared disk has been recognized as
                the X-CALL disk. If it has been recognized as a local disk, perform the following:
                A. Specify the local disk as the X-CALL disk.
                B. Restart the server.
           C. Start the ExpressCluster Disk Administrator to check the setting made in step A has been
           applied.
      4) Use the ExpressCluster Disk Administrator to check the cluster letter specified for the cluster
         partition. If the letter has been deleted, specify it again.
      5) Change Startup Type for ActiveRecoveryManager related services to Automatic.
      6) Shut down the server.
   6. Start all servers.
Q4 Tell me about the notes on using NEC Storage Manager in an MSCS environment.

 A It is highly recommended to use LAN for using NEC Storage Manager in an MSCS environment. Using FC
   connection in an MSCS environment is not recommended for the following reasons:
   1) If NEC Storage Manager uses a shared disk (not a local disk) as the control path and the ownership of
      the shared disk is moved to another machine due to a failover, disk array monitoring may be disabled.
   2) Installing MSCS while NEC Storage Manager is running may fail.
Q5 What should I take into account when using Exchange in terms of the number of users and responsiveness?

 A On a small mail delivery system such as MS-Exchange, a number of random I/O accesses having a small block
   size (less than 8 KBytes) are generated. To achieve high responsiveness in such system, take the following into
   account when configuring the system:
   ◇ Select a RAID level with high random access read performance.
    Raid level with high random read performance
    In principle, the larger number of HDDs the configuration has, the higher random read performance the
    system achieves.
    For example:
     - Raid-5: Configure a system having "4+P" or more HDDs instead of using a RANK configuration
       where a small number of HDDs such as 2+P are installed.
     - For Raid-1, use Raid-1×n configuration to increase HDDs. Alternatively, use Raid-10 (3+3 or more).
       * Assuming that up to 100 IOs are generated a second in one HDD, calculate a sufficient
         number of HDDs for your system.

    Raid level with high random write performance
    Similarly with read performance, a system where a larger number of HDDs are installed will have higher
    random write performance. However, remember that performance of one HDD varies depending on Raid
    level:
     - Raid-1 is the best choice in terms of performance of one HDD.
       (However, a small number of Raid-1 HDDs will be a bottleneck. One of the ways to prevent such
       bottleneck is employing Raid-10 (3+3 or more).)
     - The write performance of one HDD in Raid-5 is lower than Raid-1. However, there will be no problem
       with operations in a normal performance level if the system is composed of many HDDs such as
       Raid-5 (4+P), which is made up of 5 HDDs.
       *
           For Raid-1 type (Raid-1, Raid-10), assume that up to 70 IOs are generated a second in
           one HDD to calculate a sufficient number of HDDs for your system.
           For Raid-5 type, assume that up to 30 to 40 IOs are generated a second in one HDD to
           calculate a sufficient number of HDDs for your system.



   ◇ Other notes
    It is recommended to monitor loads of disk access frequency that will be increased as the number of users
    increases and as users get accustomed to the system after it is installed.
     * It is recommended to use NEC Storage PerformanceMonitor that provides functions to measure and
       monitor system performances.

Q6 Tell me about non-disruptive backup in SQL/Oracle.

 A 1) Use "SQL option" of NEC Storage Manager for non-disruptive backup in SQL server.
   2) In Oracle system, use RAW access.
      For non-disruptive backup in Filesystem mode, supported functions depend on the
      platform.
      - On Windows, non-disruptive backup is enabled in FileSystem mode unless automatic
        expansion is used.
Notes on installation

Q1 A driver error was detected when PathManager was installed on Windows. What possibly caused the error?
Q2 On a Windows NT 4.0 machine, I expanded a logical disk, connected an unused area to the disk to create a volume
   set by using Disk Administrator, and then the system automatically was rebooted. However, during the reboot, an
   error occurred in the drive I operated. What is the possible cause of the error?
Q3 I cannot create a partition in Disk Administrator on Windows. What should I do?



Q1 A driver error was detected when PathManager was installed on Windows. What possibly caused the error?
 A The following lists what you need to check and be careful when you install PathManager:

       1.   Set up the driver by following the setup procedure for HBA. Especially for Windows 2000, never skip the
            step 2 "Updating registries (by executing update.exe in the FD)."
       2.   To use NEC Storage S1100/S1200/S2100/S2200, set the NEC Storage Cross Call to On. To use
            AccessControl, configure AccessControl to allow each HBA to be connected to recognize a target logical
            disk. (It is desirable that AccessControl be configured by CE.)
       3.   To use ExpressCluster or MSCS*, be sure to set up PathManager before setting up ExpressCluster or
            MSCS.
       4.   The system disk format should be NTFS on Windows 2000. (Operations in FAT are not guaranteed.)
            * PathManager of the Windows NT4.0 version does not support MSCS.


Q2 On a Windows NT 4.0 machine, I expanded a logical disk, connected an unused area to the disk to create a volume
   set by using Disk Administrator, and then the system automatically was rebooted. However, during the reboot, an
   error occurred in the drive I operated. What is the possible cause of the error?
 A When you execute CHKDISK as prompted, an error showing it is unexecutable because of unmatched versions may
   occur. The error may be caused by NTFS versions that do not match. Windows 2000 is not fully compatible with
   Windows NT 4.0. If a Windows 2000 environment recognizes a logical disk that has been used on Windows NT 4.0,
   the NTFS control information on Windows NT 4.0 will automatically be updated (under the condition that SP4 or later
   has been applied to Windows NT 4.0). After that, while you can have general access to files, you cannot perform
   operations related to file control information such as volume sets or CHKDSK after expanding a logical disk.
Q3 I cannot create a partition in Disk Administrator on Windows. What should I do?
 A In Disk Administrator, you cannot create a partition unless you enter a signature for a newly-connected disk.
   Check if you have entered a signature. To check a signature on Windows 2000, right-click the area displaying a disk
   No. and a capacity on the upper left corner of the Disk Administrator window and select an item to display the
   signature.
Storage Management

NEC Storage Replication Navigator Suite
   Q1 What is NEC Storage Replication Navigator Suite?
   Q2 What are bundled with NEC Storage Replication Navigator Suite?
   Q3 For what is the FTP service used?

   Q1 What is NEC Storage Replication Navigator Suite?
    A NEC Storage Replication Navigator Suite is a program product that comes with products to build
      a non-disruptive backup system using the data replication function (DynamicDataReplication)
      and the snapshot function (DynamicSnap Volume) more easily for Microsoft SQL Server,
      Microsoft Exchange Server, and Windows file systems.
      NEC Storage Replication Navigator Suite is provided in the following three types.
        - NEC Storage Replication Navigator Suite for Exchange
        - NEC Storage Replication Navigator Suite for SQL
        - NEC Storage Replication Navigator Suite for FileSystem
   Q2 What are bundled with NEC Storage Replication Navigator Suite?
    A The following products are bundled.
      For more information on these products, see their FAQs.
       - NEC Storage Protection Manager for FileSystem
       - NEC Storage Protection Manager for Microsoft(R) SQL Server (only for Suite for SQL)
       - NEC Storage Protection Manager for Microsoft(R) Exchange Server (only for Suite for
         Exchange)
       - NEC Storage ControlCommand on Windows
       - NEC Storage VSS Provider
       - NEC Storage DynamicSnapVolume
       - NEC Storage DynamicDataReplication
   Q3 For what is the FTP service used?
    A The FTP service is used to transfer backup catalog information and SQL server metafiles
      between an application server and a backup server.
Storage Management

Protection Manager for Microsoft(R) SQL Server
 Q1 What file systems does Protection Manager for Microsoft(R) SQL support?
 Q2 In a multi-servers configuration, where a backup server is located in a different system, is it
    necessary to install ControlCommand in the backup server?
 Q3 On which server should Protection Manager for SQL Server be installed?
 Q4 The Replication function has the separate function with immediate specified and the restore function
    with RV protection specified. Are they available in Protection Manager?
 Q5 Executing drmfsdisplay –refresh failed in the backup server.
 Q6 Are there any prerequisite services or software programs to use Protection Manager?
 Q7 Is it necessary to enter FTP information in the operation definition file for an expand command?
 Q8 How can a still point be established for an application that does not work together with Protection
    Manager?
 Q9 What privileges or permissions do I need to run a Protection Manager command?
Q10 Is a configuration having two or more LVs supported?
Q11 Is the backup information of Protection Manager backed up?
Q12 How much of the disk is used by the directory where the dictionary map file of Protection Manager is
    stored?
Q13 The backup command timed out and ended abnormally.
Q14 The EX_DRM_DB_IMPORT or drmdbimport command failed and resulted in the KAVX0006-E error
    in the backup server.
Q15 Can the replication volume be mounted on a folder in a backup server?
Q16 Command execution failed in the backup server because of out of memory.
Q17 Which files in an SQL Server database are backed up?
Q18 How should the system database be located in a cluster environment?
Q19 How should the SQL Server database be located?
Q20 Is it possible to back up the system database?
Q21 Is it possible to back up transaction logs of the system database?
Q22 Is it possible to perform backup on a database basis?
Q23 Is it possible to back up multiple databases at a time?
Q24 Where can I find the backup metafile?
Q25 Are multiple instances supported?
Q26 Is it possible to back up transaction logs?
Q27 Is recovery by roll forward possible?
Q28 Roll forward recovery was performed by using the drmsqlrecover command but the message
    KAVX1310-I noting the data base has been recovered was shown.
Q29 Is cold backup for SQL Server database supported?
Q30 Are transaction logs truncated when a backup is performed?
    (*): a process of releasing unnecessary areas of a transaction log file
Q31 Can a database using the database mirroring function of SQL Server be backed up?
Q32 Can a database where the data partitioning function of SQL Server is used be backed up?
Q33 Is the SQL Server replication function supported?
Q34 Which SQL Server authentication mode does Protection Manager use?
Q35 Where should I save metafiles?
Q36 Can NTFS using VSS function be backed up nondisruptively?
Q37 Which cluster software is supported?
Q38 Do dictionary maps need to be shared between nodes in a cluster system?
Q39 Is setting by using the drmclusinit command necessary for using Protection Manager for
    Microsoft(R) SQL Server in an MSCS/MSFC environment?
Q40 Is setting by using the drmclusinit command necessary for using Protection Manager for
    Microsoft(R) SQL Server in an EXPRESSCLUSTER environment?
Q41 Is there anything that should be done when EXPRESSCLUSTER’s optional product, database
    monitoring option or Database Agent is used?
Q42 The drmsqlinit command failed in an EXPRESSCLUSTER X environment.
Q43 Can lowercase characters be used for virtual server names handled by Protection Manager?
Q44 Is the mirror disk system of EXPRESSCLUSTER X supported?
Q45 Does any action need to be taken for the disk RW monitoring of EXPRESSCLUSTER X?
Q46 Which backup software is supported?
Q47 Is a differential tape backup possible?
Q48 Can differential backup be performed for database files?
Q49 What should be entered in the DOS Prompt (command prompt) shown by executing the tape-restore
    command?
Q50 Backup Exec stalled and a tape-backup command did not end.
Q51 A tape-backup command using ARCserve ended abnormally.
Q52 When a tape backup was performed using NetBackup, unnecessary folders were also backed up.
Q53 When the backup of a volume which has been mounted in a folder using NetBackup was attempted,
    the data was not backed up.
Q54 A differential backup could not be performed for a volume that has been mounted in a folder using
    NetBackup or Backup Exec.
Q55 Can Protection Manager work together with the FlashBackup function of NetBackup?
Q56 Can the tape backup setting be made for each day of the week?
Q57 When a tape backup was performed, an alarm event appeared in the event log (application).
Q58 What kind of Java Runtime Environment is necessary for using the Protection Manager console?

 Q1 What file systems does Protection Manager for Microsoft(R) SQL Server support?
  A The following file system is supported.
         NTFS is supported.
 Q2 In a multi-servers configuration where a backup server is located in a different system, is it
    necessary to install Control Command in the backup server?
  A ControlCommand must be installed in the backup server. This is because while synchronization for a
    copy groups is not performed in the backup server, status of the copy group is checked by using the
    ControlCommand function.
 Q3 On which server should Protection Manager for SQL Server be installed?
  A Protection Manager for SQL Server consists of the following three software programs.
      1. Protection Manager - Copy Controller Installed in the database servers and the backup
                                                 servers.
      2. Protection Manager for SQL Server       Installed in the database servers.
      3. Protection Manager - Console(*)         Installed in the database servers and the backup
                                                 servers.

         (*) Protection Manager - Console is a program to operate Protection Manager with the user
             interface on the screen. Install it whenever necessary.
 Q4 The Replication function has the separate function with immeditate specified and the restore function
    with RV protection specified. Are they available in Protection Manager?
  A Yes.
    See “Preparation for Using Protection Manager” in the manual, Protection Manager CLI User’s
    Guide. When the separate function with immediate specified is used, backup can be done fast even
    if a difference between MV and RV is wide. The EX_DRM_SQL_BACKUP command or the
    drmsqlbackup command completes even if the changes are being reflected. The
    EX_DRM_TAPE_BACKUP command or the drmmediabackup command can be executed even if
    update is ongoing. However, note that an error is reported for restoration until asynchronous update
    for changes is complete. When the restore function with RV protection is used, you can ensure
    protection of backup data in RV. Even if there is a wide difference between MV and RV, fast
    restoration is possible. However, note that an error is reported for backup until asynchronous update
    for changes is complete.
 Q5 Executing drmfsdisplay –refresh failed in the backup server.
  A It is not necessary to update the dictionary map file in a backup server. (You cannot update it.)
    When you execute drmfsdisplay –refresh in a backup server, the following error occurs in Protection
    Manager.
          KAVX0006-E An error that stopped processing occurred.
              Cause = DRM-10015: An attempt to obtain RAID information failed.
 Q6 Are there any prerequisite services or software programs to use Protection Manager?
  A When tape backup is done by using an expand command, the FTP service is used. To use the FTP
    service, install FTP server in the backup server. You need write permission.
    To install Protection Manager – console, Java Runtime Environment (JRE) must be installed first.
 Q7 Is it necessary to enter FTP information in the operation definition file for an expand command?
  A To use an expand command, enter the FTP home directory and subdirectory in the operation
    definition file. If tape backup is not performed, the FTP service is not necessary. However, enter any
    directory name.
 Q8 How can a still point be established for an application that does not work together with Protection
    Manager?
  A Before executing a backup command with Protection Manager, stop the application temporarily to
    establish a still point.
    Restart the application after running a cold backup command.
 Q9 What privileges or permissions do I need to run a Protection Manager command?
  A Local administrator permissions are required.
Q10 Is a configuration having two or more LVs supported?
  A No.
    Set only one LV for one BV.
Q11 Is the backup information of Protection Manager backed up?
  A The backup information of Protection Manager is not backed up.
    If the backup information is lost, restoration cannot be done. Backup the backup information of
    Protection Manage as necessary. The backup information is located in the backup catalogue
    created in the directory to store the dictionary map file.
    When the OS startup disk is backed up by DDR in a SAN-Boot environment, the backup information
    may be restored together with the OS startup disk (if the dictionary map file is located in the OS
    startup disk). The backup information needs to be backed up in advance.
    For details on backing up the backup information, see “Backing Up a Protection Manager Operating
    Environment” in Protection Manager CLI User’s Guide.
Q12 How much of the disk is used by the directory where the dictionary map file of Protection Manager is
    stored?
  A The directory to store the dictionary map file contains the following:
         - Dictionary map file
         - Backup catalog file

     Use the following formula for calculation.

     The amount the dictionary map file uses in the disk (KB)
       = 0.2 +
          (the number of databases) + (the number of data files) +
          (the number of mounted drives) * 2 +
          (the number of physical disks) +
          (the number of replication volumes) * 0.2 +
          (the number of pair volumes) * 0.1

     The amount the backup catalog file uses in the disk (KB)
       = { 8.0 +
          (the number of databases) + ( the number of data files) +
          (the number of mounted drives ) * 2 +
          (the number of physical disks ) +
          (the number of replication volumes) * 0.2 +
          (the number of pair volumes ) * 0.2 +
          (the number of databases to be backed up) * 0.3 +
          (the number of data files to be backed up) * 4.0 +
          (the number of drives to be backed up) * 0.3 +
          (the number of files or directories to be backed up) * 4 +
          (the number of pair volumes to be backed up) * 0.1 } * (the number of backups performed)
Q13 The backup command timed out and ended abnormally.
  A When a huge amount of data is updated, a time out can occur while finish of replication is waited,
    which results in the following Protection Manager error.
        KAVX5119-E The retry of the pair status confirmation has timed out.
              Wait pair status = PAIR
              RESYNC_RETRY_TIME = 360 (times)
              RESYNC_RETRY_WAIT = 1000 (10 ms)
        KAVX0006-E An error that stopped processing occurred.
              Cause = DRM-10011: A timeout error occurred.
    Refer to “Specifying a Retry Count and Retry Interval for Pair Status Retires Checking” in Protection
    Manager CLI User’s Guide and configure the retry count and the retry interval of Protection
    Manager.
Q14 The EX_DRM_DB_IMPORT or drmdbimport command failed and resulted in the KAVX0006-E error
   in the backup server.
  A When the EX_DRM_DB_IMPORT or drmdbimport command is executed in the backup server
    where a copy group is locked, the following error occurs in Protection Manager.

          KAVX0006-E An error that stopped processing occurred.
                       Cause = DRM-10115: The backup data is already locked.

     A copy group is locked while; a replication volume is being mounted; command is stopped or the
     server is restarted during mounting.

     Follow the steps below to unlock the copy group.
      (1) Execute the drmcgctl command without any argument and check the status of the copy group.
      (2) If the copy group is locked, check the replication volume is mounted.
      (3) Unlock the copy group.
          <When the replication volume is mounted:>
               Unmount the replication volume by executing the EX_DRM_UMOUNT or drmumount
               command.
          <When the replication volume is not mounted:>
               Specify the –mode unlock option and execute the drmcgctl command to unlock the copy
               group.

         For details on commands, see Protection Manager Command Reference.
Q15 Can the replication volume be mounted on a folder in a backup server?
  A Yes.
    Note that if there is a chance of simultaneously executing two or more commands that mount the
    replication volume, specify a different folder for each command.
    If a mount command is executed by specifying a mounted folder, the following error occurs.

         KAVX0032-E             An invalid mount point directory was specified.

     The commands to mount the replication volume on a folder are:
       - drmmount (specify the -mount_pt option)
       - EX_DRM_MOUNT (specify the -mount_pt option)
       - EX_DRM_TAPE_BACKUP (specify the -mount_pt option)
Q16 Command execution failed in the backup server because of out of memory.
  A When the backup catalogue grows, the system runs out of memory and the following error occurs
    in command execution.

           KAVX0006-E An error that stopped processing occurred.
                  Cause = DRM-10105: Memory is insufficient.

     Execute the drmtapeinit command to adjust the number of days during which the tape backup
     catalog is saved.

     For details, see Chapter 3 “Preparation for Using Protection Manager” in Protection Manager CLI
     User’s Guide.
Q17 Which files in an SQL Server database are backed up?
  A Data files (*.mdf and *.ndf) and log files (.ldf) of the database are backed up. It is recommended to
    save data files and log files in different volumes.
Q18 How should the system database be located in a cluster environment?
  A In an EXPRESSCLUSTER environment, the system database should be stored in the local disk or
    the storage of each cluster.
    In the MSCS/MSFC environment, the system database should be stored in a shared disk.
Q19 How should the SQL Server database be located?
  A The data files (*.mdf and *.ndf) should be located in a volume other than the directory where
    metafiles are stored and the directory where the backup of transaction logs is stored.
Q20 Is it possible to back up the system database?
  A The system database can be backed up in a non-cluster or MSCS/MSFC cluster environment. The
    system database should be located on MV/BV.
    In an EXPRESSCLUSTER environment, the system database cannot be backed up.
Q21 Is it possible to back up transaction logs of the system database?
  A When the recovery mode of the system database is changed to other than “Simple”, transaction
     logs of the system database must be backed up. However, Protection Manager does not support
     backup of transaction logs of the system database.
     When the EX_DRM_SQL_TLOG_BACKUP or drmsqllogbackup command is executed for the
     system database, the following error occurs.

         KAVX1350-E           The transaction log of the system database cannot be
                              backed up.
Q22 Is it possible to perform backup on a database basis?
  A Yes.
    You can perform backup on an instance or database basis. Databases located in the same volume
    are backed up and restored simultaneously.
Q23 Is it possible to back up multiple databases at a time?
  A Yes.
    Up to 64 databases can be backed up at a time.
Q24 Where can I find the backup metafile?
  A The backup metafile is reported to the directory specified by the drmsqlinit command. It may be
    reported in the replication volume where the backup of the data file is stored. For details, see
    Command Reference.
Q25 Are multiple instances supported?
  A Yes.
    Note that data files on one disk drive should constitute one instance.
Q26 Is it possible to back up transaction logs?
  A Transaction logs are backed up together with database files (entire backup).
    You may perform differential backup for transaction logs after performing an entire backup.
    Differential backup logs are saved in the folder specified by the drmsqlinit command.
Q27 Is recovery by roll forward possible?
  A Yes.
    Roll forward recovery using transaction logs can be done by using the drmsqlrecover
    (-transact_log_list option) or drmsqlrecovertool command. To do this, transaction logs must be
    created in advance by using the EX_DRM_SQL_TLOG_BACKUP or drmsqllogbackup command.
Q28 Roll forward recovery was performed by using the drmsqlrecover command but the message
    KAVX1310-I noting the database has been recovered was shown.
  A The following message may be shown for the database to be recovered when roll-forward recovery
     is done by using the drmsqlrecover command.

          KAVX1310-I The database has already been recovered.
                 Processing will be skipped.
                    Database name = userdb1

     The database has been recovered successfully.
     Check the database status by using the SQL Server Management Studio of SQL Server
     2005/2008.
Q29 Is cold backup for SQL Server databases supported?
  A No.
Q30 Are transaction logs truncated when a backup is performed?
    (*): a process of releasing unnecessary areas of a transaction log file
  A When a backup is performed by using the EX_DRM_SQL_BACKUP or drmsqlbackup command, no
    part of transaction logs is truncated. If truncation of transaction logs is necessary, execute the
    EX_DRM_SQL_TLOG_BACKUP or drmsqllogbackup command.
Q31 Can a database using the database mirroring function of SQL Server be backed up?
  A Yes.
         - When one of the following commands is executed for a database where the data mirroring
           function is used, the command should be executed on the principal server.
               drmsqlbackup, drmsqllogbackup, drmsqldisplay -refresh
        - If a mirror database coexists, you cannot perform a backup.
        - When you restore a database where the database mirroring function is used, disable the
          Mirroring settings of the database before starting the restoration.
        - When the system database is restored together with a database where the database mirroring
          function is used, disable the mirroring settings of the database to be restored and restore the
          database after restoring the system database.
Q32 Can a database where the data partitioning function of SQL Server is used be backed up?
  A Yes.
    Note that the backup is performed on a logical disk basis. You cannot back up each partition
    individually.
Q33 Is the SQL Server replication function supported?
  A Yes.
     The following conditions must be satisfied to use the SQL Server replication function.
      - Choose “transaction replication” from three replication types (snapshot, transaction, and
         merge).
      - Name the distribution database “distribution” and create only one distribution database.
      - Configure the 'sync with backup' option for the publication and distribution databases.

     The publication database and the distribution database used in a single replication must satisfy the
     following conditions.
       - These two databases must be located in the same SQL Server instance because they must be
          backed up together.
       - These two databases must be located in a volume where the system database (master, model,
          and msdb) is not located because they must be restored separately from the system database

     The subscription database must be stored in a volume where the system database (master, model,
     and msdb) is not located because they must be restored separately from each other.
Q34 Which SQL Server authentication mode does Protection Manager use?
  A Protection Manager uses Windows authentication to log in SQL Server.
    A user who executes a Protection Manager command must be registered as a member of SQL
    Server’s sysadmin fixed server role.
Q35 Where should I save metafiles?
  A Consider the following factors to save the metafiles in a local disk or storage disk.
        - In a cluster environment, store metafiles in a shared disk.
        - When metafiles are stored in a storage disk, do not store them in the same disk that stores the
          system database or the user database.
        - Carefully select a location where metafiles are saved in a SAN Boot environment because the
          OS startup disk is the storage disk in this environment. When SQL Server is installed by
          default, the system database is located in the OS start up disk. The directory where VDI
          metafile is stored should be located in a disk other the OS startup disk.
Q36 Can NTFS using the VSS function be backed up nondisruptively?
  A a) When Windows Server is x86 architecture:
        Yes.
        See FAQ of Protection Manager for FileSystem.
     b) When Windows Server is x64 architecture:
        No.
Q37 Which cluster software is supported?
  A The following cluster software is supported:
    Windows : MSCS
                   MSFC
                   EXPRESSCLUSTER X
Q38 Do dictionary maps need to be shared between nodes in a cluster system?
  A Yes, they do.
    Refer to "Preparation for Using Protection Manager" in the manual, Protection Manager CLI User's
    Guide to allocate dictionary map files on the shared disk.
Q39 Is setting by using the drmclusinit command necessary for using Protection Manager for
    Microsoft(R) SQL Server in an MSCS/MSFC environment?
  A No, it is not.
    The system automatically recognizes the MSCS/MSFC environment and acts according to the
    environment. If the command is executed, delete the following related files:
      - (Installation directory)¥conf¥cluster¥DEFAULT.dat
      - (Installation directory)¥conf¥cluster¥MSCS.dat
Q40 Is setting by using the drmclusinit command necessary for using Protection Manager for
    Microsoft(R) SQL Server in an EXPRESSCLUSTER environment?
  A Yes, it is.
    Refer to the manual to register cluster resources by executing drmclusinit command. Register a
    cluster resource for each cluster node.
Q41 Is there anything that should be done when EXPRESSCLUSTER’s optional product, database
    monitoring option or Database Agent is used?
  A When the database monitoring option of EXPRESSCLUSTER or Database Agent of
    EXPRESSCLUSTER X is used, monitoring must be temporarily stopped before starting restoration.
Q42 The drmsqlinit command failed in an EXPRESSCLUSTER X environment.
  A If the drmsqlinit command fails with the following message shown, EXPRESSCLUSTER’s
     workaround must be performed.

     KAVX1008-E
                    An error occurred during SQL Server processing.
                    Processing = DRM-11013: Logging on to SQL Server...
                    Code = 18452
                    Cause = Failed to log in [Microsoft][ODBC SQL Server Driver][SQL Server] user
                    '(null)'. Reason: Not related to SQL Server trusted connection.




Q43 Can lowercase characters be used for virtual server names handled by Protection Manager?
  A Virtual server names are case-sensitive in the command/definition files of Protection Manager.
    Use uppercase characters for all the virtual server names to be set in the command/definition files of
    Protection Manager.
    While virtual computer names in EXPRESSCLUSTER X are all lowercase characters when
    Protection Manager is associated with EXPRESSCLUSTER X, use uppercase characters for all the
    command/definition files of Protection Manager.
Q44 Is the mirror disk system of EXPRESSCLUSTER X supported?
  A No, it is not.
Q45 Does any action need to be taken for the disk RW monitoring of EXPRESSCLUSTER X?
  A If the disk RW monitoring is used for monitoring disks to be backed up, stop the monitor resource of
    the disk RW monitoring temporarily before performing a cold backup/restore.
Q46 Which backup software is supported?
  A The following backup software is supported:
        - NetBackup
        - Backup Exec
        - ARCserve Backup
Q47 Is a differential tape backup possible?
  A The backup software needs to support time-based differential backup.
    Whether to associate with Protection Manager depends on the backup software.
       - NetBackup        : Supports time-based differential backup and backup associated with
                             Protection Manager.
       - Backup Exec : Supports time-based differential backup and backup associated with
                             Protection Manager.
       - ARCserve         : Does not support time-based differential backup.
         Backup
Q48 Can differential backup be performed for database files?
  A Differential tape backup based on date and time may not be performed for database files that are
    open 24 hours, because the update date is not changed for these files.
    Select full backup for tape backup of database files.
Q49 What should be entered in the DOS Prompt (command prompt) shown by executing the tape-restore
    command?
  A GUI operations are required for restore to be performed when ARCserve and Backup Exec that are
    supported by Windows are selected. After the GUI operations are complete, respond to the
    message shown by executing the restore command.
     For ARCserve, enter one of the following:
       YES         : Enter this when the GUI restore operation has normally ended.
       CAN         : Enter this to interrupt the GUI restore operation.
       ERR         : Enter this when the GUI restore operation has abnormally ended.
     For Backup Exec, enter one of the following:
       YES         : Enter this when the GUI restore operation has normally ended.
       CANCEL : Enter this to interrupt the GUI restore operation.
       NO          : Enter this when the GUI restore operation has abnormally ended.
    To register the tape-restore command with job scheduling software for operation, select NetBackup.
Q50 Backup Exec stalled and a tape-backup command did not end.
  A For Backup Exec, do not specify the RUN_IMMEDIATE parameter for the Schedule section in the
    backup job script file.
Q51 A tape-backup command using ARCserve ended abnormally.
  A Check if the user who has executed the command is authorized as the primary user of ARCserve
     (caroot). It can be checked by using the C:¥Program Files¥CA¥BrightStor ARCserve
     Backup¥ca_auth command.
          ca_auth -equiv getequiv User name Host name
               Example> ca_auth -equiv getequiv Administrator SV003
     If "reason: No equivalence exists for this user/host pair" appears as the execution
     result, execute the following command to authorize the user:
          ca_auth -equiv add User name Machine name Password of BrightStorUser
          caroot_username caroot
               Example> ca_auth -equiv add Administrator SV003 caroot caroot password


Q52 When a tape backup was performed using NetBackup, unnecessary folders were also backed up.
  A Check the setting of the NetBackup policy.
    When Backup Selections is set for the policy specified in NBU.dat, Protection Manager backs up
    data specified in Backup Selections as well as the data that is supposed to be backed up in a tape.
    Do not specify Backup Selections.
Q53 When the backup of a volume which has been mounted in a folder using NetBackup was attempted,
    the data was not backed up.
  A A necessary NetBackup policy setting has not been made.
    Select the Cross mount points check box for the policy specified in NBU.dat.
Q54 A differential backup could not be performed for a volume that has been mounted in a folder using
    NetBackup or Backup Exec.
  A NetBackup or Backup Exec does not support differential backup for a volume mounted in a folder.
Q55 Can Protection Manager work together with the FlashBackup function of NetBackup?
  A To use the FlashBackup function, perform a tape backup in other way than Protection Manager.
Q56 Can the tape backup setting be made for each day of the week?
  A Yes, it can.
    Use the -bup_env option of the EX_DRM_TAPE_BACKUP command to specify definition files
    including settings specified for each day of the week.
    For more information, refer to "Creating a Configuration Definition File for Tape Backup" in
    Protection Manager CLI User's Guide.
Q57 When a tape backup was performed, an alarm event appeared in the event log (application).
  A When a directory to store VDI meta files is not specified by using the drmsqlinit command, the
     following alarm event appears in the event log (application) during a tape backup:

     Event type: Warning
     Event Source: Protection Manager
     Event ID: 441
     Description: KAVX0441-W You cannot specify the -bkdir option for this backup
     ID.

     The tape backup operation will not be affected. Ignore this event.
Q58 What kind of Java Runtime Environment is necessary for using the Protection Manager console?
  A The following Java Runtime Environment is necessary:
      - Java Runtime Environment (JRE) version 1.4.2 or later (32 bit)
    Download and install Java Runtime Environment from the webpage of Sun Microsystems, Inc.
Storage Management

Protection Manager for FileSystem on Windows
 Q1 What file systems Protection Manager for FileSystem on Windows supported?
 Q2 In a multi-servers configuration where a backup server is located in a different system, is it
    necessary to install Control Command in the backup server?
 Q3 The replication function has the separate function with immeditate specified and the restore
    function with RV protection specified. Are they available in Protection Manager?
 Q4 Executing drmfsdisplay –refresh failed in the backup server.
 Q5 Are there any prerequisite services or software programs to use Protection Manager?
 Q6 Is it necessary to enter FTP information in the operation definition file for an expand command?
 Q7 How can a still point be established for an application that does not work together with Protection
    Manager?
 Q8 What privileges or permissions do I need to run a Protection Manager command?
 Q9 Is a configuration having two or more LVs supported?
Q10 Is the backup information of Protection Manager backed up?
Q11 How much of the disk is used by the directory where the dictionary map file of Protection Manager
    is stored?
Q12 The backup command timed out and ended abnormally.
Q13 The EX_DRM_DB_IMPORT or drmdbimport command failed and resulted in the KAVX0006-E
    error in the backup server.
Q14 Can the replication volume be mounted on a folder in a backup server?
Q15 Command execution failed in the backup server because of out of memory.
Q16 Is there any software necessary for using VSS?
Q17 What kind of configuration is necessary for a non-disruptive backup using the VSS function?
Q18 When VSS is used, can a backup be performed across multiple generations?
Q19 Why replication volumes should be shielded when VSS is used?
Q20 When VSS is used in a DynamicSnapVolume configuration, can tape restore be performed for the
    BV (base volume)?
Q21 When the SV was mounted (linked) in the backup server in a DynamicSnapVolume configuration,
    a non-disruptive backup using the VSS ended abnormally with the error of KAVX0006-E or
    KAVX5023-E.
Q22 When a non-disruptive backup using the VSS function was performed, an alarm message
    appeared in the event log in the backup server.
Q23 When a non-disruptive backup was performed using the VSS function on Windows Server 2003,
    an alarm message appeared in the event log in the application server.
Q24 When a non-disruptive backup was performed using the VSS function on Windows Server 2008,
    an error message appeared in the event log in the backup server.
Q25 When a non-disruptive backup was performed using the VSS function, an information message
    with the event ID 11770 appeared in the event log (application) in the backup server.
Q26 When a non-disruptive backup was performed using the VSS function, an information message
    with the event ID 3224 appeared in the event log (application) in the backup server.
Q27 Do active services need to be stopped for using the VSS?
Q28 Which cluster software is supported?
Q29 Do dictionary maps need to be shared between nodes in a cluster system?
Q30 Is setting by using the drmclusinit command necessary for using Protection Manager for
    FileSystem on Windows in an MSCS/MSFC environment?
Q31 Can lowercase characters be used for virtual server names handled by Protection Manager?
Q32 Is the mirror disk system of EXPRESSCLUSTER X supported?
Q33 Does any action need to be taken for the disk RW monitoring of EXPRESSCLUSTER X?
Q34 Which backup software is supported?
Q35 Is differential tape backup possible?
Q36 What should be entered in the DOS Prompt (command prompt) shown by executing the
    tape-restore command?
Q37 Backup Exec stalled and a tape-backup command did not end.
Q38 A tape-backup command using ARCserve ended abnormally.
Q39 When a tape backup was performed using NetBackup, unnecessary folders were also backed up.
Q40 IWhen the backup of a volume which has been mounted in a folder using NetBackup was
    attempted, the data was not backed up.
Q41 A differential backup could not be performed for a volume that has been mounted in a folder using
    NetBackup or Backup Exec.
Q42 Can Protection Manager be associated with the FlashBackup function of NetBackup?
Q43 Can the tape backup setting be made for each day of the week?
Q44 What kind of Java Runtime Environment is necessary for using the Protection Manager console?

 Q1 What file systems Protection Manager for FileSystem on Windows supported?
  A The following file system is supported.
        NTFS is supported.
 Q2 In a multi-servers configuration where a backup server is located in a different system, is it
    necessary to install Control Command in the backup server?
  A ControlCommand must be installed in the backup server. This is because while synchronization for
    a copy groups is not performed in the backup server, status of the copy group is checked by using
    the ControlCommand function.
 Q3 The replication function has the separate function with immeditate specified and the restore
    function with RV protection specified. Are they available in Protection Manager?
  A Yes.
    See “Preparation for Using Protection Manager” in the manual, Protection Manager CLI User’s
    Guide. When the separate function with immediate specified is used, backup can be done fast
    even if a difference between MV and RV is wide. The EX_DRM_SQL_BACKUP command or the
    drmsqlbackup command completes even if the changes are being reflected. The
    EX_DRM_TAPE_BACKUP command or the drmmediabackup command can be executed even if
    update is ongoing. However, note that an error is reported for restoration until asynchronous
    update for changes is complete. When the restore function with RV protection is used, you can
    ensure protection of backup data in RV. Even if there is a wide difference between MV and RV, fast
    restoration is possible. However, note that an error is reported for backup until asynchronous
    update for changes is complete.
 Q4 Executing drmfsdisplay –refresh failed in the backup server.
  A It is not necessary to update the dictionary map file in a backup server. (You cannot update it.)
    When you execute drmfsdisplay –refresh in a backup server, the following error occurs in
    Protection Manager.
           KAVX0006-E An error that stops processing occurred.
                Cause = DRM-10015: An attempt to obtain RAID information failed.
 Q5 Are there any prerequisite services or software programs to use Protection Manager?
  A When tape backup is done by using an expand command, the FTP service is used. To use the FTP
    service, install FTP server in the backup server. You need write permission.
    To install Protection Manager – console, Java Runtime Environment (JRE) must be installed first.
 Q6 Is it necessary to enter FTP information in the operation definition file for an expand command?
  A To use an expand command, enter the FTP home directory and subdirectory in the operation
    definition file. If tape backup is not performed, the FTP service is not necessary. However, enter
    any directory name.
 Q7 How can a still point be established for an application that does not work together with Protection
    Manager?
  A Before executing a backup command in Protection Manager, stop the application temporarily to
    establish a still point.
    Restart the application after running a cold backup command.
 Q8 What privileges or permissions do I need to run a Protection Manager command?
  A Local administrator permissions are required.
 Q9 Is a configuration having two or more LVs supported?
  A No.
    Set only one LV for one BV.
Q10 Is the backup information of Protection Manager backed up?
  A The backup information of Protection Manager is not backed up.
    If the backup information is lost, restoration cannot be done. Backup the backup information of
    Protection Manage as necessary. The backup information is located in the backup catalogue
    created in the directory to store the dictionary map file.
    When the OS startup disk is backed up by DDR in a SAN-Boot environment, the backup
    information may be restored together with the OS startup disk (if the dictionary map file is located in
    the OS startup disk). The backup information needs to be backed up in advance.
    For details on backing up the backup information, see “Backing Up a Protection Manager
    Operating Environment” in Protection Manager CLI User’s Guide.
Q11 How much of the disk is used by the directory where the dictionary map file of Protection Manager
    is stored?
  A The directory to store the dictionary map file contains the following:
        - Dictionary map files
        - Backup catalog files

     Use the following formula for calculation.

     The amount the dictionary map file uses in the disk (KB)
       = 0.2 +
         (the number of mounted drives) * 2 +
         (the number of physical disks) +
         (the number of replication volumes) * 0.2 +
         (the number of pair volumes) * 0.1

     The amount the backup catalog file uses in the disk (KB)
       = { 8.0 +
         (the number of mounted drives) * 2 +
         (the number of physical disks) +
         (the number of replication volumes) * 0.2 +
         (the number of pair volumes) * 0.2 +
         (the number of drives to be backed up) * 0.3 +
         (the number of files or directories to be backed up) * 4 +
         (the number of pair volumes to be backed up) * 0.1 } * (the number of backups performed)
Q12 The backup command timed out and ended abnormally.
  A When a huge amount of data is updated, a time out can occur while finish of replication is waited,
    which results in the following Protection Manager error.

           KAVX5119-E The retry of the pair status confirmation has timed out.
                 Wait pair status = PAIR
                 RESYNC_RETRY_TIME = 360 (times)
                 RESYNC_RETRY_WAIT = 1000 (10 ms)
           KAVX0006-E       An error that stopped processing occurred.
                 Cause = DRM-10011: A timeout error occurred.
    Refer to “Specifying a Retry Count and Retry Interval for Pair Status Retires Checking” in
    Protection Manager CLI User’s Guide and configure the retry count and the retry interval of
    Protection Manager.
Q13 The EX_DRM_DB_IMPORT or drmdbimport command failed and resulted in the KAVX0006-E error
    in the backup server.
  A When the EX_DRM_DB_IMPORT or drmdbimport command is executed in the backup server where
     a copy group is locked, the following error occurs in Protection Manager.

          KAVX0006-E       An error that stopped processing occurred.
                           Cause = DRM-10115: The backup data is already locked.

     A copy group is locked while; a replication volume is being mounted; command is stopped or the
     server is restarted during mounting.

     Follow the steps below to unlock the copy group.
      (1) Execute the drmcgctl command without any argument and check the status of the copy group.
      (2) If the copy group is locked, check the replication volume is mounted.
      (3) Unlock the copy group.
          <When the replication volume is mounted:>
               Unmount the replication volume by executing the EX_DRM_UMOUNT or drmumount
               command.
          < When the replication volume is not mounted>
               Specify the –mode unlock option and execute the drmcgctl command to unlock the copy
               group.

     For details on commands, see Protection Manager Command Reference.
Q14 Can the replication volume be mounted on a folder in a backup server?
  A Yes.
    Note that if there is a chance of simultaneously executing two or more commands that mount the
    replication volume, specify a different folder for each command.
    If a mount command is executed by specifying a mounted folder, the following error occurs.

           KAVX0032-E            An invalid mount point directory was specified.


     The commands to mount the replication volume on a folder are:
         - drmmount (specify the -mount_pt option)
         - EX_DRM_MOUNT (specify the -mount_pt option)
         - EX_DRM_TAPE_BACKUP (specify the -mount_pt option)
Q15 Command execution failed in the backup server because of out of memory.
  A When the backup catalogue grows, the system runs out of memory and the following error occurs in
    command execution.

           KAVX0006-E   An error that stopped processing occurred.
               Cause = DRM-10105: Memory is insufficient.

     Execute the drmtapeinit command to adjust the number of days during which the tape backup
     catalog is saved.

     For details, see “Preparation for Using Protection Manager” in the manual, Protection Manager CLI
     User’s Guide.
Q16 Is there any software necessary for using VSS?
  A VSS Provider needs to be installed in the application and backup servers.
Q17 What kind of configuration is necessary for a non-disruptive backup using the VSS function?
  A A backup server is necessary even if tape backup is not performed.
    The backup server changes volume attributes, which is required for non-disruptive backups using the
    VSS function.
Q18 When VSS is used, can a backup be performed across multiple generations?
  A Yes, it can.
    However, the backup server cannot simultaneously recognize multiple replication volumes that have
    been backed up non-disruptively with the VSS function. For DynamicDataReplication, shield all
  replication volumes from the backup server and make OS recognize the volumes if necessary. For
  more information, refer to "Preparation for Using Protection Manager" in the manual, Protection
  Manager CLI User's Guide which describes how to make OS recognize replication volumes
  dynamically.
                              One generation Multiple generations
   DynamicDataReplication             -               Shield
   DynamicSnapVolume                  -                     -

   Shield : Shielding replication volumes is required
        - : Shielding replication volumes is not required

Q19 Why replication volumes should be shielded when VSS is used?
  A When a non-disruptive backup is performed using the VSS function, the disk signature for
    replication volumes becomes identical with the signature for application volumes.
    In a configuration with multiple generations, multiple disks having the same signature may be
    recognized by the backup server at the same time. In such case, the OS changes the disk signature
    (*).
    The change of a disk signature may affect the system operation. Shield replication volumes to
    prevent the backup server from recognizing multiple disks having the same signature.

           When a signature is changed, an alarm such as the following may appear in the event log
       *
           (system):
           Event type   : Warning
           Event source : PartMgr
           Event ID     : 58
           Description    The signature of disk 22 is being changed because it is the
                        : same as disk 18.

Q20 When VSS is used in a DynamicSnapVolume configuration, can tape restore be performed for the
    BV (base volume)?
  A When tape restore is performed for backup data using the VSS function in a DynamicSnapVolume
    configuration, the restore cannot be performed directory in the application volume by linking the
    base volume (BV) and the link volume (LV). Edit NEC Storage disk array subsystem operation
    configuration file (NEC.dat) to link the snapshot volume (SV) and the LV, enabling tape restore in
    the SV.
     NEC Storage disk array subsystem operation configuration file(NEC.dat) is store in the following:
           Destination of Protection Manager installation: ¥conf¥raid¥NEC.dat
           Specify tape_restore_dest = sv.
Q21 When the SV was mounted (linked) in the backup server in a DynamicSnapVolume configuration, a
    non-disruptive backup using the VSS ended abnormally with the error of KAVX0006-E or
    KAVX5023-E.
  A To perform a non-disruptive backup using the VSS, the SV in the backup destination and SVs in
    other than the backup destination need to be unmounted from (not linked with) the backup server.
    Unmount the SV which is being mounted in the backup server and then reexecute the backup.
Q22 When a non-disruptive backup using the VSS function was performed, an alarm message appeared
    in the event log in the backup server.
  A When PathManager is installed, the following alarm may appear in the event log (system):


           Event type         :   Warning
           Event source       :   spsdsm
           Event ID           :   530
           Description        :   A path is lost.



     Take the following procedure to change an alarm message to an information message:
      (1) Boot the command prompt in the backup server.
      (2) Execute the following command:
             PROMPT > spscmd -seteventmode 1
    Then take the following procedure to set the failback mode to active:
     (1) Boot the command prompt in the backup server.
     (2) Execute the following command:
            PROMPT > spscmd -setfbmode a

Q23 When a non-disruptive backup was performed using the VSS function on Windows Server 2003, an
    alarm message appeared in the event log in the application server.
  A
     When a backup is performed using VSS, the following alarm
     message may appear in the event log in the application server:




     <Application event log>

     Event type: Warning

     Event source: EventSystem

     Event ID: 4354
     Description: The COM + event system has failed to start
                  with the RequestWriterInfo method in the
                  subscription
                  {1ACBFF9B-00D7-4546-9608-73DDBC995F4C}
                  -{00000000-0000-0000-0000-000000000000}
                  -{00000000-0000-0000-0000-000000000000}.
                  The subscriber has returned HRESULT
                  80010105.


     This alarm message is logged when a problem occurs in the COM+
     component related to the VSS writer.
     The problem may be solved by re-registering the registry
     information in accordance with the following open information:
     http://support.microsoft.com/kb/940184
Q24 When a non-disruptive backup was performed using the VSS function on Windows Server 2008, an
     error message appeared in the event log in the backup server.
  A        If a volume in Not Ready or Not Available state exists in the backup server and a
           backup is performed using VSS, the following error may appear in the event log in the
           backup server.

             <System event log>
             Event type        : Error
             Event source      : Virtual Disk Service
             Event ID          :1
             Description       : An unexpected error occurred.
                                  Error code: 13@02000018

             <Application event log>
             Event type         : Error
             Event source       : VSS
             Event ID           : 12289
             Description        : Volume shadow copy service error
                                   Unexpected error IOCTL_DISK_GET_DRIVE_LAYOUT_EX


           This error does not affect the system operation.
Q25 When a non-disruptive backup was performed using the VSS function, an information message with
     the event ID 11770 appeared in the event log (application) in the backup server.
  A Due to the iSM host agent service function of ControlCommand Ver5.1 or later, the following
    message may appear in an event log (application). It does not affect non-disruptive backups using
    the VSS function.

         Event type          :   Information
         Event source        :   iSMcc_hostinfo
         Event ID            :   11770
         Description         :   iSM11770: Host Information was exported successfully.


     If iSM host agent service does not need to automatically collect and register the host information,
     the system can be operated with iSM host agent service stopped.
     To prevent the iSM host agent service from automatically booting during system reboot, click
     Start, All Programs, Administrative Tools, and click NEC Storage Manager Host Agent to
     change the start-up type from Automatic to Manual.
Q26 When a non-disruptive backup was performed using the VSS function, an information message with
    the event ID 3224 appeared in the event log (application) in the backup server.
  A When a non-disruptive backup is performed using the VSS function, the following error message
     may appear in the event log in the backup server:

     <Application event log>
     Event type: Error
     Event source: NEC StorageManager
     Event ID: 3224
     Description: iSM : 0000001880 Err iSMagcomma iSM03224:Control path is blockaded.

     This error has occurred because the disk that NEC StorageManager uses for monitoring with FC
     connection is the replication volume for non-disruptive backups using the VSS function.

     If only this error appears, the error message can be ignored because monitoring has already been
     switched to other LD.
     Change the way NEC StorageManager monitors disk arrays to one of the following to prevent this
     error:
         - Monitoring with IP connection
        - For monitoring with FC connection, specifying the number of a disk that is not the replication
          volume for non-disruptive backups using the VSS function.
Q27 Do active services need to be stopped for using the VSS?
  A Active services do not need to be stopped.
Q28 Which cluster software is supported?
  A The following cluster software is supported:
    Windows : MSCS
                   MSFC
                   EXPRESSCLUSTER X
Q29 Do dictionary maps need to be shared between nodes in a cluster system?
  A Yes, they do.
    Refer to "Preparation for Using Protection Manager" in the manual, Protection Manager CLI User's
    Guide to allocate dictionary map files on the shared disk.
Q30 Is setting by using the drmclusinit command necessary for using Protection Manager for FileSystem
    on Windows in an MSCS/MSFC environment?
  A No, it is not.
     The system automatically recognizes the MSCS/MSFC environment and acts according to the
     environment. If the command is executed, delete the following related files:
        - (Installation directory)¥conf¥cluster¥DEFAULT.dat
        - (Installation directory)¥conf¥cluster¥MSCS.dat
Q31 Can lowercase characters be used for virtual server names handled by Protection Manager?
  A Virtual server names are case-sensitive in the command/definition files of Protection Manager.
    Use uppercase characters for all the virtual server names to be set in the command/definition files
    of Protection Manager.
    While virtual computer names in EXPRESSCLUSTER X are all lowercase characters when
    Protection Manager is associated with EXPRESSCLUSTER X, use uppercase characters for all the
    command/definition files of Protection Manager.
Q32 Is the mirror disk system of EXPRESSCLUSTER X supported?
  A No, it is not.
Q33 Does any action need to be taken for the disk RW monitoring of EXPRESSCLUSTER X?
  A If the disk RW monitoring is used for monitoring disks to be backed up, stop the monitor resource of
    the disk RW monitoring temporarily before performing a cold backup/restore.
Q34 Which backup software is supported?
  A The following backup software is supported:
        - NetBackup
        - Backup Exec
        - ARCserve Backup
Q35 Is a differential tape backup possible?
  A The backup software needs to support time-based differential backup.
     Whether to associate with Protection Manager depends on the backup software.
      - NetBackup       : Supports time-based differential backup and backup associated with
                          Protection Manager.
      - Backup Exec : Supports time-based differential backup and backup associated with
                          Protection Manager.
      - ARCserve        : Does not support time-based differential backup.
        Backup
Q36 What should be entered in the DOS Prompt (command prompt) shown by executing the
    tape-restore command?
  A GUI operations are required for restore to be performed when ARCserve and Backup Exec that are
    supported by Windows are selected. After the GUI operations are complete, respond to the
    message shown by executing the restore command.
     For ARCserve, enter one of the following:
      YES       : Enter this when the GUI restore operation has normally ended.
      CAN       : Enter this to interrupt the GUI restore operation.
      ERR       : Enter this when the GUI restore operation has abnormally ended.
     For Backup Exec, enter one of the following:
      YES       : Enter this when the GUI restore operation has normally ended.
      CANCEL : Enter this to interrupt the GUI restore operation.
       NO         : Enter this when the GUI restore operation has abnormally ended.
    To register the tape-restore command with job scheduling software for operation, select NetBackup.
Q37 Backup Exec stalled and a tape-backup command did not end.
  A For Backup Exec, do not specify the RUN_IMMEDIATE parameter for the Schedule section in the
    backup job script file.
Q38 A tape-backup command using ARCserve ended abnormally.
  A Check if the user who has executed the command is authorized as the primary user of ARCserve
    (caroot). It can be checked by using the C:¥Program Files¥CA¥BrightStor ARCserve
    Backup¥ca_auth command.
         ca_auth -equiv getequiv User name Host name
             Example> ca_auth -equiv getequiv Administrator SV003
    If "reason: No equivalence exists for this user/host pair" appears as the execution
    result, execute the following command to authorize the user:
         ca_auth -equiv add User name Machine name Password of BrightStorUser
         caroot_username caroot
             Example> ca_auth -equiv add Administrator SV003 caroot caroot password


Q39 When a tape backup was performed using NetBackup, unnecessary folders were also backed up.
  A Check the setting of the NetBackup policy.
    When Backup Selections is set for the policy specified in NBU.dat, Protection Manager backs up
    data specified in Backup Selections as well as the data that is supposed to be backed up in a
    tape. Do not specify Backup Selections.
Q40 When the backup of a volume which has been mounted in a folder using NetBackup was attempted,
    the data was not backed up.
  A A necessary NetBackup policy setting has not been made.
    Select the Cross mount points check box for the policy specified in NBU.dat.
Q41 A differential backup could not be performed for a volume that has been mounted in a folder using
    NetBackup or Backup Exec.
  A NetBackup or Backup Exec does not support differential backup for a volume mounted in a folder.
Q42 Can Protection Manager be associated with the FlashBackup function of NetBackup?
  A To use the FlashBackup function, perform a tape backup in other way than Protection Manager.
Q43 Can the tape backup setting be made for each day of the week?
  A Yes, it can.
    Use the -bup_env option of the EX_DRM_TAPE_BACKUP command to specify definition files
    including settings specified for each day of the week.
    For more information, refer to "Creating a Configuration Definition File for Tape Backup" in
    Protection Manager CLI User's Guide.
Q44 What kind of Java Runtime Environment is necessary for using the Protection Manager console?
  A The following Java Runtime Environment is necessary:
       - Java Runtime Environment (JRE) version 1.4.2 or later (32 bit)
     Download and install Java Runtime Environment from the webpage of Sun Microsystems, Inc.
Storage Management

Protection Manager for Microsoft(R) Exchange Server
 Q1 What file systems does Protection Manager for Microsoft(R) Exchange Server support?
 Q2 In a multi-servers configuration where a backup server is located in a different system, is it necessary
    to install Control Command in the backup server?
 Q3 On which server should Protection Manager for Exchange Server be installed?
 Q4 The replication function has the separate function with immeditate specified and the restore function
    with RV protection specified. Are they available in Protection Manager?
 Q5 Executing drmfsdisplay –refresh failed in the backup server.
 Q6 Are there any prerequisite services or software programs to use Protection Manager?
 Q7 Is it necessary to enter FTP information in the operation definition file for an expand command?
 Q8 How can a still point be established for an application that does not work together with Protection
    Manager?
 Q9 What privileges or permissions do I need to run a Protection Manager command?
Q10 Is a configuration having two or more LVs supported?
Q11 Is the backup information of Protection Manager backed up?
Q12 How much of the disk is used by the directory where the dictionary map file of Protection Manager is
    stored?
Q13 The backup command timed out and ended abnormally.
Q14 The EX_DRM_DB_IMPORT or drmdbimport command failed and resulted in the KAVX0006-E error
    in the backup server.
Q15 Can the replication volume be mounted on a folder in a backup server?
Q16 Command execution failed in the backup server because of out of memory.
Q17 Which files in an Exchange Server database are backed up?
Q18 Are multiple storage groups supported?
Q19 Is recovery by roll forward possible?
Q20 Is the circular logging setting effective?
Q21 How should the Exchange Server database be located?
Q22 Can transaction logs of the Exchange Server database be deleted?
Q23 Does the dependence of cluster resources need to be set in a single copy cluster (SCC) environment
    with Exchange Server 2007?
Q24 In a single copy cluster (SCC) environment with Exchange Server 2007, the restore command for
    Exchange abnormally ended with the error of KAVX1729.
Q25 Can cold backup be performed for Exchange Server 2007?
Q26 Are the high-availability functions of Exchange Server 2007 (SCC, CCR, LCR, and SCR) supported?
Q27 Is there any software necessary for using VSS?
Q28 What kind of configuration is necessary for a non-disruptive backup using the VSS function?
Q29 When VSS is used, can a backup be performed across multiple generations?
Q30 Why replication volumes should be shielded when VSS is used?
Q31 When VSS is used in a DynamicSnapVolume configuration, can tape restore be performed for the BV
    (base volume)?
Q32 When the SV was mounted (linked) in the backup server in a DynamicSnapVolume configuration, a
    non-disruptive backup using the VSS ended abnormally with the error of KAVX0006-E or
    KAVX5023-E.
Q33 When a non-disruptive backup using the VSS function was performed, an alarm message appeared
    in the event log in the backup server.
Q34 When a non-disruptive backup was performed using the VSS function on Windows Server 2003, an
    alarm message appeared in the event log in the application server.
Q35 When a non-disruptive backup was performed using the VSS function on Windows Server 2008, an
    error message appeared in the event log in the backup server.
Q36 When a non-disruptive backup was performed using the VSS function, an information message with
    the event ID 11770 appeared in the event log (application) in the backup server.
Q37 When a non-disruptive backup was performed using the VSS function, an information message with
    the event ID 3224 appeared in the event log (application) in the backup server.
Q38 Do active services need to be stopped for using the VSS?
Q39 A non-disruptive backup for the Exchange Server database took long time or ended abnormally due
    to timeout.
Q40 Which cluster software is supported?
Q41 Do dictionary maps need to be shared between nodes in a cluster system?
Q42 Is setting by using the drmclusinit command necessary for using Protection Manager for Microsoft(R)
    Exchange Server in an MSCS/MSFC environment?
Q43 Can lowercase characters be used for virtual server names handled by Protection Manager?
Q44 Is the mirror disk system of EXPRESSCLUSTER X supported?
Q45 Does any action need to be taken for the disk RW monitoring of EXPRESSCLUSTER X?
Q46 Which backup software is supported?
Q47 Is a differential tape backup possible?
Q48 What should be entered in the DOS Prompt (command prompt) shown by executing the tape-restore
    command?
Q49 Can differential tape backup be performed for database files?
Q50 Backup Exec stalled and a tape-backup command did not end.
Q51 A tape-backup command using ARCserve ended abnormally.
Q52 When a tape backup was performed using NetBackup, unnecessary folders were also backed up.
Q53 When the backup of a volume which has been mounted in a folder using NetBackup was attempted,
    the data was not backed up.
Q54 A differential backup could not be performed for a volume that has been mounted in a folder using
    NetBackup or Backup Exec.
Q55 Can Protection Manager be associated with the FlashBackup function of NetBackup?
Q56 Can the tape backup setting be made for each day of the week?
Q57 What kind of Java Runtime Environment is necessary for using the Protection Manager console?
Q58 Does Protection Manager support Exchange Server 2010?

 Q1 What file systems does Protection Manager for Microsoft(R) Exchange Server support?
  A The following file system is supported.
         NTFS is supported.
 Q2 In a multi-servers configuration where a backup server is located in a different system, is it necessary
    to install Control Command in the backup server?
  A ControlCommand must be installed in the backup server. This is because while synchronization for a
    copy groups is not performed in the backup server, status of the copy group is checked by using the
    ControlCommand function.
 Q3 On which server should Protection Manager for Exchange Server be installed?
  A Protection Manager for Exchange Server consists of the following three software programs.
      1. Protection Manager - Copy Controller Installed in the database servers and the backup
                                                 servers.
      2. Protection Manager for Exchange          Installed in the database servers.
         Server
      3. Protection Manager - Console(*)          Installed in the database servers and the backup
                                                  servers.

         (*) Protection Manager - Console is a program to operate Protection Manager with the user
             interface on the screen. Install it whenever necessary.
 Q4 The replication function has the separate function with immeditate specified and the restore function
    with RV protection specified. Are they available in Protection Manager?
  A Yes.
    See “Preparation for Using Protection Manager” in the manual, Protection Manager CLI User’s Guide.
    When the separate function with immediate specified is used, backup can be done fast even if a
    difference between MV and RV is wide. The EX_DRM_SQL_BACKUP command or the
    drmsqlbackup command completes even if the changes are being reflected. The
    EX_DRM_TAPE_BACKUP command or the drmmediabackup command can be executed even if
    update is ongoing. However, note that an error is reported for restoration until asynchronous update
    for changes is complete. When the restore function with RV protection is used, you can ensure
    protection of backup data in RV. Even if there is a wide difference between MV and RV, fast
    restoration is possible. However, note that an error is reported for backup until asynchronous update
    for changes is complete.
 Q5 Executing drmfsdisplay –refresh failed in the backup server.
  A It is not necessary to update the dictionary map file in a backup server. (You cannot update it.)
    When you execute drmfsdisplay –refresh in a backup server, the following error occurs in Protection
    Manager.
          KAVX0006-E An error that stopped processing occurred.
              Cause = DRM-10015: An attempt to obtain RAID information failed.
 Q6 Are there any prerequisite services or software programs to use Protection Manager?
  A When tape backup is done by using an expand command, the FTP service is used. To use the FTP
    service, install FTP server in the backup server. You need write permission.
    To install Protection Manager – console, Java Runtime Environment (JRE) must be installed first.
 Q7 Is it necessary to enter FTP information in the operation definition file for an expand command?
  A To use an expand command, enter the FTP home directory and subdirectory in the operation
    definition file. If tape backup is not performed, the FTP service is not necessary. However, enter any
    directory name.
 Q8 How can a still point be established for an application that does not work together with Protection
    Manager?
  A Before executing a backup command with Protection Manager, stop the application temporarily to
    establish a still point.
    Restart the application after running a cold backup command.
 Q9 What privileges or permissions do I need to run a Protection Manager command?
  A Local administrator permissions are required.
Q10 Is a configuration having two or more LVs supported?
  A No.
    Set only one LV for one BV.
Q11 Is the backup information of Protection Manager backed up?
  A The backup information of Protection Manager is not backed up.
    If the backup information is lost, restoration cannot be done. Backup the backup information of
    Protection Manage as necessary. The backup information is located in the backup catalogue created
    in the directory to store the dictionary map file.
    When the OS startup disk is backed up by DDR in a SAN-Boot environment, the backup information
    may be restored together with the OS startup disk (if the dictionary map file is located in the OS
    startup disk). The backup information needs to be backed up in advance.
    For details on backing up the backup information, see “Backing Up a Protection Manager Operating
    Environment” in Protection Manager CLI User’s Guide.
Q12 How much of the disk is used by the directory where the dictionary map file of Protection Manager is
    stored?
  A The directory to store the dictionary map file contains the following:
         - Dictionary map file
         - Backup catalog file

     Use the following formula for calculation.

     The amount the dictionary map file uses in the disk (KB)
        = 0.2 +
          (the number of storage groups) + (the number of data files) +
          (the number of mounted drives) * 2 +
          (the number of physical disks) +
          (the number of replication volumes) * 0.2 +
          (the number of pair volumes) * 0.1

     The amount the backup catalog file uses in the disk (KB)
        = { 8.0 +
          (the number of storage groups) + ( the number of data files) +
          (the number of mounted drives ) * 2 +
          (the number of physical disks ) +
          (the number of replication volumes) * 0.2 +
          (the number of pair volumes ) * 0.2 +
          (the number of storage groups to be backed up) * 0.3 +
          (the number of data files to be backed up) * 4.0 +
          (the number of drives to be backed up) * 0.3 +
          (the number of files or directories to be backed up) * 4 +
          (the number of pair volumes to be backed up) * 0.1 } * (the number of backups performed)
Q13 The backup command timed out and ended abnormally.
  A The backup information on Protection Manager is not backed up.
    If a large amount of data is updated, waiting for replicate completion will time out, resulting in the
    following error in Protection Manager:
        KAVX5119-E The retry of the pair status confirmation has timed out.
               Wait pair status = PAIR
               RESYNC_RETRY_TIME = 360 (times)
               RESYNC_RETRY_WAIT = 1000 (10 ms)
        KAVX0006-E An error that stopped processing occurred.
               Cause = DRM-10011: A timeout error occurred.
    Refer to “Specifying a Retry Count and Retry Interval for Pair Status Retires Checking” in Protection
    Manager CLI User’s Guide and configure the retry count and the retry interval of Protection Manager.
Q14 The EX_DRM_DB_IMPORT or drmdbimport command failed and resulted in the KAVX0006-E error in
    the backup server.
  A When the EX_DRM_DB_IMPORT or drmdbimport command is executed in the backup server where
     a copy group is locked, the following error occurs in Protection Manager.

           KAVX0006-E     An error that stopped processing occurred.
                          Cause = DRM-10115: The backup data is already locked.

     A copy group is locked while; a replication volume is being mounted; command is stopped or the
     server is restarted during mounting.

     Follow the steps below to unlock the copy group.
     (1) Execute the drmcgctl command without any argument and check the status of the copy group.
     (2) If the copy group is locked, check the replication volume is mounted.
     (3) Unlock the copy group.
          <When the replication volume is mounted:>
              Unmount the replication volume by executing the EX_DRM_UMOUNT or drmumount
              command.
          <When the replication volume is not mounted:>
              Specify the –mode unlock option and execute the drmcgctl command to unlock the copy
              group.

     For details on commands, see Protection Manager Command Reference.
Q15 Can the replication volume be mounted on a folder in a backup server?
  A Yes.
    Note that if there is a chance of simultaneously executing two or more commands that mount the
    replication volume, specify a different folder for each command.
    If a mount command is executed by specifying a mounted folder, the following error occurs.

          KAVX0032-E            An invalid mount point directory was specified.

     The commands to mount the replication volume on a folder are:
        - drmmount (specify the -mount_pt option)
        - EX_DRM_MOUNT (specify the -mount_pt option)
        - EX_DRM_TAPE_BACKUP (specify the -mount_pt option)
Q16 Command execution failed in the backup server because of out of memory.
  A When the backup catalogue grows, the system runs out of memory and the following error occurs in
    command execution.

          KAVX0006-E An error that stopped processing occurred.
              Cause = DRM-10105: Memory is insufficient.

     Execute the drmtapeinit command to adjust the number of days during which the tape backup
     catalog is saved.

     For details, see “Preparation for Using Protection Manager” in the manual, Protection Manager CLI
     User’s Guide.
Q17 Which files in an Exchange Server database are backed up?
  A Data files (*.edb or *.stm) for the information store, check point files (*.chk), and transaction log files
    (*.log).
Q18 Are multiple storage groups supported?
  A Yes, they are.
    However, it is recommended to assign a physical disk to each storage group and perform backup and
    restore on a storage-group basis.
Q19 Is recovery by roll forward possible?
  A Yes.
    When using the EX_DRM_EXG_RESTORE or drmexgrestore command for restore, specify the
    -recovery option to perform roll forward recovery using the transaction log. Allocate the transaction log
    file to a different volume than the volume where data files of the information store are stored.
Q20 Is the circular logging setting effective?
  A Non-disruptive backup for Exchange database does not support circular logging.
     Check the Exchange Server setting to cancel the circular logging setting.

     When a non-disruptive backup/restore is performed with the circular logging set, the following error
     occurs in Protection Manager during restore:

          KAVX0006-E           : An error that stopped processing occurred.
                                 Cause = DRM-10434: An error occurred in VSS.

     Then, the following error is reported in the event log (application):
        --------------------------------------------
        Event type                 : Error
        Event source               : MSExchangeIS
        Event category             : Exchange VSS Writer
        Event ID                   : 9664
        Description                : Restore of the database was not permitted because circular
                                        logging has been set for the storage group XXX.
        --------------------------------------------
        Event type                 : Error
        Event source               : MSExchangeIS
        Event category             : Exchange VSS Writer
        Event ID                   : 9621
        Description                : The error code 0x80004005 was returned during an operation
                                      before restore. Check if the component mounting has been
                                      canceled.
        --------------------------------------------
Q21 How should the Exchange Server database be located?
  A The data files should be located in a physical volume different from the volume where transaction log
    files or check point files are stored.
Q22 Can transaction logs of the Exchange Server database be deleted?
  A If the -transact_log_del option is specified for backup, committed transaction log files will be deleted.
    This specification will be ignored if the circular logging is specified.
Q23 Does the dependence of cluster resources need to be set in a single copy cluster (SCC) environment
    with Exchange Server 2007?
  A The following dependence setting is required (procedure recommended by Microsoft):

         Dependence of physical disk resources on the Microsoft Exchange Database Instance resources

     Boot the cluster administrator and change Dependence of the Microsoft Exchange Database
     Instance resources. Add the physical disk resource to which the files related with the selected
     Microsoft Exchange Database Instance resource are allocated.
     Do not set the following dependence:

         Dependence of physical disk resources on the Microsoft Exchange Information Store resources
     For more information, access the following URLs:
     http://technet.microsoft.com/en-us/library/aa998607.aspx
     http://technet.microsoft.com/en-us/library/aa997696.aspx
Q24 In a single copy cluster (SCC) environment with Exchange Server 2007, the restore command for
    Exchange abnormally ended with the error of KAVX1729.
  A When the following dependence is set for resources that belong to the Exchange Server 2007 group,
    the restore command ends abnormally.

         Dependence of physical disk resources on the Microsoft Exchange Information Store resources

     Boot the cluster administrator and delete all the physical resources to be restored at Dependence
     for Exchange Information Store resources.

     For more information about how to change Dependence, access the following URL:
     http://technet.microsoft.com/en-us/library/aa997696.aspx

     If the above dependence is set, the following error will occur in Protection Manager during restore:
          KAVX1729-E: The Exchange Information Store cluster resource depends on the
          physical disk resource to be restored.
               Physical disk resource = physical disk resources to be restored
Q25 Can cold backup be performed for Exchange Server 2007?
  A The cold backup for Exchange Server 2007 is not supported. Only non-disruptive (VSS) backup is
    supported.
Q26 Are the high-availability functions of Exchange Server 2007 (SCC, CCR, LCR, and SCR) supported?
  A The supported functions are the following:
     High-availability function for Exchange Server 2007 Whether to support
     Single copy cluster (SCC)                                    S
     Cluster Continuous Replication (CCR)                         S
     Local Continuous Replication (LCR)                           N
     Standby Continuous Replication (SCR)                          S
    S: supported N: not supported
Q27 Is there any software necessary for using VSS?
  A VSS Provider needs to be installed in the application and backup servers.
Q28 What kind of configuration is necessary for a non-disruptive backup using the VSS function?
  A A backup server is necessary even if tape backup is not performed.
    The backup server changes volume attributes, which is required for non-disruptive backups using the
    VSS function.
Q29 When VSS is used, can a backup be performed across multiple generations?
  A Yes, it can.
    However, the backup server cannot simultaneously recognize multiple replication volumes that have
    been backed up non-disruptively with the VSS function. For DynamicDataReplication, shield all
    replication volumes from the backup server and make OS recognize the volumes if necessary. For
    more information, refer to Chapter 3 "Preparation for Using Protection Manager" in the manual,
    Protection Manager CLI User's Guide which describes how to make OS recognize replication volumes
    dynamically.
                               One generation Multiple generations
     DynamicDataReplication            -                Shield
     DynamicSnapVolume                 -                      -

     Shield : Shielding replication volumes is required
          - : Shielding replication volumes is not required
Q30 Why replication volumes should be shielded when VSS is used?
  A When a non-disruptive backup is performed using the VSS function, the disk signature for replication
    volumes becomes identical with the signature for application volumes.
    In a configuration with multiple generations, multiple disks having the same signature may be
    recognized by the backup server at the same time. In such case, the OS changes the disk signature
    (*).
    The change of a disk signature may affect the system operation. Shield replication volumes to prevent
    the backup server from recognizing multiple disks having the same signature.

            When a signature is changed, an alarm such as the following may appear in the event log
        *
            (system):
            Event type    : Warning
            Event source : PartMgr
            Event ID      : 58
            Description     The signature of disk 22 is being changed because it is the
                          : same as disk 18.

Q31 When VSS is used in a DynamicSnapVolume configuration, can tape restore be performed for the BV
    (base volume)?
  A When tape restore is performed for backup data using the VSS function in a DynamicSnapVolume
     configuration, the restore cannot be performed directory in the application volume by linking the base
     volume (BV) and the link volume (LV). Edit NEC Storage disk array subsystem operation
     configuration file (NEC.dat) to link the snapshot volume (SV) and the LV, enabling tape restore in the
     SV.
     NEC Storage disk array subsystem operation configuration file(NEC.dat) is store in the following:
            Destination of Protection Manager installation: ¥conf¥raid¥NEC.dat
            Specify tape_restore_dest = sv.
Q32 When the SV was mounted (linked) in the backup server in a DynamicSnapVolume configuration, a
    non-disruptive backup using the VSS ended abnormally with the error of KAVX0006-E or
    KAVX5023-E.
  A To perform a non-disruptive backup using the VSS, the SV in the backup destination and SVs in
    other than the backup destination need to be unmounted from (not linked with) the backup server.
    Unmount the SV which is being mounted in the backup server and then reexecute the backup.
Q33 When a non-disruptive backup using the VSS function was performed, an alarm message appeared in
    the event log in the backup server.
  A When PathManager is installed, the following alarm may appear in the event log (system):


            Event type         :   Warning
            Event source       :   spsdsm
            Event ID           :   530
            Description        :   A path is lost.



     Take the following procedure to change an alarm message to an information message:
      (1) Boot the command prompt in the backup server.
      (2) Execute the following command:
              PROMPT > spscmd -seteventmode 1
     Then take the following procedure to set the failback mode to active:
      (1) Boot the command prompt in the backup server.
      (2) Execute the following command:
              PROMPT > spscmd -setfbmode a
Q34 When a non-disruptive backup was performed using the VSS function on Windows Server 2003, an
    alarm message appeared in the event log in the application server.
  A
     When a backup is performed using VSS, the following alarm message may appear in the event log
     in the application server:

     <Application event log>
     Event type: Warning
     Event source: EventSystem
     Event ID: 4354
     Description: The COM + event system has failed to start with the RequestWriterInfo
                  method in the subscription {1ACBFF9B-00D7-4546-9608-73DDBC995F4C}
                  -{00000000-0000-0000-0000-000000000000}
                  -{00000000-0000-0000-0000-000000000000}.
                  The subscriber has returned HRESULT 80010105.

     This alarm message is logged when a problem occurs in the COM+ component related to the VSS
     writer.
     The problem may be solved by re-registering the registry information in accordance with the
     following open information:
     http://support.microsoft.com/kb/940184
Q35 When a non-disruptive backup was performed using the VSS function on Windows Server 2008, an
    error message appeared in the event log in the backup server.
  A If a volume in Not Ready or Not Available state exists in the backup server and a backup is
    performed using VSS, the following error may appear in the event log in the backup server.

                                 <System event log>
                                 Event type             :   Error
                                 Event source           :   Virtual Disk Service
                                 Event ID               :   1
                                 Description            :   An unexpected error occurred.
                                                            Error code: 13@02000018

                                 <Application event log>
                                 Event type             :   Error
                                 Event source           :   VSS
                                 Event ID               :   12289
                                 Description            :   Volume shadow copy service error
                                                            Unexpected error
                                                            IOCTL_DISK_GET_DRIVE_LAYOUT_EX

     This error does not affect the system operation.
Q36 When a non-disruptive backup was performed using the VSS function, an information message with
    the event ID 11770 appeared in the event log (application) in the backup server.
  A Due to the iSM host agent service function of ControlCommand Ver5.1 or later, the following
     message may appear in an event log (application). It does not affect non-disruptive backups using
     the VSS function.

         Event type          :   Information
         Event source        :   iSMcc_hostinfo
         Event ID            :   11770
         Description         :   iSM11770: Host Information was exported successfully.


     If iSM host agent service does not need to automatically collect and register the host information, the
     system can be operated with iSM host agent service stopped.
     To prevent the iSM host agent service from automatically booting during system reboot, click Start,
     All Programs, Administrative Tools, and click NEC Storage Manager Host Agent to change the
     start-up type from Automatic to Manual.
Q37 When a non-disruptive backup was performed using the VSS function, an information message with
    the event ID 3224 appeared in the event log (application) in the backup server.
  A When a non-disruptive backup is performed using the VSS function, the following error message
     may appear in the event log in the backup server:

     <Application event log>
     Event type: Error
     Event source: NEC StorageManager
     Event ID: 3224
     Description: iSM : 0000001880 Err iSMagcomma iSM03224:Control path is blockaded.

     This error has occurred because the disk that NEC StorageManager uses for monitoring with FC
     connection is the replication volume for non-disruptive backups using the VSS function.

     If only this error appears, the error message can be ignored because monitoring has already been
     switched to other LD.
     Change the way NEC StorageManager monitors disk arrays to one of the following to prevent this
     error:
         - Monitoring with IP connection
         - For monitoring with FC connection, specifying the number of a disk that is not the replication
           volume for non-disruptive backups using the VSS function.
Q38 Do active services need to be stopped for using the VSS?
  A Active services do not need to be stopped.
Q39 A non-disruptive backup for the Exchange Server database took long time or ended abnormally due to
    timeout.
  A Perform non-disruptive backup when the Exchange Server database has a low workload, especially
    when the online optimization of the Exchange Server database and the backup scheduling are not
    performed simultaneously.
    For information about the online optimization of the Exchange Server database, access the following
    URL:
    http://support.microsoft.com/default.aspx?scid=kb;ja;328804
Q40 Which cluster software is supported?
  A The following cluster software is supported:
     Windows : MSCS
                    MSFC
                    EXPRESSCLUSTER X
Q41 Do dictionary maps need to be shared between nodes in a cluster system?
  A Yes, they do.
    Refer to Chapter 3 "Preparation for Using Protection Manager" in the manual, Protection Manager CLI
    User's Guide to allocate dictionary map files on the shared disk.
Q42 Is setting by using the drmclusinit command necessary for using Protection Manager for Microsoft(R)
    Exchange Server in an MSCS/MSFC environment?
  A No, it is not.
     The system automatically recognizes the MSCS/MSFC environment and acts according to the
     environment. If the command is executed, delete the following related files:
        - (Installation directory)¥conf¥cluster¥DEFAULT.dat
        - (Installation directory)¥conf¥cluster¥MSCS.dat
Q43 Can lowercase characters be used for virtual server names handled by Protection Manager?
  A Virtual server names are case-sensitive in the command/definition files of Protection Manager.
    Use uppercase characters for all the virtual server names to be set in the command/definition files of
    Protection Manager.
    While virtual computer names in EXPRESSCLUSTER X are all lowercase characters when Protection
    Manager is associated with EXPRESSCLUSTER X, use uppercase characters for all the
    command/definition files of Protection Manager.
Q44 Is the mirror disk system of EXPRESSCLUSTER X supported?
  A No, it is not.
Q45 Does any action need to be taken for the disk RW monitoring of EXPRESSCLUSTER X?
  A If the disk RW monitoring is used for monitoring disks to be backed up, stop the monitor resource of
    the disk RW monitoring temporarily before performing a cold backup/restore.
Q46 Which backup software is supported?
  A The following backup software is supported:
        - NetBackup
        - Backup Exec
        - ARCserve Backup
Q47 Is a differential tape backup possible?
  A The backup software needs to support time-based differential backup.
      Whether to associate with Protection Manager depends on the backup software.
        - NetBackup         : Supports time-based differential backup and backup associated with
                               Protection Manager.
        - Backup Exec : Supports time-based differential backup and backup associated with
                               Protection Manager.
        - ARCserve        :   Does not support time-based differential backup.
          Backup
Q48 What should be entered in the DOS Prompt (command prompt) shown by executing the tape-restore
    command?
  A GUI operations are required for restore to be performed when ARCserve and Backup Exec that are
    supported by Windows are selected. After the GUI operations are complete, respond to the message
    shown by executing the restore command.
     For ARCserve, enter one of the following:
       YES         : Enter this when the GUI restore operation has normally ended.
       CAN         : Enter this to interrupt the GUI restore operation.
       ERR         : Enter this when the GUI restore operation has abnormally ended.
     For Backup Exec, enter one of the following:
       YES         : Enter this when the GUI restore operation has normally ended.
       CANCEL : Enter this to interrupt the GUI restore operation.
       NO          : Enter this when the GUI restore operation has abnormally ended.
    To register the tape-restore command with job scheduling software for operation, select NetBackup.
Q49 Can differential tape backup be performed for database files?
  A Differential tape backup based on date and time may not be performed for database files that are
    open 24 hours, because the update date is not changed for these files.
    Select full backup for tape backup of database files.
Q50 Backup Exec stalled and a tape-backup command did not end.
  A For Backup Exec, do not specify the RUN_IMMEDIATE parameter for the Schedule section in the
    backup job script file.
Q51 A tape-backup command using ARCserve ended abnormally.
  A Check if the user who has executed the command is authorized as the primary user of ARCserve
     (caroot). It can be checked by using the C:¥Program Files¥CA¥BrightStor ARCserve
     Backup¥ca_auth command.
          ca_auth -equiv getequiv User name Host name
               Example> ca_auth -equiv getequiv Administrator SV003
     If "reason: No equivalence exists for this user/host pair" appears as the execution
     result, execute the following command to authorize the user:
          ca_auth -equiv add User name Machine name Password of BrightStorUser
          caroot_username caroot
               Example> ca_auth -equiv add Administrator SV003 caroot caroot password


Q52 When a tape backup was performed using NetBackup, unnecessary folders were also backed up.
  A Check the setting of the NetBackup policy.
    When Backup Selections is set for the policy specified in NBU.dat, Protection Manager backs up
    data specified in Backup Selections as well as the data that is supposed to be backed up in a tape.
    Do not specify Backup Selections.
Q53 When the backup of a volume which has been mounted in a folder using NetBackup was attempted,
    the data was not backed up.
  A A necessary NetBackup policy setting has not been made.
    Select the Cross mount points check box for the policy specified in NBU.dat.
Q54 A differential backup could not be performed for a volume that has been mounted in a folder using
    NetBackup or Backup Exec.
  A NetBackup or Backup Exec does not support differential backup for a volume mounted in a folder.
Q55 Can Protection Manager be associated with the FlashBackup function of NetBackup?
  A To use the FlashBackup function, perform a tape backup in other way than Protection Manager.
Q56 Can the tape backup setting be made for each day of the week?
  A Yes, it can.
    Use the -bup_env option of the EX_DRM_TAPE_BACKUP command to specify definition files
    including settings specified for each day of the week.
    For more information, refer to "Creating a Configuration Definition File for Tape Backup" in Protection
    Manager CLI User's Guide.
Q57 What kind of Java Runtime Environment is necessary for using the Protection Manager console?
  A The following Java Runtime Environment is necessary:
       - Java Runtime Environment (JRE) version 1.4.2 or later (32 bit)
     Download and install Java Runtime Environment from the webpage of Sun Microsystems, Inc.
Q58 Does Protection Manager support Exchange Server 2010?
  A No, it doesn’t.

				
DOCUMENT INFO
Shared By:
Categories:
Tags:
Stats:
views:415
posted:8/27/2011
language:English
pages:242