![]() Go to the Manage tab and click VM/Host Rules > Add.In the vCenter Web Client, go to Host and Clusters and select the cluster.To achieve this if you install the manager and database on VMs, make sure they are always run in the same ESXi host. 2 ms latency or less is recommended for the connection from the manager to the database. (WAN connections are not recommended.) The same applies to additional Deep Security Manager nodes. It is also important that the database and the Deep Security Manager be co-located on the same network with a 1 Gb LAN connection to ensure unhindered communication between the two. The database should be installed on a dedicated server that is separate from the manager nodes. Database maintenance is a crucial part of Deep Security operations.When using Windows Authentication, click the "Advanced" button to display additional options. The installation supports both SQL and Windows Authentication. Enter the database hostname under "Hostname" and the database that you created for Deep Security under "Database Name". During the Deep Security Manager installation, you will be asked for database connection details.See Port numbers, URLs, and IP addresses. Allow communication from the Deep Security Manager computer to the database computer.Ensure that the database and the manager use the same time zone and that they are synchronizing their time to the same time source. The database time must be synchronized with the time on the Deep Security Manager computer.For this reason, database mirroring is recommended over database replication. For example, some database replication technologies add columns to the database tables during replication which can result in critical failures. For high availability, the Deep Security database is compatible with database failover protection so long as no alterations are made to the database schema. ![]() For details, see Microsoft SQL Server Express considerations. ![]() Microsoft SQL Server Express is supported only in certain limited deployments with Deep Security 10.0 Update 2 or later. Depending on which database you choose, see Microsoft SQL Server or Oracle Database for database-specific considerations.For a list of supported databases, see Database. Any increase in latency can have a serious negative impact on Deep Security Manager’s performance and availability. Deep Security Manager relies on the database to function. The Deep Security Manager must be co-located on the same network as its database, with the connection speed of 1 GB LAN or higher. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |