Gravatar for grant.killian@rackspace.com

Question by grantkillian, Sep 26, 2016 3:28 PM

Disaster Recovery references to Coveo Cloud

I’m working on the disaster recovery documentation for a Coveo license holder. They are using Coveo Cloud edition for their customer-facing indexes. In the event of a failover to the disaster recovery environment, what changes would be necessary to sync the Coveo Cloud indexes to this DR scenario? Since they will replicate their SQL Server databases and implementation code, the DR environment should be a good replica of their production environment and I don’t think any special measures are required for Coveo Cloud in terms of returning query results. I want to confirm that with you.

Also, in terms of document ingestion, is there any machine key or other identification Coveo Cloud includes in the service request? Assuming the Coveo license holder uses the same Coveo license key, would there be any reason the DR environment couldn’t send Coveo Cloud index updates?

I think Coveo Cloud makes this very easy, but I want to check with you to be sure.

1 Reply
Gravatar for slangevin@coveo.com

Answer by Simon, Sep 26, 2016 4:30 PM

Hi,

" They are using Coveo Cloud edition for their customer-facing indexes. In the event of a failover to the disaster recovery environment, what changes would be necessary to sync the Coveo Cloud indexes to this DR scenario? Since they will replicate their SQL Server databases and implementation code, the DR environment should be a good replica of their production environment and I don’t think any special measures are required for Coveo Cloud in terms of returning query results. I want to confirm that with you. "

  • Install Coveo for Sitecore on your DR Sitecore instance. (warm or cold)
  • Use the same Farm Name for both your live and DR instances :https://developers.coveo.com/display/SitecoreV4/Understanding+the+Coveo+Search+Provider's+Configuration+File
  • In case of a disaster, switch your queries to your DR environment, which will already know both the org and the farm containing your documents

"Also, in terms of document ingestion, is there any machine key or other identification Coveo Cloud includes in the service request? Assuming the Coveo license holder uses the same Coveo license key, would there be any reason the DR environment couldn’t send Coveo Cloud index updates?"

During the installation of the package, an API key will be created for your environments. The instances will use this API key to push and retrieve documents. This API key is independent so you will not have any restrictions preventing you from switching in the case of a DR.

Hope I answered your questions.
Simon

Gravatar for grant.killian@rackspace.com

Comment by grantkillian, Sep 26, 2016 5:06 PM

Thanks Simon, that's good info.

To clarify, the <sitecore><coveo><cloudPlatformConfiguration><apiKey> value should be the same in the DR environment as in Production? When you say to "Install Coveo for Sitecore on your DR Sitecore instance" I'm not sure if the client was planning to do a simple deploy (essentially x-copy) dlls and other file-based assets or if there's an actual .exe install you're referring to. When you wrote "During the installation of the package, an API key will be created for your environments" that has me confused on if the apiKey is for an entire implementation (different locations etc) or for a specific environment.

Gravatar for slangevin@coveo.com

Comment by Simon, Sep 26, 2016 5:21 PM

You could indeed to this as well. The API value and the Encryption key (in the Data folder) should be the same. In which case Coveo for Sitecore will be able to decrypt the key and communicate with your cloud instance.

Ask a question