01-27-2015 04:48 AM
01-27-2015 08:31 AM
Hi Rich,
I'm sorry to hear of the Disk Crash. First off, I would recommend working with your first line of support as soon as possible to find a solution. In general, all you should need to do is create a new Copy 1 path. For this you would need to,
These steps will create an uncommitted copy for each of your disk groups. Without knowing more about your Disk Group design it is hard to say if there are any other changes which are necessary to get you up and running (ie do you have multiple copies? are the other copies still accessible? etc). These conversations should take place with your first line of support.
Good luck.
01-27-2015 08:55 AM
Another note, if you are able to import data and your Copy 1 is ok (meaning the only issue is with the commit process), then all you would need to do is set Copy 2 as a Backup copy and promote. If your secondary copy is a Backup, OnBase will not attempt to write data during the commit process. This will help to get around the issue until you have secondary copy strategy in place.
Take care.
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.