job take 8 to end after finish backup all vm

[bensh]

since i upgrade from v7 to v8 i had a problem with specific job i cahnged from synthetic full to revers incremnetal
after the job is finish to backup all vm it takes like 8 hours to finish.
at other job i canged from synthetic full to revers incremnetal works good.
any suggestion?

[Vitaliy S.]

What is your destination target and bottleneck stats for both backup job configurations?

[bensh]

destination target is lun from storage
bottleneck is source 82%
destination for the good job is othe lun from same storage
bootleneck is source 67%

[Vitaliy S.]

Also one question I forgot to ask... Does it take 8 hours to finish incremental run or synthetic full creation?

[bensh]

since i upgrade to version 8 it's forever incremnetal.
but i think i was misunderstood , it's finish to backup in good time , but the job still running 8 more hours after
all the vm finish.

[veremin]

but i think i was misunderstood , it's finish to backup in good time , but the job still running 8 more hours after all the vm finish.

You mean there is a transformation activity taking place? Do you see something like "Merging oldest incremental backup into full backup file"?

Thanks.

[Vitaliy S.]

In addition to Vladimir's question, can you please navigate to job session and tell us what operation takes most of the time in the log?

[bensh]

all the vm on status processing finished at , but the job still run
1.how cn i upload screenshot ?
2.how can i find the log path ?

[Vitaliy S.]

You can place the screenshot of the job session in any 3rd party hosting site and then post a link to this page. As to logs retrieval, then you can do that via Help->Support Information and ask our technical team with its review.

[bensh]

http://postimg.org/image/uumh6yxft/

thats exactly the situation the all the vm is finish and the job still running

and the logs still write events
[storagelock] relocking storages for retention alg as write only
[storagelock] resolving lock conflict with current session id
[storagelock] locking additional storages as write for retention alg
[storagelock] storage(s) have been locked , lockids
[leasekeeper] create , ttl 300sec
[backupmeta] generate backup meta for

[dellock6]

Ben, just a not if you are concerned about privacy, the name of the VMs are visible in the details on the right even if you cancelled them on the left.

[Vitaliy S.]

What about the debug log file? Can you send it to our technical team for review and post your case ID for future readers?

[bensh]

i didn't open an case , i will do it right now

[bensh]

after i open case and upload logs
veeam support suggest me to cancel under advanced settings the vm retention "remove deleted vms data from backup after"
after that the job works good.