Backup Exec 10 failure after install SCCM 2007 Client/Secondary Site
We are running Backup Exec to backup a remote Windows 2003 AD/File/Print server which we have also installed the SCCM 2007 client and have made the server a secondary SCCM site. Since we made the server a secondary the Backup Exec 10 backups have been failing with the following error. Has anyone seen thiserror with Backup Exec 10 and SCCM 2007 client/secondary sites? I knowSymantec solution will be upgrade Backup Exec to anewer version, but I need togetbackups ASAP. Any help is much appreciated! Job ended: Friday, October 02, 2009 at 1:46:10 AM Completed status: Failed Final error: 0xe00084af - The directory or file was not found, or could not be accessed. Final error category: Job Errors For additional information regarding this error refer to link V-79-57344-33967
October 21st, 2009 5:25pm

All the SCCM directories are excluded from the backup solutions Every SCCM directory has been excluded from the backups. Any other ideas?
Free Windows Admin Tool Kit Click here and download it now
October 21st, 2009 7:18pm

You've only pasted the error message in this thread. What does your full Job Log look like? It should specify what exactly is not found or accessible.
October 22nd, 2009 11:15am

This is all the shows up in the log. when the Backup Exec tries to backup the remote server (which is the SCCM secondary) this is all that is in the logs. The log does not specify particular files or components. I have tried including only data folders (user home directories, department shares, etc) and left all other directories and shadow copy components unchecked in the backup selection list and it fails everytime if the SCCM secodary services are started. Note we have other servers that are running Backup Exec 11d and new versions that are SCCM secondaries that do not have this issue, it only happens withversion 10. Job Completion Status Job ended: Tuesday, October 13, 2009 at 1:48:01 AM Completed status: Failed Final error: 0xe00084af - The directory or file was not found, or could not be accessed. Final error category: Job Errors For additional information regarding this error refer to link V-79-57344-33967 Errors Click an error below to locate it in the job log Backup- <Server Name>Directory was not found, or could not be accessed. None of the files or subdirectories contained within will be backed up. Directory was not found, or could not be accessed. None of the files or subdirectories contained within will be backed up.
Free Windows Admin Tool Kit Click here and download it now
October 22nd, 2009 5:55pm

Eirik,This is the extend of the detail. It does this for everything is tries to backup on the secondary. Unfortunately there is not much detail. Thanks again for your help! FROM JOB History: Set type : BackupSet status : CompletedSet description : Resource name : \\<ServerName>\D:Logon account : <DOMAINNAME>\<USERACCOUNT> Error : e00084af - The directory or file was not found, or could not be accessed. Agent used : YesAdvanced Open File Option used : NoImage used : No From Job Log: Server - <ServerName> Network control connection is established between <IP Address>:4609 <--> <IP Address>::10000 Network data connection is established between <IP Address:4614 <--> <IP Address>:4052 Directory was not found, or could not be accessed. None of the files or subdirectories contained within will be backed up. Directory was not found, or could not be accessed. None of the files or subdirectories contained within will be backed up.
October 22nd, 2009 6:42pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics