Azure SQL Policy - Elastic Pool

[scrat]

Hi team,
I've already opened a ticket with support but the analysis is a bit slow, so I'm asking here too, to see if anyone in the community has experienced this.

I have a SQL Server on Azure with an Elastic Pool configured. That server has 2 databases, one with a size of 700G and another with 1300G. When Veeam tries to copy the databases to the staging server, the 1300G one gives the error:
Long running operation failed with status ‘Failed’. Additional Info: ‘The specified max size is invalid.’

The other DB, the 700G, is created with 2 vCores (MaxSize = 1TB), and I have the impression that it tries to do the same with the 1300G DB and that's why it gives the error.

Is it possible check in the logs the Performance Tier with which it tries to create the DB?

I have asked in the case if "elastic pool" is supported or not, I don't see anything in the documentation.

Thanks,
Best regards.

[lyudmila.ezerskaya]

Hi! Could you please share the support case ID for clarity?
We’ll review the details and respond to your questions shortly.