Remember that you can produce a report from multiple report logs as long as each report log is written by a single vendor daemon running on a single machine. (Vendor daemons running on more than one redundant server must write to their own report logs.) Therefore, to keep the size of report logs manageable, you should regularly close out a current report log and begin to write to a new one. This process is known as rotating report logs. A recommended method for rotating report logs is provided later in this section.
You may want to automate the process of managing each license server's report logs. The following steps can be performed on a regular basis:
You must rotate a report log at the following times:
If SAMreport-Lite detects that the license server hostid changes in a report log used to generate a report, it will stop processing the report log and include only the data preceding the hostid change in the report.
If SAMreport-Lite detects that the vendor daemon name changes in the report log used to generate a report, it will stop processing the report log and include only the data preceding the vendor daemon name change in the report.
You may want to rotate a report log at a regular time interval, such as weekly or monthly, depending on how quickly the report log grows. The rotation of a report log does not need to be tied to the interval over which you run your reportsâ€”remember that you can run a report on multiple report logs and that you can filter report data with designated start and end dates. You may also want to rotate report logs when the license limit for a feature changes, but alternatively, you can also set start and end date filters to isolate usage for given license limits.
The report log will have no header and will be corrupted if you manually copy an active report log to a new file name, delete the original active report log, and keep the vendor daemon writing to the original active report log file name.