disk space
Moderator: SourceGear
disk space
We have over 90GB in the vault DB so far.
We have the database on our larger drive
where there is more room.
But we are running out of space on C:
Inspection shows the largest culprit to be
Vault. It is storing more than 2GB *per user*
under Docs&Settings.
So on our 30GB main drive, for 5 users, 10GB
of it is used up just by the SG cache.
Is there anyway this can be consolidated so
that each user doesn't need their own copy?
Thanks,
Brad.
We have the database on our larger drive
where there is more room.
But we are running out of space on C:
Inspection shows the largest culprit to be
Vault. It is storing more than 2GB *per user*
under Docs&Settings.
So on our 30GB main drive, for 5 users, 10GB
of it is used up just by the SG cache.
Is there anyway this can be consolidated so
that each user doesn't need their own copy?
Thanks,
Brad.
re: disk space
That's a fair question.
We use RDP sessions.
Instead of perpetually buying new workstations,
we buy adequate workstations and very nice servers.
All our development is done on the server.
Not necessarily the same server that the Vault
server is running on.
HTH,
Brad.
We use RDP sessions.
Instead of perpetually buying new workstations,
we buy adequate workstations and very nice servers.
All our development is done on the server.
Not necessarily the same server that the Vault
server is running on.
HTH,
Brad.
Can you give me the full path to where you are seeing the huge amounts of files? I need to verify first that these really are cache files or if your user's working directories are there. You can't delete their working directories on them because they may have changes there that aren't checked in.
If it's the cache files, they will need a cache, but it might be possible to make them smaller.
The other culprit could be the _sgbak folders which are backup copies of files that are overwritten. Those can be cleared out. Technically, you don't have to have that, but a user has the potential to overwrite his changes on disk and that folder is the way to get them back.
If it's the cache files, they will need a cache, but it might be possible to make them smaller.
The other culprit could be the _sgbak folders which are backup copies of files that are overwritten. Those can be cleared out. Technically, you don't have to have that, but a user has the potential to overwrite his changes on disk and that folder is the way to get them back.
re: disk space
C:\Documents and Settings\jwood\Local Settings\Application Data\SourceGear\Vault_1\Client\7D4E2715-6D5B-4422-AA1D-ABF4DBFDD04F\jwood
A quick estimate shows this folder to hold 2,648,439 KB.
On the same system, same project,
C:\Documents and Settings\ldaniels\Local Settings\Application Data\SourceGear\Vault_1\Client\7D4E2715-6D5B-4422-AA1D-ABF4DBFDD04F\ldaniels\_sgvault
A quick estimate shows this folder to hold 2,395,175 KB.
On the same system, same project,
C:\Documents and Settings\sspear\Local Settings\Application Data\SourceGear\Vault_1\Client\7D4E2715-6D5B-4422-AA1D-ABF4DBFDD04F\sspear\_sgvault
A quick estimate shows this folder to hold 2,671,648 KB.
HTH,
Brad.
A quick estimate shows this folder to hold 2,648,439 KB.
On the same system, same project,
C:\Documents and Settings\ldaniels\Local Settings\Application Data\SourceGear\Vault_1\Client\7D4E2715-6D5B-4422-AA1D-ABF4DBFDD04F\ldaniels\_sgvault
A quick estimate shows this folder to hold 2,395,175 KB.
On the same system, same project,
C:\Documents and Settings\sspear\Local Settings\Application Data\SourceGear\Vault_1\Client\7D4E2715-6D5B-4422-AA1D-ABF4DBFDD04F\sspear\_sgvault
A quick estimate shows this folder to hold 2,671,648 KB.
HTH,
Brad.
If you are using Vault 4.x, then there's a setting where one can limit the number of baselines kept. Your clients can go to Tools - Options - Local Files - Cache Location. About halfway down, they will see the setting they can adjust. 2-3 should be about right. That won't completely remove the cache, but it may make it smaller.
It won't remove things immediately, but I think it's when it downloads the next version, it will cut it down to 2-3 baselines. You could have your clients check in and then perform a big Get, or just do a Get with automatic merge, and see if their cache gets smaller.
It won't remove things immediately, but I think it's when it downloads the next version, it will cut it down to 2-3 baselines. You could have your clients check in and then perform a big Get, or just do a Get with automatic merge, and see if their cache gets smaller.