#Veeam backup sql server code

3:23:22 AM 4328 WARN Description = SSL Security error. 3:23:22 AM 4328 WARN Source = Microsoft OLE DB Provider for SQL Server

#Veeam backup sql server code

3:23:22 AM 4328 WARN Code meaning = Unspecified error 3:23:04 AM 4328 INFO Connecting to mssql, connection string: Provider='sqloledb' Data Source='(local)' Integrated Security='SSPI' Persist Security Info=False, timeout: 15 Ok, so checking the helper log I found these, 3:23:04 AM 4328 Using default SQL provider 'sqloledb' to connect to SQL server Failed to truncate SQL server transaction logs for instances: MYINSTANCE. Details: Failed to process 'TruncateSQLLog' command. Unable to truncate Microsoft SQL Server transaction logs. What is worth discussing however is that, once this has been rectified and tls1 was disabled then Veeam Backup & Replication 9.5 could no longer do the application aware processing on MS SQL instances running on these machines. The reasons why it wasnРІР‚в„ўt are out of scope of this blog post. Finally, we rejoiced to see VSS snaps succeeding, SQL backups happening, and data transferring into DPM.A recent vulnerability scan had flagged that the GPO to disable tls1 (think PCIDSS) wasnРІР‚в„ўt picked up by all systems that it should. Then we click РІР‚СљResume BackupРІР‚Сњ on the critical event in the DPM Monitoring console. Plus, changing the value posed no real risk or service restarts (woot!).Р”В«eing conservative as we try to be most of the time, we raised it to 1024 and clicked OK. We resorted more to speculation at this point, but given that 276 databases were attached, SQL background and agent processes also were running, and VSS would need to grab at least 276 threads of its own for the backup, we took a stab in the dark that we might be blowing that 512 cap. Hopping over to MSDN, we looked up the automatically set value for max worker threads in SQL 2014 on a 2-CPU 64-bit server. Of course, it could be deep in there, but the SQL server in question happens to have 276 databases attached, so the errors are prolific. We had most of his errors, but didnРІР‚в„ўt quite have the glaring message about РІР‚СљCannot create worker threadРІР‚Сњ in our events (that we could find). Our third (more like 50th) find was the colorfully-named blog with one of our error codes. The TechNet thread seemed initially promising, but wasnРІР‚в„ўt exactly on track for us and also involved stopping SQL (to re-register SQLVDI.dll). The KB would have helped us narrow down the cause as SQL, but itРІР‚в„ўs a production server (so no stopping the SQL instance), and we already knew SQL was the issue thanks to РІР‚Сљvssadmin list writersРІР‚Сњ. In search for the answer, we came across MS KB 2615182, a Social TechNet thread about SQLVDI errors, and finally a blog about РІР‚Сљvolume shadow barfs with 0x80040e14 codeРІР‚Сњ. Still the same failure.Р”Вigging further into the event logs, we accumulated these: Hyper-V host: Event 10172, Hyper-V-VMMS We restarted VSS writers and even took downtime to restart the VM.

Retrying didnРІР‚в„ўt make a difference this time, though. We had seen an occasional VSS-related backup failure from time to time in DPM, but most were tied to available disk space for the protection group (DPM doesnРІР‚в„ўt do so well with deduplication of images, so growing has been near-continual). Backup method: Crash-consistent image to VSS-quiesced image.Backup product: EMC Avamar 7.0.1 to MS DPM 2012 R2.Hypervisor: vSphere 5.5 to Hyper-V 2012 R2.The third of such SQL environments ran into a host of VSS errors once its data was populated and a backup attempted.

Two of our SQL environments had moved over just fine and were being backed up successfully with Microsoft Data Protection Manager 2012 R2 for the time being (other products are being considered, including Veeam). The transition had been smooth for the most part and we used the project to bring aging Windows/SQL 2008 servers up to 2012 R, respectively.

In our ongoing (sort-of pilot) migration from VMware vSphere 5.5 to Microsoft Hyper-V 2012 R2, we encountered a very concerning and puzzling issue with backups.