CA Data Protection low disk space.

Document ID : KB000109796
Last Modified Date : 06/08/2018
Show Technical Document Details
Introduction:
Settings in the machine policy let you monitor levels of free disk space on CA Data Protection machines and suspend the CA Data Protection infrastructure when free disk space falls below a critical level.

When free disk space falls below this level, CA Data Protection adds a warning to the Activity logfile. The default warning level is 25 MB. If free disk space continues to fall, further warnings are added to the logfile until eventually free space falls to the error level and the CA Data Protection infrastructure is suspended. Up to 10 warnings are issued, with a minimum fall in free disk space of 1 MB between each warning.

When the Disk space error level is met (the default value is 5 MB), the CA Data Protection infrastructure is suspended. Following a suspension, the infrastructure automatically restarts when free disk space recovers to the warning level (not the error level).
Background:
CA Data Protection comprises of the following object components:

1. Program Files (files required to execute the application).
2. System files (BLOB files containing the system configuration).
3. Data Files (BLOB files containing the encrypted data captured during policy violation).
4. A Database which stores meta data and reference to the stored objects (Data Files),

Due to the complexities and relationships between the system, data and the database, we cannot offer arbitrary advise on which files to delete as this could stop the system functioning entirely.  

In some circumstances there are no temporary files or surplus objects that can be removed from the data drive in order to restart the infrastructure so the only option is to move the Data Files onto a new drive which has more disk space.
 
Environment:
CA Data Protection 14.x\15.x
Instructions:
The following instructions assume that the administrator has the Administrative rights to make changes to the hardware, registry and file system locations.

1. Allocate new storage space (For example, add a new Hard drive to the host machine).

2. Stop the CA Data Protection Infrastructure Service (and Web Publishing Service if the iConsole Server is installed on the CMS machine)

3. Move the Data folder from the original location (C:\ProgramData\CA\CA DataMinder\) to its new location allocated in Step 1.

4. locate the startup.properties file in "C:\Program Files (x86)\CA\CA DataMinder\system" and open the file with "notepad.exe".

5. Locate the line "db.DataLocation=C:\\ProgramData\\CA\\CA DataMinder\\data\\" and replace it with the location of the new data folder location (as per Step 3).

For example: 
db.DataLocation=E:\\data\\

**************** NOTE ****************
The double slashes \\ are required.
*****************************************

6. Save the changes and exit notepad.exe

7. Use Regedit.exe to edit and update the "DataLocation" in the registry hives listed below. 

On a 64-bit installation. 
HLKM\SOFTWARE\WOW6432Node\ComputerAssociates\CA DataMinder\CurrentVersion\Properties\DataLocation 

On a 32-bit installation. 
HLKM\SOFTWARE\ComputerAssociates\CA DataMinder\CurrentVersion\Properties\DataLocation 

For example:
E:\Data


**************** NOTE ****************
Only single slashes \ are required.
*****************************************

8. Update the %wgndatadir% Environment variable to reflect the new data path.  

There are various ways of doing this, however I would suggest you open a Windows Command Window and execute the following command.

rundll32.exe sysdm.cpl,EditEnvironmentVariables

Locate the wgndatadir variable and update it to the new data path (i.e. E:\data) and click OK

9. Reboot the machine to restart all the required services in the correct order and for the variable changes to take effect.

10. You can check that the system is now accessible by loggin in to the CA Data Protection Administration Console (Acon).

11.  Review the latest "activity log" in the E:\data\log\ folder (log files are text files saved with a naming convention of "Activity_<Data_Time>.log") for any errors.
Additional Information:
This will get your system up and running but you need to look at what data is stored and for how long it is retained before it is removed.  The following link discussed event purging.

https://docops.ca.com/ca-data-protection/15-2/en/implementing/database/infrastructure-based-purging

If your intention is to keep many years of data you will need to consider your storage requirements to ensure that you do not run out of space again in the future.