Exchange 2010 Hard Drive Space Issues
-
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.
-
@Texkonc Cheaper than an outage for sure. With 2 million log files (2.2TB of logs/1024kB each) if this exchange server has something go wrong it will be very hard to to get it all working again.
-
I read that the Veeam backup is around 10x faster than a windows server backup. Normally this would sound like a marketing ploy but everyone here on ML seems to swear by Veeam. Can anyone confirm? The windows backup took 3 days to complete, thats why I ask.
-
I dont know about speed, but i do know from my previous xp with Veeam that it is a great product. I was never not able to do restores of exchange (vm/brick level) at my last job. It was really quick to restore individual mailbox items and deleted-on-accident contacts without issue. It also provides central backup and restore services for you entire virtual infrastucture, something WSB and Cobian cant.
-
@momurda said in Exchange 2010 Hard Drive Space Issues:
I dont know about speed, but i do know from my previous xp with Veeam that it is a great product. I was never not able to do restores of exchange (vm/brick level) at my last job. It was really quick to restore individual mailbox items and deleted-on-accident contacts without issue. It also provides central backup and restore services for you entire virtual infrastucture, something WSB and Cobian cant.
Yeah I know it's good, but my issue is I can't bog down the server for 3 days again until the weekend. I'd like to resolve this sooner, but I'm kind of stuck.
-
@wirestyle22 said in Exchange 2010 Hard Drive Space Issues:
@momurda said in Exchange 2010 Hard Drive Space Issues:
I dont know about speed, but i do know from my previous xp with Veeam that it is a great product. I was never not able to do restores of exchange (vm/brick level) at my last job. It was really quick to restore individual mailbox items and deleted-on-accident contacts without issue. It also provides central backup and restore services for you entire virtual infrastucture, something WSB and Cobian cant.
Yeah I know it's good, but my issue is I can't bog down the server for 3 days again until the weekend. I'd like to resolve this sooner, but I'm kind of stuck.
Bog it down for 3 days or trying to recover it with the massive log file db?
-
@Texkonc said in Exchange 2010 Hard Drive Space Issues:
@wirestyle22 said in Exchange 2010 Hard Drive Space Issues:
@momurda said in Exchange 2010 Hard Drive Space Issues:
I dont know about speed, but i do know from my previous xp with Veeam that it is a great product. I was never not able to do restores of exchange (vm/brick level) at my last job. It was really quick to restore individual mailbox items and deleted-on-accident contacts without issue. It also provides central backup and restore services for you entire virtual infrastucture, something WSB and Cobian cant.
Yeah I know it's good, but my issue is I can't bog down the server for 3 days again until the weekend. I'd like to resolve this sooner, but I'm kind of stuck.
Bog it down for 3 days or trying to recover it with the massive log file db?
That is word for word what I said to my boss. I don't have deciding power though
-
@wirestyle22 said in Exchange 2010 Hard Drive Space Issues:
@Texkonc said in Exchange 2010 Hard Drive Space Issues:
@wirestyle22 said in Exchange 2010 Hard Drive Space Issues:
@momurda said in Exchange 2010 Hard Drive Space Issues:
I dont know about speed, but i do know from my previous xp with Veeam that it is a great product. I was never not able to do restores of exchange (vm/brick level) at my last job. It was really quick to restore individual mailbox items and deleted-on-accident contacts without issue. It also provides central backup and restore services for you entire virtual infrastucture, something WSB and Cobian cant.
Yeah I know it's good, but my issue is I can't bog down the server for 3 days again until the weekend. I'd like to resolve this sooner, but I'm kind of stuck.
Bog it down for 3 days or trying to recover it with the massive log file db?
That is word for word what I said to my boss. I don't have deciding power though
What if that massive log file gets corrupt when you go down? Then you are burned even more.
Have you measured the strain it puts on it? IF you use an enterprise backup product, will he even notice? You brought up the concerns, but you feel it is the best move. You know the environment, you know what it can handle. Your ass is on the line, even though you told mgt. -
@Texkonc said in Exchange 2010 Hard Drive Space Issues:
@wirestyle22 said in Exchange 2010 Hard Drive Space Issues:
@Texkonc said in Exchange 2010 Hard Drive Space Issues:
@wirestyle22 said in Exchange 2010 Hard Drive Space Issues:
@momurda said in Exchange 2010 Hard Drive Space Issues:
I dont know about speed, but i do know from my previous xp with Veeam that it is a great product. I was never not able to do restores of exchange (vm/brick level) at my last job. It was really quick to restore individual mailbox items and deleted-on-accident contacts without issue. It also provides central backup and restore services for you entire virtual infrastucture, something WSB and Cobian cant.
Yeah I know it's good, but my issue is I can't bog down the server for 3 days again until the weekend. I'd like to resolve this sooner, but I'm kind of stuck.
Bog it down for 3 days or trying to recover it with the massive log file db?
That is word for word what I said to my boss. I don't have deciding power though
What if that massive log file gets corrupt when you go down? Then you are burned even more.
Have you measured the strain it puts on it? IF you use an enterprise backup product, will he even notice? You brought up the concerns, but you feel it is the best move. You know the environment, you know what it can handle. Your ass is on the line, even though you told mgt.It's not my job on the line. My boss just asked me to take a look at it for a second pair of eyes and that was my conclusion. I'm not the server administrator but I've solved a few server issues so far. I'm of the opinion that getting aggressive with my employer is just burning bridges. I let them learn it themselves and cover my ass with e-mails and paperwork.
-
@wirestyle22 said in Exchange 2010 Hard Drive Space Issues:
@Texkonc said in Exchange 2010 Hard Drive Space Issues:
@wirestyle22 said in Exchange 2010 Hard Drive Space Issues:
@Texkonc said in Exchange 2010 Hard Drive Space Issues:
@wirestyle22 said in Exchange 2010 Hard Drive Space Issues:
@momurda said in Exchange 2010 Hard Drive Space Issues:
I dont know about speed, but i do know from my previous xp with Veeam that it is a great product. I was never not able to do restores of exchange (vm/brick level) at my last job. It was really quick to restore individual mailbox items and deleted-on-accident contacts without issue. It also provides central backup and restore services for you entire virtual infrastucture, something WSB and Cobian cant.
Yeah I know it's good, but my issue is I can't bog down the server for 3 days again until the weekend. I'd like to resolve this sooner, but I'm kind of stuck.
Bog it down for 3 days or trying to recover it with the massive log file db?
That is word for word what I said to my boss. I don't have deciding power though
What if that massive log file gets corrupt when you go down? Then you are burned even more.
Have you measured the strain it puts on it? IF you use an enterprise backup product, will he even notice? You brought up the concerns, but you feel it is the best move. You know the environment, you know what it can handle. Your ass is on the line, even though you told mgt.It's not my job on the line. My boss just asked me to take a look at it for a second pair of eyes and that was my conclusion. I'm not the server administrator but I've solved a few server issues so far. I'm of the opinion that getting aggressive with my employer is just burning bridges. I let them learn it themselves and cover my ass with e-mails and paperwork.
Oh, well in that case...
-
@Texkonc said in Exchange 2010 Hard Drive Space Issues:
@wirestyle22 said in Exchange 2010 Hard Drive Space Issues:
@Texkonc said in Exchange 2010 Hard Drive Space Issues:
@wirestyle22 said in Exchange 2010 Hard Drive Space Issues:
@Texkonc said in Exchange 2010 Hard Drive Space Issues:
@wirestyle22 said in Exchange 2010 Hard Drive Space Issues:
@momurda said in Exchange 2010 Hard Drive Space Issues:
I dont know about speed, but i do know from my previous xp with Veeam that it is a great product. I was never not able to do restores of exchange (vm/brick level) at my last job. It was really quick to restore individual mailbox items and deleted-on-accident contacts without issue. It also provides central backup and restore services for you entire virtual infrastucture, something WSB and Cobian cant.
Yeah I know it's good, but my issue is I can't bog down the server for 3 days again until the weekend. I'd like to resolve this sooner, but I'm kind of stuck.
Bog it down for 3 days or trying to recover it with the massive log file db?
That is word for word what I said to my boss. I don't have deciding power though
What if that massive log file gets corrupt when you go down? Then you are burned even more.
Have you measured the strain it puts on it? IF you use an enterprise backup product, will he even notice? You brought up the concerns, but you feel it is the best move. You know the environment, you know what it can handle. Your ass is on the line, even though you told mgt.It's not my job on the line. My boss just asked me to take a look at it for a second pair of eyes and that was my conclusion. I'm not the server administrator but I've solved a few server issues so far. I'm of the opinion that getting aggressive with my employer is just burning bridges. I let them learn it themselves and cover my ass with e-mails and paperwork.
Oh, well in that case...
Pointing someone in the right direction and being responsible are two very different things
-
@wirestyle22 said in Exchange 2010 Hard Drive Space Issues:
@Texkonc said in Exchange 2010 Hard Drive Space Issues:
@wirestyle22 said in Exchange 2010 Hard Drive Space Issues:
@Texkonc said in Exchange 2010 Hard Drive Space Issues:
@wirestyle22 said in Exchange 2010 Hard Drive Space Issues:
@Texkonc said in Exchange 2010 Hard Drive Space Issues:
@wirestyle22 said in Exchange 2010 Hard Drive Space Issues:
@momurda said in Exchange 2010 Hard Drive Space Issues:
I dont know about speed, but i do know from my previous xp with Veeam that it is a great product. I was never not able to do restores of exchange (vm/brick level) at my last job. It was really quick to restore individual mailbox items and deleted-on-accident contacts without issue. It also provides central backup and restore services for you entire virtual infrastucture, something WSB and Cobian cant.
Yeah I know it's good, but my issue is I can't bog down the server for 3 days again until the weekend. I'd like to resolve this sooner, but I'm kind of stuck.
Bog it down for 3 days or trying to recover it with the massive log file db?
That is word for word what I said to my boss. I don't have deciding power though
What if that massive log file gets corrupt when you go down? Then you are burned even more.
Have you measured the strain it puts on it? IF you use an enterprise backup product, will he even notice? You brought up the concerns, but you feel it is the best move. You know the environment, you know what it can handle. Your ass is on the line, even though you told mgt.It's not my job on the line. My boss just asked me to take a look at it for a second pair of eyes and that was my conclusion. I'm not the server administrator but I've solved a few server issues so far. I'm of the opinion that getting aggressive with my employer is just burning bridges. I let them learn it themselves and cover my ass with e-mails and paperwork.
Oh, well in that case...
Pointing someone in the right direction and being responsible are two very different things
The fact that they need those pointers just makes me shutter!
-
