Comments
Sort by recent activity
Hi Jon, thanks for your suggestion, I'll check it out [image] / comments
Hi Jon, thanks for your suggestion, I'll check it out
Hi @Jon_Kirkwood thank you very much for your suggestions. My colleagues had a play around with them and are pretty close to what we were hoping for! / comments
Hi @Jon_Kirkwood thank you very much for your suggestions. My colleagues had a play around with them and are pretty close to what we were hoping for!
Hi all, I believe I have figured out what I'm doing wrong. The issue only occurs if I am editing a job that had a one-off schedule, not a repeating one. So, if I have an ad-hoc backup job that runs just once, if I then edit the schedule, because it's run successfully its 1 scheduled time, the schedule remains disabled, and so I have to manually enable it. It's not (for me) the expected behaviour but I can see why it happens. / comments
Hi all, I believe I have figured out what I'm doing wrong. The issue only occurs if I am editing a job that had a one-off schedule, not a repeating one.So, if I have an ad-hoc backup job that runs...
Hi, I'm on SQL Backup version 10.1.15.1874 and this behaviour has been seen on SQL 2017 RTM CU15. Thanks, Ric. / comments
Hi, I'm on SQL Backup version 10.1.15.1874 and this behaviour has been seen on SQL 2017 RTM CU15.Thanks,Ric.
Hi @Jon_Kirkwood our example is a SQL 2017 RTM Enterprise Edition clustered instance hosted on 2 Windows Server 2012 Datacenter servers. A manual upgrade as specified in the documentation was successful so we are now on 10.1.15 / comments
Hi @Jon_Kirkwood our example is a SQL 2017 RTM Enterprise Edition clustered instance hosted on 2 Windows Server 2012 Datacenter servers.A manual upgrade as specified in the documentation was succes...
Hi, not hijacking this thread but I am also experiencing the same issue on 1 particular server (other servers show the upgrade components window absolutely fine). Just an FYI in case it's something more. Thanks. / comments
Hi, not hijacking this thread but I am also experiencing the same issue on 1 particular server (other servers show the upgrade components window absolutely fine). Just an FYI in case it's somethin...
Hi @Ben_P thanks for that. I found the same part of the documentation over the weekend. Now to speak to the team who created the server(s). / comments
Hi @Ben_P thanks for that. I found the same part of the documentation over the weekend. Now to speak to the team who created the server(s).
Hi @Ben_P to clarify, in our Azure portal when looking at the resource, it should be the login shown as the Server Admin in the Essentials section? Server admin: xxxxxxx / comments
Hi @Ben_P to clarify, in our Azure portal when looking at the resource, it should be the login shown as the Server Admin in the Essentials section?Server admin: xxxxxxx
please remove, I accidentally logged the question in the wrong product forum. I've reposted in the correct forum so this is no longer needed. Thanks. / comments
please remove, I accidentally logged the question in the wrong product forum. I've reposted in the correct forum so this is no longer needed. Thanks.
Hi, my server admin has helped me resolve this. If anyone is looking for this in the future, the MSA had nothing to do with it - my restore path was looking for an admin share on serverA when the SQL Agent account wasn't a local admin. I've pointed the Agent account to the non-admin share and the restore is working as expected. / comments
Hi,my server admin has helped me resolve this. If anyone is looking for this in the future, the MSA had nothing to do with it - my restore path was looking for an admin share on serverA when the S...