{"id":99,"date":"2018-07-16T09:13:20","date_gmt":"2018-07-16T07:13:20","guid":{"rendered":"https:\/\/vmoller.dk\/?p=99"},"modified":"2018-07-16T09:24:48","modified_gmt":"2018-07-16T07:24:48","slug":"veeam-9-5-update-3a-and-sql-backups","status":"publish","type":"post","link":"https:\/\/vmoller.dk\/index.php\/2018\/07\/16\/veeam-9-5-update-3a-and-sql-backups\/","title":{"rendered":"Veeam 9.5 update 3a and SQL backups"},"content":{"rendered":"<p>Ill like to highlight that after updating \u201cVeeam Backup and Replication\u201d to \u201cversion 9.5 update 3a\u201d you might start to see warnings like this in your Veeam status reports:<\/p>\n<p><div id=\"attachment_100\" style=\"width: 1512px\" class=\"wp-caption alignnone\"><img loading=\"lazy\" decoding=\"async\" aria-describedby=\"caption-attachment-100\" class=\"wp-image-100 size-full\" src=\"https:\/\/vmoller.dk\/wp-content\/uploads\/2018\/07\/veeamsqlerror.jpg\" alt=\"\" width=\"1502\" height=\"230\" srcset=\"https:\/\/vmoller.dk\/wp-content\/uploads\/2018\/07\/veeamsqlerror.jpg 1502w, https:\/\/vmoller.dk\/wp-content\/uploads\/2018\/07\/veeamsqlerror-300x46.jpg 300w, https:\/\/vmoller.dk\/wp-content\/uploads\/2018\/07\/veeamsqlerror-768x118.jpg 768w, https:\/\/vmoller.dk\/wp-content\/uploads\/2018\/07\/veeamsqlerror-1024x157.jpg 1024w\" sizes=\"auto, (max-width: 1502px) 100vw, 1502px\" \/><p id=\"caption-attachment-100\" class=\"wp-caption-text\">Warning:\u00a0[TDB]Unable to update SQL backupset for instance : Code = 0x80040e09 Code meaning = IDispatch error #3081 Source = Microsoft OLE DB Provider for SQL Server Description = The UPDATE permission was denied on the object &#8216;backupset&#8217;, database &#8216;msdb&#8217;, schema &#8216;dbo&#8217;.<\/p><\/div><!--more--><\/p>\n<p>The reason for this is that in \u201cupdate 3a\u201d Veeam has changed their way of taking backing up and handling the transaction log of MS SQL servers.<\/p>\n<p>Veeam <a href=\"https:\/\/www.veeam.com\/kb2689\">KB2689<\/a> will give you some useful information on this topic.<\/p>\n<p>I have a dedicated account on the domain called \u201cVeeamVSS\u201d which I\u2019m using for all domain servers so the only thing that I did to solve the problem was to include &#8220;VeeamVSS&#8221; in the local \u201cLog on as a batch job\u201d group on the SQL server and then assign it the \u201csysadmin\u201d role inside the SQL server.\u00a0If you would like to know more about the needed permissions for SQL db and log backup for Veeam, then look here in the Veeam helpcenter: <a href=\"https:\/\/helpcenter.veeam.com\/docs\/backup\/explorers\/vesql_permissions.html?ver=95\">Link<\/a><\/p>\n<p>The backup email report is again showing my favorite color \u2013 <span style=\"color: #008000;\"><strong>GREEN!<\/strong><\/span><\/p>\n<p>The above issue was also mentioned in Anton Gostev weekly newsletter, which I can highly recommend that you assign yourself to. Here is a guide on subscribing to his weekly digest: <a href=\"https:\/\/www.cragdoo.co.uk\/2018\/04\/23\/veeam-weekly-digest-how-do-i-get-it\/\">Link<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"<p>Ill like to highlight that after updating \u201cVeeam Backup and Replication\u201d to \u201cversion 9.5 update 3a\u201d you might start to see warnings like this in your Veeam status reports:<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"footnotes":""},"categories":[18],"tags":[19],"class_list":["post-99","post","type-post","status-publish","format-standard","hentry","category-veeam","tag-veeam"],"_links":{"self":[{"href":"https:\/\/vmoller.dk\/index.php\/wp-json\/wp\/v2\/posts\/99","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/vmoller.dk\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/vmoller.dk\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/vmoller.dk\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/vmoller.dk\/index.php\/wp-json\/wp\/v2\/comments?post=99"}],"version-history":[{"count":5,"href":"https:\/\/vmoller.dk\/index.php\/wp-json\/wp\/v2\/posts\/99\/revisions"}],"predecessor-version":[{"id":106,"href":"https:\/\/vmoller.dk\/index.php\/wp-json\/wp\/v2\/posts\/99\/revisions\/106"}],"wp:attachment":[{"href":"https:\/\/vmoller.dk\/index.php\/wp-json\/wp\/v2\/media?parent=99"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/vmoller.dk\/index.php\/wp-json\/wp\/v2\/categories?post=99"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/vmoller.dk\/index.php\/wp-json\/wp\/v2\/tags?post=99"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}