Stiffboard

Message also says: You can only specify one of the parameters @databases and @AvailabilityGroups. That will give you all possibilities??

Installing scripts take care of that I believe... One of the variables, SQLLOGDIR I think, is not available in older versions. So if you script the job from a newer...

Hi, did UPPER work without any issues? That's good. I haven't experienced any other collation related conflict. The problem is Case sensitive.

Ther is a check for backup preference before backing up. It really shouldn't go ahead if no backup has been done on other node...then it would delete the last backup....

Modified jobs and prepared my Zabbix monitoring with looking for UpdateStatistics - USER_DATABASES so glad if you decide to go with that name 😃

Search for msg in the output file. Or "come: F" as in Outcome: Failed and you will find a deadlock or something similar.

> I did find an error message on the RESTORE VERIFYONLY FROM DISK command: Command: RESTORE VERIFYONLY FROM DISK = N'\my_path\mydatabase.bak' WITH CHECKSUM [SQLSTATE 01000] Msg3203, Sev 16, State 1,...

I've created PowerShell jobs that restored databases (from one servers backup to another servers instance) using ps1 files...this requires you to add password for the user first time and then...

Not asking for help. My restore script works fine. Just adding information to the request that it might be difficult to use the Cohesity API for backup as it requires...

I haven't come across. I've only used the PowerShell scripts here on GitHub to schedule restore from prod to test environments. But PowerShell isn't very good as jobsteps in server...