ContributionsMost RecentMost LikesSolutionsRe: BE failling to run jobHi, Kindly perform the following to isolate the cause of issue; 1. Move one media to Scratch media set. 2. Configure an ovewrite backup job. 3. Run the job and verify the result. 4.Check for any active alerts in Alert tab. Hopefully this would resolve your issue. Thanks JavedRe: Slow throughput with remote agent (BE 9.1 SP2) SBS 2003Hi' There are number of steps to be followed, 1)Are you using AOFO. Kindly refer to this technote:- http://seer.support.veritas.com/docs/263139.htm 2)This could be a network related issue aswell. Try Copying any large folder from the remote server and check the throughput. 3)Try performing a backup job on backup to disk folder so that we can make sure it is not a device related isue. 4)Check the version which is being used on the remote server for the compatibility issue. Trying out these steps would hopefully resolve your issue. ThanksRe: Alpha suppoprtHi Eddy, You cannot perform an agentless backup. You need to purchase an extra licence for backing up your new Exchange 2003 server. Please note:- You will find; there is no support for the Alpha platform in 9.1 because it has not been supported by MS since 31-Dec 2001. Thanks JavedRe: Backup failed ErrorHi, To resolve this error refer to the following technote: Title: An error message: "When accessing a new tape of a multi volume partition the current block size is incorrect" is displayed when performing an erase media operation. URL: http://support.veritas.com/docs/190750 If the issue persists please revert back with the following logs in a single ZIP file: 1. Begather file: How to run the BEGATHER utility http://seer.support.veritas.com/docs/264719.htm 2. Job log : Refer to the following technote: <> 3. SGMON Log (start sgmon.exe just before starting the backup job; this helps us see the sequence of events) How to create SGMON.LOG please refer the following technote <> Note: Start sgmon before starting the Backup Exec/backup/restore operation. 4. System Information file (for Windows 2000) Select My Computer--->Right Click --->Manage --->Select System Information --->Save As (.txt and .nfo) System Information file (for Windows 2003) - Run winmsd.exe >Save As >5.0/6.0 version (.nfo format) Thanks JavedRe: Failed JobsHI; according to the question asked by you that u would like to know a quicker way for finding errors by not going into job logs. Unfortunately this is not possible. A backup job when fails gives a poppup for the specific category of reason. Uusually for backup selections where open files are present and AOFO is not used the the job gives a pop up saying the job succeeded but with exceptions. And for the other reson for not being able to attach the drive it gives a pop up saying not able to attach the drive or access denied but to know the exact issue we have to go to job logs. U can try to split jobs and verify as well. Thanks JavedRe: Intelligent Disaster Recovery Wizard Not Creating ISO Image FilesHi Kindly have a look at the technote below ; How to create an Intelligent Disaster Recovery CD image for Windows NT or Windows 2000 servers with Backup Exec 9.x http://support.veritas.com/docs/257061. Thanks JavedRe: Creating Recyclable MediaHi Recyclable Media:- It is nothing but a Allocated Media that is part of a User Media Set and has had its overwrite retention period expire. The media is available for overwrite operations or append operations (append operations are only possible if the "Append Period" still allows the media to be appended to). The media will be displayed in blue under the User Media Set. For more details kindly refer the following technical notes:- 1)Document ID: 192265 http://support.veritas.com/docs/192265 The basics of Advanced Device and Media Management for VERITAS Backup Exec (tm) for Windows Servers 2)Document ID: 237374 http://support.veritas.com/docs/237374 An explanation of the "Overwrite Protection Period" and the "Append Period" Thanks Javed