-
- Novice
- Posts: 5
- Liked: never
- Joined: Oct 18, 2019 2:00 pm
- Full Name: Marcus Deubel
- Contact:
SQL Server restore speed up
Hi there,
is it planned to use instant file initialization for Veeam SQL Server databases?
it would speed up significantly the restore time.
Right now we do some testing and can confirm that in our scenario the restore with veeam is three times slower than using the SQL Server restore command
and instant file initialization enabled for the SQL Server Service account.
Regards
Marcus
is it planned to use instant file initialization for Veeam SQL Server databases?
it would speed up significantly the restore time.
Right now we do some testing and can confirm that in our scenario the restore with veeam is three times slower than using the SQL Server restore command
and instant file initialization enabled for the SQL Server Service account.
Regards
Marcus
-
- Veeam Software
- Posts: 21138
- Liked: 2141 times
- Joined: Jul 11, 2011 10:22 am
- Full Name: Alexander Fogelson
- Contact:
Re: SQL Server restore speed up
Hi Marcus, if I'm getting it right, then it should work transparently for Veeam B&R, since it is configured on the SQL Server itself and Veeam B&R doesn't control these settings when restoring databases.
-
- Chief Product Officer
- Posts: 31804
- Liked: 7298 times
- Joined: Jan 01, 2006 1:01 am
- Location: Baar, Switzerland
- Contact:
Re: SQL Server restore speed up
Most likely, this is an "apple to oranges comparison" issue, as opposed to anything else.
There will always be some performance difference, since you're performing a restore from different backup formats: native SQL database backup vs. deduplicated image-level backup of the entire SQL Server VM that has the required database file fragmented across the VM image. Plus, when doing such tests you should always make sure both backups are sitting on the same storage volume.
There will always be some performance difference, since you're performing a restore from different backup formats: native SQL database backup vs. deduplicated image-level backup of the entire SQL Server VM that has the required database file fragmented across the VM image. Plus, when doing such tests you should always make sure both backups are sitting on the same storage volume.
-
- Novice
- Posts: 5
- Liked: never
- Joined: Oct 18, 2019 2:00 pm
- Full Name: Marcus Deubel
- Contact:
Re: SQL Server restore speed up
It's not a SQL Server option. It's a operating system permission.
-
- Novice
- Posts: 5
- Liked: never
- Joined: Oct 18, 2019 2:00 pm
- Full Name: Marcus Deubel
- Contact:
Re: SQL Server restore speed up
Most likely, it's a real world comparision and we don't talk about vms here.Gostev wrote: ↑Nov 01, 2019 9:41 pm Most likely, this is an "apple to oranges comparison" issue, as opposed to anything else.
There will always be some performance difference, since you're performing a restore from different backup formats: native SQL database backup vs. deduplicated image-level backup of the entire SQL Server VM that has the required database file fragmented across the VM image. Plus, when doing such tests you should always make sure both backups are sitting on the same storage volume.
A three times slower restore with Veeam B&R is not some performance difference.
The reason why Veeam B&R is so slow with a restore is the fact that they do an ordenary file copy over iSCSI and don't use instant file initialisation as recommended by Microsoft.
BTW. How do I restore dbs with Veeam B&R if the iSCSI protocol is not permitted in the LAN?
-
- Chief Product Officer
- Posts: 31804
- Liked: 7298 times
- Joined: Jan 01, 2006 1:01 am
- Location: Baar, Switzerland
- Contact:
Re: SQL Server restore speed up
Sorry, it doesn't actually matter if it's a VM or not.
What matters the most is that you're comparing restore speed from an image-level backup of the entire SQL Server machine vs. application-level backup of the specific SQL Server database. The issue that Instant File Initialization is intended to solve doesn't exist for Veeam in the first place, because image-level backups force us to perform database file restore in a certain way, which is absolutely different than restore from a native SQL backup into the newly provisioned database file.
If iSCSI protocol is not permitted in the LAN, you could install Veeam console on the SQL Server itself, and import backups from the remote repository (this will not use iSCSI).
What matters the most is that you're comparing restore speed from an image-level backup of the entire SQL Server machine vs. application-level backup of the specific SQL Server database. The issue that Instant File Initialization is intended to solve doesn't exist for Veeam in the first place, because image-level backups force us to perform database file restore in a certain way, which is absolutely different than restore from a native SQL backup into the newly provisioned database file.
If iSCSI protocol is not permitted in the LAN, you could install Veeam console on the SQL Server itself, and import backups from the remote repository (this will not use iSCSI).
Who is online
Users browsing this forum: No registered users and 119 guests