Revolving around the core of technology
Document ID: | 2009 |
---|---|
Subject: | Creating custom reports in Syncrify |
Creation date: | 3/29/12 4:41 PM |
Last modified on: | 11/21/22 1:39 PM |
Field position | Field description |
---|---|
1 | Time backup started. This field is defined in milliseconds since Jan 01, 1970 |
2 | Time backup ended. To get duration, subtract start time from this value. |
3 | Instance number. This is internally used by Syncrify. |
4 | Job number. This is internally used to identify each job |
5 | Total files transferred in this backup job |
6 | Total bytes transferred in this job |
7 | Profile name |
8 | Client's build number |
9 | Client's IP address |
10 | Number of errors |
11 | Name of the CSV file as explained in the Detailed Report section below. |
12 | Next run time - contains milliseconds for the next run. This number should be added to second field (Time backed ended) to give you an absolute time. |
By default, there are several access.log
files, one for every user. When importing these files into SQL server,
it is easier if all of these files are combined by Syncrify into a single file. This is done by following the steps below.
logconfig.xml
file in the installation folder, which is typically C:\Syncrify
or C:\Program Files\Syncrify on Windows and /opt/Syncrify on Linux.logconfig.xml
, in case you need to rollback.logconfig.xml
file in any editor.<appender name="COMBINED_ACCESS_LOG" class="org.apache.log4j.RollingFileAppender"> <param name="File" value="logs/CombinedAccessLog.log" /> <param name="Append" value="true" /> <param name="MaxFileSize" value="5MB" /> <layout class="org.apache.log4j.PatternLayout"> <param name="ConversionPattern" value="%m%n"/> </layout> </appender>The section for
appender
appears towards the top of the file.
<category name="CombinedAccessLog" additivity="false"> <priority value="DEBUG" /> <appender-ref ref="COMBINED_ACCESS_LOG" /> </category>The section for
category
goes towards the bottom of the file.
YYYYMMDD.srep
Field position | Field description |
---|---|
1 | User's email address |
2 | Time backup started. This field is defined in milliseconds since Jan 01, 1970 |
3 | Time backup ended. To get duration, subtract start time from this value. |
4 | Instance number. This is internally used by Syncrify. |
5 | Job number. This is internally used to identify each job |
6 | Total files transferred in this backup job |
7 | Total bytes transferred in this job |
8 | Profile name |
9 | Client's build number |
10 | Client's IP address |
11 | Total Errors |
12 | CSV File name for logs |
13 | Next run time - contains milliseconds since Jan 01, 1970 when next scheduled backup will run |
When this option is turned on, the Syncrify client will send the backup log to the server, which then converts that into a CSV file and saves it to a local folder. These files are located on the $INSTALLDIR/ClientBackupLogs folder.
File names use the following format:
DATE_ELAPSEDTIME.csv
The first token contains a date with the value represented in milliseconds since January 01, 1970. The second token holds the number of
milliseconds the backup ran for.
Do you have a helpful tip related to this document that you'd like to share with other users?