Database Mirroring:
•In database mirroring Real time transaction log shipping to secondary SQL Server. Incase of primary SQL server failure latest information will be available on Secondary SQL Server.
•As Database on Secondary SQL Server would be “Mirror, Synchronized / Restoring” We will not be able to attach the databases to web application on DR farm. Incase of Failover we will need to make the databases active and attach the databases to web applications.
•After failover when we attach the content database to the web application, it will automatically refresh the site map on Configuration database.
•As we cant attach the databases to the web applications, Search Service Application wont be able to crawl the content. After Fail-over you need to crawl the content.
•When failover happens we need to run SQL script to make the all content databases writeable.
Database Log Shipping:
•In Log shipping transaction log backup, copy and restore happens on scheduled time (Minimum time 1Min). Incase of fail-over from primary SQL Server to Secondary SQL Server we might loose some data if that's not restored on SQL Secondary SQL Server or manually restore the transaction log backup to Secondary SQL Server database.
•As Database on Secondary SQL Server would be “Stand by/ Read-only” It will allow you to attach the databases to web application on DR farm and we can crawl the content using Search Service Application.
•As the databases are attached to the web application we can run a script to refresh the Site Map on Configuration database.
•As we cant attach the databases to the web applications, Search Service Application wont be able to crawl the content. After Fail-over you need to crawl the content.
•When failover happens we need to run SQL script to make the all content databases writeable.
Changes required when you failover from Primary SharePoint 2010 to SharePoint 2010 DR Farm.
If you are using SQL database mirroring:
•On the DNS Server make the changes so that all the request can be reached to DR Farm SharePoint 2010 WFEs.
•Run the SQL Query to make the database active. (ALTER DATABASE ContentDatabaseName SET PARTNER FORCE_SERVICE_ALLOW_DATA_LOSS)
•Attach content databases to the web applications.
•Start a full Crawl process on Search Server.
If you are using SQL database log shipping:
•On the DNS Server make the changes so that all the request can be reached to DR Farm SharePoint 2010 WFEs.
•Restore all the pending transaction logs backup to database.
•Run the SQL Query to make the database active. (RESTORE DATABASE contentdbname WITH RECOVERY)
•Start an Incremental Crawl process on Search Server.
After knowing both the options, now you can choose between database mirroring and Database log shipping for DR farm configuration.
•In database mirroring Real time transaction log shipping to secondary SQL Server. Incase of primary SQL server failure latest information will be available on Secondary SQL Server.
•As Database on Secondary SQL Server would be “Mirror, Synchronized / Restoring” We will not be able to attach the databases to web application on DR farm. Incase of Failover we will need to make the databases active and attach the databases to web applications.
•After failover when we attach the content database to the web application, it will automatically refresh the site map on Configuration database.
•As we cant attach the databases to the web applications, Search Service Application wont be able to crawl the content. After Fail-over you need to crawl the content.
•When failover happens we need to run SQL script to make the all content databases writeable.
Database Log Shipping:
•In Log shipping transaction log backup, copy and restore happens on scheduled time (Minimum time 1Min). Incase of fail-over from primary SQL Server to Secondary SQL Server we might loose some data if that's not restored on SQL Secondary SQL Server or manually restore the transaction log backup to Secondary SQL Server database.
•As Database on Secondary SQL Server would be “Stand by/ Read-only” It will allow you to attach the databases to web application on DR farm and we can crawl the content using Search Service Application.
•As the databases are attached to the web application we can run a script to refresh the Site Map on Configuration database.
•As we cant attach the databases to the web applications, Search Service Application wont be able to crawl the content. After Fail-over you need to crawl the content.
•When failover happens we need to run SQL script to make the all content databases writeable.
Changes required when you failover from Primary SharePoint 2010 to SharePoint 2010 DR Farm.
If you are using SQL database mirroring:
•On the DNS Server make the changes so that all the request can be reached to DR Farm SharePoint 2010 WFEs.
•Run the SQL Query to make the database active. (ALTER DATABASE ContentDatabaseName SET PARTNER FORCE_SERVICE_ALLOW_DATA_LOSS)
•Attach content databases to the web applications.
•Start a full Crawl process on Search Server.
If you are using SQL database log shipping:
•On the DNS Server make the changes so that all the request can be reached to DR Farm SharePoint 2010 WFEs.
•Restore all the pending transaction logs backup to database.
•Run the SQL Query to make the database active. (RESTORE DATABASE contentdbname WITH RECOVERY)
•Start an Incremental Crawl process on Search Server.
After knowing both the options, now you can choose between database mirroring and Database log shipping for DR farm configuration.
No comments:
Post a Comment