Differences

This shows you the differences between two versions of the page.

--- software:backupexec [2015/11/07 22:36] – superwizard
+++ software:backupexec [2020/09/22 03:24] (current) – [Notes] superwizard
@@ Line 1: / Line 1: @@
+====== UnLock Will not Run - Server Paused ======
+-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:
+.  Select "Devices" tab in Backup Exec
+.  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 ======
@@ Line 41: / Line 64: @@
     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.
+From: http://www.symantec.com/connect/forums/backupexec-125-sp4-keeps-failing-system-state-backup-v-79-57344-65149
+    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.
+From: http://www.symantec.com/connect/forums/backupexec-125-sp4-keeps-failing-system-state-backup-v-79-57344-65149
+    •Quantum SuperLoader 3
+. Run LiveUpdate on your media server, apply all the patches available, and then run the Device COnfiguration Wizard to install the drivers.
+. 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.
+More From: http://www.symantec.com/business/support/index?page=content&id=TECH44668&actp=search&viewlocale=en_US&searchid=1366141242424
+    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
+. Confirm that the SQL(Bkupexec) service on the Media server is running under Local System Account
+. 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 ======
+http://forums.techarena.in/small-business-server/703661.htm
+====== 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.