Exchange 2010 Hard Drive Space Issues
-
Your first full backup is going to take a long time.
-
@wirestyle22 said in Exchange 2010 Hard Drive Space Issues:
It's a copy backup. That's why this has been happening for over a year. It needs to be either a full backup or incremental to truncate.
There you go.
-
@momurda said in Exchange 2010 Hard Drive Space Issues:
Your first full backup is going to take a long time.
I'm expecting at least 24 hours
-
@JaredBusch said in Exchange 2010 Hard Drive Space Issues:
@wirestyle22 said in Exchange 2010 Hard Drive Space Issues:
It's a copy backup. That's why this has been happening for over a year. It needs to be either a full backup or incremental to truncate.
There you go.
Thank your for your help
-
A full backup did not truncate the logs. Took 3 days.
-
@wirestyle22 said in Exchange 2010 Hard Drive Space Issues:
A full backup did not truncate the logs. Took 3 days.
The backup was taken using SQL Manager, right?
-
@travisdh1 No, windows server backup as I discussed above
-
I read this in a MS article:
"After about six hours on the phone with MS Support, the problem is related to the Microsoft Exchange Search Indexer Service. I don't know if it is a bug in Exchange or something in my design, but I had to dismount databases, stop the Exchange Information Store Service then delete catalogs from all database copies (active and passive). After restarting Exchange Information Store Service and remounting the databases the backs now truncate logs. The rep said the Microsoft Exchange Search Indexer Service wasn't allowing the Replication Service to truncate logs.
In addition to this issue I am seeing problems with the ContentIndexState, upon replica creation, being set to Crawling and never coming out. If I restart the Microsoft Exchange Search Indexer Service, the state moves to Healthy.
It appears all my issues point to the Microsoft Exchange Search Indexer Service and it's manifesting itself in different ways. My case is in the process of being escalated so I'll post back with an update. Hopefully someone else won't have to spend weeks fighting this too."
-
Definitely sounds like one possibility.
-
So what's your plan to fix this?
If you have another server with enough storage on it, you might be able to stand up another Exchange server and migration fully over to that, then decom the old one.
-
@Dashrender I don't have anything I can use to migrate it. I'm not sure. The full backup took 3 days, I was hoping to have a little more time to resolve this. Not sure.
-
@wirestyle22 said in Exchange 2010 Hard Drive Space Issues:
@Dashrender I don't have anything I can use to migrate it. I'm not sure. The full backup took 3 days, I was hoping to have a little more time to resolve this. Not sure.
What about those new servers that were ordered a few weeks ago? are they coming in?
-
Was the backup successful? What Event viewer logs were generated on completion of your backup?
-
@Dashrender said in Exchange 2010 Hard Drive Space Issues:
@wirestyle22 said in Exchange 2010 Hard Drive Space Issues:
@Dashrender I don't have anything I can use to migrate it. I'm not sure. The full backup took 3 days, I was hoping to have a little more time to resolve this. Not sure.
What about those new servers that were ordered a few weeks ago? are they coming in?
Politics slow everything down.
-
@momurda said in Exchange 2010 Hard Drive Space Issues:
Was the backup successful? What Event viewer logs were generated on completion of your backup?
I haven't been able to look at it myself. My boss said they were. I can't verify. I'm out in the world today
-
Two exceptions. From what I read you have to have 100% log files backed up for them to truncate. New log files are being generated still.
Writer Id: {76FE1AC4-15F7-4BCD-987E-8E1ACB462FB7} Instance Id: {7C0EF254-BE27-4017-BAE7-E0F158B6BD01} Writer Name: Microsoft Exchange Writer Writer State: 5 Failure Result: 800423F3 Application Result: 1 Application Message: (null) Component: fd52b799-9220-44b7-a01f-227c24c674ef Logical Path: Microsoft Exchange Server\Microsoft Information Store\Exchange Server Component Result: 800423F3 Component Message: (null) File Spec: D:\Data\MailBoxes\Domain\Mailbox -Exchange Server.edb Recursive: 0 File Spec: D:\Data\Logs\Domain\Mailbox -Domain\\E00*.log Recursive: 0 File Spec: D:\Data\Logs\Domain\Mailbox -Domain\\E00.chk Recursive: 0 Component: 14106486-6449-412c-b568-54b405837a54 Logical Path: Microsoft Exchange Server\Microsoft Information Store\Exchange Server Component Result: 800423F3 Component Message: (null) File Spec: D:\Data\Public Folders\Domain\Public Folder-Domain.edb Recursive: 0 File Spec: D:\Data\Public Folders\Domain\Logs\Public Folder-Domain.edb\\E01*.log Recursive: 0 File Spec: D:\Data\Public Folders\Domain\Logs\Public Folder-Domain.edb\\E01.chk Recursive: 0``` *-----------------------------* -
Note: I have a meeting at 10:00 AM. Was just notified.
Note 2: It's a vendor. Not like I'm in trouble
-
Do you have the ability to setup a temp server and setup something like Veam, BackupExec, etc... in trial mode that are exchange aware just to trunk the logs and still use your target media?
-
@Texkonc said in Exchange 2010 Hard Drive Space Issues:
Do you have the ability to setup a temp server and setup something like Veam, BackupExec, etc... in trial mode that are exchange aware just to trunk the logs and still use your target media?
Good call. Install Veeam B&R in trial mode, make a full backup to any media you got, even a USB HDD.
Once it all truncates, let your normal backup kick off again.
-
@JaredBusch said in Exchange 2010 Hard Drive Space Issues:
@Texkonc said in Exchange 2010 Hard Drive Space Issues:
Do you have the ability to setup a temp server and setup something like Veam, BackupExec, etc... in trial mode that are exchange aware just to trunk the logs and still use your target media?
Good call. Install Veeam B&R in trial mode, make a full backup to any media you got, even a USB HDD.
Once it all truncates, let your normal backup kick off again.
Surely he has an old server laying around, hell, even leave windows in trial mode, and buy a USB drive that is at least double the databases or more. It is cheaper than a outage i bet.
