We’re very happy to announce that DocAve High Availability now supports the synchronization, failover, and fallback of SharePoint 2013 content and service application databases. For service application databases, we’ve taken extra consideration to ensure that we protect the configurations for SharePoint 2013 specific functionality such as Yammer integration in the User Profile Service. [caption id="attachment_3222" align="alignnone" width="622"] 1. SharePoint 2013 Support for Content and Service Application Databases

Since the re-introduction of DocAve High Availability in SP 3, we’ve received some questions from our customers. Some of them include, “How can I verify that my production content is actually being synchronized to our standby environment without performing a failover?” And, “It is possible for DocAve High Availability to provide a scenario where we can utilize our standby farm so that the hardware isn’t wasted?” To answer these questions, we’ve included a new option that allows users to access synchronized content from their standby environment in a “read-only” mode. To make this possible, our engineering staff has implemented some clever techniques which include taking snapshot backups of synchronized databases and mounting them to the standby SharePoint farms. Now users can verify whether or not content has been properly synchronized and also utilize their “unused” SharePoint hardware by accessing the content in a protected “read-only” mode. 2. Read-Only Mode
As you know, AvePoint offers a wide range of solutions for infrastructure management, data governance, compliance, and productivity. DocAve High Availability has been updated to integrate with two of our offerings: DocAve 3. Integration with DocAve Storage Manager and DocAve Backup and RestoreStorage Manager and DocAve Backup and Restore. If you have externalized your SharePoint Binary Large Object (BLOB) content through DocAve Storage Manager, DocAve High Availability can ensure that the externalized blobs will seamlessly failover to the disaster recovery environment along with the SharePoint databases. Within DocAve Backup and Restore’s Platform Backup capability, we’ve added a new Platform Backup Log Shipping method for synchronizing databases from production to standby. Standard Log Shipping takes logs from native SQL backups and “ships” those to a standby farm for replication. If you are using DocAve Platform Backup, however, you are probably not doing native SQL backups and therefore cannot use this native SQL log shipping approach. To enable DocAve Platform Backup customers to use log shipping, we have added the option for using log shipping from the DocAve backups instead of the native SQL backups, thus covering all backup and Disaster Recovery (DR) scenarios required for DocAve High Availability. [caption id="attachment_3223" align="alignnone" width="622"]

Although DocAve High Availability is primarily a SharePoint solution, we’ve added the functionality to include custom databases into your High Availability groups. In some cases, the SharePoint content and service application databases may not be the only databases that you want to synchronize to a DR site. Custom solutions of applications that are critical to your farm may depend on databases other than those natively used by SharePoint. In order to have a fully functioning standby environment, HA can synchronize, failover, and fallback any custom database that may be required. [caption id="attachment_3224" align="alignnone" width="622"] 4. Custom Database Support
