unable to meet data policy

[pswiatek]

Has anyone experience an warning in Veeam 9 that says Moving backups to extent XXXXX (unable to meet data placement policy) ?

We have Two repository servers

Repo-A is suppose to store incremental and Repo-B is suppose to store full backups.

Repo-A has 3.06TB Free out of 5TB, and Repo-B has 14.0TB out of 21.5TB Free,

Veeam is not storing the incrementals on the proper extent, and give us the error.

We have opened a ticket with support 01693389, but have not heard back yet.

[nielsengelen]

Hi,

I notice your case is being handled and it's best to let support handle this for now to see why you are getting this error.

[veremin]

The quoted message means that backup should have been placed on one extent (as it's dictated by the specified policy), but due to some force majeur, such as absence of free space or something different, it was placed on other extent.

However, it seems that both extents have quite a lot of free space, so, the described behaviour doesn't look expected and should be investigated by support team.

Thanks.

[soehl]

Hi,

we have the same issuse, exist a easy solution for the problem?!

Thanks.

[foggy]

In OP's case, active full backup helped to resolve the issue. Btw, do you have Veeam B&R v9 Update 2 installed?

[soehl]

Okay, i will try a full backup on a few jobs that have that issue. If that don´t help I will open a support case.
B&R 9 Update 2 is installed since it was available.

Thanks!

[foggy]

Even in case full helps, feel free to contact support if you observe similar behavior later again.

[d3nz]

Hello guys.
Any news about fixing this warnings?

[d3nz]

I mean is it possible to fix this warnings without creating active full backup?
We haven't abbility to do it, too much data.

[veremin]

Have you reached our support team to investigate the root cause of the behaviour experienced? Thanks.

[wandersick]

Hello,

We have the exact same issue on Veeam 9.5 Update 3 and we are planning to solve it with an Active Full backup. Just wondering (if this is a product issue) whether updating Veeam to 9.5 Update 3A would help with the issue or not? (If not, will a future version do?)

Thanks.

[foggy]

I'd contact technical support first to verify the nature of the issue. If there's a more elegant solution than performing an active full, they will advise you.