![]() We are going to focus on the VDP server for this article. In this example, we have created 1 production VDP server, 1 production Scheduler server and 1 production Data Catalog server. We can create different servers depending on the Denodo Platform tools we have installed in our environment. The final step is creating the servers in the cluster. You can check the Creating clusters section for more information about this process. In our example, we will create just one cluster. Once we have created our production environment, we should proceed with the creation of the cluster. In addition, you can check the Configuring Deployment Scripts section in case you want to configure some scripts to be executed in the Load Balancer to enable/disable clusters or servers. ![]() You can check the Configuring Deployments section for more information regarding the different parameters in this menu. In order to enable deployments on the full environment, so all the servers will be updated at once, we need to enable the deployments in the Deployments tab for this environment. Do not select BACKUP scenario a t this point, it will be configured later. In the License scenario, we will select the value to be used in this environment for the main servers, in this example, it will be PRODUCTION. You can follow the section Creating Environments of the Solution Manager Administration Guide for more information regarding the different parameters. Virtual DataPort, Scheduler, ITPilot or Data Catalog Servers. The first step is creating a new environment that will contain all the Production servers in our Denodo installation. In the example, we are going to show how to create a Production environment together with a Hot Backup. Important note : The steps described here are valid from Denodo Solution Manager 7.0 Update 20190312. In this section, you will learn how to configure a Backup Server (Hot Backup or Cold Backup) in the Denodo Solution Manager so the Solution Manager server will be able to automatically deploy the same metadata as in the production nodes in those backup servers that you have configured for the same environment. Ĭonfiguring the VDP Backup Server in the Solution Manager The Cold backup server can be started only for synchronizing the metadata when a new deployment is performed through the Solution Manager. When one of the Production VDP servers fails, the Cold backup servers should be manually turned on and added to the cluster. ![]() The difference with the Hot Backup is that the Cold backup servers must remain turned off unless a failure is detected on any of the Production ones. When this happens, the Load Balancer will add the Hot backup server to the cluster.Ī Cold Backup architecture will have one or more Denodo VDP servers that will host the same VDP metadata as the Production servers. ![]() ![]() The difference is that they must not receive any petition from the Load Balancer unless one of the Production VDP servers fails. Let’s see the difference between a Hot Backup and a Cold Backup:Ī Hot Backup architecture contains one or more Denodo VDP servers that will be up and running with exactly the same metadata as the Production VDP servers. In a Denodo production installation, it is recommended to have a backup server that will be connected to the Load Balancer when some of the main servers are not working for an unexpected reason.įor those scenarios, if it’s allowed by your license, you can configure Hot Backups or Cold Backup servers in order to maintain its metadata in sync with the Production servers so they can quickly replace the Production ones if they fail. This document describes the recommended approach to configuring the environments and servers in the Denodo Solution Manager for those scenarios where there is a Hot Backup or a Cold Backup server. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |