Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
- VOX
- Data Protection
- Backup Exec
- Exchange Backup.
Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
Exchange Backup.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-02-2005 02:48 AM
Problems backing up Indidividual mailboxes and Information Store. Error e000fe09- The directory is invalid.
Product version:- Backup Exec 10d for windows Servers.
Server:- Windows 2003.
Although the public folder are able to be backed up successfully.
Any help appreciated.
Kind regards
Nicole
Product version:- Backup Exec 10d for windows Servers.
Server:- Windows 2003.
Although the public folder are able to be backed up successfully.
Any help appreciated.
Kind regards
Nicole
Labels:
3 REPLIES 3
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-02-2005 08:33 AM
Can you provide more details? That will help narrow it down.
Are you attempting to backup the mailbox(es) and Information Store at the same time?
Are all storage groups/databases mounted?
Are you using an Offhost backup method?
Using Snapshots (AOFO)?
Is this also a Lotus server by chance?
Is Site Replication Service being used by Exchange?
Is this being run on a Central Admin server setup?
Are you attempting to backup the mailbox(es) and Information Store at the same time?
Are all storage groups/databases mounted?
Are you using an Offhost backup method?
Using Snapshots (AOFO)?
Is this also a Lotus server by chance?
Is Site Replication Service being used by Exchange?
Is this being run on a Central Admin server setup?
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-02-2005 09:29 AM
Hi Dave, Thanks for your reply here is the answers to the additional information you require:-
Are you attempting to backup the mailbox(es) and Information Store at the same time?. Selections are via the same Backup job..
Are all storage groups/databases mounted?. Yes.
Are you using an Offhost backup method? No.
Using Snapshots (AOFO)?. No, remote server agent, and Exchange server agent.
Is this also a Lotus server by chance? No. It’s an Exchange server. Installed on the Exchange server is:- Exchange 2003 Service Pack1, Windows 2003 Server Service Pack1. The Exchange Server is a child domain, of a parent Server which is located in the US.
Is Site Replication Service being used by Exchange? No.
Is this being run on a Central Admin server setup?. Backups are run on a dedicated Windows 2003 server, and backed up to a Robotic Library.
Additonal error messages from log file:-
Unable to attach to this resource. Make sure that this resource exists, and then try again.
The Media Server was unable to connect to Remote Machine MARGE. The machine could not be found on the network.
The Media Server will fall back on the local agent to try and complete the operation.
WARNING: Media servers cannot completely protect remote
Windows-based servers or workstations unless the Backup
Exec Remote Agent is installed
and running on each remote Windows-based server or
workstation to be protected. Data loss can occur if the
Remote Agent is not running
while backing up remote Windows-based computers.
Please refer to the documentation or online help for more information.
AOFO: Initialization failure on: "\\Server\Microsoft Exchange Mailboxes". Advanced Open File Option used: No.
Unable to attach to this resource. Make sure that this resource exists, and then try again.
AOFO: Started for resource: "\\Server\Shadow?Copy?Components". Advanced Open File Option used: Microsoft Volume Shadow Copy Service (VSS).
The following volumes are dependent on resource: "C:" .
The snapshot provider used by VSS for volume C: - Microsoft Software Shadow Copy provider 1.0 (Version 1.0.0.7).
Network control connection is established between Ip address:3038 <--> Ip address:10000
Network data connection is established between Ip address:3043 <--> Ip address:31347
And another error:-
Set type : BackupSet status : CompletedSet description :
Resource name : \\server\Microsoft Information Store\First Storage GroupLogon account : System Logon Account
Error : e000fe09 - The directory is invalid.
Cheers Nicole.
Are you attempting to backup the mailbox(es) and Information Store at the same time?. Selections are via the same Backup job..
Are all storage groups/databases mounted?. Yes.
Are you using an Offhost backup method? No.
Using Snapshots (AOFO)?. No, remote server agent, and Exchange server agent.
Is this also a Lotus server by chance? No. It’s an Exchange server. Installed on the Exchange server is:- Exchange 2003 Service Pack1, Windows 2003 Server Service Pack1. The Exchange Server is a child domain, of a parent Server which is located in the US.
Is Site Replication Service being used by Exchange? No.
Is this being run on a Central Admin server setup?. Backups are run on a dedicated Windows 2003 server, and backed up to a Robotic Library.
Additonal error messages from log file:-
Unable to attach to this resource. Make sure that this resource exists, and then try again.
The Media Server was unable to connect to Remote Machine MARGE. The machine could not be found on the network.
The Media Server will fall back on the local agent to try and complete the operation.
WARNING: Media servers cannot completely protect remote
Windows-based servers or workstations unless the Backup
Exec Remote Agent is installed
and running on each remote Windows-based server or
workstation to be protected. Data loss can occur if the
Remote Agent is not running
while backing up remote Windows-based computers.
Please refer to the documentation or online help for more information.
AOFO: Initialization failure on: "\\Server\Microsoft Exchange Mailboxes". Advanced Open File Option used: No.
Unable to attach to this resource. Make sure that this resource exists, and then try again.
AOFO: Started for resource: "\\Server\Shadow?Copy?Components". Advanced Open File Option used: Microsoft Volume Shadow Copy Service (VSS).
The following volumes are dependent on resource: "C:" .
The snapshot provider used by VSS for volume C: - Microsoft Software Shadow Copy provider 1.0 (Version 1.0.0.7).
Network control connection is established between Ip address:3038 <--> Ip address:10000
Network data connection is established between Ip address:3043 <--> Ip address:31347
And another error:-
Set type : BackupSet status : CompletedSet description :
Resource name : \\server\Microsoft Information Store\First Storage GroupLogon account : System Logon Account
Error : e000fe09 - The directory is invalid.
Cheers Nicole.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-02-2005 11:15 AM
oh... you have a variety of issues. :p
First off, I would seperate you IS backup from the Mailbox backups. Do this for two reasons: 1) It is much easier to plan a backup window around these seperately since the backup of an IS will be far faster than the mailbox backup. Mailbox backups are quite slow due to limits on MAPI (each individual message is open and closed during backup) By having these together, your IS is done, but the job will not compelete until much later due to the mailbox speed and you never know when a power failure or other annoyance will pop up. :) 2) it makes troubleshooting much easier.
Here are some of your issues:
Unable to attach to this resource. Make sure that this resource exists, and then try again.
If this is for the mailbox portion of the job:
- This can occur when you are using a mailbox which is not unique in order to connect to the mailbox resources to do the backup. For instance, you have BE services using the Administrator mailbox to connect to mailboxes, but then someone creates a Administrator2 account. Now that it is no longer unique, it can throw up the "unable to attach" message.
- If you have a backup job which has "Archive" selected as the general File backup method, then the "Unable to attach" message will be displayed since BE cannot atach to a mailbox to archive it.
If it is for the IS part of the job, see below:
The Media Server was unable to connect to Remote Machine MARGE. The machine could not be found on the network.
WARNING: Media servers cannot completely protect remote
Windows-based servers or workstations unless the Backup Exec Remote Agent is installed
- It seems as though you have the remote agent license installed, but did you push the remote agent itself from the media server to the exchange server? Do this under Tools\Serial Numbers and Installation. Select Remote isntall and deselect the local install option. Target the exchange server and select remote agent.
AOFO: Started for resource: "\\Server\Shadow?Copy?Components". Advanced Open File Option used: Microsoft Volume Shadow Copy Service (VSS).
- Check your job settings and see if you actually did select the "Use advanced open file option" from the AOFO node. I am not sure what OS you have, but if it is pre-2003 you won't have the writer to use, and if it is SBS then the writer is turned off by default. Microsoft has a technote on how to turn it on for SBS.
Error : e000fe09 - The directory is invalid.
This one is a bit harder since many things cause it, some more common ones:
- On a storage group for exchange, this can be caused when the job was created for an existing storage group which later was deleted. Then a new storage group is created with the same name. The id number of the new storage group no longer matches the one BE is looking for so it fails.
- Snapshots (AOFO) of Site Replication Service will cause this. We know from above that AOFO tried to run so this is possible.
I'm sure there are other issues as well. Try clearing up the ones mentioned above and try an IS job seperate from the mailbox job. If that works, run a mailbox only job. See which one is causing which errors if any.
Dave
First off, I would seperate you IS backup from the Mailbox backups. Do this for two reasons: 1) It is much easier to plan a backup window around these seperately since the backup of an IS will be far faster than the mailbox backup. Mailbox backups are quite slow due to limits on MAPI (each individual message is open and closed during backup) By having these together, your IS is done, but the job will not compelete until much later due to the mailbox speed and you never know when a power failure or other annoyance will pop up. :) 2) it makes troubleshooting much easier.
Here are some of your issues:
Unable to attach to this resource. Make sure that this resource exists, and then try again.
If this is for the mailbox portion of the job:
- This can occur when you are using a mailbox which is not unique in order to connect to the mailbox resources to do the backup. For instance, you have BE services using the Administrator mailbox to connect to mailboxes, but then someone creates a Administrator2 account. Now that it is no longer unique, it can throw up the "unable to attach" message.
- If you have a backup job which has "Archive" selected as the general File backup method, then the "Unable to attach" message will be displayed since BE cannot atach to a mailbox to archive it.
If it is for the IS part of the job, see below:
The Media Server was unable to connect to Remote Machine MARGE. The machine could not be found on the network.
WARNING: Media servers cannot completely protect remote
Windows-based servers or workstations unless the Backup Exec Remote Agent is installed
- It seems as though you have the remote agent license installed, but did you push the remote agent itself from the media server to the exchange server? Do this under Tools\Serial Numbers and Installation. Select Remote isntall and deselect the local install option. Target the exchange server and select remote agent.
AOFO: Started for resource: "\\Server\Shadow?Copy?Components". Advanced Open File Option used: Microsoft Volume Shadow Copy Service (VSS).
- Check your job settings and see if you actually did select the "Use advanced open file option" from the AOFO node. I am not sure what OS you have, but if it is pre-2003 you won't have the writer to use, and if it is SBS then the writer is turned off by default. Microsoft has a technote on how to turn it on for SBS.
Error : e000fe09 - The directory is invalid.
This one is a bit harder since many things cause it, some more common ones:
- On a storage group for exchange, this can be caused when the job was created for an existing storage group which later was deleted. Then a new storage group is created with the same name. The id number of the new storage group no longer matches the one BE is looking for so it fails.
- Snapshots (AOFO) of Site Replication Service will cause this. We know from above that AOFO tried to run so this is possible.
I'm sure there are other issues as well. Try clearing up the ones mentioned above and try an IS job seperate from the mailbox job. If that works, run a mailbox only job. See which one is causing which errors if any.
Dave
