Did you ever run that SQL code above? I think that may be your issue. Run it on one of the DBs that's failing.
I ran it on one of the DBs failing with the arithmetic overflow.
It returned a value of 418.94
Ok, run the backup from BackupDB instead of BackupMaster.
Also try running it with @StmtOnly = 1. That'll tell me more about the nature of the problem.
I switched gears and am now trying it in Production, where all DBs back up successfully except one (which gets the arithmetic overflow), and there is no path error to muddy the waters.
I ran the BackupDB stored procedure there, and it returned the following error (regardless of the StmtOnly parameter):
Msg 8115, Level 16, State 6, Procedure Minion.DBMaintDBSizeGet, Line 195 [Batch Start Line 1]
Arithmetic overflow error converting float to data type numeric.
I also got this same error in Production when running the short GetSize script you sent earlier. )Note that in Production, I am still running Minion Backup 1.4.)
Previously in Production, one of my DBA colleagues ran a native full backup on the same data base, and that worked perfectly.
Believe it or not that's good news. Tell me how big is that failing DB in prod?
This DB is 3.7 TB in size. There is also another big DB on another Production server that is failing. It is 4.8 TB. I'm willing to bet there are others as well on other servers.
I don't know if you installed that last version of DBSize I sent, but it looks like you may not have. I've attached it again.
Sean,
I'm opening a change form to update Minion to 1.5 with the size fix on the Production SQL Servers tonight. Those do not have the path issue that exists in Test.
Sure, but you could just install the new size sp under a new name and test it w/o any trouble. This way you'll know if it'll actually fix your problem.
Perfect. Let me know if you need anything else.
Also, just replace that file in your install folder and you'll be good to go.
Yes, the backup is running now.
Thank you for your help.
I'm afraid things are still not working correctly.
Last night, on multiple SQL Servers running Minion Backup 1.4, I updated DBMaintDBSizeGet. To do that, I also had to add MMAGInfo, MMSQLInfoGet, and MMCmdServerNameGet because of Missing Dependency messages.
The log backups kept running normally everywhere (as they always have). In Test (where Minionware is in its own DB), the differential backups seemed to run normally as well (those are usually smaller data bases), though on the server with the path errors (Windows support looking into that), there were still some arithmetic overflow errors.
However, on my Acceptance and Production SQL Servers, which have availability groups (and Minionware is in the master DB), the differential backups for all data bases returned this error:
"FATAL ERROR: @BackupCmd is empty. Common causes are misconfigured BackupSettings and BackupTuningThresholds tables. If you need help configuring them, consult the documentation as it has examples of proper configurations outlined."
I checked the backup settings and they look normal.
What could the problem be, how do we fix it, and why does it behave differently in Test than in Acceptance and Production?
Let me know what info you need to troubleshoot.
Thanks!
Yeah, let's hookup today and do some live tshooting. You have my email right? If so, then send me a couple times that work for you.
Sean,
I've found another problem, possibly related to the last fix we did. This is happening on a server that does not have an availability group.
On a simple recovery or full recovery data base, BackupMaster works fine, but when I try to do any type of backup (full, diff, log) using BackupDB, it gets this error in SSMS (3 times if it's a log backup):
Msg 201, Level 16, State 4, Procedure Minion.MMAGInfo, Line 0 [Batch Start Line 4]
Procedure or function 'MMAGInfo' expects parameter '@AGRole', which was not supplied.
In the log, it says that @BackupCmd is empty.
There's a different problem with full recovery data bases, BackupMaster works fine for Full and Diff backups, but for log backups, it looks like it works in SSMS (same output as for Full and Diff), but in the BackupLogDetails, it has a Fatal error (same one as above):
FATAL ERROR: HResult 0xC9, Level 16, State 4 Procedure or function 'MMAGInfo' expects parameter '@AGRole', which was not supplied. HResult 0xC9, Level 16, State 4 Procedure or function 'MMAGInfo' expects parameter '@AGRole', which was not supplied. HResult 0xC9, Level 16, State 4 Procedure or function 'MMAGInfo' expects parameter '@AGRole', which was not supplied.
Please advise.
Richard Seltzer
I have Minion Backup 1.4 installed on many of my SQL Servers, and on several (including Production), I am getting fatal arithmetic overflow errors when it tries to do a full or a differential backup. Transaction log backups continue to run successfully.
The Status column of the BackupLogDetails menu says "FATAL ERROR: Arithmetic overflow occurred."
Other backups on the Production server are running successfully.
There is no error message in the SQL Server Error Log around that time, so I believe this is a Minion Backup issue. I don't see any other information abut the error in the Minion logs.
Please advise as soon as possible