mshabalin
asked on
Wierd error when performing Backup2Disk - BackupExec 11d
Hello Experts,
I'm getting this wierd error when performing Backup to Disk.
V-79-57344-4611 - An error occurred creating or accessing the directory ???? specified for this operation. Ensure that the directory is accessible and can be written to.
The "????" marks shows all kind of ascii symbols, each backup the different set
The screenshot of this error can be seen here:
http://www.msbdigital.com/SC/veritas_error.JPG
When running the same selection list on backup tape the job runs flawless. The error happens only when running the job on Backup2Disk
The backup is performed locally+ remote agents.
The error happens on the remote server running exchange 2003.
Please Help!
I'm getting this wierd error when performing Backup to Disk.
V-79-57344-4611 - An error occurred creating or accessing the directory ???? specified for this operation. Ensure that the directory is accessible and can be written to.
The "????" marks shows all kind of ascii symbols, each backup the different set
The screenshot of this error can be seen here:
http://www.msbdigital.com/SC/veritas_error.JPG
When running the same selection list on backup tape the job runs flawless. The error happens only when running the job on Backup2Disk
The backup is performed locally+ remote agents.
The error happens on the remote server running exchange 2003.
Please Help!
Japanese characters cause erratic behavior in job names, policy names, template names and selection list names.
http://support.veritas.com/docs/287922
After performing Granular Restore Technology (GRT) enabled restore, Japanese Exchange mail message appears unreadable
http://support.veritas.com/docs/288398
Backup Exec 10.x - 11.d for Windows Servers: Synthetic incremental backup misses or duplicates directories with double-byte count properties.
http://support.veritas.com/docs/285986
http://support.veritas.com/docs/287922
After performing Granular Restore Technology (GRT) enabled restore, Japanese Exchange mail message appears unreadable
http://support.veritas.com/docs/288398
Backup Exec 10.x - 11.d for Windows Servers: Synthetic incremental backup misses or duplicates directories with double-byte count properties.
http://support.veritas.com/docs/285986
ASKER
Hello Experts,
Thank you for your replies.
I've installed all possible Service packs , patches and updates, and my exchange has nothing to do with Japanese characters as we are located in Canada and use English language only.
The problem still persists and occurs only when using Backup2Disk backup. The same selection list works just fine when backing up to tape.
Any ideas?
Thanks a bunch!
Thank you for your replies.
I've installed all possible Service packs , patches and updates, and my exchange has nothing to do with Japanese characters as we are located in Canada and use English language only.
The problem still persists and occurs only when using Backup2Disk backup. The same selection list works just fine when backing up to tape.
Any ideas?
Thanks a bunch!
In the screenshot, the errors happens just before the Utility Partition backup.
Is this always the case?
What resource is backed up just before the "Utility Partition"?
Is this always the case?
What resource is backed up just before the "Utility Partition"?
ASKER
honmapog:
The resource is D: driver on my Exchange server, and yes it happens all the time.
The drive has some user's PST files on it and the Exchange log directory.
The resource is D: driver on my Exchange server, and yes it happens all the time.
The drive has some user's PST files on it and the Exchange log directory.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
hi i also have the same problem, only when try to restore the individual mail messages. the backup goes through perfectly, and i am able to restore all other data, i.e files and folders.
Does it happen on every backup set? (C, D, Microsoft Information Store). Or only on backups of Exchange (Microsoft Information Store)?
If it happens only on Exchange, make sure you're running revision/build 7170 of Backup Exec (not 6235). Also make sure to apply SP1 for build 7170 and then apply any other hotfixes via LiveUpdate.