Are you moving the source LUN from the production host (Windows 2003) to a new production host (Windows 2008)? That process cannot be done by RM for multiple reasons. The primary reason is that RM manages replication of a source device and is not really a migration tool. RM also cannot mount the replica of a Windows 2003 LUN to a Windows 2008 server. They are different Operating Systems and therefore have different Logical Volume Managers so RM will not list the Windows 2008 host as a viable target for the mount of a replica.
The simplest way to change the LUN from one host to another on the same array is just to unmask the LUN from the original host and then mask the LUN to the new host. Before doing this you should delete the RM job and then create a new RM job once the move is complete and the SQL database has attached to the DB files on the LUN.
AranH1
2.2K Posts
0
May 18th, 2010 13:00
Are you moving the source LUN from the production host (Windows 2003) to a new production host (Windows 2008)? That process cannot be done by RM for multiple reasons. The primary reason is that RM manages replication of a source device and is not really a migration tool. RM also cannot mount the replica of a Windows 2003 LUN to a Windows 2008 server. They are different Operating Systems and therefore have different Logical Volume Managers so RM will not list the Windows 2008 host as a viable target for the mount of a replica.
The simplest way to change the LUN from one host to another on the same array is just to unmask the LUN from the original host and then mask the LUN to the new host. Before doing this you should delete the RM job and then create a new RM job once the move is complete and the SQL database has attached to the DB files on the LUN.