Large Redstor folders filling up C -Drive
PROBLEM
The Redstor Agent works very well in managing the working space it uses. However, in some cases, it can utilize a lot of space relative to the free space available on the C-drive of a Windows folder, where, by default, the Redstor Agent is installed. Users can notice that there C-drive is filling up quickly and that the culprit appears to be the Redstor folder.
EXPLANATION
Redstor tracks, at the block level, changes in files from one backup to the next. These tracking files are called indexes. It retains these indexes to allow, if necessary, the rollback of backups to a "last known good" state in case of corruption or data loss. The larger the dataset, the more blocks need to be tracked, the larger these indexes are. Indexes are deleted when a monthly roll-up takes place.
In addition Redstor also generated detailed log files for each backup and restore. Each file has at least one line entry in the detail log. Obviously as file-count increases, logs get larger. In addition, if there are errors or warnings, these will add to the log size.
RESOLUTION
To resolve this problem, move the data history and logs location to a different drive that has more space. The installation and configuration files (which are typically very small) will remain on C-drive. A drive with more space needs to be identified and a folder created to house the Redstor data. For instance if the D drive has more space, create a D:\Redstor (or D:\Program Files\Redstor) folder.
1. Open up the Agent Console on the individual server then selecting Options from the ribbon:
2.Under the Advanced tab in the "Working Folders" section select the Change:
3. ...from there you can choose a new location (say D:\Redstor\Data)
4. Repeat the process under the Logging section of the Options and select a new location (say D:\Redstor\Logs)
We would suggest not changing the default settings for the retention of those indexes and logs unless absolutely necessary.
You never know you need them until you do!
Related Articles
SAV22 and SAVLIB for OS720
These screen shots are from a OS720 system executing a SAV22 with additional save of libraries QGPL, QUSRSYS, and QSYS2 (If you are a CORNERSTONE customer, you would also save the libraries CORNERST and CORNERST1.) The parameters mentioned in this ...