Planning Data Security Deployment > Planning network resources

Planning network resources

Applies to

Data Security v7.6.x

In this topic

Overview

Allocating disk space

Modifying the disk space setting

Distributing resources

Overview

To decide on things like disk space allocation, number of servers, and network distribution, start by answering these questions:

What volume of daily data do you expect in the number of transactions?

What is your user count?

Are you covering geographically distributed offices?

What is your user directory structure (Active Directory, ADAM, Domino) and the IP addresses of the LDAP servers?

Which ports are used and what are the port numbers?

Allocating disk space

Disk space for archiving fingerprint and forensic repositories is allocated by the Websense Data Security by default. The default settings are the nominal values defined by Websense; however, you can modify these values. The tables below indicates the default and maximum disk space for archives, forensics repository and endpoint client incident storage, log file and fingerprint storage.

On TRITON management server

Type	Description	Default Setting	Max Disk Space
Archive	The disk space of the incident archive folder on a local or external partition.	50 GB	No Max.
Forensic repository	The disk space of the forensic records stored in the archive folder.	40 GB	No Max.

On endpoint client

Type	Description	Default Setting	Max Disk Space
Endpoint client incident storage	The disk space that each endpoint client should allocate for incident storage when the endpoint host is disconnected from the TRITON Management Server.	100 MB	100 MB
Endpoint client log file	The disk space of the log file viewed on the endpoint client.	16 MB	100 MB
Endpoint client PreciseID fingerprint storage	The disk space that each endpoint client should allocate for storing directory and SharePoint fingerprints.	50 MB	1,000 MB

Modifying the disk space setting

Follow the instructions below to modify the default disk-space settings for either archives, endpoint client incident storage, PreciseID fingerprint or forensic repositories.

To modify disk space settings:

1.	Access TRITON - Data Security and choose the Settings tab.

2.	Depending on the disk space to modify, do the following:

a.	Archives: Select Settings > Configuration > System > Archive Storage. In the Maximum archive disk space field, modify the value.

b.	Forensics repository: Select Settings > Deployment > System Modules. In the list of modules, select the Forensics Repository entry. In the Maximum Disk Space field, set the value.

c.	Endpoint client (incident storage, log file and fingerprint storage): Select Settings > Configuration > System > Endpoint. In the section labeled Disk Space, modify the relevant disk-space value.

3.	Click OK. The disk space values are set and changes saved.

4.	Click Deploy to deploy your settings.

Distributing resources

Websense Data Security supports multi-site, distributed deployments. You can have a local policy engine on the protector, for example, and distributed (primary and secondary) fingerprint repositories.

You can have a management server in one location and one or more supplemental Data Security servers in other locations.

You can utilize the crawlers on the Data Security servers alone to do your fingerprint and discovery scans, or you can install the crawler agent on additional servers to improve performance.

These are just a few of the possibilities.

Your network architecture and the geographical location of your offices determine how you will want to distribute your resources.

See Most common deployments for distributions our customers commonly use.

Load balancing

In a multi-component system, you can configure load-balancing by selecting Settings > Deployment > System Modules in TRITON - Data Security and then clicking the Load Balancing button at the top of the screen.

Load balancing enables you to manage how each module sends its data to specified policy engines for analysis. This lets you distribute the load, but more important, it ensures that your vital email and HTTP performance is never harmed. For example, you can designate 1-2 dedicated servers to analyze inline HTTP traffic (where analysis latency is critical) and use another set of servers to analyze other channels.

An agent or a protector service can be analyzed by all listed policy engines or it can be analyzed by specifically selected policy engines. (Note that protector services can be analyzed only by local or Windows-based policy engines.) In addition, you can choose which policy engine analyzes a specific agent or service of the protector.

 

Note  Websense recommends that you do not distribute the load to the TRITON management server.

The Load Balancing screen shows a list of items where each item represents a protector or agent.

Click each item in the tree to define which policy engine it should be analyzed by. For further information on load balancing, refer to the TRITON - Data Security Help.

Planning Data Security Deployment > Planning network resources