Skip to main content
  • EN

Hello everyone!

 

I have a SQL environment where the error below started appearing after migrating between repositories:

 

With this error it won't let me:

  • Delete the jobs;
  • Enable the job;
  • Finalize the job configuration summary;

Nothing about that specific job has worked again!!

 

Background:

Previously we needed to move the backup file and then map them to their target repository.

Today we have the “Move backup” option:

 

After clicking move, it tells me that it needs to move all the cluster backups:

In addition to enabling Move via console, we can also choose which Job it will be linked to:

That's awesome!

Now let's get back to troubleshooting!

 

I executed the sequence below to solve the problem:

  • Clone the current job;
  • Move the backups to the repository and cloned job;
  • Run full backup;
  • Continue transaction log;

After that my job is working perfectly!

 

Remembering that I am using Windows Agents within a protection group as good practices for Always ON protection

Very interesting issue as I never use AlwaysOn.  Nice to see you fixed the problem and shared it with the community.

Great explanation! This type of error can be a challenge in Always On environments. Thank you for sharing this troubleshooting and solution

Very interesting issue as I never use AlwaysOn.  Nice to see you fixed the problem and shared it with the community.

I have many clients with Always ON. If I can help, we are available!

Great explanation! This type of error can be a challenge in Always On environments. Thank you for sharing this troubleshooting and solution

Exactly! It's not so simple

I wonder, did this job have transaction log processing enabled? Perhaps that persistent session staying open was part of the problem when migrating between repositories.

I wonder, did this job have transaction log processing enabled? Perhaps that persistent session staying open was part of the problem when migrating between repositories.

Hello!

Yes, I did, but all log backups were paused before the migration attempt.

There were no sessions or processes open during the attempt.

Comment


Terms & Conditions