Best practices to manage disk space on the Information Server (IS) in Control Compliance Suite (CCS) Data Collection
|Article:TECH113554|||||Created: 2007-01-25|||||Updated: 2010-01-30|||||Article URL http://www.symantec.com/docs/TECH113554|
How to save or free disk space on the CCS IS.
Following are best practices to save disk space on the CCS IS:
- Save the Dataset To Query Binder
- Limit Max Historical Runs
- Free disk space
- The raw XML files in the \PROGRAM FILES\SYMANTEC\RMS\DATA\USER\PATCHASSESSMENT folder are no longer needed and may be deleted.
The first two suggestions are dependent on each other. The first regards managing data in the Task Status window. Once this data is saved to a query binder, then the second option can be utilized.The third option is to free up disk space by deleting stale datasets by running a query; the third can be used independent of the first two suggestions.
Save Dataset To Query Binder
Datasets are saved to maintain a history of the information collected about resource objects. Saving datasets in a query binder using either the Save or Save As command removes the query task from the Task Status dialog because the corresponding dataset has been "moved" into a query binder.
- OPTION #1
- Return the results of any query to the Grid.
- While closing the Grid, click Save when prompted.
- In the "Save Query" dialog box, choose the location to save the results.
- Build a new task list and add the desired queries to the task list.
- In the Query Task Item dialog box, check the box "Save Results Back To Query".
- Repeat step 2 for each query added to the task list.
Limit Max Historical Runs
The Max Historical Runs dialog box displays the maximum number of historical datasets that can be linked to the query binder per user. Once the maximum number of historical datasets is reached, the oldest dataset is deleted each time a new dataset is saved to the query binder. If a dataset is marked as "Locked", it will not be deleted. Instead, the next-oldest dataset will be deleted.
- Right Click on an existing Query Binder, then click Manage > Historical Data on the floating menu.
- The Manage Historical Data dialog box will appear.
- At the bottom right, reduce the number of "Max Historical Runs (per user)".
- NOTE: The default Historical Runs is 50.
- NOTE: Maximum Historical Runs can be as low as 2 or 3
- NOTE: Historical Runs is user specific, that is each user who logs into the console may have a different number of runs.
Free Disk Space
- Create a new query using the "Historical Dataset" data source.
- NOTE: To Find this datasource, in the Query Builder Wizard click the check box next to "Show Advanced Data Sources", then expand "Bindview Internal Data Sources"
- On the "Field Specification" Tab, add the following to "Selected Fields" at the bottom
- Database Size
- Start Time
- End Time
- Run the query being sure to select the radio button View as Grid.
- Delete the databases from the Grid based on the criteria such as size, age, user name, etc.
- NOTE: The items listed in the Task Manager Window are .MDB files. These are referred to as datasets.
For additional assistance managing disk space, see "How to engage Symantec Support for help with Control Compliance Suite" at http://service1.symantec.com/support/intrusiondetectkb.nsf/docid/2007110510041753.
Article URL http://www.symantec.com/docs/TECH113554