Error: 1
This is a common error message that occurs when a user is deleted and the
mailbox retention time is set to a value other than 0.
The Job Notification reports:
(Server: “Servername”) (Job: “Backup 00006″) Backup 00006 — The job
failed with the following error: The directory is invalid.
The error in the job log reports:
Completed status: Failed
Final error: 0xe000fe09 – The directory is invalid.
Final error category: Resource Errors
For additional information regarding this error refer to
link V-79-57344-65033
Backup- \\SERVER\Microsoft Exchange Mailboxes V-79-57344-65033
- Directory not found. Cannot backup directory ?User Name [uname] and its subdirectories.
Link to Veritas Support Doc:
mhttp://seer.entsupport.symantec.com/docs/241981.htm
You can set the deleted mailbox retention time to 0 to fix the
problem, but this will disable the ability to recover a deleted
mailbox. Open the Server Management screen on the server and
expand the Advanced Management section. Drill down through the
Exchange instance, Servers, Servername, First Storage Group,
Mailbox Store. Right click on the Mailbox Store and select
Properties. Go to the Limits tab, and change the option Keep
Deleted Mailboxes for (Days) to the appropriate amount of
days that the mailbox should stay on the server to 0.
The other option is to train the person that is responsible
for deleting users to purge the mailbox after deleting the
user. Open the Server Management screen on the server and
expand the Advanced Management section. Drill down through
the Exchange instance, Servers, Servername, First Storage
Group, Mailbox Store, Mailboxes. Right click the Mailboxes
folder in the left pane and click the Run Cleanup Agent.
Recently deleted user’s mailboxes will be in the list with
a small red “x” on them. Right click the recently deleted
user.s mailbox and select Purge. Please note that selecting
yes will permanently delete the mailbox and the email therein
will not be retrievable except from previous backups.
Error: 2
I have only run into this error once, and I am still not
sure what caused the problem. My guess is that a program
that included an SQL SP3a backend was installed on the
server that had SP4 already installed on it.
The job log reported:
V-79-57344-33938 – Backup or restore operation terminated
abnormally. An error occurred on a query to database.
0xe0008492 – Database Query Failure. See the job log for details.
Link to Veritas Support Doc:
http://seer.entsupport.symantec.com/docs/276443.htm
The solution was as follows:
- In the SQL 7.0 installation path (by default \Mssql7\Binn)
rename the DLL’s Sqlresld.dll and Sqlvdi.dll to
Sqlresld7.old and Sqlvdi7.old
- Copy from the SQL 2000 installation path (by default
\Program Files\Microsoft SQL Server\80\COM) the DLL’s
Sqlresld.dll and Sqlvdi.dll into the SQL 7.0 installation
path (by default \Mssql7\Binn)
- According to the Microsoft article, it is also recommended
to place the Sqlunirl.dll and Sqlsvc.dll (into \Mssql7\Binn)
due to the DLL’s dependencies.
Before I overwrote the files as the support document suggested,
I checked the file dates and sizes. The files to be overwritten
were older. I also stopped all SQL services before overwriting
the files, though the article did not specify to do so.
Error: 3
This was a seemingly random error that occurred out of the blue
after several weeks of successful backups.
The job log reported:
Completed status: Failed
Final error: 0xe00084f8 – The network connection to the Backup
Exec Remote Agent has been lost. Check for network errors.
Final error category: Resource Errors
Backup- SERVER\SHAREPOINT AOFO: Initialization failure on:
“\\SERVER\Microsoft Information Store\First Storage Group”.
Advanced Open File Option used: No.
The network connection failed during the snapshot. Check
the network, and then run the job again.
V-79-57344-65072 – The Exchange Store service is not
responding. Backup set canceled.
AOFO: Initialization failure on: “Shadow?Copy?Components”.
Advanced Open File Option used: No.
The network connection failed during the snapshot. Check the
network, and then run the job again.
V-79-57344-65072 – The connection to target system has
been lost. Backup set canceled.
This was resolved by changing the Resource Order of the
Exchange items. The Veritas solution was to try to backup
the Exchange Public Folders and Mailboxes in separate
jobs, but I found an alternate solution that resolved
the problem. It was as simple as setting the Public
Folder Store to be backed up before the Mailbox Store.
Thanks to the original poster in the Veritas Newsgroups.
I was not able to find the Newsgroup thread again to give
proper credit to the gentleman who came up with the solution.