Incremental: How does Veeam handle restored SQL databases?

[bunger]

I am doing reverse incremental backups nightly.

I noticed that one of my 6 servers takes about 2.5 hours to backup, while the others take that much time combined. When digging into the specifics on that one server, I am finding that we have a SQL Server database that is being restored nightly to that server. Essentially, it is a copy of another production database that is used for reporting. Each night's restoration for that database is 185GB.

Is it possible that Veeam is seeing that entire database as new and backing up the entire 185GB every night? If so, are there any other options I might employ to only backup changes to the DB instead of the entire thing?

Thanks in advance!

[PTide]

Hi,

Is it possible that Veeam is seeing that entire database as new and backing up the entire 185GB every night?

It is not only possible, it is the reason why your backup takes so long. May I ask you why do you need to backup the copy of a database?

Thanks!

[foggy]

I'd place the restored DB on a separate disk and exclude it from the backup job. You do back up the original DB server, right?

[bunger]

Foggy - that is where I am leaning.

The vendor for that database is requiring that specific setup, so I can't get around it.

[chrisdearden]

You could use the file level exclusions as well.