Product specifications

History Configuration
360 3BDS011222-510 B
13. History logs will not collect data until they are activated. Test the operation of
one or more property logs. You can use the Status tab on the Log Configuration
aspect, or you can use one of the installed desktop tools such as DataDirect or
Desktop Trends.
The file system must be in a consistent state at all times. Defragment disks on a
regular basis using the defragmentation software provided with the operating
system.
• Size disks so they will be 25 percent empty for
defragmentation purposes.
• Check the system for fragmented files on all nodes where
trend and history logs reside, and defragment the applicable
disks as required.
• History configuration impacts not only the History Server
disks, but also Connectivity Server disks where trend logs
are configured. Therefore, check the disks on Connectivity
Servers where trend or history logs reside, and defragment
them as required.
• Extensive use of the Bulk Configuration tool may cause
disks to become fragmented. Check the system for
fragmented files after any such procedure, and defragment
disks as required.
• Configuration procedures that involve creating, deleting,
and then recreating of a large quantity of objects may cause
the associated disks to become fragmented. Check the
system for fragmented files after any such procedure, and
defragment disks as required.
• Deleting and then creating the Aspect System may cause
associated disks to become fragmented. Check the system
for fragmented files after any such procedure, and
defragment disks as required.
Even though server components keep most of their data in cache, it is fairly disk
intensive. Thus they may benefit from RAID 5 systems.