I must say that the subject line of this post greatly concerned me at first glance. I immediately assumed (for obvious reasons) that this meant that Shook's long planned upgrade to ShookieMonster 2.0 had gone terribly wrong. Whew....The relief. TVK
-----Original Message----- From: Kurt Buff [mailto:kurt.b...@gmail.com] Sent: Thursday, March 12, 2009 12:02 PM To: MS-Exchange Admin Issues Subject: Re: A very odd problem... I think the Exchange patch levels are the same on both boxes - Help/About on EMS for both machines says 6.5.7638.1 - but is there something else I should check? I could try doing the Exchange backup first, then appending the local backup to that. Kurt On Thu, Mar 12, 2009 at 05:22, Michael B. Smith <mich...@theessentialexchange.com> wrote: > There were early issues with vss causing backups to fail - most of the time > but not all - if you backed up the systemstate at the same time as Exchange. > I thought all of those were fixed by sp2 tho...You might try splitting them > up. > > Have you patched the backup server, specifically have you patched the > Exchange tools to match the Exchange server? > > What's going on in the logs and in the backup log? Only that single failure > message? > > -----Original Message----- > From: Kurt Buff [mailto:kurt.b...@gmail.com] > Sent: Wednesday, March 11, 2009 8:54 PM > To: MS-Exchange Admin Issues > Subject: Re: A very odd problem... > > Anyone? Bueller? > > After lots of fiddling, still no success. > > Can do the backups manually, but the batchfile tanks. I've even > regenerated the .bks file. > > Kurt > > On Thu, Mar 5, 2009 at 19:05, Kurt Buff <kurt.b...@gmail.com> wrote: >> All, >> >> In my UK office, I've got three servers - a DC, a file server and an >> E2k3 server - all are SP2���R2. There is no AV running on the Exchange >> server. >> >> The file server has an external LTO3 tape drive attached to it, and >> for about a year it was working just fine pulling backups from the >> Exchange server - I installed the ESM on it for just this purpose. >> The DC is doing a system state backup to a share the file server. >> >> However, the NTBackup batch job that I'm running to pull the Exchange >> backup to the file server's tape drive has recently stopped working . >> I was able to get it going again last month by rebooting the Exchange >> server, but it was failing with this error message: >> >> �� �� �� �� ��The requested media failed to mount. The operation was aborted. >>���������������The operation was ended. >> >> I am able to pull a backup by manually starting the wizard as the >> same user that the scheduled batch file was using and specifying the >> Exchange server's storage group. But when running as a batch file, >> whether launching the batch file manually or as a scheduled task, it >> fails to pull the backup of the Exchange server. The batch file backs >> up the entire file server first, then goes to the Exchange server. >> >> I just tried launching the batch file again, and the error message I >> got this time is different, but still a failure: >> >�������������� The network disk drive has stopped responding. Backup set >aborted. >> >> >> I'm not finding anything on google, either - most were regarding SBS, >> and pre-SP1 at that, and the rest don't seem to fit my circumstances. >> >> >> Any help much appreciated. >> >> Thanks, >> >> Kurt >> > > ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ > ~������������������ > http://www.sunbeltsoftware.com/Ninja �� �� �� �� �� �� �� ��~ > > > > ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ > ����������������� > http://www.sunbeltsoftware.com/Ninja������������������������~ > > ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ ~ http://www.sunbeltsoftware.com/Ninja ~ ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ ~ http://www.sunbeltsoftware.com/Ninja ~
