Macrovision Corporation SAMREPORT-LITE 2005, Manual

Page: 36 / 44

32
|
Appendix A Enabling and Managing Report Logs
1 Rotate a report log. To avoid corruption in your report logs, we recom-
mend that you rotate your logs with the FLEX
lm utility,
lmswitchr
(found in the
lmtools
interface).
2 Update the vendor daemon’s options file(s).
3 Move the older report log to a designated location.
4 Archive (and probably compress) a report log when it is no longer needed
to run reports.
You must rotate a report log at the following times:
■ If you move the license server to a new machine.
If SAM report -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 a vendor daemon name changes.
If SAM report -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.
Note You can corrupt a report log by rotating it incorrectly. A report log must
begin with a header that is written by the vendor daemon. Without this header,
the report log is corrupted. The data in the report log is unusable and unsalvaga-
ble from the start of the report log until the first time in that report log that the
license server is restarted.
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.