20 million object limit?

As I heard this is not a DX limit, it is coming from Microsoft, they have a recommendation for the file coubnt on a NTFS volume. Unfortunately I do not have information which on witch operating system, wich version.

Krisztian

Hmm.... I have not seen anything from Microsoft on that. The NTFS documentation on the Microsoft developers site states that the NTFS file system can hold over 4 billion objects and I could not find a practical file count limit in the documentation, just the 4 billion theoretical design limitation.

I currently have 5 extended drives on our DX install. One of my extended drives has 34,440,505 files and another one has 25,295,783. I am using DX for Windows ver 6.20.060 with the latest patch applied.

Thanks for the information Ralph, I appreciate the response. We are running an older version, 5.60.049, and hopefully the object count won't be an issue as it has not been for you.

Aran

Hi Ralph!!

When you mentioned that your currently have 5 extended drives on our DX install. One of my extended drives has 34,440,505 files and another one has 25,295,783. I am using DX for Windows ver 6.20.060 with the latest patch applied.

Could you tell me you hardware specifications:

Like: How many processor have the server?

We want be sure that DX 6.x support more than 7 extended drives....


Best Regards,
Rodrigon

Hi All,

In DX Install Guide, page 37, it states:
A drive that contains (or will contain) no more than 20 million to 25 million files.
As a drive approaches this limit, system functions such as background scans and
backups can take a significant amount of time.

Number of extended drives
The appropriate number of extended drives depends on the environment. In general,
however, it is better for each DiskXtender installation to manage fewer extended
drives. Fewer extended drives typically mean less impact on the system, and
therefore improved system performance.
If possible, a good rule of thumb is to use n-node processors, where n is equal to the
number of extended drives plus one. For example, a server with a four-node
processor should manage only three extended drives. This provides the equivalent of
a dedicated processor for each extended drive, leaving one processor free for any
other processing.
In environments where some of the extended drives are relatively inactive, a good
rule of thumb is seven or fewer extended drives, where only three or fewer are active.
Inactive extended drives can be used for retrieval of files, but access should be
relatively infrequent.

I have seen a system with over 130 million files on one extended drive. Definitely not recommended. The system performance is just fine, but background scans take weeks and backups also take too long.