Tips, calculating space for recording sessions

[schfa02]

Hi, does someone have some tip for calculating the amount of space a customer will require to assign for storing the recordings.

 

Or is there a formula to calculate, for example a video of X second will use X kb of space.

 

Regards.

[wonsa03]

Hi Farid,

 

There are some sizing calculator from Pre-Sales team. Check out the following thread in EF:

Spreadsheet: Session Recording Calculator 

[Ralf Prigl]

Pre-sales uses a sizing calculator which provides numbers like shown below. The basic parameters to work with are 600kB/min for high quality recording of WEB portal sessions, 200kB/min for RDP sessions and 20kB/min for SSH sessions. Percentage or users can be greater than 100% if users have multiple sessions running in parallel. Numbers below are based on 500 users and 4 hrs average length of sessions. Determining how many users actually connect to x servers for y time in your environment will make it much more accurate. We recommend referencing a pilot group that is using CA PAM exclusively to gauge the storage required.

 

[Sandeep Sharma]

Hi @Ralf Prigl for configuring mounting (for session recording), are Windows servers supported for NFS/ CIFS?

One of our clients (PAM v3.2.4) is currently using NFS share on Windows 2016 server (as NAS is not available in their environment). When session recording is activated and few users initiate RDP sessions concurrently, it seems the Windows server hangs/ crashes, perhaps due to high disk IO acitivity. This results in users complaining about slowness during sessions, disconnection or PAM disallowing RDP access (due to PAM session recording Security Safe policy). 

Hence, the client would like to know if Windows OS is a supported NFS mount configuration for PAM session recording. If is is supported, is there any disk IO guideline as currently the Windows server is running on normal disk i.e. not SSD etc. Are there any known issues reported by customers?

Thanks
Sandeep


​

[Stefan Muris]

You can use NFS in windows server, it is supported by Windows. Access should be given based on source IP of PAM, however if PAM supports SMB V3, I would opt to use ​NTFS share as I have seen NFS slows down performance when connected to windows