I use windirstat - disk space, other than what I mentioned just now, looks fine.
Forgot to say: I doubled the disk size for the backup disk on the VM, and extended the partition, and last night the backups finished without error. Kurt On Mon, Feb 2, 2015 at 6:15 PM, Jonathan Raper <[email protected]> wrote: > Hey Kurt - Just a thought. Might be nothing, but I have seen VSS go nuts > and eat up all my hard disk space. It was with Symantec BackupExec, but I > suppose it could happen with other backup routines. Check the available > space with an app such as Treesize and see if you have a ton of space > mysteriously eaten up. If you do, stop and start the VSS in services and see > if that frees it up, and then try your backup again. > > Let us know what you find! > > Jonathan > > > Sent from my Verizon Wireless 4G LTE smartphone > > > -------- Original message -------- > From: Kurt Buff > Date:02/02/2015 8:14 PM (GMT-05:00) > To: [email protected] > Subject: Re: [Exchange] Exchange 2010, SP3 backups not working > > Fine - be logical that way! :) > > So, yes, there are some problems. I see a warning that backups might > fail because of not enough space, and a few other things. > > So, I haven't completely figured it out, but that should lead me in > right direction. > > Thanks again. > > Kurt > > On Mon, Feb 2, 2015 at 4:56 PM, Michael B. Smith <[email protected]> > wrote: >> Applications and Services Logs --> Microsoft --> Windows --> Backup --> * >> >> -----Original Message----- >> From: [email protected] >> [mailto:[email protected]] On Behalf Of Kurt Buff >> Sent: Monday, February 2, 2015 7:34 PM >> To: [email protected] >> Subject: Re: [Exchange] Exchange 2010, SP3 backups not working >> >> Thanks for the hint. Unfortunately, I see nothing in there that seems to >> have relevance. >> >> Just to make sure I'm looking in the right place, I went to Eventviewer >> >> Applications and Services Log >> Microsoft >> Exchange, and looked at >> everything in HighAvailablilty, MailboxDatabaseFailureItems and >> Troubleshooters. >> >> Nada. Nothing correlates with the missing backups by time or error >> message. The only failure items I see in there are the ones associated with >> mounting databases just before and right after the nice clean reboot. >> >> I also looked in the MSExchangeManagement log under Applications and >> Services Logs - nothing in there, either. >> >> I'm thinking I should just delete and recreate the event. Seem reasonable? >> >> Kurt >> >> On Mon, Feb 2, 2015 at 3:51 PM, Michael B. Smith <[email protected]> >> wrote: >>> There is usually some pretty detailed information in the crimson log. >>> That's where I would go. >>> >>> -----Original Message----- >>> From: [email protected] >>> [mailto:[email protected]] On Behalf Of Kurt Buff >>> Sent: Monday, February 2, 2015 3:18 PM >>> To: [email protected] >>> Subject: [Exchange] Exchange 2010, SP3 backups not working >>> >>> All, >>> >>> I have a server (Hub, Transport and Database roles all in one) in our AU >>> office that has had a functioning backup to a file server share until the >>> 28th. >>> >>> I have checked the event logs, and see nothing untoward. >>> >>> I manually started the task, and the task interface says that it >>> completed successfully, but no new backup files appear on the file server >>> share. I expect the new ones to overwrite the old ones, but nothing dated >>> past the 28th. >>> >>> I even rebooted the server and tried again to manually run the job - same >>> thing. No errors, just messages from Backup saying that the Block Level >>> Backup Engine starts, then wbsexchange service starts three minutes later >>> and stops 5 minutes after that, and then some VSS Writer successes from >>> MSExchangeIS and some ESE ShadowCopy successes, then finally about 55 >>> minutes later the Block Level Backup Engine stops. >>> >>> Any place else I can look for clues on this? I've googled a fair amount, >>> but it seems my fu is weak. >>> >>> Kurt >>> >>> >> >> > > > > ________________________________ > Note: This message and any attachments is intended solely for the use of the > individual or entity to which it is addressed and may contain information > that is non-public, proprietary, legally privileged, confidential, and/or > exempt from disclosure. If you are not the intended recipient, you are > hereby notified that any use, dissemination, distribution, or copying of > this communication is strictly prohibited. If you have received this > communication in error, please notify the original sender immediately by > telephone or return email and destroy or delete this message along with any > attachments immediately.
