RSA SecurID for Microsoft Windows space requirements for offline data
Originally Published: 2006-01-18
Last Modified: 2023-09-22
Article Number
000053721
Applies To
THIS SOLUTION IS IN PROGRESS - Please use this for your edification and edit as necessary before sending outside.
RSA SecurID for Microsoft Windows
Issue
RSA SecurID for Microsoft Windows space requirements for offline data
Resolution
Dayfiles in 6.0.x are ~46K per full day file per user.  In 6.1 this is slightly different by ~1-2K, but the exact size is not clear.

So for a single 6.0.x user with 14 days of dayfiles that would be 14 * 46K = 644K.

The DAC tries to keep a full complement of day files on each desktop that the user logs into, provided it has a DAC installed and the user is allowed offline data.  So for every user logging into a particular DAC there would be 644K of offline day files for 14 days.  Typically with a single user using their own desktop or laptop, they will be the only person with dayfiles on that system.

Now the DAH is a different story.  In the 6.0.x versions the DAH also stored a copy of ALL of these day files to allow for domain reconnections.  This meant that if the domain had 1500 users, all with offline data, then the DAH would need to store 1500 * 644K or 966MB of data in the replicated file system.  And since this data is replicated across the domain, ALL domain controllers would have nearly 1GB of dayfiles stored.

This was obviously an issue and so in 6.1 we introduced the user secret which replaces the dayfiles on the DAH for domain reconnections.  This file is ~90 BYTES in size per user and replaces all of the dayfiles previously stored on the DC for each user.  This brings the previous 1GB on each DC down to a much more manageable (1500 * 90) 135K on each domain controller.

Just keep in mind that the DAC still gets a ~46K file per day per user downloaded regardless of the version.

Related Articles

Trending Articles

Don't see what you're looking for?