Hi,
We have a customer who is testing the Veeam SQL Plug-in instead of creating local native SQL backups.
With the native backup, he is using the attributes 'CHECKSUM' and 'RESTORE VERIFYONLY'. These options are not available with the Plugin.
I found this post about the verify option: veeam-backup-replication-f2/v12-veeam-p ... 85221.html
Any news about it?
About the Checksums, does Veeam also create them for plug-in backups by default? It's a different approach, but it's something..
-
- Enthusiast
- Posts: 26
- Liked: 1 time
- Joined: Feb 05, 2019 9:59 am
- Full Name: DBeerts
- Contact:
-
- Veeam Software
- Posts: 3818
- Liked: 643 times
- Joined: Aug 28, 2013 8:23 am
- Full Name: Petr Makarov
- Location: Prague, Czech Republic
- Contact:
Re: MS SQL Plugin missing arguments
Hello,
These requests are absolutely valid and valuable for the plug-in. However, the status remains the same: I want to include this functionality in one of our future releases, but I'm not ready to provide even preliminary estimations.
Regarding checksums, the plug-in utilizes our core storage engine, which involves storing data blocks in the backup with MD5 checksums. By default, digests are calculated by the Data Mover on the source (by the way, you can move this operation to a repository to reduce CPU load). If there is a backup data corruption (f.g. hardware issue) and a checksum change, a recovery operation will fail.
I also recommend performing periodic test restores if you have a test environment that is isolated from production. Additionally, you can use our backup copy job to adhere to the 3-2-1 rule.
Thanks!
These requests are absolutely valid and valuable for the plug-in. However, the status remains the same: I want to include this functionality in one of our future releases, but I'm not ready to provide even preliminary estimations.
Regarding checksums, the plug-in utilizes our core storage engine, which involves storing data blocks in the backup with MD5 checksums. By default, digests are calculated by the Data Mover on the source (by the way, you can move this operation to a repository to reduce CPU load). If there is a backup data corruption (f.g. hardware issue) and a checksum change, a recovery operation will fail.
I also recommend performing periodic test restores if you have a test environment that is isolated from production. Additionally, you can use our backup copy job to adhere to the 3-2-1 rule.
Thanks!
Who is online
Users browsing this forum: No registered users and 3 guests