when using the Portal Drive, it is possible to make a folder offline available. Let's say I have a huge repository of 2GB, if a user say's offline available, this means 2GB will be copied to his laptop? I've seen it's possible to set the cache size to i.e 64mb, but this is not related to the offline folder size I guess. If you have like 500 users, using the portal drive, this can create a huge network load.
Is there a way to restrict this from the side of the portal?
usually your users shouldn't map the root folder of your repository but specific subfolders they're working with depending on their access rights. This already should restrict the theoretical amount of data.
In addition, the default setting for mapping folders offline is, that you have to select all the files you really want to replicate to your local disc manually by choosing 'always available offline' on a file or folder basis. Otherwise they don't get copied to your local HD.
Best regards, Christopher