July 30, 2014 at 9:30 pm
Hello everyone
I have two sql servers
It is setup as a mirror databases
1) database 1(principle, synchronized)
2) database 2 (Mirror, Synchronized / Restoring)
I do not know how this happen
We are able to connect to the database 1 and work in it without any problems
I do get an error message:
Error: [The database "ContinuumDB" cannot be opened. It is acting as a mirror database. BACKUP LOG is terminating abnormally. An exception occurred while executing a Transact-SQL statement or batch.]
Source: shd-continuum-sql2, Process: SQLiDA
shd-continuum-sql2 Win FS /
N/A defaultBackupSet/
How do I get the database 2 back to show secondary and get rid of restoring ?
July 31, 2014 at 12:01 am
lescobar (7/30/2014)
Hello everyoneI have two sql servers
It is setup as a mirror databases
1) database 1(principle, synchronized)
2) database 2 (Mirror, Synchronized / Restoring)
I do not know how this happen
Someone implemented a database mirroring session
lescobar (7/30/2014)
How do I get the database 2 back to show secondary and get rid of restoring ?
Failover or remove the session
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
July 31, 2014 at 6:25 am
lescobar (7/30/2014)
Hello everyoneI have two sql servers
It is setup as a mirror databases
1) database 1(principle, synchronized)
2) database 2 (Mirror, Synchronized / Restoring)
Nothing wrong there. That looks like a mirroring set working perfectly. The mirror is *supposed* to be restoring and inaccessible.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
July 31, 2014 at 7:38 am
The mirrored databases are there for disaster purposes. When the principal database/server goes down you could (manually or automatically when configured) failover. At that moment the partner database will come out of restoring state and will be available. This configuration will minimize donwtime and data loss.
July 31, 2014 at 10:36 am
so how do I stop or correct this error message?
Failure Reason:
ERROR CODE [30:325]: Error encountered during backup. Error: [Database "VIEWCOMPOSERDB' cannot be opened because it is offline. BACKUP DATABASE is terminating abnormally. An exception occurred while executing a Transact-SQL statement or batch.] Source: shdnapvc01, Process: SQLiDA
July 31, 2014 at 11:04 am
lescobar (7/31/2014)
so how do I stop or correct this error message?Failure Reason:
ERROR CODE [30:325]: Error encountered during backup. Error: [Database "VIEWCOMPOSERDB' cannot be opened because it is offline. BACKUP DATABASE is terminating abnormally. An exception occurred while executing a Transact-SQL statement or batch.] Source: shdnapvc01, Process: SQLiDA
You don't. You can't run backups or log backups against the mirror database. You have to run those against the principal database.
July 31, 2014 at 11:06 am
Disable the jobs on the mirror that are trying to perform the backups (or other maintenance). Those should only be enabled in the event of a failover.
Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events
July 31, 2014 at 1:11 pm
SQLRNNR (7/31/2014)
Disable the jobs on the mirror that are trying to perform the backups (or other maintenance). Those should only be enabled in the event of a failover.
You could build some logic inside the backup process to skip inaccessable databases. Apply this logic on both the principle and the partner, so a backup of your database is always created.
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply