RE: Backup issue in Exchange 2007
The server only runs Exchange 2007. Any danger of removing the VSS max limit
and having Exchange crash due to lack of free space during the backup? I assume
you mean remove VSS limit on the D and E drives (see below)?
Here is the current setup:
OS, logs and DB all on separate drives.
Drive Data SizeFree
C OS 68gb 40gb
D Logs 136gb130gb
E DB 836gb387gb
C:\Users\ExchangeAdminvssadmin list shadowstorage
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2005 Microsoft Corp.
Shadow Copy Storage association
For volume: (C:)\\?\Volume{efb56814-7941-11dd-846d-806e6f6e6963}\
Shadow Copy Storage volume:
(C:)\\?\Volume{efb56814-7941-11dd-846d-806e6f6e6963}\
Used Shadow Copy Storage space: 0 B
Allocated Shadow Copy Storage space: 0 B
Maximum Shadow Copy Storage space: 6.833 GB
Shadow Copy Storage association
For volume: (D:)\\?\Volume{efb56815-7941-11dd-846d-806e6f6e6963}\
Shadow Copy Storage volume:
(D:)\\?\Volume{efb56815-7941-11dd-846d-806e6f6e6963}\
Used Shadow Copy Storage space: 0 B
Allocated Shadow Copy Storage space: 0 B
Maximum Shadow Copy Storage space: 300 MB
Shadow Copy Storage association
For volume: (E:)\\?\Volume{e88c87c0-312e-11df-99d9-806e6f6e6963}\
Shadow Copy Storage volume:
(E:)\\?\Volume{e88c87c0-312e-11df-99d9-806e6f6e6963}\
Used Shadow Copy Storage space: 0 B
Allocated Shadow Copy Storage space: 0 B
Maximum Shadow Copy Storage space: 300 MB
From: Michael B. Smith [mailto:mich...@smithcons.com]
Sent: Thursday, January 13, 2011 5:02 PM
To: MS-Exchange Admin Issues
Subject: RE: Backup issue in Exchange 2007
You should REMOVE the VSS max limit and allow VSS to police itself.
That being said - my advice is appropriate if only Exchange is on that volume.
If other things are installed, then all bets are off. :-P
Regards,
Michael B. Smith
Consultant and Exchange MVP
http://TheEssentialExchange.com
From: Leedy, Andy [mailto:ale...@butlerschein.com]
Sent: Thursday, January 13, 2011 4:50 PM
To: MS-Exchange Admin Issues
Subject: Backup issue in Exchange 2007
It appears that the VSS file is changing or something, so that the backup is
not able to verify. I believe the Backup is ok, but it would be nice to
verify. Does anyone have any ideas how to resolve the issue? Do I need to
increase the VSS max limit?
We are using Backup Exec 12.5 I believe.
Backup log contains this warning:
WARNING: \\TBCMAIL\Microsoft Information Store\Associates MBX Storage
Group\Associates MBX
Storefile:///\\TBCMAIL\Microsoft%20Information%20Store\Associates%20MBX%20Storage%20Group\Associates%20MBX%20Store
is a corrupt file. This file cannot verify. Backup completed on 1/13/2011 at
12:21:47 AM.
.
.
.
Completed status: Failed
Final error: 0xe000fedf - A failure occurred reading an object.
Final error category: Resource Errors
For additional information regarding this error refer to link
http://eventlookup.veritas.com/eventlookup/EventLookup.jhtml?EvtID=V-79-57344-65247
The event log contains this error:
EventID 36 - The shadow copies of volume D: were aborted because the shadow
copy storage could not grow due to a user imposed limit. We are using the
latest Backup Exec. Volume D contains the databases. The largest is around 120
GB. Any ideas?
Thanks,
Andy
**
CONFIDENTIALITY NOTICE - The information transmitted in this message is
intended only for the person or entity to which it is addressed and may contain
confidential and/or privileged material. Any review, retransmission,
dissemination or other use of this information by persons or entities other
than the intended recipient is prohibited. If you received this in error,
please contact the sender and destroy all copies of this document. Thank you.
Butler Schein Animal Health
**
---
To manage subscriptions click here:
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to
listmana...@lyris.sunbeltsoftware.commailto:listmana...@lyris.sunbeltsoftware.com
with the body: unsubscribe exchangelist
---
To manage subscriptions click here:
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to
listmana...@lyris.sunbeltsoftware.commailto:listmana...@lyris.sunbeltsoftware.com
with the body: unsubscribe exchangelist
---
To manage subscriptions click here:
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to listmana...@lyris.sunbeltsoftware.com
with the body: unsubscribe exchangelist
RE: Backup issue in Exchange 2007
No danger of that as long as the backup itself doesn't crash. If you are
concerned about THAT possibility then set the shadow storage to a more
reasonable number, such as 5 GB. The current values are way too low for an
active server.
Sent from my HTC Tilt™ 2, a Windows® phone from ATT
From: Leedy, Andy ale...@butlerschein.com
Sent: Friday, January 14, 2011 8:36 AM
To: MS-Exchange Admin Issues exchangelist@lyris.sunbelt-software.com
Subject: RE: Backup issue in Exchange 2007
The server only runs Exchange 2007. Any danger of removing the VSS max limit
and having Exchange crash due to lack of free space during the backup? I assume
you mean remove VSS limit on the D and E drives (see below)?
Here is the current setup:
OS, logs and DB all on separate drives.
Drive Data SizeFree
C OS 68gb 40gb
D Logs 136gb130gb
E DB 836gb387gb
C:\Users\ExchangeAdminvssadmin list shadowstorage
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2005 Microsoft Corp.
Shadow Copy Storage association
For volume: (C:)\\?\Volume{efb56814-7941-11dd-846d-806e6f6e6963}\
Shadow Copy Storage volume:
(C:)\\?\Volume{efb56814-7941-11dd-846d-806e6f6e6963}\
Used Shadow Copy Storage space: 0 B
Allocated Shadow Copy Storage space: 0 B
Maximum Shadow Copy Storage space: 6.833 GB
Shadow Copy Storage association
For volume: (D:)\\?\Volume{efb56815-7941-11dd-846d-806e6f6e6963}\
Shadow Copy Storage volume:
(D:)\\?\Volume{efb56815-7941-11dd-846d-806e6f6e6963}\
Used Shadow Copy Storage space: 0 B
Allocated Shadow Copy Storage space: 0 B
Maximum Shadow Copy Storage space: 300 MB
Shadow Copy Storage association
For volume: (E:)\\?\Volume{e88c87c0-312e-11df-99d9-806e6f6e6963}\
Shadow Copy Storage volume:
(E:)\\?\Volume{e88c87c0-312e-11df-99d9-806e6f6e6963}\
Used Shadow Copy Storage space: 0 B
Allocated Shadow Copy Storage space: 0 B
Maximum Shadow Copy Storage space: 300 MB
From: Michael B. Smith [mailto:mich...@smithcons.com]
Sent: Thursday, January 13, 2011 5:02 PM
To: MS-Exchange Admin Issues
Subject: RE: Backup issue in Exchange 2007
You should REMOVE the VSS max limit and allow VSS to police itself.
That being said – my advice is appropriate if only Exchange is on that volume.
If other things are installed, then all bets are off. :-P
Regards,
Michael B. Smith
Consultant and Exchange MVP
http://TheEssentialExchange.com
From: Leedy, Andy [mailto:ale...@butlerschein.com]
Sent: Thursday, January 13, 2011 4:50 PM
To: MS-Exchange Admin Issues
Subject: Backup issue in Exchange 2007
It appears that the VSS file is changing or something, so that the backup is
not able to verify. I believe the Backup is ok, but it would be nice to
verify. Does anyone have any ideas how to resolve the issue? Do I need to
increase the VSS max limit?
We are using Backup Exec 12.5 I believe.
Backup log contains this warning:
WARNING: \\TBCMAIL\Microsoft Information Store\Associates MBX Storage
Group\Associates MBX
Storefile:///\\TBCMAIL\Microsoft%20Information%20Store\Associates%20MBX%20Storage%20Group\Associates%20MBX%20Store
is a corrupt file. This file cannot verify. Backup completed on 1/13/2011 at
12:21:47 AM.
.
.
.
Completed status: Failed
Final error: 0xe000fedf - A failure occurred reading an object.
Final error category: Resource Errors
For additional information regarding this error refer to link
http://eventlookup.veritas.com/eventlookup/EventLookup.jhtml?EvtID=V-79-57344-65247
The event log contains this error:
EventID 36 - The shadow copies of volume D: were aborted because the shadow
copy storage could not grow due to a user imposed limit. We are using the
latest Backup Exec. Volume D contains the databases. The largest is around 120
GB. Any ideas?
Thanks,
Andy
**
CONFIDENTIALITY NOTICE - The information transmitted in this message is
intended only for the person or entity to which it is addressed and may contain
confidential and/or privileged material. Any review, retransmission,
dissemination or other use of this information by persons or entities other
than the intended recipient is prohibited. If you received this in error,
please contact the sender and destroy all copies of this document. Thank you.
Butler Schein Animal Health
**
---
To manage subscriptions click here:
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to
listmana...@lyris.sunbeltsoftware.commailto:listmana...@lyris.sunbeltsoftware.com
with the body: unsubscribe exchangelist
---
To manage subscriptions click here:
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to
listmana...@lyris.sunbeltsoftware.commailto:listmana...@lyris.sunbeltsoftware.com
RE: Backup issue in Exchange 2007
Thanks Michael!
I made the change to 5 GB on the OS drive, and 10 GB on the DB and Log drive.
Running the backup now.
Thanks,
Andy
From: Michael B. Smith [mailto:mich...@smithcons.com]
Sent: Friday, January 14, 2011 9:12 AM
To: MS-Exchange Admin Issues
Subject: RE: Backup issue in Exchange 2007
No danger of that as long as the backup itself doesn't crash. If you are
concerned about THAT possibility then set the shadow storage to a more
reasonable number, such as 5 GB. The current values are way too low for an
active server.
Sent from my HTC Tilt(tm) 2, a Windows(r) phone from ATT
From: Leedy, Andy ale...@butlerschein.com
Sent: Friday, January 14, 2011 8:36 AM
To: MS-Exchange Admin Issues exchangelist@lyris.sunbelt-software.com
Subject: RE: Backup issue in Exchange 2007
The server only runs Exchange 2007. Any danger of removing the VSS max limit
and having Exchange crash due to lack of free space during the backup? I assume
you mean remove VSS limit on the D and E drives (see below)?
Here is the current setup:
OS, logs and DB all on separate drives.
Drive Data SizeFree
C OS 68gb 40gb
D Logs 136gb130gb
E DB 836gb387gb
C:\Users\ExchangeAdminvssadmin list shadowstorage
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2005 Microsoft Corp.
Shadow Copy Storage association
For volume:
(C:)\\?\Volume{efb56814-7941-11dd-846d-806e6f6e6963}\file:///\\%3f\Volume%7befb56814-7941-11dd-846d-806e6f6e6963%7d\
Shadow Copy Storage volume:
(C:)\\?\Volume{efb56814-7941-11dd-846d-806e6f6e6963}\file:///\\%3f\Volume%7befb56814-7941-11dd-846d-806e6f6e6963%7d\
Used Shadow Copy Storage space: 0 B
Allocated Shadow Copy Storage space: 0 B
Maximum Shadow Copy Storage space: 6.833 GB
Shadow Copy Storage association
For volume:
(D:)\\?\Volume{efb56815-7941-11dd-846d-806e6f6e6963}\file:///\\%3f\Volume%7befb56815-7941-11dd-846d-806e6f6e6963%7d\
Shadow Copy Storage volume:
(D:)\\?\Volume{efb56815-7941-11dd-846d-806e6f6e6963}\file:///\\%3f\Volume%7befb56815-7941-11dd-846d-806e6f6e6963%7d\
Used Shadow Copy Storage space: 0 B
Allocated Shadow Copy Storage space: 0 B
Maximum Shadow Copy Storage space: 300 MB
Shadow Copy Storage association
For volume:
(E:)\\?\Volume{e88c87c0-312e-11df-99d9-806e6f6e6963}\file:///\\%3f\Volume%7be88c87c0-312e-11df-99d9-806e6f6e6963%7d\
Shadow Copy Storage volume:
(E:)\\?\Volume{e88c87c0-312e-11df-99d9-806e6f6e6963}\file:///\\%3f\Volume%7be88c87c0-312e-11df-99d9-806e6f6e6963%7d\
Used Shadow Copy Storage space: 0 B
Allocated Shadow Copy Storage space: 0 B
Maximum Shadow Copy Storage space: 300 MB
From: Michael B. Smith [mailto:mich...@smithcons.com]
Sent: Thursday, January 13, 2011 5:02 PM
To: MS-Exchange Admin Issues
Subject: RE: Backup issue in Exchange 2007
You should REMOVE the VSS max limit and allow VSS to police itself.
That being said - my advice is appropriate if only Exchange is on that volume.
If other things are installed, then all bets are off. :-P
Regards,
Michael B. Smith
Consultant and Exchange MVP
http://TheEssentialExchange.com
From: Leedy, Andy [mailto:ale...@butlerschein.com]
Sent: Thursday, January 13, 2011 4:50 PM
To: MS-Exchange Admin Issues
Subject: Backup issue in Exchange 2007
It appears that the VSS file is changing or something, so that the backup is
not able to verify. I believe the Backup is ok, but it would be nice to
verify. Does anyone have any ideas how to resolve the issue? Do I need to
increase the VSS max limit?
We are using Backup Exec 12.5 I believe.
Backup log contains this warning:
WARNING: \\TBCMAIL\Microsoft Information Store\Associates MBX Storage
Group\Associates MBX
Storefile:///\\TBCMAIL\Microsoft%20Information%20Store\Associates%20MBX%20Storage%20Group\Associates%20MBX%20Store
is a corrupt file. This file cannot verify. Backup completed on 1/13/2011 at
12:21:47 AM.
.
.
.
Completed status: Failed
Final error: 0xe000fedf - A failure occurred reading an object.
Final error category: Resource Errors
For additional information regarding this error refer to link
http://eventlookup.veritas.com/eventlookup/EventLookup.jhtml?EvtID=V-79-57344-65247
The event log contains this error:
EventID 36 - The shadow copies of volume D: were aborted because the shadow
copy storage could not grow due to a user imposed limit. We are using the
latest Backup Exec. Volume D contains the databases. The largest is around 120
GB. Any ideas?
Thanks,
Andy
**
CONFIDENTIALITY NOTICE - The information transmitted in this message is
intended only for the person or entity to which it is addressed and may contain
confidential and/or privileged material. Any review, retransmission,
dissemination or other use of this information by persons or entities other
than
Backup issue in Exchange 2007
It appears that the VSS file is changing or something, so that the backup is not able to verify. I believe the Backup is ok, but it would be nice to verify. Does anyone have any ideas how to resolve the issue? Do I need to increase the VSS max limit? We are using Backup Exec 12.5 I believe. Backup log contains this warning: WARNING: \\TBCMAIL\Microsoft Information Store\Associates MBX Storage Group\Associates MBX Store is a corrupt file. This file cannot verify. Backup completed on 1/13/2011 at 12:21:47 AM. . . . Completed status: Failed Final error: 0xe000fedf - A failure occurred reading an object. Final error category: Resource Errors For additional information regarding this error refer to link http://eventlookup.veritas.com/eventlookup/EventLookup.jhtml?EvtID=V-79-57344-65247 The event log contains this error: EventID 36 - The shadow copies of volume D: were aborted because the shadow copy storage could not grow due to a user imposed limit. We are using the latest Backup Exec. Volume D contains the databases. The largest is around 120 GB. Any ideas? Thanks, Andy ** CONFIDENTIALITY NOTICE - The information transmitted in this message is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and destroy all copies of this document. Thank you. Butler Schein Animal Health ** --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe exchangelist
RE: Backup issue in Exchange 2007
You should REMOVE the VSS max limit and allow VSS to police itself. That being said - my advice is appropriate if only Exchange is on that volume. If other things are installed, then all bets are off. :-P Regards, Michael B. Smith Consultant and Exchange MVP http://TheEssentialExchange.com From: Leedy, Andy [mailto:ale...@butlerschein.com] Sent: Thursday, January 13, 2011 4:50 PM To: MS-Exchange Admin Issues Subject: Backup issue in Exchange 2007 It appears that the VSS file is changing or something, so that the backup is not able to verify. I believe the Backup is ok, but it would be nice to verify. Does anyone have any ideas how to resolve the issue? Do I need to increase the VSS max limit? We are using Backup Exec 12.5 I believe. Backup log contains this warning: WARNING: \\TBCMAIL\Microsoft Information Store\Associates MBX Storage Group\Associates MBX Storefile:///\\TBCMAIL\Microsoft%20Information%20Store\Associates%20MBX%20Storage%20Group\Associates%20MBX%20Store is a corrupt file. This file cannot verify. Backup completed on 1/13/2011 at 12:21:47 AM. . . . Completed status: Failed Final error: 0xe000fedf - A failure occurred reading an object. Final error category: Resource Errors For additional information regarding this error refer to link http://eventlookup.veritas.com/eventlookup/EventLookup.jhtml?EvtID=V-79-57344-65247 The event log contains this error: EventID 36 - The shadow copies of volume D: were aborted because the shadow copy storage could not grow due to a user imposed limit. We are using the latest Backup Exec. Volume D contains the databases. The largest is around 120 GB. Any ideas? Thanks, Andy ** CONFIDENTIALITY NOTICE - The information transmitted in this message is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and destroy all copies of this document. Thank you. Butler Schein Animal Health ** --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.commailto:listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe exchangelist --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe exchangelist
