As mentioned in an earlier post since our systems administrator left our company I am taking care of the backups until the position is replaced. The backup scheduled for last Friday failed as the backup agent was stuck on a server. Since it was the weekend I thought I will rerun the backup after fixing up the cause. I had a look at the log and restarted the server where the backup agent was stuck.
Now I wanted to reschedule the Friday backup as it is with the same features as to going into the same tape (we have multiple tapes in the backup rack). So I was looking for some options as to how to do this when I saw the option "Retry the Job Now".
So I thought I will try this option. What I expected was the backup job to finish earlier as the ob was sstuck on the last server. So I expected it to be finished within an hour. But when I didn't get the alert even after 4 hrs, I started to get worried and logged in to check what was happening. Only then I realised that the backup was running from he beginning. This was the first time I tried this option and worked very well as the job has completed in the way I wanted without much configuration.
As you can see Clean Drive job failed and I will have to resolve this as well. :)
Another learning for me.
Subscribe to:
Post Comments (Atom)
Navigating the Data Science Seas: A Journey with Microsoft Fabric
Data science is a vast and exciting field, brimming with the potential to unlock valuable insights. But like any seafaring voyage, navigatin...
-
From the past 3 days I have been working on resolving merged and hidden cells issues when an SSRS reports is exported to excel. ...
-
I was trying to build an SSIS package that one of my colleagues has created. The first error that was thrown was as below: Exception des...
-
Today I was trying Node.js to connect to SQL Server, the connection to the sql server failed with the below error. name: 'ConnectionE...
No comments:
Post a Comment