upgrade sanmelody 2.0.2 2.0.4

SANmelody™ Upgrade Guide Upgrading from SANmelody 2.0 PSP2 to PSP4 November 2, 2009

Applicable to:

SANmelody 2.0 PSP2 No Update, PSP2 Update 1 or PSP2 Update 2

SANmelody Upgrade Guide Cumulative Change Summary Date

Republished and reformatted with new steps to include moving to PSP4 Update 1 during the PSP3 upgrade process. Minor changes to copyright notice. February 4, 2009

Made some minor typographical corrections, added procedure to section called “Considerations for Partnered SANmelody configurations” for customers using 4GB, direct-connected Emulex HBAs, also included Important Notes throughout the procedure referencing this section.

February 27, 2009

Minor revisions for clarification. March 19, 2009

Added note requesting support bundles prior to upgrade March 20, 2009

Note added that support bundles only needed for partnered SANmelody servers March 26, 2009

Added note requesting time differences of SANmelody servers if support bundles submitted April 21, 2009

Updated the guide to include upgrading to SANmelody 2.0 PSP4 Update 2 April 30, 2009

Removed contradicting reference in “Pre-Installation Notes” section about not manually stop/starting services when the procedure itself states it. Removed page 12 entirely as this was unnecessary to check the application servers until PSP4 Update 2 had been installed. Also added note about what DcsLeaveregion.exe does.

May 21, 2009

Re-applied the changes that occurred on April 30, 2009, but were removed by mistake. May 26, 2009

Corrected the name of executable files that should have been updated when the last update was released. June 2, 2009

Updated the guide to include upgrading to SANmelody 2.0 PSP4 Update 3 August 5, 2009

Updated the guide to include upgrading to SANmelody 2.0 PSP4 Update 4 September 16, 2009

Revised the guide to include upgrading to SANmelody 2.0 PSP4 (no update) first before upgrading to the latest version of SANmelody 2.0.4.x. October 28, 2009

Revised the guide to emphasize the differences in the upgrade procedure for partnered configurations. November 2, 2009

DataCore SANmelody Upgrade Guide (from 2.0.2 to 2.0.4.x)

2

COPYRIGHT

Copyright © 2008 - 2009 by DataCore Software Corporation. All rights reserved.

DataCore, the DataCore logo, SANsymphony, and SANmelody are trademarks of DataCore Software Corporation. Other DataCore product or service names or logos referenced herein are trademarks of DataCore Software Corporation. All other products, services and company names mentioned herein may be trademarks of their respective owners.

ALTHOUGH THE MATERIAL PRESENTED IN THIS DOCUMENT IS BELIEVED TO BE ACCURATE, IT IS PROVIDED “AS IS” AND USERS MUST TAKE ALL RESPONSIBILITY FOR THE USE OR APPLICATION OF THE PRODUCTS DESCRIBED AND THE INFORMATION CONTAINED IN THIS DOCUMENT. NEITHER DATACORE NOR ITS SUPPLIERS MAKE ANY EXPRESS OR IMPLIED REPRESENTATION, WARRANTY OR ENDORSEMENT REGARDING, AND SHALL HAVE NO LIABILITY FOR, THE USE OR APPLICATION OF ANY DATACORE OR THIRD PARTY PRODUCTS OR THE OTHER INFORMATION REFERRED TO IN THIS DOCUMENT. ALL SUCH WARRANTIES (INCLUDING ANY IMPLIED WARRANTIES OF MERCHANTABILITY, NON-INFRINGEMENT, FITNESS FOR A PARTICULAR PURPOSE AND AGAINST HIDDEN DEFECTS) AND LIABILITY ARE HEREBY DISCLAIMED TO THE FULLEST EXTENT PERMITTED BY LAW.

No part of this document may be copied, reproduced, translated or reduced to any electronic medium or machine-readable form without the prior written consent of DataCore Software Corporation

Table of Contents Notes on Technical Support and System Requirements ............................................................. 1 Pre-Installation Notes ............................................................................................................... 2

