Error 5149 Status 1 Severity
360 games PC games error: 1453, severity: 16, state: 1. Windows games Windows phone games Entertainment All Entertainment error: 1454, severity: 16, state: 1. Movies & TV Music Business & Education Business Students & educators Developers Sale Sale Find a store Gift cards Products Software & services Windows Office Free downloads & security Internet Explorer Microsoft Edge Skype OneNote OneDrive Microsoft Health MSN Bing Microsoft Groove Microsoft Movies & TV Devices & Xbox All Microsoft devices Microsoft Surface All Windows PCs & tablets PC accessories Xbox & games Microsoft Lumia All Windows phones Microsoft HoloLens For business Cloud Platform Microsoft Azure Microsoft Dynamics Windows for business Office for business Skype for business Surface for business Enterprise solutions Small business solutions Find a solutions provider Volume Licensing For developers & IT pros Develop Windows apps Microsoft Azure MSDN TechNet Visual Studio For students & educators Office for students OneNote in classroom Shop PCs & tablets perfect for students Microsoft in Education Support Sign in Cart Cart Javascript is disabled Please enable javascript and refresh the page Cookies are disabled Please enable cookies and refresh the page CV: {{ getCv() }} English (United States) Terms of use Privacy & cookies Trademarks © 2016 Microsoft
to transaction logs If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. Results 1 to 11 of 11 Thread: SQL 2008 Mirroring running out of disk space due to transaction logs Tweet Thread Tools Show Printable Version Subscribe to this Thread… Search Thread Advanced Search Display Linear Mode Switch to Hybrid Mode Switch to Threaded Mode 12-28-10,13:47 #1 Qik View Profile View Forum Posts Registered User Join Date Dec 2010 Posts 6 Unanswered: SQL 2008 Mirroring https://support.microsoft.com/en-us/kb/975681 running out of disk space due to transaction logs Last month I mirrored a SQL 2008 db to another server running sql 2008. Everything was fine until last week. The backups went from 60GB to 220GB in about 1 weeks time. I checked the mirror and noticed it is in a suspended state. I then checked the folder holding the transaction log file for the principal db and noticed it was over 150gb in size but the actual http://www.dbforums.com/showthread.php?1663160-SQL-2008-Mirroring-running-out-of-disk-space-due-to-transaction-logs db is only 2gb. On the mirror server I am seeing a 2GB file which matches the principal db but I am am also seeing a 48GB file which has the same name as the principal db with a "_1" after it. I have a second file which is only a few meg and it is being mirrored on the same servers with no issue. I am getting desperate and planning to drop the mirror before my prodcution servers comes to a halt. Suggestions? I see the followin on the Principal server: Log Name: Application Source: MSSQLSERVER Date: 12/28/2010 10:28:16 AM Event ID: 1453 Task Category: Server Level: Error Keywords: Classic User: N/A Computer: DB.lp.local Description: 'TCP://SQLREPL.lp.local:5022', the remote mirroring partner for database 'UTOPIA', encountered error 5149, status 3, severity 25. Database mirroring has been suspended. Resolve the error on the remote server and resume mirroring, or remove mirroring and re-establish the mirror server instance. and the following on the mirror server Log Name: Application Source: MSSQLSERVER Date: 12/28/2010 10:28:16 AM Event ID: 5149 Task Category: Server Level: Error Keywords: Classic User: N/A Computer: SQLREPL.lp.local Description: MODIFY FILE encountered operating system error 112(There is not enough space on the disk.) while attempting to expand the physical file 'C:\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\DATA\UTOPIA_1.LDF '. Reply With Quote 12-28-10,15:22 #2 rdjabarov View Profile View Forum Posts Registered User Join Date Jul 2003 Locat
for mirroring to be suspended. Often you can just resume mirroring and it resolves http://mattsnotes.com/sql-server/why-is-the-sql-server-mirroring-suspended itself. Check the logs From SQL Server Management Studio go https://ask.sqlservercentral.com/questions/138463/mirrored-database-out-of-space-error.html to Management/SQL Server Logs and open the current log. 5149 Errors The primary error log contains the following error: 'TCP://STANDBY:10022', the remote mirroring partner for database 'MyDatabase', encountered error 5149, status 3, severity 25. Database mirroring has been suspended. Resolve the error on severity: 16, the remote server and resume mirroring, or remove mirroring and re-establish the mirror server instance. Check the error log from the mirror server. For example: 09/16/2013 07:03:10,spid150s,Unknown,Bypassing recovery for database 'MyDatabase' because it is marked as a mirror database
0 Hi Experts, Principal Database of 300GB where log file consumed 150GB. Database participating in asynchronous mirroring with log files on different drive than principal server. When we check the log_reuse_wait_desc we got database_mirroring and mirroring found in suspended error. Post resuming the mirror, after some time, mirroring again changed its status to suspended and below error logged in error log. Error: 5149, Severity: 16, State: 3. MODIFY FILE encountered operating system error 112(There is not enough space on the disk.) while attempting to expand the physical file 'G Error: 1454, Severity: 16, State: 1. Database mirroring will be suspended. Server instance encountered error 5149, state 3, severity 25 when it was acting as a mirroring partner for database **. The database mirroring partners might try to recover automatically from the error and resume the mirroring session. For more information, view the error log for additional error messages. Upon checking the disk space on mirror server, we found that 60GB space is still available but not sure why mirror database not able to grow. Please confirm below? Does SQL Server calculate the disk requirement before streaming the log records to mirror server or grow based on autogrow setting? Like it has 100GB pending transactions on principal but only 60GB left on mirror? Ideally, it should grow as it streams log records. What is the logic applied here? Thanks, Neeraj more ▼ 1 total comment 1468 characters / 231 words asked May 15 at 07:10 AM in Default NeerajTripathi 600 ● 7 ● 13 ● 18 edited May 20 at 01:41 PM Shawn_Melton 6.4k ● 21 ● 25 ● 34 what are your autogrowth settings? May 23 at 10:13 AM Kev Riley ♦♦ add new comment (comments are locked) 10|1200 characters needed characters left ▼ Everyone Moderators Original poster and moderators Other... Viewable by all users 0 answers: sort voted first ▼ oldest newest voted first Be the first one to answer this question toggle preview: Attachments: Up to 2 attachments (including images) can