Primary Storage

 View Only
  • 1.  Windows Server 2019 and a V5020

    Posted Wed August 23, 2023 09:42 AM

    I have an old V5020 that will go out of support later this year.  To get the data off I need to take the existing disks and move them to a Windows server 2019 system and let that system handle the migration of the data to the new Storage.  I have always gone to the IBM docs and looked up how to attach a host and followed that each time I have added a new system.  The issue is I cannot find any documentation on how to install a Windows server 2019 to a V5020 system.  

    I have support on the V5020 but that is hardware support and I would think how to attach the system to a host would be part of the expected documentation.  I have thought about opening a case with IBM but I know they will want me to pay to get support seeing that I do not pay for the SAN software support side of things.  

    Has anyone ever attached a V5020 to a Windows Server 2019 server?  I know the IBM SDDDSM is done and surely there must be some settings to change.  

    Any thoughts and help will be helpful.

    Matthew Jamison

  • 2.  RE: Windows Server 2019 and a V5020

    Posted Thu August 24, 2023 02:25 AM

    Hello Matthew,

      The Documentation does detail this here: Hosts that run the Microsoft Windows Server operating system

    Whether you are running a V5020 or a more Recent FS5000, the host attach is the same,


  • 3.  RE: Windows Server 2019 and a V5020

    Posted Thu August 24, 2023 09:05 AM
    Feel free to reach out to me directly.

    Andrew 'AJ' Greenfield

    WW Storage / Security

    +1 480-294-1342

    Public Box Folder:

  • 4.  RE: Windows Server 2019 and a V5020

    Posted Mon August 28, 2023 04:06 PM

    Migrating data from an IBM V5020 storage system to a Windows Server 2019 system can indeed involve several steps and considerations, even though the documentation might not be as readily available as for more common scenarios. Here's a general guide to help you get started:

    1. **Hardware and Connectivity Check**:
       Ensure that the Windows Server 2019 system has compatible hardware and connectivity (such as Fibre Channel or iSCSI) to connect to the V5020 storage. Verify that the relevant ports and protocols are configured on both the server and the storage.

    2. **Storage Configuration**:
       On the V5020, you will likely need to configure LUNs (Logical Unit Numbers) that will be presented to the Windows Server. Each LUN will be seen as a separate disk on the server.

    3. **Host Attachment**:
       You will need to add the Windows Server 2019 system as a host on the V5020 storage. Even though you can't find specific documentation for Windows Server 2019, the steps for attaching a host are often similar across different systems. You might refer to the general documentation for attaching a host and adapt the steps to Windows Server 2019.

    4. **Multipathing and Drivers**:
       Install the appropriate drivers for your chosen connectivity method (Fibre Channel or iSCSI). You mentioned that IBM SDDDSM is not supported, so ensure you're using the correct native multipathing software or drivers provided by Microsoft.

    5. **Zoning and Security**:
       If you're using Fibre Channel, make sure the zoning is correctly configured on the SAN switches to allow communication between the Windows Server and the V5020 storage. For iSCSI, ensure proper IP configuration and security settings.

    6. **LUN Mapping**:
       Once the host is attached, you'll need to map the configured LUNs to the Windows Server. This process might involve specifying which LUNs the Windows Server has access to.

    7. **Windows Server Configuration**:
       On the Windows Server 2019 side, you will need to scan for new disks to recognize the newly attached LUNs. You can use the "Disk Management" tool to initialize, format, and assign drive letters to the new disks.

    8. **Data Migration**:
       With the new disks visible on the Windows Server, you can initiate the data migration from the old storage to the new one. This might involve using tools like Robocopy, Microsoft's Storage Migration Service, or third-party data migration software.

    9. **Testing and Verification**:
       After the migration, thoroughly test the data integrity and accessibility on the Windows Server. Ensure that all applications and services relying on the migrated data are functioning correctly.

    big redd