This product tracks the last SMF record dumped from a logstream, so there is no need to make any major changes to retry a logstream dump. Make any corrections that are needed, and restart the procedure or resubmit the dump job.
When not using ARCHIVE, the logstream files do not get emptied when dumping and are more like a continuous queue of data. While it is important to archive data properly, the process of archival is not as urgent as it has been before. The only concern is to ensure that the dump is completed before the records are deleted from the logstream that is based on the logstream's autodelete policy.
When using ARCHIVE when dumping, the data is removed from the logstream once a dump completes successfully. This means that the data has been copied into CA SMF Director’s history files and has been indexed. Once this procedure is completed, then and only then is the data removed from the logstream. As with dumping without ARCHIVE, if there is a failure, the dump process job can be resubmitted or restarted once any errors have been corrected.
Note: The time it takes to make the correction, more SMF data can be added to the logstream, therefore it is important to check to see that SMFDOUT is sufficiently large (if on DASD) to handle the records from the previous dump as well as any new records that are added.
|
Copyright © 2014 CA Technologies.
All rights reserved.
|
|