As part of the archive process, the system creates uniquely named archive files and folders that identify the type of archive (manual or scheduled) and the date on which the archive was performed.
By default, these folders are located in the Archives directory where the Enterprise Server or Enterprise Central are installed. However, you can change the directory to another valid location.
During the archive process, the system creates a new folder in the path specified in the Archive Settings Manager. The system generates and then places the CSV or XML files within this folder. To prevent accidental overwriting, the system uses the Method_date.file extension format, which makes the folder name unique. For example, if you manually generate an archive on April 11, 2012, the system creates a folder named Manual_Archive20120411 (yyyymmdd). If you generate an archive the following day, the system creates a new folder with the new date.
When archiving is enabled, the system creates resource files that collect the data from the selected extended trend logs prior to archiving. The system names the files using random hexadecimal characters, such as a2d9e877, and then places them in the path specified in the Archive Settings Manager. These files should not be deleted.
The system names extended trend log archive files using the Method_(Address)_date.file extension format. If you generate a manual archive in CSV format for extended trend logs on on July 8, 2012, the system names the file, Manual_Archive_(Server_1_<Extended_Trend_Log name>)_2012-07-01_2012-07-08.csv.
The system names the event log archives using the Method_(EventLog)_date.file extension format. If you manually generate an archive on April 11, 2012 for the Alarm, User, and System events, the system names the archive file Manual_Archive_(Server_1_System_Events_EventLog_EventRecords)_2012-04-02_2012-04-11.csv.
If you generate more than one archive file on the same date, the system appends a number to the end of each similarly named archive to ensure that the files are not overwritten. For example, if you manually generate an archive named Manual_(Server_1_System_Events_EventLog_EventRecords)_2012-04-02_2012-04-11.csv and immediately generate another identical archive, the system names the second archive, Manual_(Server_1_System_Events_EventLog_EventRecords)_2012-04-02_2012-04-11_1.csv. Using the appended number (_1), the system creates a unique name for the second archive with the same method on the same date.
You use a structured database editor to view archive information in rows and columns, which may contain text strings, paths, identities, or enumeration values.
Para obtener más información, consulte Archive Log Contents .