Adding a VISULOX Revision Server
OverviewIn a VISULOX Cluster one node can be enabled/promoted to be a Revision / Archive Server. The Revision Server is disabled for VISULOX application loadbalancing (no session controllers, no recorders).
VISULOX supports one Revision Server to guarantee 100% of the audit data from all production servers.
|
Requirement
- All nodes must be joined in one cluster before Archive mode is enabled
- Archive retention times must be defined before setting the node tag "archive"
- Configuration of nodes must be in sync (visulox config list -name layout)
- If the node runs the VISULOX Cockpit (and is not on the VISULOX Access Node), the replication mode has to be set to all
Configuration
Enable Archive mode on the node which will be promoted to be an Archive Node
visulox archive -set
(From another node: visulox archive -set -node <archive-nodename>)
Forced enabling of the Archive mode without prompting
visulox archive -set -force
(From another node: visulox archive -set -force -node <archive-nodename>)
Setting the Archive lifetimes
Archive lifetimes are separated from the lifetimes in the production environment:
Archive lifetimes
visulox config list -name lifetime.archive
--------------------------------------------------------
| parameter | type | value |
--------------------------------------------------------
| lifetime.archive.application | OPERATION | 180 |
| lifetime.archive.bigfiletransfer | OPERATION | 180 |
| lifetime.archive.default | OPERATION | 180 |
| lifetime.archive.filetransfer | OPERATION | 180 |
| lifetime.archive.input | OPERATION | 180 |
| lifetime.archive.login | OPERATION | 180 |
| lifetime.archive.script | OPERATION | 180 |
| lifetime.archive.sgdaudit | OPERATION | 180 |
| lifetime.archive.system | OPERATION | 180 |
--------------------------------------------------------
The lifetimes (in days) are adjusted with:
visulox config edit -name lifetime.archive.filetransfer=360
During replication of the data on the Revision Server, the new retention time is set, if is is greater than the time in the production environment.
Standard retention data is 90 days, on the Revision Server it is 180 days. If an application enforces 500 days, this will not be overwritten.
X11 native port
The Revision Server must be able to communicate via X11 native (port 6000+).
See also: VISULOX SSH X11 Forwarding to VISULOX Application Nodes
Accessing the information
To access the data on the Revision Server a VISULOX Cockpit has to be configured in the VISULOX PORTAL Datastore with the assigned Revision Server.
It is helpful to use -name vlxarchive in the "Arguments of Command" field of the Archive Cockpit to display only the relevant pages.
Troubleshooting
Is the Archive mode enabled?
visulox archive
Relevant services
vlxService replication.tcl
vlxService archive.tcl