software:backupexec
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
software:backupexec [2014/01/08 08:04] – superwizard | software:backupexec [2020/09/22 03:24] (current) – [Notes] superwizard | ||
---|---|---|---|
Line 1: | Line 1: | ||
+ | ====== UnLock Will not Run - Server Paused ====== | ||
+ | |||
+ | |||
+ | 2018-12-06 | ||
+ | |||
+ | |||
+ | 05-24-2007 08: | ||
+ | Hi Kevin, | ||
+ | |||
+ | Normally, when you see " | ||
+ | |||
+ | 1. Select " | ||
+ | 2. Right-click on the server name and select " | ||
+ | |||
+ | Everything should now be back to " | ||
+ | |||
+ | Regards, | ||
+ | |||
+ | Christiane. | ||
+ | |||
+ | From < | ||
+ | |||
+ | |||
+ | ====== system lock chk bkup sw cfg ====== | ||
+ | |||
+ | From: https:// | ||
+ | |||
+ | < | ||
+ | HKLM\software\Symantec\Backup Exec for Windows\Adamm\Disable Library Door Lock | ||
+ | </ | ||
+ | |||
+ | {{ : | ||
+ | |||
====== Catalog Location ====== | ====== Catalog Location ====== | ||
Line 31: | Line 64: | ||
To manually take a backup of a Backup Exec database, use the Dump database option of BEUtility. | 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. | 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: | ||
+ | Unable to open the item \\G-SERVER1\E: | ||
+ | |||
+ | ====== Update to SP4 ====== | ||
+ | |||
+ | INstall SP4, and then push-install the application' | ||
+ | |||
+ | From: http:// | ||
+ | |||
+ | Right I thought I best update this thread as I have FINALLY solved this issue! | ||
+ | For some reason " | ||
+ | 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, | ||
+ | •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 " | ||
+ | •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:// | ||
+ | |||
+ | 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:// | ||
+ | |||
+ | •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:// | ||
+ | If the drivers don't work, then you have a hardware error. | ||
+ | |||
+ | More From: http:// | ||
+ | |||
+ | Notes | ||
+ | Storage device " | ||
+ | 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:// | ||
+ | |||
+ | From: http:// | ||
+ | |||
+ | " | ||
+ | NDMP port 10000 reserve for beremote.exe | ||
+ | Note to Change this port number: | ||
+ | http:// | ||
+ | http:// | ||
+ | | ||
+ | |||
+ | From: http:// | ||
+ | |||
+ | 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 ====== | ||
+ | |||
+ | http:// | ||
+ | |||
+ | ====== Server 2008 info at computerperformance.co.uk ====== | ||
+ | |||
+ | http:// | ||
+ | |||
+ | In a nutshell Microsoft' |
software/backupexec.1389168274.txt.gz · Last modified: 2014/01/08 08:04 by superwizard