Backup exec engine crashing - ver 9.1
Hey Guys, First off I'm new to this, and the company I work for AND I get to deal with the previous persons mess. Doesn't help I was trapped behind a helpdesk for a couple years. I've looked around for a couple of fixes but couldn't find anything solid. Ran a test yesterday for backup exec and it was sucessful. But it crashed before I left to go home Error: szAppName : bengine.exe szAppVer : 9.1.4691.58 szModName : bemsdk.dll szModVer : 9.1.4691.0 offset : 0007809f Event log: Tuesday - Incremental") Tuesday - Incremental -- The job failed with the following error: The Backup Exec job engine system service is not responding. This morning when I come in the job is still running for wed, so I don't want to try anything just yet. If it failed overnight I was going to come in this morning and reboot the box, can any suggest a fix if you had this problem before? Thanks
B2D extremely slow?
Recently our tape library died, making all of our tape backups worthless as the model has been discontinued by Sony and it makes little sense to pay more than MSRP for used components. So I thought I'd give backup-to-disk a chance and was considering using a collection of cheap USB drives instead of tapes. I reasoned that the speed should be faster than tape, but instead I found that the tape drive was doing about 450-500 MB/min, while the B2D backup only recorded about 35 MB/min. The full backup job we run on Saturdays usually takes 12 hours, but when I came in Monday morning I found the B2D job was still running after 35 hours and was only about 75% done. Obviously this is unacceptable. Is there something I am doing wrong? I know USB is not as fast as SCSI, but even so it should be doing better than 35 MB/min right?BackupExec skipping other Symantec files
Found this in our BE logs. This is BE 10d SP4. The item C:\Program Files\VERITAS\Backup Exec\NT\Catalogs\{0D072BCE-DCFE-48AD-800B-0CDBC23A2E4D}_1.img in use - skipped. The item C:\Program Files\VERITAS\Backup Exec\NT\Data\BEX_SERVER_02580.xml in use - skipped. The item C:\Program Files\VERITAS\Backup Exec\NT\Logs\adamm.log in use - skipped. The item D:\Program Files\Symantec\Symantec Endpoint Protection\AVMan.log in use - skipped. The item D:\Program Files\Symantec\Symantec Endpoint Protection\GUProxy.log in use - skipped. The item D:\Program Files\Symantec\Symantec Endpoint Protection\LUMan.log in use - skipped. The item D:\Program Files\Symantec\Symantec Endpoint Protection\NacMan.log in use - skipped. The item D:\Program Files\Symantec\Symantec Endpoint Protection\processlog.log in use - skipped. The item D:\Program Files\Symantec\Symantec Endpoint Protection\rawlog.log in use - skipped. The item D:\Program Files\Symantec\Symantec Endpoint Protection\seclog.log in use - skipped. The item D:\Program Files\Symantec\Symantec Endpoint Protection\SnacDebug.log in use - skipped. The item D:\Program Files\Symantec\Symantec Endpoint Protection\syslog.log in use - skipped. The item D:\Program Files\Symantec\Symantec Endpoint Protection\tralog.log in use - skipped. The item D:\Program Files\Symantec\Symantec Endpoint Protection Manager\data\inbox\log\ersecreg.log in use - skipped. The item D:\Program Files\Symantec\Symantec Endpoint Protection Manager\data\inbox\log\exsecars.log in use - skipped. The item D:\Program Files\Symantec\Symantec Endpoint Protection Manager\db\out.log in use - skipped. The item D:\Program Files\Symantec\Symantec Endpoint Protection Manager\db\sem5.db in use - skipped. The item D:\Program Files\Symantec\Symantec Endpoint Protection Manager\db\sem5.log in use - skipped. The item D:\Program Files\Symantec\Symantec Endpoint Protection Manager\tomcat\logs\agent_register-0.log in use - skipped. The item D:\Program Files\Symantec\Symantec Endpoint Protection Manager\tomcat\logs\agent_register-0.log.lck in use - skipped. The item D:\Program Files\Symantec\Symantec Endpoint Protection Manager\tomcat\logs\catalina.err in use - skipped. The item D:\Program Files\Symantec\Symantec Endpoint Protection Manager\tomcat\logs\catalina.out in use - skipped. The item D:\Program Files\Symantec\Symantec Endpoint Protection Manager\tomcat\logs\db_connection-0.log in use - skipped. The item D:\Program Files\Symantec\Symantec Endpoint Protection Manager\tomcat\logs\db_connection-0.log.lck in use - skipped. The item D:\Program Files\Symantec\Symantec Endpoint Protection Manager\tomcat\logs\localhost_scm_log.2010-07-15.txt in use - skipped. The item D:\Program Files\Symantec\Symantec Endpoint Protection Manager\tomcat\logs\replication-0.log in use - skipped. The item D:\Program Files\Symantec\Symantec Endpoint Protection Manager\tomcat\logs\replication-0.log.lck in use - skipped. The item D:\Program Files\Symantec\Symantec Endpoint Protection Manager\tomcat\logs\scm-server-0.log in use - skipped. The item D:\Program Files\Symantec\Symantec Endpoint Protection Manager\tomcat\logs\scm-server-0.log.lck in use - skipped. I have never seen these files skipped in other BE isntallations, no matter the BE version. I'm afraid that in a disaster situation where we had to restore from backup, my SEPM installation would be hosed. Thoughts? Let's also try for answers that don't insist on updating to another version (that will be last resort). Let me know if you need further information.
Symantec BackupExec Duplicate Jobs
Hi all: The situsation we have here Symantec Backup Exec 12.5 configured as the following: B2D weekly----------------------------->Duplicate to Tape No problem here as the Dupe job is linked to Weekly B2D directly We have a scheduled Dupe job Monthly to take B2D at the end of month (Last Friday) to Tape. the problem we have here that Sceduled Dupe job is trying to backup all media sets in the B2D pool, we keep B2D data for a as long as we can so we have muliple sets, What I am trying to say , can we run Scheduled Duplicate Backup job to backup only last set not all media sets in the source? Regards
When to use "Enable advanced log backup options"
I would like to do transaction log backups to be able roll forward using a transaction log backup. When I select the backup method "Log - Back up transaction log" I get the option to "Enable advanced log backup options." It looks like this option either puts the SQL database in a loading or standby state. I have searched and cannot find any explanation on when one should enable this option. I do not want to do anything with the DB except to backup the transaction logs. I was hoping someone could educate me as to when I would/would not use the advanced log backup options.