Table of Contents
UnLock Will not Run - Server Paused
2018-12-06
05-24-2007 08:24 AM Hi Kevin, Normally, when you see “server paused”, jobs would not be running. To remove the “server paused” simply do the following: 1. Select “Devices” tab in Backup Exec 2. Right-click on the server name and select “Paused” to “un-pause” the server. Everything should now be back to “normal”. Regards, Christiane.
From <https://vox.veritas.com/t5/Backup-Exec/A-Simple-Question-Server-Paused/td-p/138931>
system lock chk bkup sw cfg
From: https://www.veritas.com/support/en_US/article.TECH67698
HKLM\software\Symantec\Backup Exec for Windows\Adamm\Disable Library Door Lock
Catalog Location
From: http://serverfault.com/questions/259324/how-to-backup-symantec-backup-execs-catalog
look at the catalog settings in the Options menu, under "Settings" and "Catalog", and see where the catalogs are stored
Catalog Period
From: http://serverfault.com/questions/259324/how-to-backup-symantec-backup-execs-catalog
I wonder if your catalog retention period is set to an exceedingly long period, regular catalog pruning operations aren't taking place, or something has gone crazy. I'd have a look at the catalog settings in the Options menu, under "Settings" and "Catalog", and see what the retention period looks like. Do you see any odd "alerts" re: catalogs?
Backup Exec tapes refuse to catalog
From: http://pcloadletter.co.uk/2012/02/08/backup-exec-tapes-refuse-to-catalog/
The workaround was was to select the problem tapes in the Media tab, associate them with the Retired Media Media Set, then right-click and delete them from the media view. This removes any mention of that media from Backup Exec’s database. Then rescan the autoloader’s slots in the Devices tab, and run an Inventory job on them all. Finally, run the Catalog job once again – then it works.
How to run a dump database with the Backup Exec for Windows Servers Utility (BEUtility) to backup the database file to hard disk
From: http://www.symantec.com/business/support/index?page=content&id=TECH83082
To manually take a backup of a Backup Exec database, use the Dump database option of BEUtility. The database file is dumped to a file on the hard disk and is maintained until the next dump operation.
Notes
Unable to open the item \\G-SERVER1\E:\TSM1058175DATA\Dat.mdf - skipped. Unable to open the item \\G-SERVER1\E:\TSM1058175DATA\log.ldf - skipped.
Update to SP4
INstall SP4, and then push-install the application's updates to the RAWS agents. So you did that all by the book.
Right I thought I best update this thread as I have FINALLY solved this issue! For some reason "pushing" the agent didnt seem to work quite right (even though it said successful and could back up the drives). After installing SP4 I then had to go to each Win2k3 machine: •log in using the service account (so the account backup exec would use) •Ensure the service account has these credentials •- Administrator, Backup Operators, Domain Admin, DnsAdmin, Enterprise Admin, Group Policy creator ownsers, Schema Admins. •I am sure they are not all neccessary but I do not have time to find out the only ones you need. A Must is Domain Admins must be set as Primary Group •Make sure no other users are logged on to it remotely, this is imperative otherwise the agent will not uninstall correctly!!! •So then uninstall the agent. •Map a network drive to the media server i.e. \\Server_Name\c\Program Files\Symantec\Backup Exec\Agents\RAWS32 - then run "setup.exe". Basically pulling the agent down rather than pushing it, follow the setup instructions. •Job Done! So installing the agent that way allowed me to backup VSS & System state on the servers.
Symantec BackupExec Utility
C:\Program Files\Symantec\Backup Exec\BEUtility.exe Database repair and other tools
Backup program is unsuccessful when you back up a large system volume
From: http://support.microsoft.com/default.aspx?scid=kb;en-us;304101
Veritas error: v-79-57344-33992
V-79-57344-33992 - The request could not be performed because of an I/O device error.
V-79-57344-33992 - The backup storage device has failed.
•Quantum SuperLoader 3
1. Run LiveUpdate on your media server, apply all the patches available, and then run the Device COnfiguration Wizard to install the drivers.
2. Go to the link below and hit the Drivers tab. You can then filter for BE 12.5.
http://www.symantec.com/business/support/index?page=content&key=15047&channel=TECHNICAL_SOLUTION&basecat=DOWNLOADS
If the drivers don't work, then you have a hardware error.
Notes
Storage device "QUANTUM 1" reported an error on a request to read data from media.
Error reported:
The request could not be performed because of an I/O device error.
V-79-57344-33992 - The backup storage device has failed.
In most of the cases, these messages are being reported due to hardware issue with
either the controller or,
more likely, a device that is attached to the controller.
The hardware problems can be associated with
poor cabling,
incorrect termination
or transfer rate settings,
lazy or slow device responses to relinquish the SCSI bus,
a faulty device, or,
in very rare cases, a poorly written device driver
Check: http://support.microsoft.com/?kbid=154690
From: http://www.symantec.com/connect/forums/backup-exec-job-fails-0
"netstat -a -b"
NDMP port 10000 reserve for beremote.exe
Note to Change this port number:
http://www.symantec.com/business/support/index?page=content&id=TECH24410 and
http://www.symantec.com/business/support/index?page=content&id=TECH45768
remote agent on the remote server matches the version
From: http://www.symantec.com/business/support/index?page=content&id=TECH78329
2. Confirm that the SQL(Bkupexec) service on the Media server is running under Local System Account 3. Confirm that the Backup Exec Remote Agent For Windows Systems is running under Local System account on all the servers being backed up Note: Backup Exec account needs to be a Domain Administrator with the following rights mentioned in the article
Turn off Firewall in SBS 2003
Server 2008 info at computerperformance.co.uk
http://www.computerperformance.co.uk/w2k3/index.htm
In a nutshell Microsoft's Windows Server 2008 is more forgiving then W2K3, in particular it requires less work to install and configure the server's role on the network. I hope that you enjoy exploring the new 'Longhorn' features as much as I did.