Share via

Microsoft iSCSI Software Target 3.3 Migration Guide

  • Article

Check out the new iSCSI migration guide that was just posted on TechNet under the “Planning and Deployment” section of the iSCSI Software Target 3.3 Technical Library. This is located in the TechNet tree-view here:

image

If you have iSCSI Targets and LUNs already configured on Windows Storage Server 2008 or 2008 R2 and want to move them to a different Windows Storage Server 2008 R2 system then you can save hundreds of clicks and data entry steps by leveraging the new PowerShell based migration cmdlets. If you’ve ever had to manually migrate a set of targets and LUN mappings, you know what a time saver this can be. The scripts will record all the configuration settings and after you move the data to the new server, you just run the scripts to replay all the configuration steps.

The documentation provided in the Microsoft iSCSI Software Target Migration Guide eases the migration of server role settings and data from an existing server to a destination server that is running Windows Storage Server 2008 R2. By using the tools that are described in this guide, you can simplify the migration process, reduce migration time, increase the accuracy of the migration process, and help eliminate possible conflicts that might otherwise occur during the migration process.

https://technet.microsoft.com/en-us/library/gg509007(WS.10).aspx

The following configurations are supported:

  • Migration from a non-clustered configuration to a non-clustered configuration
  • Migration from a clustered configuration to a non-clustered configuration (with the restrictions regarding the scope of the settings).
  • Migration from a clustered configuration to another clustered configuration (with the restrictions regarding the scope of the settings).

Cheers,
Scott

Comments

  • Anonymous
    January 01, 2003
    If I understood well, in-place upgrade from 2008 to 008R2 is not supported. This migration script for iSCSI  cn save the day if the configuration is complicated to be recreated. But what about SiS store? Can I physically plug in the disk with the 2008 SiS partition on a R2 server or will it break? Is that a viable upgrade path or should I transfer all the data through the network? m a r c