Summary
If the backup is slow, it may be caused by disk load or network.
In troubleshooting such a situation, check the performance by setting the parameters.
Open the aip.ini in the installation path and add the parameter in the [aipcopy] section.
[aipcopy]
profile_data_pipeline=1
The information is acquired by the next tasklog, if you add a parameter.
— tasklog excerpt —
03/29/2018 02:10:47.069 [config] profile_data_pipeline=1
03/29/2018 02:10:47.069 actual threadcount 4
03/29/2018 02:10:47.070 actual packet_queue_size 4
03/29/2018 02:57:51.838 Busy for what:
STATUS_CREATE_READ: 0 / 18737 347
STATUS_CREATE_ZERO_UNUSED: 0 / 18737 0
STATUS_CREATE_CALC_CRC: 0 / 18737 15
STATUS_CREATE_DEDUP: 0 / 18737 0
STATUS_CREATE_COMPRESS_LZO: 0 / 18737 622
STATUS_CREATE_COMPRESS_ZLIB: 0 / 0 0
STATUS_CREATE_COMPRESS_eLZS: 0 / 0 0
STATUS_CREATE_ENCRYPT_RC5: 0 / 0 0
STATUS_CREATE_ENCRYPT_AES: 0 / 0 0
STATUS_CREATE_ENCRYPT_AES256: 0 / 0 0
STATUS_CREATE_WRITE: 0 / 18737 2869
————————
How to read logs.
STATUS_CREATE_READ: 0 / 18737 347
—> This is the number of times and the time that snapshot was read in the process of creating an image.
18737 times of reading are executed which took 347 seconds.
STATUS_CREATE_WRITE: 0 / 18737 2869
—> It is the number of times and the time that writing to the destination in the process of creating the image.
18737 times of reading are executed which took 2869 seconds.
Comparing this time, the write time is about 8 times.
Therefore, it can be concluded that writing to the destination is slow.
Resolution
In the case of NAS, it is thought to depend on network load and the NAS.
In the case of a local disk, check the write policy of the disk controller and the load of the OS.
Comments
0 comments
Article is closed for comments.