How to update Backup Exec Remote Agent For Windows System_
Hi all! I'm excperiencing connecting problems during night becakup to random clients - V-79-57344-65072 "the connection to target system has been lost". I've checked Backup Exec RAWS version at media server as well as on all remote systems - it's 13.0.5204.109. The Backup Exec RAWS version on the media serverin newer than enywhere else - it's 13.0.5204.114. In order to try to resolve this issue I want to update agents first. Is it possible to do it automaticly? The uninstallation process and push install doesn't help - the older version is installed.14KViews1like18CommentsError bptm(pid=5832) error requesting media, TpErrno = Robot operation failed
Hi, I have been having big problem with one of our Media Servers. We had an un-related problem with the OS, and had to rebuild the server. I've finally got our backups working again, but am unable to Vault images to tape. Robtest is able to successfully move tapes from slots to drives and visa versa, but no images are mounted to tape. Our backup procedure is as follows: Backup to Disk > Vault to ON site and OFF site copies > Set ON site copy to primary and delete the disk backup on Image Cleanup. Here is the full Vault job status report: 20/12/2013 20:06:46 - begin Duplicate 20/12/2013 20:07:13 - requesting resource backup4-dlt2-robot-tld-2 20/12/2013 20:07:13 - requesting resource backup4-dlt2-robot-tld-2 20/12/2013 20:07:13 - granted resource ON2348 20/12/2013 20:07:13 - granted resource QUANTUM.DLT-S4.006 20/12/2013 20:07:13 - granted resource backup4-dlt2-robot-tld-2 20/12/2013 20:07:13 - granted resource OF2562 20/12/2013 20:07:13 - granted resource QUANTUM.DLT-S4.009 20/12/2013 20:07:13 - granted resource backup4-dlt2-robot-tld-2 20/12/2013 20:07:16 - started process bptm (5800) 20/12/2013 20:07:23 - started process bpdm (5920) 20/12/2013 20:07:26 - started process bptm (5800) 20/12/2013 20:07:26 - mounting ON2348 20/12/2013 20:07:44 - begin reading 20/12/2013 20:18:57 - Error bptm(pid=5800) error requesting media, TpErrno = Mount canceled, device daemon is terminating 20/12/2013 20:18:57 - Warning bptm(pid=5800) media id ON2348 load operation reported an error 20/12/2013 20:18:57 - current media ON2348 complete, requesting next resource Any 20/12/2013 20:19:01 - Error nbjm(pid=8264) NBU status: 98, EMM status: The media server reported a system error 20/12/2013 20:19:11 - Error nbjm(pid=8264) nbrb status: LTID reset media server resources 20/12/2013 20:19:29 - Error bptm(pid=5800) INF - error requesting media (tpreq) (98), cannot continue with copy 2 20/12/2013 20:20:23 - Error bpduplicate(pid=8380) host backup4 backup id doradb04_1386981799 read failed, termination requested by administrator (150). 20/12/2013 20:20:23 - Error bpduplicate(pid=8380) host backup4 backupid doradb04_1386981799 write failed, error requesting media (tpreq) (98). 20/12/2013 20:21:17 - Error bpduplicate(pid=8380) Duplicate of backupid doradb04_1386981799 failed, error requesting media (tpreq) (98). 20/12/2013 20:21:18 - started process bptm (5832) 20/12/2013 20:21:18 - requesting resource backup4-dlt2-robot-tld-2 20/12/2013 20:21:18 - granted resource ON2348 20/12/2013 20:21:18 - granted resource QUANTUM.DLT-S4.007 20/12/2013 20:21:18 - granted resource backup4-dlt2-robot-tld-2 20/12/2013 20:21:20 - requesting resource backup4-dlt2-robot-tld-2 20/12/2013 20:21:20 - granted resource OF2562 20/12/2013 20:21:20 - granted resource QUANTUM.DLT-S4.008 20/12/2013 20:21:20 - granted resource backup4-dlt2-robot-tld-2 20/12/2013 20:21:24 - started process bpdm (4524) 20/12/2013 20:21:27 - started process bptm (5832) 20/12/2013 20:21:27 - mounting ON2348 20/12/2013 20:21:45 - begin reading 20/12/2013 20:21:50 - Error bptm(pid=5832) error requesting media, TpErrno = Robot operation failed 20/12/2013 20:21:50 - Warning bptm(pid=5832) media id ON2348 load operation reported an error 20/12/2013 20:21:51 - current media ON2348 complete, requesting next resource Any 20/12/2013 20:22:13 - started process bptm (5832) 20/12/2013 20:22:13 - mounting ON2348 20/12/2013 20:22:13 - granted resource ON2348 20/12/2013 20:22:13 - granted resource QUANTUM.DLT-S4.006 20/12/2013 20:22:13 - granted resource backup4-dlt2-robot-tld-2 20/12/2013 20:37:37 - Error bptm(pid=5832) error requesting media, TpErrno = Robot operation failed 20/12/2013 20:37:38 - Warning bptm(pid=5832) media id ON2348 load operation reported an error 20/12/2013 20:37:38 - current media ON2348 complete, requesting next resource Any 20/12/2013 20:37:44 - granted resource ON2348 20/12/2013 20:37:44 - granted resource QUANTUM.DLT-S4.009 20/12/2013 20:37:44 - granted resource backup4-dlt2-robot-tld-2 20/12/2013 20:37:46 - started process bptm (5832) 20/12/2013 20:37:46 - mounting ON2348 20/12/2013 20:53:12 - Error bptm(pid=5832) error requesting media, TpErrno = Robot operation failed 20/12/2013 20:53:12 - Warning bptm(pid=5832) media id ON2348 load operation reported an error 20/12/2013 20:53:12 - current media ON2348 complete, requesting next resource Any 20/12/2013 20:53:19 - granted resource ON2064 20/12/2013 20:53:19 - granted resource QUANTUM.DLT-S4.007 20/12/2013 20:53:19 - granted resource backup4-dlt2-robot-tld-2 20/12/2013 20:53:20 - started process bptm (5832) 20/12/2013 20:53:20 - mounting ON2064 20/12/2013 20:54:48 - started process bptm (5832) 20/12/2013 20:54:48 - mounting OF2562 20/12/2013 21:10:14 - Error bptm(pid=5832) error requesting media, TpErrno = Robot operation failed 20/12/2013 21:10:14 - Warning bptm(pid=5832) media id OF2562 load operation reported an error 20/12/2013 21:10:15 - current media OF2562 complete, requesting next resource Any 20/12/2013 21:10:21 - granted resource OF2562 20/12/2013 21:10:21 - granted resource QUANTUM.DLT-S4.006 20/12/2013 21:10:21 - granted resource backup4-dlt2-robot-tld-2 20/12/2013 21:10:23 - started process bptm (5832) 20/12/2013 21:10:23 - mounting OF2562 20/12/2013 21:24:16 - Error bptm(pid=5832) FREEZING media id OF2562, Medium identifiers do not match 20/12/2013 21:24:16 - Warning bptm(pid=5832) media id OF2562 load operation reported an error 20/12/2013 21:24:17 - current media OF2562 complete, requesting next resource Any 20/12/2013 21:45:53 - started process bptm (5832) 20/12/2013 21:45:53 - mounting OF2142 20/12/2013 21:45:53 - granted resource OF2142 20/12/2013 21:45:53 - granted resource QUANTUM.DLT-S4.009 20/12/2013 21:45:53 - granted resource backup4-dlt2-robot-tld-2 20/12/2013 22:01:19 - Error bptm(pid=5832) error requesting media, TpErrno = Robot operation failed 20/12/2013 22:01:19 - Warning bptm(pid=5832) media id OF2142 load operation reported an error 20/12/2013 22:01:20 - current media OF2142 complete, requesting next resource Any 20/12/2013 22:01:26 - started process bptm (5832) 20/12/2013 22:01:26 - mounting OF2142 20/12/2013 22:01:26 - granted resource OF2142 20/12/2013 22:01:26 - granted resource QUANTUM.DLT-S4.008 20/12/2013 22:01:26 - granted resource backup4-dlt2-robot-tld-2 I am able to inventory the robot successfully, and the robot is capable of emptying tapes from the media access port, and placing them in slots. We are using NetBackup 6.5.6. Up until last week the full procedure worked perfectly, so our OS, library and NetBackup version are all definitely cross-compatible. Any help would be gratefully received!Solved11KViews2likes9CommentsExchange lässt sich nicht mehr sichern
Hallo! Wir haben BackupExec 2010 R3 im Einsatz mit "Agent for MS Exchange Server", "Active Directory Recovery Agent" und "Remote Agent for Windows and Netware Servers". Backup Exec läuft auf einem Server 2003 R2 mit allen Servicepacks und Updates Exchange läuft auf einem Server 2003 R2 64bit mit allen Servicepacks und Updates. Der Remote Agent wurde auf dem Server aktualisiert. Das Problem: Bis letzte Woche wurde der Exchange-Server problemlos gesichert - auch eine Wiederherstellung war kein Problem. Leider habe ich dann das SP2 von BackupExec eingespielt und die 5 angebotenen Hotfixes. Seither lässt sich Exchange nicht mehr sichern und wir bekommen folgende Fehlermeldung: V-79-57344-34070 - AOFO: Initialisierung fehlgeschlagen: "Microsoft Information Store". Advanced Open File Option verwendet: Microsoft Volume Shadow Copy Service (VSS). Fehler im Snapshot-Provider (0xE0008516): Die für einen Snapshot angegebenen Ressourcen verfügen über keine gültigen Daten. Überprüfen Sie, ob Dateien gelöscht oder umbenannt wurden. Ausführliche Angaben finden Sie in der Windows-Ereignisanzeige. Der Link zur entsprechenden Supportseite erzählt irgendwas von Advanced Open File Option - welche nicht verwendet wird. Dies habe ich vorhin überprüft. In der Auswahlliste der Sicherungsjobs wird der Microsoft Information Store seit den Updates nicht mehr angezeigt. Lediglich im Registerreiter "Auswahldetails anzeigen" stehen die Einträge nach wie vor drinnen: \\servername.domäne.inhouse\Microsoft Information Store\First Storage Group|*.* /SUBDIR \\servername.domäne.inhouse\Microsoft Information Store\Second Storage Group|*.* /SUBDIR Kennt dieses Problem jemand und hat vielleicht eine Lösung dafür? Ansonsten müsste ich BackupExec komplett de- und wieder installieren (OHNE irgendwelchen Updates) und hoffen, dass das Programm danach wieder so läuft wie es soll. Das wäre die letzte Option, denn alle Versuche die Exchange-Sicherung seit einigen Tagen wieder zum laufen zu bringen, sind fehlgeschlagen. Vielen Dank10KViews0likes12CommentsSystem State backups slow all of a sudden
All of a sudden all my System State backups appear to be running dreadfully slow, to the point of being unable to complete the backup within a 24hour timeframe. Throughput seems stalled, and BEremote.exe is running at 100% CPU on the affected servers. All servers are running 2008 R2. Checking the sgmon logs I notice that files are still being added to the VSS snapshot. I've tried reinstalling the agents with no change, NTbackup seems to run just fine. Anyone else with this problem? It's happened all at the same time pretty much, I suspect windows update to have pushed some update out that screws things up.Solved9.9KViews0likes13CommentsBackup is not completed - Connection timeout is <300> seconds.
Hello Folks! I need some help! I have a problem in my Netbackup environment. The backup is not completed in a client, because just stay on status "Connection timeout is <300> seconds". No change from this status. 15/01/2014 17:17:15 - Info nbjm(pid=3920) starting backup job (jobid=116434) for client srvvm63, policy srvvm63-sql_server, schedule Diario 15/01/2014 17:17:15 - Info nbjm(pid=3920) requesting MEDIA_SERVER_WITH_ATTRIBUTES resources from RB for backup job (jobid=116434, request id:{30A7A23C-5CDB-41E2-BD49-B2D33D29F3B5}) 15/01/2014 17:17:15 - requesting resource srv03-hcart-robot-tld-1 15/01/2014 17:17:15 - requesting resource srv03.grupomaggi.corp.NBU_CLIENT.MAXJOBS.srvvm63 15/01/2014 17:17:15 - requesting resource srv03.grupomaggi.corp.NBU_POLICY.MAXJOBS.srvvm63-sql_server 15/01/2014 17:17:15 - granted resource srv03.grupomaggi.corp.NBU_CLIENT.MAXJOBS.srvvm63 15/01/2014 17:17:15 - granted resource srv03.grupomaggi.corp.NBU_POLICY.MAXJOBS.srvvm63-sql_server 15/01/2014 17:17:15 - granted resource srv03-hcart-robot-tld-1 15/01/2014 17:17:15 - estimated 0 Kbytes needed 15/01/2014 17:17:15 - Info nbjm(pid=3920) started backup job for client srvvm63, policy srvvm63-sql_server, schedule Diario on storage unit srv03-hcart-robot-tld-1 15/01/2014 17:17:16 - started process bpbrm (8064) 15/01/2014 17:17:17 - Info bpbrm(pid=8064) srvvm63 is the host to backup data from 15/01/2014 17:17:17 - Info bpbrm(pid=8064) reading file list from client 15/01/2014 17:17:17 - connecting 15/01/2014 17:17:20 - Info bpbrm(pid=8064) starting bphdb on client 15/01/2014 17:17:20 - Info bphdb(pid=1664) Backup started 15/01/2014 17:17:20 - connected; connect time: 00:00:03 15/01/2014 17:17:24 - Info dbclient(pid=4460) INF - BACKUP STARTED USING 15/01/2014 17:17:24 - Info dbclient(pid=4460) Microsoft SQL Server 2008 R2 (RTM) - 10.50.1600.1 (X64) 15/01/2014 17:17:24 - Info dbclient(pid=4460) Apr 2 2010 15:48:46 15/01/2014 17:17:24 - Info dbclient(pid=4460) Copyright (c) Microsoft Corporation 15/01/2014 17:17:24 - Info dbclient(pid=4460) Standard Edition (64-bit) on Windows NT 6.1 <X64> (Build 7601: Service Pack 1) (Hypervisor) 15/01/2014 17:17:24 - Info dbclient(pid=4460) Batch = C:\Program Files\Veritas\NetBackup\DbExt\MsSql\backup_full.bch, Op# = 1 15/01/2014 17:17:24 - Info dbclient(pid=4460) INF - Using backup image SRVVM63.MSSQL7.SRVVM63.db.Creditflow_AMaggi_Des.~.7.001of001.20140115171723..C 15/01/2014 17:17:24 - Info dbclient(pid=4460) INF - backup database "Creditflow_AMaggi_Des" to VIRTUAL_DEVICE='VNBU0-4460-4400-1389817044' with compression, stats = 10, blocksize = 65536, maxtransfersize = 4194304, buffercount = 2 15/01/2014 17:17:25 - Info dbclient(pid=4460) INF - Number of stripes: 1, Number of buffers per stripe 2. 15/01/2014 17:17:25 - Info dbclient(pid=4460) INF - Created VDI object for SQL Server instance <SRVVM63>. Connection timeout is <300> seconds. ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- Anyone has seen this error? I appreciate if could help me.6.9KViews0likes24CommentsBE 2014 won't backup VMs on Hyper-V 2012 R2
Hi all. The Backup Server is running Server 2008 R2 Standard with Backup Exec 2014 installed. All updates have been applied from live update. I'm trying to backup VMs on a server running Hyper-V 2012 R2, but I continue to receive a "Final error: 0xa0009679 - A failure occurred querying the Writer status for a Hyper-V virtual machine" error. Running VSS Admin List results in a "Retryable Error" for the Microsoft Hyper-V VSS Writer. I have tried restarting the server already and that didn't help. Any tips? Event Viewer also gives me this at the time of the backup failure: 1) Application and Service Logs > Microsoft > Windows > Hyper_V-VMMS > Admin: Failed to fix-up absolute VHD paths in configuration of virtual machine 'VM Name': Account restrictions are preventing this user from signing in. For example: blank passwords aren't allowed, sign-in times are limited, or a policy restriction has been enforced. (0x8007052F). (Virtual machine ID AEB2B426-05DD-4C4F-AC8F-330B0D57B8D4) 2) Windows Logs > Application: A VSS writer has rejected an event with error 0x800423f3, The writer experienced a transient error. If the backup process is retried, the error may not reoccur. . Changes that the writer made to the writer components while handling the event will not be available to the requester. Check the event log for related events from the application hosting the VSS writer. Other details: The Hyper-V 2012 R2 OS has been separated from the VMs on the HD. OS is on C and the VMs are on D. VM backups continue to run perfectly fine from a Hyper-V 2008 R2 server. All servers mentioned are using the same storage device. Any help will be much appreciated. Thanks everyone.5.7KViews1like20CommentsBackup of SQL fails - wrong user access
Hi, Trying to figure out an issue with backup an sql server 2008 databases on a remote server. Below is the erros I am getting. Now I have looked at TECH144230 and TECH69132 which basically says to check to make sure that the logon account has the sysadmin role on the DB which it does. So I am not sure what the next step is. Backup- PBCA-DOC1V-79-57344-65088 - WARNING: The DBCC NEWALLOC command requires SA rights. The consistency check cannot be completed. User 'guest' does not have permission to run DBCC checkdb for database 'master'. V-79-57344-65088 - WARNING: The DBCC NEWALLOC command requires SA rights. The consistency check cannot be completed. User 'guest' does not have permission to run DBCC checkdb for database 'msdb'. Backup- PBCA-DOC1\CCHDM_SQLEXP2008V-79-57344-37951 - Database master has failed to freeze for the snapshot backup. V-79-57344-37951 - Database msdb has failed to freeze for the snapshot backup.Solved5.7KViews0likes2CommentsFailed Final error: 0xe00084bd - The system cannot find the path specified - unable to restore file or directory.
Hello I can't backup only this Vm with Backup Exec 2014 since a very long time. They are no snapshot existed in snapshot Manager. When i select manually only one VM using snapshot technology .. Could you help me ? it says always .. And after the message appears.... ANd, Why it talk about restore ? I giev a backup not arestore. Error : e00084bd - The system cannot find the path specified - unable to restore file or directory. See the job log for details. Agent used : Yes Advanced Open File Option used : No5.5KViews1like16CommentsRestart required after agent update?
Hi I just upgraded to Backupexec 2014 service pack 1 As after each upgrade, it's adviced to upgrade remote agents. As after each upgrade, it's required to restart servers... Is this really mandatory? No way to just restart remote agent service on remote server? Restarting a server is nothing, but restarting up to 50 or 60 servers take some time. And this should most of times be done during night. It really becomes time consuming to take a few hours each time a hotfix is released No way to solve this Symantec guys? Would be really happy ;)Solved5.5KViews1like3Comments