Retain 4.9.2: Planning
- Retain 4.9.2: Planning
- Are You Creating a New Retain System?
- Are You New to an Existing Retain System?
- Retain Planning and Design Best Practices
- Retain Architecture
- Retain is Modular and Flexible
- Worker Locations
- System Requirements
- VMware Support
- Retain Component Locations Dictate Resource Needs
- The Number of Users Affects Resource Needs
- Minimum Retain System Requirements
- Single-Server RAM
- Separate Database Server RAM
- Separate Index servers, Database server, and Retain Server
- Securing the Database Connection
- High Availability Indexer Requirements
- Software installed by Retain
- Linux Server
- Windows Server
- SQL Database
- Browsers
- Hardware Planning
- Network Bandwidth
- CPU Requirements
- Planning for Disk Storage
- RAM
- VM Configuration
- Storage Planning
- Introduction to Storage Requirements
- Considerations for Storage Requirements
- Storage Minimums
- Index Size During Migration
- Changing the Log File Location
- About Storage Paths
- Setting Custom Storage Path Rights on Linux
- Tomcat Memory Requirements
- General Recommendations
- Tomcat Configuration Parameters
- Checking memory
- Ports Used
- Retain Server
- Retain Worker
- Retain Message Router
- Retain Reporting & Monitoring Server
- Retain Stubbing Server
- From RSM WAN IP to Untrusted, all TCP/UDP ports.
- Database Management Systems
- Blackberry
- Exchange
- Google Apps Module
- GroupWise
- Mobile
- Office 365
- CellTrust Secureline
- Messaging Systems Supported for Retain Archiving
- System File Locations
- Legal Notice