4 minor spelling correction
source | link

We are using SQL Mirroring as an HA solution and Log Shipping as ana DR solution.

Recently, the mirror database has been configured as a log shipping primary (the mirror/primary database) to allow log shipping to continue after database mirroring fails over, using the same configuration we used for the primary on the principal database.

Now the problem is every so often the restore job fails due to:

Exclusive access could not be obtained because the database is in use.

This is because two restore jobs (one from principal/Primary, and one from the mirror/primary) start at the same time. I have changed the job schedules to be run at different times, however.

For example, the restore job from the principal/Primary is scheduled for every 13 minutes and the restore job from mirror/Primary is scheduled for every 10 minutes. But there are still some times that they start at the same time.

Is there any way to prevent this?

We are using SQL Mirroring as an HA solution and Log Shipping as an DR solution.

Recently, the mirror database has been configured as a log shipping primary (the mirror/primary database) to allow log shipping to continue after database mirroring fails over, using the same configuration we used for the primary on the principal database.

Now the problem is every so often the restore job fails due to:

Exclusive access could not be obtained because the database is in use.

This is because two restore jobs (one from principal/Primary, and one from the mirror/primary) start at the same time. I have changed the job schedules to be run at different times, however.

For example, the restore job from the principal/Primary is scheduled for every 13 minutes and the restore job from mirror/Primary is scheduled for every 10 minutes. But there are still some times that they start at the same time.

Is there any way to prevent this?

We are using SQL Mirroring as an HA solution and Log Shipping as a DR solution.

Recently, the mirror database has been configured as a log shipping primary (the mirror/primary database) to allow log shipping to continue after database mirroring fails over, using the same configuration we used for the primary on the principal database.

Now the problem is every so often the restore job fails due to:

Exclusive access could not be obtained because the database is in use.

This is because two restore jobs (one from principal/Primary, and one from the mirror/primary) start at the same time. I have changed the job schedules to be run at different times, however.

For example, the restore job from the principal/Primary is scheduled for every 13 minutes and the restore job from mirror/Primary is scheduled for every 10 minutes. But there are still some times that they start at the same time.

Is there any way to prevent this?

3 title spelling changed
| link

Mirroring and log shipping toghethertogether

2 Formatting, grammar, tags
source | link

weWe are using SQL Mirroring as an HA solution and Log Shipping as an DR solution  . Recently

Recently, the mirror database has been configured as a log shipping primary (the mirror/primary database) to allow log shipping to continue after database mirroring fails over, using the same configuration we used for the primary on the principal database. Now

Now the problem is every so often the restore job fails due to Exclusive access could not be obtained because the db is in use . actually this:

Exclusive access could not be obtained because the database is in use.

This is because two restore jobs  (one from principal/Primary  ,one and one from the mirror/primary) startsstart at the same time however. I have changechanged the scheduled jobsjob schedules to be run onat different time fortimes, however.

For example, the restore job from the principal/Primary is scheduled for every 13 minutes and the restore job from mirror/Primary is scheduled for every 10 minutes  . butBut there are still some times that they start at the same time. 

Is there any way to prevent this  ?

any help is much appreciated.

we are using SQL Mirroring as an HA solution and Log Shipping as an DR solution  . Recently the mirror database has been configured as a log shipping primary (the mirror/primary database) to allow log shipping to continue after database mirroring fails over, using the same configuration we used for the primary on the principal database. Now the problem is every often restore job fails due to Exclusive access could not be obtained because the db is in use . actually this is because two restore jobs(one from principal/Primary  ,one from mirror/primary) starts at the same time however I have change the scheduled jobs to be run on different time for example restore job from principal/Primary scheduled for every 13 minutes and restore job from mirror/Primary scheduled for every 10 minutes  . but there are some times that they start at the same time. Is there any way to prevent this  ?

any help is much appreciated.

We are using SQL Mirroring as an HA solution and Log Shipping as an DR solution.

Recently, the mirror database has been configured as a log shipping primary (the mirror/primary database) to allow log shipping to continue after database mirroring fails over, using the same configuration we used for the primary on the principal database.

Now the problem is every so often the restore job fails due to:

Exclusive access could not be obtained because the database is in use.

This is because two restore jobs  (one from principal/Primary, and one from the mirror/primary) start at the same time. I have changed the job schedules to be run at different times, however.

For example, the restore job from the principal/Primary is scheduled for every 13 minutes and the restore job from mirror/Primary is scheduled for every 10 minutes. But there are still some times that they start at the same time. 

Is there any way to prevent this?

1
source | link