VeeamON 2024 - Use Code "COMMUNITY10" for 10% Off!
Thanks Chris. I thought that same thing - that SQL doesn’t understand the Veeam PS commands. Wouldn’t modifying the global (PowerShell) profile fix that? Then, regardless of what user is logged in, the Veeam modules would be loaded. Why does it work as a Windows Scheduled Task and not a SQL job. I’d like to fix this problem so that it can be demonstrated that Veeam can interact with SQL. Otherwise, other DBAs, like myself, are going to have issue using this product… :-(
Hey Chris, Let me check that out...
Bummer… I’m still getting this error message when I run the script in a SQL job:The term 'Start-VESQLRestoreSession' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
OK…. When I run that command interactively now, using the import-module command, I get this message: WARNING: The names of some imported commands from the module'Veeam.Backup.PowerShell' include unapproved verbs that might makethem less discoverable. To find the commands with unapproved verbs,run the Import-Module command again with the Verbose parameter. For a list of approved verbs, type Get-Verb. Any thoughts?
Thanks Joe. I appreciate everyone’s comments here. I’m sure that it’s something simple that I’m overlooking. I guess it’s time to roll up the sleeves and debug this code…If, and when, I discover the solution, I’ll share it with the group.
Update: Since I originally posted this question, I have been successfully restoring the SQL database on a daily basis using a (Windows) Scheduled Task. However, until today, the SQL job created to restore the database has been unsuccessful. For mysterious reasons that I can’t explain, it’s now working correctly as a SQL job. I’m going to test it some more but it’s working!
My next step is to replicate this environment on the backup (DR) server and get it working there. Once that’s successful, I will move the final product to production...
Thanks for your prompt replies. I generate a report every morning and, across all of the SQL servers I manage, the VeeamBackup database is the only on that it shows that’s not backed up. So, if that’s the case, then I want to make sure that it gets backed up one way or another. Maybe I need another way to verify that the backups were done….
I have a series of PowerShell reports that I review every morning. They are set up to send me emails upon completion and include a full array of information that includes a summary of SQL errors, job failures, integrity (DBCC) checks, and other metrics that have occurred within the past 24 hours. These reports are in addition to the alerts and (job) failure notifications that I get. This information have been very helpful in the past. So, I’d like to continue using them. According to these scripts, the VeeamBackup database isn’t being backed up. It sounds like a native backup of that database is the way to go…..
Thanks for your suggestions! I appreciate all of your comments. It’s time that I take a different look at this problem and, hopefully, come up with a different solution.
Already have an account? Login
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.
