cancel
Showing results for 
Search instead for 
Did you mean: 

Server 2016 and Storage Replica (SR) for HA

Sean_Dass1
Champ in-the-making
Champ in-the-making

Windows Server 2016 introduced Storage Replica (SR) as an option for file replication which functions at a block level.  Has anyone configured OnBase to utilize this method and are there any gotchas or considerations when going this route?

1 REPLY 1

Jim_Dimmick
Confirmed Champ
Confirmed Champ

Hi Sean,

I can't say I have run into any OnBase customers who are running this but, there are a few things to consider.  I assume you are asking about using this for OnBase Disk Groups (your document archive).

First, for Storage Replica (SR) you will need Windows Server 2016 Datacenter Edition.  Currently, OnBase would have to be version 16 SP2 or higher to work with Windows Server 2016.  The considerations fall into either functional or performance categories.

Next you have to determine Sync or Async SR?  You'd have to determine if the SR config would meet your HA/DR goals.  Synchronous will give you a recovery point of zero (no data loss) however, it will likely slow the application down while writes are replicated across the network to alternate locations.  There is also background activity that must complete in the SR layer which will slow file write response time to OnBase.  Imagine a batch import of documents with a lot of files, the delay could be pretty painful especially if writing to a long distance SR location.  With Asynchronous, you reduce performance impacts but may have some data loss after fail over.  Either will likely work but you'd have to determine what performance would be acceptable (or not).

You want to size your SR log to cover the span of time you want to protect against.  Depending on the length of an outage, smaller logs generally require longer recovery times and larger logs will help to reduce recovery times.  Microsoft recommends using dedicated SSD's for the SR logs.  You also need low latency networks for SR activity.  There are also several known issues with SR that Microsoft has published.    

Keep in mind that OnBase 18 and lower require an SMB share for OnBase Disk Groups.  If you have a storage system that natively supports SMB, you could write directly to an SMB share without the need for a file server.  If that storage has replication, you could use back end storage replication to push files to an alternate site.  If the UNC path does not change (use of an alias or DFS) recovery steps and time is reduced.

Hope this helps - Jim

Getting started

Find what you came for

We want to make your experience in Hyland Connect as valuable as possible, so we put together some helpful links.