Before Beginning your Upgrade:.......................................................................................... 2 Considerations for Standalone SANmelody Configurations................................................... 2 Considerations for Partnered SANmelody Configurations ..................................................... 3 Considerations for Snapshot ............................................................................................... 4 Considerations for AIM ....................................................................................................... 4

Overview of the Upgrade Procedure.......................................................................................... 5 Obtaining Executable Files for the Upgrade .............................................................................. 5 The Upgrade Procedure ........................................................................................................... 6

Upgrading Server1.............................................................................................................. 6 After Upgrading Server1 in a Partnered Configuration.......................................................... 8 Verifying Application Server Access after Upgrade to PSP4 (no update) .............................. 9 Continuing the Upgrade on Server2................................................................................... 10 Re-establishing the Partnership ........................................................................................ 11 Completing the Upgrade on Server2 to PSP4 (no update) .................................................. 12 Verifying Application Server Access after Server2 Upgrade to PSP4 (no update)................ 13


1

Notes on Technical Support and System Requirements

For answers to technical questions regarding SANmelody, visit our Web site at www.datacore.com, or our knowledgebase at SANmelody Technical Support (http://www.datacore.com/support/support_home.asp). If you do not find your answer there, email your specific question to [email protected].

Registered customers with a valid premium support plan may use our Web support, phone or email for personal assistance. If you have a support plan, you must register at http://www.datacore.com/index_frame.asp?frame_subnav_content=2 before requesting personal assistance.

DataCore Software offers support plans and personal assistance for its products for a nominal fee. To learn about support policies and plans and purchase a support plan, visit our Web site or contact your DataCore Sales representative for more information.

DataCore Technical Support shall be limited to products manufactured by DataCore Software. Technical support of products other than those manufactured by DataCore shall be the sole responsibility of the end-user or installer. Installation of non-qualified software or hardware (please reference our Technical Support Web site referenced above for the most current list) is at the sole risk of the end-user or installer.

For the current system requirements for SANmelody storage servers, please visit our Web site, http://www.datacore.com/products/prod_SANmel_prerequisites.asp.


2

Pre-Installation Notes This section provides information about upgrading SANmelody software to PSP3 or greater. Read the following upgrade. You cannot directly upgrade to SANmelody 2.0 PSP4 Update 4, but the following procedure details at what point you should install the latest version on each storage server so that you can finish the upgrade with your storage servers the latest PSP4 update.

Before Beginning your Upgrade:

• Before scheduling any upgrades for partnered SANmelody configurations only, customers must open an incident with the subject of SANmelody Upgrade Check Request and provide support bundles from both storage servers. NOTE: This does not affect standalone SANmelody servers (single node installations). Please indicate time difference of the SANmelody servers if the times are not in synchronization.

If you do not know how to make a support bundle please see: How to: Collect information to send to Customer Support http://sanmelody.custhelp.com/cgi-bin/sanmelody.cfg/php/enduser/std_adp.php?p_faqid=699

The specific issue is:

A failed mirrored virtual volume could be marked healthy without the expected recovery, if the storage server was stopped or the server rebooted and then while the mirrored virtual volume had been waiting to recover (but not yet started), the storage server was stopped or rebooted again.

While we will do our best to check your configuration as quickly as we can, we recommend that you do not schedule any dates until we have done our analysis.

Important Note: If you do not submit the support bundles before you upgrade and wait for the approval of DataCore Support to proceed then DataCore Software takes no responsibility for any problems with your data caused by the above issue.

• The upgrade is only for the existing license. If you have been given a new license (because you have added features), you have to upgrade the license first in SANmelody 2.0 PSP2.

• SANmelody licenses must be activated before upgrading.

• No configuration changes can be made during the entire upgrade process and ensure that all virtual volumes are healthy and up.

• This procedure is only supported on storage servers that have SANmelody 2.0 PSP2, 2.0 PSP2 Update 1 or PSP2 Update 2. Earlier versions of SANmelody must be upgraded to at least 2.0 PSP2 before you begin.

• If any DataCore services have been set to Manual previously, they should be reset to Automatic before the upgrade begins to ensure that the procedure below is followed correctly.

• For partnered configurations, both partners must be upgraded during this procedure. You cannot safely run on partnered configurations running on a mix of storage servers at PSP2 and PSP3 (or later) for any period of time without risking access to your data. Standalone configurations that are part of an Asynchronous IP Mirroring (AIM) source and destination pair may be upgraded at different times (see the “Considerations for AIM” section on page 4 for more details).

• Create an Emergency Repair Disk – refer to the SANmelody Help on how to do this.

Considerations for Standalone SANmelody Configurations

• Application servers will need to be shutdown during the upgrade process as all virtual volumes will be inaccessible.

• Application servers using the DataCore MPIO for Windows software must be at version 2.4 or later, and application servers using DataCore Alternate Pathing software must be at version 2.3. Upgrade any application servers to the minimum level and ensure all access to virtual volumes before starting this procedure. Check the relevant release notes for these products on how to upgrade if required.

• Existing NMV pools that had been previously converted to Do Not Erase will start reclamation of any previously unallocated storage allocation units (SAUs) once the upgraded software is


3

restarted. Also note that after the upgrade, all NMV pools will no longer be recognized on storage servers with earlier versions of SANmelody.

Considerations for Partnered SANmelody Configurations

• Upgrade one storage server at a time only.

• Keep the first storage server that is being upgraded in Read/Write mode during the procedure.

• To ensure High Availability (HA) for application servers using multi-path mirrors, all mirrored virtual volumes must be healthy before you begin.

• Application servers using linear or standard mirror virtual volumes will need to be shutdown when the primary storage server is upgraded, as these virtual volumes will not be accessible while the primary storage server is shutdown, restarting or waiting for the SANmelody software to start.

• Application servers using the DataCore MPIO for Windows software must be at version 2.4 or later, and application servers using DataCore Alternate Pathing software must be at version 2.3. Upgrade any application servers to the minimum level and ensure all access to virtual volumes before starting this procedure. Check the relevant release notes for these products on how to upgrade if required.

• If using any Windows protected file system volumes (a DataCore volume that preserves a pre-existing Windows file system and data on a physical disk) as secondary volumes in mirror, please note: The Windows protected file system volume must be either (1) split into a linear virtual volume or (2) replaced with another DataCore volume (partition-based or NMV) and the mirror should be fully synchronized.

• Existing NMV pools that had been previously converted to Do Not Erase will start reclamation of any previously unallocated storage allocation units (SAUs) once the upgraded software is restarted. Also note that after the upgrade, all NMV pools will no longer be recognized on storage servers with earlier versions of SANmelody.

• If you are using direct-connected 4GB, Emulex HBAs between the storage servers for mirroring, you will need to perform some additional steps during the “Upgrade Procedure” (see page 6) on Server1 only. This is to avoid a potential hang of the installer during the first part of the upgrade when running the SANmelody 2.0 PSP3 executable file:

1. After step 2 of the “The Upgrade Procedure” but before step 3, manually stop the DataCore Start Service from the Services Console. This will stop the storage server software completely and all volumes configured on this storage server node from being presented to application servers.

2. Next on Server1, physically remove the cables from the HBAs used for these mirror connections to Server2.

3. On Server2, use the SANmelody Fibre Channel Manager snap-in to check that the connections have been removed correctly. Locate the corresponding mirror channels on Server2 in the snap-in and click each of them one at a time. In the right pane, the WWNs for the mirror connections on Server1 that you have just disconnected, should have a status of Not Present and show a red X.

4. Once all mirror connections have been removed, proceed to step 3 of the “The Upgrade Procedure” and follow the instructions through step 15.

5. After step 15 of the “Upgrade Procedure” but before step 16, reconnect the cables to Server1 and proceed to step 16.

6. Do not open any SANmelody snap-ins on either storage server at this point, just continue the upgrade procedure until you get to the section “After Upgrading Server1 in a Partnered Configuration” on page 8.

7. After step 2 of the “After Upgrading Server1 in a Partnered Configuration,” but before step 3, on Server2 use the SANmelody Fibre Channel Manager snap-in to check that the mirror connections are now re-established. Locate the corresponding mirror channels on Server2 in the snap-in and click on each of them one at a time. In the right pane, the WWNs for the mirror connections on Server1 that you have just disconnected, should have a status of Logged In and show a green check mark.


4

Considerations for Snapshot • Since SANmelody 2.0 PSP3, snapshot uses a single mapstore to preserve data for all snapshot

relationships. All relationships will automatically use this mapstore if it exists.

• Mapstore behavior has changed since SANmelody 2.0 PSP3, so after upgrading, any “enabled” snapshot relationships will be disabled and will have to be re-enabled after upgrading. Therefore, if you need to preserve the point-in-time copies of your enabled relationships, you must perform a Complete Image on the snapshot sets before upgrading your storage servers.

• Since SANmelody 2.0 PSP3, the Enable command has the same function as the EnableNew command did in version 2.0 PSP2. The EnableNew command has been deprecated in later releases and is only maintained for backward compatibility.

Considerations for AIM • It is recommended that you upgrade any standalone AIM destination storage servers first. If you

plan to upgrade any standalone AIM destination storage server at a later date after upgrading the AIM source server, please contact DataCore Customer Support as some extra configuration may be needed on the AIM destination server using earlier versions of SANmelody.

• If your AIM destination storage server is also partnered, you must consider that you will need to upgrade both the AIM destination storage server and its partner as you would any normal SANmelody partnered configuration.

• AIM data transfers and initialization of AIM sets will be stopped during the upgrade process. After all storage servers are upgraded, AIM data transfers will resume.

Important Note: If AIM sets have been previously set to use Asynchronous Replication Mode on the AIM destination server, you must re-initialize all your AIM sets after you have completed the upgrade on both the source and destination servers.

• The upgrade may not keep some customized AIM settings for the storage server. After upgrading, check any customized settings as it may be necessary to reset them.


5

Overview of the Upgrade Procedure For the purposes of this procedure, ‘Server1’ is the first storage server being upgraded and ‘Server2’ is the second. Non-partnered AIM destination storage servers should be treated as standalone storage servers. Partnered storage servers are storage servers that share the same configuration or are synchronously mirroring volumes between them. Storage server configurations where one storage server is an AIM source server and another is an AIM destination server are not considered partnered; although an AIM source server or AIM destination server can be partnered with another storage server that is not part of the AIM configuration.

For partnered configurations, the upgrade procedure can be broken down into six parts:

1. Installation/Upgrade to SANmelody 2.0 PSP3 and then apply SANmelody 2.0 PSP4 (no update) on Server1.

2. For partnered SANmelody configurations, performing the steps in “After Upgrading Server1 in a Partnered Configuration” on page 8 to finalize the process for Server1 and start SANmelody.

3. Installing SANmelody 2.0 PSP3 on Server2. 4. For partnered SANmelody configurations, performing steps in “Re-establishing the Partnership” on

page 11 to re-partner the newly installed SANmelody 2.0 PSP3 storage servers. 5. After partnering the storage servers, you will then apply PSP4 (no update) on Server2. 6. Then apply the latest update for PSP4 on each storage server in turn to upgrade them to the latest

version of SANmelody 2.0.4.x. Use the installation instructions that come with the latest update. For standalone configurations, the upgrade procedure is simply to upgrade to SANmelody 2.0 PSP3 and then apply SANmelody 2.0 PSP4 Update 4 on Server1. The upgrade will be complete at this point; performing the “post upgrade” steps for Server1 re-establishing the storage server partnership does not apply for standalone configurations.

Note: Standalone configurations using AIM destinations are considered as two separate standalone configurations.

Follow the upgrade steps exactly as they appear.

Obtaining Executable Files for the Upgrade The SANmelody 2.0 PSP3 executable file can be obtained directly from:

ftp://support.datacore.com/psp/2.0.0/SANmelody2.0PSP3.exe

This executable file should be copied to all storage servers that are to be upgraded and run locally when instructed.

The latest SANmelody 2.0 Release Notes from here:

ftp://support.datacore.com/psp/2.0.0/RelNotesSMY2.0.4update4.pdf

Part of the upgrade procedure requires that an additional executable file be downloaded and run on Server2 only, during the procedure.

Please download the DcsLeaveRegion.exe file from here:

ftp://support.datacore.com/psp/2.0.0/DcsLeaveRegion.exe

Very Important Note: This executable file is only used during the upgrade process for partnered SANmelody configurations and only to be run locally on Server2 when instructed to do so.

The executable removes Server2 from the partnership in such a way that prevents unnecessary full recoveries from taking place on both Storage Servers. This is unique to this upgrade procedure and should not be used in any other situation (for example when replacing storage server hardware which would require a reinstallation of the Storage Server software).

Do not run this on Server1 (either in a partnered or standalone configuration) or at a time in the procedure when you are not instructed, you risk losing your configuration entirely.

The SANmelody 2.0 PSP4 (no update) executable file can be obtained directly from:

ftp://support.datacore.com/psp/2.0.0/SANmelody2.0PSP4.exe

This executable file should be copied to all storage servers that are to be upgraded and run locally when instructed.

Very Important Note: Only run the PSP4 (no update) executable file when instructed to do so. Do not use the PSP4 (no update) executable file instead of PSP3; otherwise your upgrade will fail.


6

The Upgrade Procedure Upgrading Server1

1. On Server1, log on to Windows as using a local administrator account.

2. In Computer Management, open the Services and Applications snap-in and select Services in the console tree. In the right pane, double-click DataCore Start Service and change the Startup type to Manual. Click OK and close Computer Management.

Very Important Note: If you are using 4GB, Emulex HBAs in a direct-connection configuration for mirror paths between storage server partners, then please do not continue the procedure until you have read the “Considerations for Partnered SANmelody Configurations” section on page 3 relating to this.

3. Double-click on the SANmelody2.0PSP3.exe. The SANmelody splash will be displayed followed by the DataCore Installshield Wizard dialog boxes. Click Next to continue with the installation.

4. You will see a message that all DataCore windows will be closed that DataCore Software services will be stopped and that disks presented by this disk server will be disabled before continuing with the installation. Please ensure that all DataCore windows in all sessions are closed and all other applications are closed. Click Yes to continue with the installation. Wait for the services to be stopped and then click then at the Welcome window, click Next.

5. On the License Agreement window, click Yes to accept the terms of the agreement.

6. The SANmelody installation and upgrade begins. During this time, you may have to respond to different messages or wizards to successfully complete the installation process, including:

• Microsoft Security Alert messages for DataCore driver installations; select Yes to install.

• The Found New Hardware Wizard may appear during the loading of the DataCore iSCSI Target Driver. Click Next, Yes, or Finish as appropriate to configure your hardware during this part of the upgrade.

Important Note: If you see any other Microsoft Windows message asking you if you want to restart your system for ‘…settings to take effect’, choose No.

7. When the installation has completed you will see the SANmelody Maintenance Complete window informing you to restart your computer. Ensure that the Yes radio button is selected and click Finish to restart the storage server.

8. Wait for Server1 to restart and log on to the storage server with the same account used to run the upgrade (in step 1) above. This will complete the installation of the upgraded drivers for PSP3 on the storage server. Please be patient, as it may take some time for your system settings to update with the new information.

9. Once this process has completed and you are able to access the desktop of Server1, do not open any SANmelody GUIs at this point. Double-click on the SANmelody2.0PSP4.exe to continue the upgrade of Server1 from PSP3 to PSP4 (no update).

10. The SANmelody splash will be displayed followed by the DataCore Installshield Wizard dialog boxes. Click Next to continue with the installation. Then click Next again to begin.

11. You will receive a message informing you that DataCore Software Services will be stopped and asking if you wish you to continue. Click Yes. The DataCore services will be stopped and the upgrade will start.




Important Note: If you see any other Microsoft Windows message asking you if you want to restart your system for ‘…settings to take effect’, choose No.

13. When the installation has completed, you will see the SANmelody Maintenance Complete window informing you to restart your computer. Ensure that the Yes radio button is selected and click Finish to restart the storage server.


7

14. Wait for Server1 to restart and log on to the storage server with the same account used to run the upgrade (in step 1) above. This will complete the installation of the upgraded drivers for PSP4 (no update) on the storage server. Please be patient, as it may take some time for your system settings to update with the new information.

15. Still on Server1, do not open any SANmelody GUIs at this point, but from the Start>Run menu, open Services.msc. Find the DataCore Start Service and reset this service from Manual (as was configured in step 2 above) to Automatic. Click OK and close the Services snap-in.

Very Important Note: This is the point where all 4GB, direct-connected Emulex mirror connections should be reconnected. Please read the “Considerations for Partnered SANmelody Configurations” section on page 3.

16. Restart Server1 again. This extra restart is required to prevent known issues in certain cases during the PSP3 to PSP4 (no update), where some DataCore drivers may not be correctly unloaded and the new updated drivers may not be correctly reloaded during the first restart.

17. Wait for Server1 to restart and log on to Server1 using the same account as before. Do not open the SANmelody snap-in at this point. From the Start>Run menu, open Services.msc. Find the DataCore Start Service and ensure this service is Started.

Note: If this service has not started, manually start it from the Windows Services snap-in – do not use any SANmelody GUIs at this point. Wait for the service to have the status Started, then click OK and close the Services snap-in.

18. The software upgrade of Server1 is now complete.

Very Important Note:

For partnered configurations, do not open any SANmelody GUIs, until specifically instructed to do so. Continue to the next section “After Upgrading Server1 in a Partnered Configuration.”

For standalone SANmelody configurations, the upgrade process for the storage server is almost complete. Open the SANmelody GUI and re-apply the configuration in the normal manner to finish the upgrade. Restart all application servers to access the virtual volumes.


8

After Upgrading Server1 in a Partnered Configuration This section is for partnered configurations only and does not apply to standalone configurations.

1. Do not open any SANmelody GUIs on Server1 until specifically instructed to do so. Log on to Server2 (still on SANmelody 2.0 PSP2) using the same local administrator account that you used when upgrading Server1.

2. On Server2, open the SANmelody Storage Server snap-in to check the health of all mirrored volumes. When all mirrors have recovered, the volume Status field will to display Up. See the screenshot below.

Very Important Note: This is the point where all 4GB, direct-connected Emulex mirror connections previously removed and reconnected on Server1, should be checked on Server2, do not open any GUIs on Server1 at this point. Please read the “Considerations for Partnered SANmelody Configurations” section on page 3.

.

Very Important Note: Server1 is shown as Unreachable in the Partner field on Server2 at this time (see the screenshot above). This is expected and should be ignored. Do not proceed to the next step until all mirrored volumes have a status of Up on the Server2 GUI, do not open any GUIs on Server1 at this point. Please be patient at this point. Recoveries will only be logged, not full recoveries, but they may still require time to complete.

3. When all volumes on Server2 have the status of Up, log on to Server1 with the same account as before. Open the SANmelody snap-in and select Storage Server.

Very Important Note: Server2 is missing from the Partner field (see the screenshot below). This is expected and should be ignored. (Unlike the screenshot though, at this point, volumes will have a status of N/A. This too is expected.)

4. On Server1, perform an Apply and wait for the GUI to confirm the Apply has completed and click

OK. The volume status for all volumes on Server1 will now have a status of Up (see screenshot above). The configuration upgrade for Server1 is now complete. Close all SANmelody GUIs on Server1 and continue to the next section.


9

Verifying Application Server Access after Upgrade to PSP4 (no update) Before continuing the upgrade of Server2, it is important to check each application server to ensure full access to any HA virtual volumes. During the upgrade of Server1, access to any virtual volumes on this storage server would have been lost. Only when the apply was completed in step 4 of the previous section, would the access to the virtual volumes have been re-established from Server1.

For Application Servers running DataCore Alternate Pathing for Windows software:

1. On the application server, open Computer Management and select Device Manager.

2. In the right pane, select Disk Drives, and select Scan for Hardware Changes from the context menu.

Respond to any prompts related to new hardware. If you see a message asking you to restart, click No. Do not restart at this time.

3. In Computer Management, expand the DataCore SANmelody folder, select DataCore Alternate Pathing Monitor, and choose Refresh from the context menu to view updated volume and channel status.

4. Check that all volume and channel status indicators are green. Refresh as needed. If necessary, refer to the DataCore AP Help for more information.

For Application Servers running DataCore MPIO for Windows:


2. In the right pane, select Disk Drives, and select Scan for Hardware Changes from the context menu. There should a DataCore SCSI Disk device for each path on the application server to each storage server, but only one DataCore Multipath Disk device for each mirrored virtual volume.


3. In Computer Management, expand the DataCore SANmelody folder, select MPIO Management, and choose Refresh from the context menu to view updated volume and path status.

4. Check that your disks show up under Volumes and that all paths and storage servers are displayed and are either active or passive. Refresh the MPIO GUI if needed. Refer to the DataCore MPIO Help for more information.

For Application Servers using non-DataCore High Available software:

See your software vendor’s documentation on how to determine the health and access of a volume and its available paths.


10

Continuing the Upgrade on Server2 1. On Server2, from Computer Management, open the Services and Applications snap-in and

select Services in the console tree. In the right pane, double-click DataCore Start Service and change the Startup type to Manual. Click OK and close Computer Management.

2. Double-click on the SANmelody2.0PSP3.exe. The SANmelody splash will be displayed followed by the DataCore Installshield Wizard dialog boxes. Click Next to continue with the installation.

3. You will see a message that all DataCore windows will be closed that DataCore Software services will be stopped and that disks presented by this disk server will be disabled before continuing with the installation. Please ensure that all DataCore windows in all sessions are closed and all other applications are closed. Click Yes to continue with the installation. Wait for the services to be stopped and then click then at the Welcome window, click Next.

4. On the License Agreement window, click Yes to accept the terms of the agreement.




Important Note: If you see any other Microsoft Window message asking you if you want to restart your system for ‘…settings to take effect’, choose No.

6. When the installation has completed you will see the SANmelody Maintenance Complete window informing you must restart your computer. Ensure that the Yes radio button is selected and click Finish to restart the storage server.

7. Wait for Server2 to restart and log on to the storage server with the same account used to run the upgrade above. This will complete the installation of the upgraded drivers for PSP3 on the storage server. Please be patient, as it may take some time for your system settings to update with the new information.

8. Once the Server2 desktop appears, do not open any SANmelody snap-ins, but from the Start>Run menu open Services.msc. Find the DataCore Start Service and reset this service from Manual (as was configured in step 1 above) to Automatic. Click OK and close the Services snap-in.

9. Restart Server2 again. This extra restart is required to prevent known issues in certain cases during the PSP3 to PSP4 (no update), where some DataCore drivers may not be correctly unloaded and the new updated drivers may not be correctly reloaded during the first restart.

10. Wait for Server2 to restart and log on to Server1 using the same account as before. Do not open any SANmelody snap-ins at this point, but again, from the Start>Run menu, open Services.msc. Find the DataCore Start Service and ensure that this service is Started.

Note: If this service has not started, manually start it from within this Services snap-in – do not use any SANmelody GUIs. Wait for service to have the status of Started, then click OK and close the Services snap-in.


11

Re-establishing the Partnership Before applying PSP4 (no update) to Server2, the partnership must be re-established between the two storage servers.

1. On Server2, do not open any SANmelody GUIs at this point (if you have, then close them immediately and do not save any configuration changes if prompted).

2. Double-click on the DcsLeaveRegion.exe executable. A command prompt will open (see screenshot) and when the process has finished will close automatically.

Very Important Note: You must not open any SANmelody GUIs on Server2 until you have completed the partnership process on Server1 (see next steps) otherwise the upgrade procedure may fail.

3. On Server1, open the SANmelody Storage Server snap-in. From the top right pane, right-click on the Server1 icon and choose Partner… from the context menu.

4. In the dialog box, select Add Partner, type the machine name of Server2 in the text field and click OK. You will see a message, reminding you about the DataCore Storage Domain Service logon and password settings, while this message can be ignored, you must still click Continue.

5. The Establishing Partnership progress bar will appear and when the partnership has been completed successfully, click OK. The Partnership window will close automatically.

6. On Server1, perform an Apply. You will see a message asking if you want to re-apply the current configuration, click OK. When you receive the message that the configuration has been applied, click OK.

After the storage server partnership has been re-established Server2 will shown as Online in the Partner field. See screenshot below.

7. This completes the process to re-establish the partnership for two SANmelody storage servers.

Continue to the following section to verify your application server volumes. There is no need to wait for mirrors to be healthy at this point. Please continue on to the next section.


12

Completing the Upgrade on Server2 to PSP4 (no update) 1. Close all SANmelody GUIs on Server2 and double-click on the SANmelody2.0PSP4.exe to

continue the upgrade of Server2 from PSP3 to PSP4 (no update).

2. The SANmelody splash will be displayed followed by the DataCore Installshield Wizard dialog boxes. Click Next to continue with the installation. Then click Next again to begin.

3. A message will inform you that DataCore Software Services will be stopped and asking if you wish you to continue. Click Yes the DataCore services will be stopped and the upgrade will start.

4. During this time, you may have to respond to different messages or wizards to successfully complete the installation process, including:



Important Note: If you see any other Microsoft Window message asking you if you want to restart your system for ‘…settings to take effect’, choose No.

5. When the installation has completed you will see the SANmelody Maintenance Complete window informing you must restart your computer. Ensure that the Yes radio button is selected and click Finish to restart the storage server.

6. Wait for Server2 to restart and log on to the storage server with the same account used to run the upgrade above. This will complete the installation of the upgraded drivers for PSP4 (no update) on the storage server. Please be patient, as it may take some time for your system settings to update with the new information. Do not open any SANmelody snap-ins at this point, but again, from the Start>Run menu, open Services.msc. Find the DataCore Start Service and ensure that this service is Started.

Note: If this service has not started, manually start it from the Services snap-in – do not use any SANmelody snap-ins at this point. Wait for service to have the status of Started, then click OK and close the Services snap-in.

7. Once Server2 has restarted and the DataCore Start Service has started, wait for any mirrors to recover for a final time and when healthy verify your application server volumes for a final time.


13

Verifying Application Server Access after Server2 Upgrade to PSP4 (no update) After the upgrade of Server2, it is important to check each application server to ensure full access to any HA virtual volumes. During the upgrade of Server1, access to any virtual volumes on this storage server would have been lost. Only when the Apply was completed in step 6 of “Re-establishing the Partnership,” would the access to the virtual volumes have been re-established from Server1.

For Application Servers running DataCore’s Alternate Pathing for Windows software:


2. In the right pane, select Disk Drives, and select Scan for Hardware Changes from the context menu.


3. In Computer Management, expand the DataCore SANmelody folder, select DataCore Alternate Pathing Monitor, and choose Refresh from the context menu to view updated volume and channel status.

4. Check that all volume and channel status indicators are green. Refresh as needed. If necessary, refer to the DataCore AP Help for more information.

For Application Servers running DataCore’s MPIO for Windows:


2. In the right pane, select Disk Drives, and select Scan for Hardware Changes from the context menu. There should a DataCore SCSI Disk device for each path on the application server to each storage server, but only one DataCore Multipath Disk device for each mirrored virtual volume.


3. In Computer Management, expand the DataCore SANmelody folder, select MPIO Management, and choose Refresh from the context menu to view updated volume and path status.

4. Check that your disks show up under Volumes and that all paths and storage servers are displayed and are either active or passive. Refresh the MPIO GUI if needed. Refer to the DataCore MPIO Help for more information.

For Application Servers using non-DataCore High Available software:

See your software vendor’s documentation on how to determine the health and access of a volume and its available paths.

The upgrade of your storage servers is now complete. You can now upgrade them to the latest version of SANmelody 2.0.4.x. Please refer to the installation instructions that come with the latest PSP/update.

upgrade sanmelody 2.0.2 2.0.4

Documents

software vendors

select device

datacore driver

relevant release

select disk

datacore software

view updated

primary storage