Yesterday I posted a way to change the cache folder location for CloudBerry’s mapped drives. Today I’m updating this article with an even easier way to change the cache folder. There’s actually a setting for it in advanced options!
The GUI Way (Recommended)
- Right click on the CloudBerry icon near your click and go to Options… > Advanced Tab. The Cached location is right there! For bigger moves that will take much longer I’d suggest removing the cache retention period.
The XML file way
We were recently moving files for a customer using CloudBerry Lab’s Backup Software. I kicked off some huge exports to the mapped drive configured with the CloudBerry install and I found I ran out of space on the root of the server because CloudBerry creates a TEMP directory to hold things while they move. Here’s how to change that location:
You need to change a line in the mappedDrives.xml file:
- Server 2003\XP: C:\Documents and Settings\username\Local Settings\Application Data\CloudBerryLab\CloudBerry Drive
- Vista\Server 2008\Win8: C:\Users\username\AppData\Local\CloudBerryLab\CloudBerry Drive
If you right click and edit the file it will look something like this by default. I highlighted what we’ll be changing:
<?xml version="1.0"?> <MappedDrives xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema"> <Logging> <Level>Warning</Level> <LogErrorMessages>true</LogErrorMessages> </Logging> <MappedDriveCollection> <MappedDriveSettings> <DriveLetter>Z</DriveLetter> <Path>archive-ev</Path> <VolumeLabel>s3-data</VolumeLabel> <SerialNumber>B8DFE602</SerialNumber> <ReadOnly>false</ReadOnly> </MappedDriveSettings> </MappedDriveCollection> <Cache> <FileCacheBaseDirectory>%TEMP%\CloudBerryLab\Drive\</FileCacheBaseDirectory> </Cache> </MappedDrives>
Here’s a screenshot of my old 2003 Box:
You need to change the FileCacheBaseDirectory to a path that already exists on a drive with plenty of space. I chose my DATA Drive. So the changes looked like this:
<Cache> <FileCacheBaseDirectory>E:\CloudBerryCache</FileCacheBaseDirectory> </Cache>
I rebooted for good measure. Odds are you could just close the program and open it back up, or at the most restart services or relog.
Let me know if you guys find anything different.