Andrew Jackson

Yes, it is a AlwaysOn drawback. SQL Server Replication uses very high bandwidth. I think its best to use log shipping for a DR solution, because you can use DR db in standby mode & it uses very low traffic.

So it appears that you are migrating the instance to another server and this instance is working as a publisher, distributor and subscriber (at least this is what I am guessing from your short explanation).

• Backup your publisher and subscriber databases.
• Restore them on the destination instance with norecovery and setup log shipping or mirroring between the two servers.
• At this time the replication is intact and there is no downtime been taken i.e. your application is still up and running.
• Take the downtime
• Remove LS or mirroring from the target instance after ensuring that the source and destination DBs are in sync.
• Take the last log backup of subscriber and publisher databases and restore them on the target databases with recovery. 
• Setup the distribution and publication on the new instance.
• Setup replication between the publisher DB and whatever subscribers you have but do not initialize them as the data is in sync already.
• Do the same with the subscriber database.
• Change the connection strings in the application to point to the new server.

Hope it will help you

 BEGIN TRAN
BEGIN TRY
    EXEC sp_rename '[SomeTable].[Id]', 'OldId';

    ALTER TABLE [SomeTable] ADD Id int NULL

    EXEC ('UPDATE [SomeTable] SET Id = OldId')

    ALTER TABLE [SomeTable] NOCHECK CONSTRAINT ALL

    ALTER TABLE [SomeTable] DROP CONSTRAINT [PK_constraintName];
    ALTER TABLE [SomeTable] DROP COLUMN OldId
    ALTER TABLE [SomeTable] ALTER COLUMN [Id] INTEGER NOT NULL
    ALTER TABLE [SomeTable] ADD CONSTRAINT PK_JobInfo PRIMARY KEY (Id)

    ALTER TABLE [SomeTable] CHECK CONSTRAINT ALL

    COMMIT TRAN
END TRY
BEGIN CATCH
    ROLLBACK TRAN   
    SELECT ERROR_MESSAGE ()
END CATCH

• Make sure that your SQL Server port is not blocked by the system Firewall
• Go to Computer Management >> Service and Application >> SQL Server 2005 Configuration >> Network Configuration

Enable TCP/IP protocol.

For more information: http://www.sqlserverlogexplorer.com/database-mirroring-error-1418/

The reason of error is self explained means that the error reason is explained in error message.
Use BACKUP LOG WITH NORECOVERY to backup the log if it contains work you do not want to lose.
You need to restore the database from full backup using WITH REPLACE clause something like this:

RESTORE DATABASE DATABASE_NAME FROM DISK = 'C:\database.BAK'
WITH REPLACE
GO

You can use this sample query to find out when the table was last updated.

SELECT OBJECT_NAME(OBJECT_ID) AS DatabaseName, last_user_update,*
FROM sys.dm_db_index_usage_stats
WHERE database_id = DB_ID( 'DB_name')
AND OBJECT_ID=OBJECT_ID('Table_name')