Backup copy job to cloud connect provider stuck

[sambsamb]

Backup copy job to cloud connect provider stuck "waiting for new restore points"

Steps attempted to troubleshoot: - Delete and recreate backup copy job. - "Remove from disk" all backups under this job under backups\cloud - Synchronize cloud repository - Ask cloud connect provider to make sure cloud repository is empty and try again - Identical backup copy job to another cloud connect provider works just fine - Right click/Sync now - Start the underlying backup job manually to ensure a new restore point is available on local repository - Same thing happens with/without using WAN accelerator

Other information: - Hyper-V environment - Off-host proxy - Hardware VSS provider: EqualLogic - 1 Hyper-V cluster including 15 VMs - about 400GB total

I don't know if anyone has seen this before.

[foggy]

Sam, need more details like the copy job configuration (sync interval specifically) and backup job schedule. Does it get stuck right after creation (so before processing anything) or after the initial sync is performed?

[sambsamb]

https://onedrive.live.com/?cid=c632399f ... 59%2117967

[veremin]

I'm wondering when the latest restore point was created by source backup job. Thanks.

[foggy]

And what about other questions?

... backup job schedule. Does it get stuck right after creation (so before processing anything) or after the initial sync is performed?

[sambsamb]

Veeam support examined the logs that showed that the underlying backup job block size changed. As a result the backup copy job could not identify new restore points.

[02.12.2014 00:03:21] <01> Info [OibFinder] Following Oibs are located in storages with different (KbBlockSize256 expected) block sizes and excluded from search:
[02.12.2014 00:03:21] <01> Info id='5af64457-e94a-4053-a166-e8319ad176ee', time='11/13/2014 10:21:17 PM', block_size='KbBlockSize1024'

The solution was to do an Active Full. This immediately fixed the problem.
This case is resolved.

[foggy]

Thanks for letting us know, much appreciated. However, I'm a bit confused by the fact it did not warn about different block size right in the job session window, as it did previously.