How do you do....it? Thread, exchange maintenance? in Technical; When using BackupExec to backup the information store I get this error
How to troubleshoot the error "A failure occurred ...
26th January 2010, 01:34 AM #16
When using BackupExec to backup the information store I get this error
How to troubleshoot the error "A failure occurred querying the Writer status" (a000fed1 HEX or e000fed1 HEX or 0xfffffed1 HEX) that occurs when a backup or restore is attempted
and have so far been unable to work out why so I use ntbackup to backup the store. Of course because of this I can't use the restore option in BackupExec for mailboxes.
Not sure on this one?
After the ntbackup has ran there are numerous entries from ESE about defragmentation on the database. What else should I be looking for? The ntbackup jobs are completing and the reports say successful.
Last edited by Edu-IT; 26th January 2010 at 01:38 AM.
IDG Tech News
26th January 2010, 09:56 AM #17
Back to BE basics here I think, where is the Backup Exec Application installed?
Is it on the Exchange server itself?
Do you have an Backup Exec Exchange License number appearing in the serial numbers list?
26th January 2010, 10:03 AM #18
BackupExec is installed on another server and I am using a remote agent to back it up.
Originally Posted by m25man
Yes there are keys there for the remote agent and the Exchange agent.
26th January 2010, 12:47 PM #19
Aha! Bingo! Jackpot! Whatever you want to say.
I think I've cracked it.
Edit: Working fine now! Recreated the ntbackup job and told it to overwrite the old backup. That seems to be it. Does that seem okay? Also, should I be verifying the backup or am I okay not to on this?
I'm also wondering whether it would be okay to move the backup from C: to F: where the storage groups are as this drive is bigger, C: is becoming rapidly full with the backup.
Last edited by Edu-IT; 26th January 2010 at 01:15 PM.
26th January 2010, 03:53 PM #20
I wouldn't commit a backup to the same volume as your data for obvious reasons.
1. Recovery, what if the drive fails completely.
2. Read/Write throughput.
If your hardware supports USB2 or ESATA why not target your backups to an external disk or NAS this is the defacto nowadays.
26th January 2010, 03:56 PM #21
Do you have the Exchange Server Management Tools from the Exchange CD installed on the Backup Server?
Originally Posted by Edu-IT
26th January 2010, 03:57 PM #22
Originally Posted by Edu-IT
26th January 2010, 05:08 PM #23
Yes management tools are installed.
The ntbackup job backs up to the C: drive before BackupExec kicks in ten minutes after the ntbackup job has finished and this then backs everything up to disk.
Would it be better to put the ntbackup somewhere else then? It's there for minutes before being backed up elsewhere so I'm not sure that backing up to another drive elsewhere is going to add any redundacy?
26th January 2010, 05:09 PM #24
Would be nice to work out why I'm having to use ntbackup over BackupExec though if you have any ideas still?
26th January 2010, 07:34 PM #25
I use BackUp Exec 11d to back up our Exchange 2007 box. Took a while to get it working right though. You do need the 'Remote Agent for Exchange 2007' not just a standard Remote Agent.
I also found out that if your backing up multiple Servers with remote agents the Exchange box has to be done first otherwise it would fail. Found a KB article on their site somewhere.
I have my transaction logs writing to a different set of (faster) disks than the stores, so it's quite easy to quickly see if the logs are being cleared out.
26th January 2010, 09:09 PM #26
If you've got time then it does no harm to do the verify but it's less useful when you're backing up to disc than tape (I think tape goes wrong far, far more often than disc!) The way the backup works, it will either complete and log the fact followed by deleting the log files or it won't complete - you shouldn't ever be in a situation where you think you've got a backup but it's not really there.
Originally Posted by Edu-IT
No real problem with backing up to the F: drive (assuming you've got space). It might be a bit slower but if you've got time in your overnight tasks then that's no big deal.
26th January 2010, 09:19 PM #27
Really? Have you got a link to such product?
Originally Posted by FragglePete
26th January 2010, 11:06 PM #28
One other thing which is absolutely critical with backups - make sure you know how to restore!
This is true for any backup but it's a bit more complex with Exchange. Since 2003, it's been possible to restore to a recovery storage group. This makes it quite easy to restore mail for a single user but it's not as easy as just restoring a few files and choosing a separate folder so you don't overwrite.
26th January 2010, 11:14 PM #29
Backup Exec AOFO appears to break restoring to recovery storage that for E2K3 (don't know about E2K7) i.e. do not backup an E2K3 in a multi-server job that needs AOFO switched on for other servers/parts of the backup.
Since 2003, it's been possible to restore to a recovery storage group
26th January 2010, 11:24 PM #30
I can't find an Exchange 2007 specific remote agent.
Originally Posted by PiqueABoo
Last edited by Edu-IT; 26th January 2010 at 11:30 PM.
By TechMonkey in forum Hardware
Last Post: 9th June 2009, 02:41 PM
By Bluetooth in forum Hardware
Last Post: 30th April 2008, 10:35 AM
By EvLPhenom in forum Recommended Suppliers
Last Post: 9th January 2008, 09:11 PM
By bishopsgarthstockton in forum How do you do....it?
Last Post: 24th November 2007, 07:55 PM
Users Browsing this Thread
There are currently 1 users browsing this thread. (0 members and 1 guests)