An upgrade is required from a SharePoint 2007 Farm with an existing disaster recovery (DR) site to a new SharePoint 2013 Farm with a DR site. 

Currently, the production environment has a web server (Win Server 2003 R2 Standard), application server (Win Server 2003 R2 Enterprise) and a SQL 2005 standard  ( Win Server 2003 R2 Enterprise) 

The DR site has a web server (Win Server 2003 R2 Standard), application server (Win Server 2003 R2 Enterprise) and a SQL 2005 standard  (Win Server 2003 R2 Enterprise) as well. 

So just to clarify if these are the right steps to execute the upgrade.  

1. Build a SharePoint 2010 Farm ( 2 Servers - 1 web app + SQL) and perform a database attach upgrade to 2010 from the 2007

2. Build a Full SharePoint 2013 ( 2 Web Front Servers + 1 Application Server and SQL) and perform a database attach upgrade from 2010 to 2013. 

3. Build an identical farm of the SharePoint 2013 Farm as the DR site 

4. Create a Network Load Balance between the SharePoint Environment with the DR or Hot site by using network load balancing. 

5. Configure the SharePoint SQL to sync with the DR SQL by using log shipping from the Primary SQL Server to Secondary SQL Server 

In summary does most of the work in the upgrade is smoothly migrating the SQL databases from 2007 to 2010 and then finally 2013 and if this goes well everything should be fine? I know its complex but is this the general idea behind the upgrade? 

These articles helped but I'm still uncertain if these are all the right steps involve from experiences. 

http://blogs.msdn.com/b/sambetts/archive/2013/10/11/hot-standby-disaster-recovery-sharepoint-farms-basic-setup-amp-failover-high-availability-sharepoint.aspx 

https://technet.microsoft.com/en-us/library/cc262483.aspx 

https://technet.microsoft.com/library/ff607663(v=office.14) 

Is there anything else I should keep in mind and review. 

Please advise. 

Thanks, 

• Edited by aslr12 Thursday, April 30, 2015 11:20 PM

4) NLB between production and DR? If that is what you're asking about, then no that wouldn't be appropriate

5) Yes, Log Shipping is one option, others include Database Mirroring and AlwaysOn. For those technologies, if the site is > 1 ms away from your production SQL and/or SharePoint servers, you need to use a asynchronous commit.

You certainly have the right ideas behind the upgrade.

You might also be interested in this:

http://blogs.msdn.com/b/sambetts/archive/2015/04/24/setting-up-sharepoint-disaster-recovery-sites-with-sql-alwayson.aspx