Backup Exec 2012 backup very slow (catalog problem?)
We've been having some problems with the speed of our backup. The setup is the following: physical BE2012 server coonected to disk storage via fibre and connected to VmWare enviroment via Fibre as well. When backup up our file and print server to DeDupe location on our disk storage it takes a very long time (+19hr) for 900GB of data. It seems to hang on updating catalog. History: Everything working fine and backupjob of all servers (1.4TB) runnning at speeds of between 4000MB/min to 6000MB/min. Then from one day to the other (no windows or BE updates done) the speed slowed down to between 600MB/min and 900MB/min. Things allready tried: delete and recreate the backup job. update to SP1a. Thick all the boxes under the catalog tab and set to trucate after 4 weeks. run database maintenance at a time when no backup jobs are running. split up the job into different jobs (this alleviated the problem a bit) After splitting the job up so that the exchange server, the SQL server and the file and print server had different jobs I noticed that the exchange and SQL were backing up at normal speeds (+4000MB/min) but the file and print server was still taking 18Hrs to backup. a bit more digging and a couple of days later I noticed that the data of file and print was backing up at speeds of +4000MB/min itself but it was hanging (going verrry slow) on updating the catalog at the end of the job while the size stayed unchanged. My counterpart in our other location the other side of Australia is having the same problem for the exact same setup. (his problem started about 2 weeks before mine) He has been testing with going from full daily backups to incremental but the same problem stays. We do not have a bottleneck problem with our disks, speed of our servers or any other hardware but it seems to come backup to the updating of the catalog for the file and print server. (my counterpart has also tried to uninstall and reinstall BE2012 but no sollution there either) Does anyone have an idea how to clean, compact or do anything else with the catalog to get it back to normal speed? (catalog folder is currently 9GB with 16GB available) Thanks in advanceSolved8.8KViews2likes37CommentsBkf format in Symantec Backup Exec
Hello. Does anybody know - bkf format of "backup files to disk" is excatly like Windows bkf format? I have a bkf file, which contains some data. This bkf was be done with Symantec Backup Exec 2010 R2. When i try to restore data from it thru NtBackup - i get about 64 Kb and then process is frozen. When i try to restore data from it thru Symantec Backup Exec 2010 R2 - all be allright. I try to restore thru Ntbackup on three differential computers (Windows XP and Windows Server 200 and 2003 R2) - same error. The catalogization is all right - a see all data, bur restore process frozen about restoring 64 kb. My question is: - Can i restore data from bkf files with Ntbackup? Or i must use ONLY Symantec Backup?2.9KViews1like5CommentsBackup Exec hangs when opening job properties, new job, or new selections list
Backup Exec hangs when opening job properties, new job, or new selections list. I have repaired the database, restored blank database, uninstalled and reinstalled BackupExec 12.5, and still when I go to create a new job or selections list it just hangs indefinitely. The only way I found to get around it is to open Task Manager and kill beremote.exe manually. The new job/selection list interface opens up immediately but it's of no use becase without the remote agent service running I can't see selection details. Does anyone have any ideas on how to fix this?Solved2.7KViews1like13CommentsNBU 7.5.0.3 - Replication Fail(Status 84)
Hi Forum, Just wondering if the experts can help me troubleshoot the issue. I have logged a case, but it takes a long time for them to respond and it seems they arent sure how to approach this. Here is the scenario: from Local Master. Two master servers(Local and DR), replication setup one way(Local to DR). replication fails from local master to DR master. Status 84. Details of error: 17/05/2013 10:34:38 - requesting resource LCM_STU-MSDP-Source 17/05/2013 10:34:38 - granted resource LCM_STU-MSDP-Source 17/05/2013 10:34:38 - started process RUNCMD (13884) 17/05/2013 10:34:39 - requesting resource @aaaac 17/05/2013 10:34:39 - reserving resource @aaaac 17/05/2013 10:34:39 - reserved resource @aaaac 17/05/2013 10:34:39 - granted resource MediaID=@aaaac;DiskVolume=PureDiskVolume;DiskPool=xxxxxxx-dp;Path=PureDiskVolume;StorageServer=xxxxxxbak01;MediaServer=xxxxxx-bak01 17/05/2013 10:34:42 - Info bpdm(pid=13900) started 17/05/2013 10:34:42 - started process bpdm (13900) 17/05/2013 10:34:47 - Info xxxxxxbak01(pid=13900) Using OpenStorage to replicate backup id xxxxx-nfs01xxxxx.xxxxxx.local_1368795600, media id @aaaac, storage server xxxxxx-bak01, disk volume PureDiskVolume 17/05/2013 10:34:47 - Info xxxxxxx-bak01(pid=13900) Replicating images to target storage server xxxxxxbak01, disk volume PureDiskVolume 17/05/2013 10:35:18 - Error bpdm(pid=13900) wait failed: error 2060014 17/05/2013 10:35:18 - Error bpdm(pid=13900) <async> cancel failed: error 2060001: one or more invalid arguments 17/05/2013 10:35:18 - Error bpdm(pid=13900) copy cancel failed: error 2060001 17/05/2013 10:35:18 - Info xxxxxxxbak01(pid=13900) StorageServer=PureDisk:xxxxxxx-bak01; Report=PDDO Stats for (xxxxxbak01): scanned: 4 KB, CR sent: 0 KB, CR sent over FC: 0 KB, dedup: 100.0% 17/05/2013 10:35:18 - Error (pid=13884) ReplicationJob::Replicate: Replication failed for backup id xxxxxxxnfs01.xxxxxxxx_1368795600: media write error (84) 17/05/2013 10:35:18Replicate failed for backup id xxxxnfs01.xxxxxxxx_1368795600 with status 84 17/05/2013 10:35:18 - end operation From the DR Master: 5/17/2013 2:47:27 AM - requesting resource @aaaac 5/17/2013 2:47:27 AM - Error nbjm(pid=6492) NBU status: 2074, EMM status: Disk volume is down Disk volume is down(2074) 5/17/2013 2:47:27 AM - Error nbjm(pid=6492) NBU status: 2074, EMM status: Disk volume is down When I look on the DR Master, Media and Device Mgmt > Credentials > Storage Servers > under properties or replication I get the following error. "Internal application error. Please contact your administrator. invalid comman parameter. RDSM has encountered an issue with STS where the server was not found: getDiskVolumeInfoList" I have tried to UP thedisk volume through command prompt,but same issues continue. Let me know which logs might be useful for you experts reading this. Thanks in advance, Luis S.2.4KViews0likes19CommentsEvent ID 33808 An error occurred while processing a B2D command.
BackupExec 2010R2, Windows 2008 (64bit) SP2, backup destination DELL TL2000. Backup job completes with successful status according to schedule. No alerts or errors recorded within BackupExec, however each time when backup starts an application error is recorded in windows event log. Event ID 33808 Description: An error occurred while processing a B2D command. spnRequest: Initialize() CreateFileMapping failed (SPN_DeviceMemory). Error=5 I have 3 sites with same hardware, OS and backup configuration. However only one of the site is giving this error. Please share if you can think of a solution for this error.2.3KViews1like4Commentspx12-400r LenovoEMC & BACKUP EXEC
Hello I have a px12-400r LenovoEMC with firmware version 4.0.2.9960. I use Backup Exec 2012 and when I enable a shared resource in the "Allow users to change the file-level security" Backup Exec can not access resources to capture the backup. Is there any posibildad to solve this problem? A greeting and thank you very much2.2KViews1like13CommentsCan't install Backup Exec Archiving Option
Because we are ordering a new backup server I'm creating a test installation on a virtual machine. I've installed Windows 2008 R2 and SQL Express 2008. The installation of Backup Exec 2010 R3 goes ok except for the Archiving Option which doesn't install. BKUPINST.HTM says: 03-26-2012,11:48:44 : ERROR: EVRunDll.exe process has returned error code -2147024827. 03-26-2012,11:48:44 : Review silent configuration log in C:\Program Files\Symantec\Backup Exec\Enterprise Vault\Reports for more details. 03-26-2012,11:48:44 : Review Symantec Enterprise Vault event logs for errors. 03-26-2012,11:48:44 : AgentSeqDlgs::Misc_BE_CommonOps 03-26-2012,11:48:44 : The Backup Exec Archiving Option installation did not complete successfully. To find a solution, go to: http://entsupport.symantec.com/umi/V-225-277 TheSilentCfgLog says, Failed to create Enterprise Vault Directory database Silent Configuration Registry key value written (ReturnCode = 46). I have tried reinstalling Backup Exec, and a reinstall of the whole machine but got no luck. Can anyone tell me what causes this error? Thanks1.9KViews0likes16Commentsbackup Performence
how to improve backup performance(For example I am running a backup operation it is taking 10 hours (consider ) then I need it to finish it within 5 hours or below mean as early as possible is it possible or not if possible means how Give me an example )Solved1.9KViews2likes8CommentsTransaction Logs for SQL Database - Backup Exec 2012
Hi All, Would appreciate some help please. I get the following error.... "Transaction log backups are not being performed. This will result in the log growing to fill all available disk space. Regular log backups should be scheduled or the database should be changed to the simple recovery mode.Transaction log backups are not being performed. This will result in the log growing to fill all available disk space. Regular log backups should be scheduled or the database should be changed to the simple recovery mode." Now I was getting the same error before, only it said i needed to switch the simple recovery mode to full backup mode, which I did, and then got the above error. Now could someone please explain to me as simply as possible (and please assume i am a complete idiot!!!!!!!), how I clear this error in a good way. That is to say, perform the log backups, and prevent the logs from growing out of control. Please highlight if you are talking about settings in the SQL section of BE, or indeed on the actual SQL server management conseol itself. Apart from this (really annoying) error, BE is working amazingly fine. If i could solve this issue, i would get green lights accross the board each day and i would be over the button moon!!! Thankyou so much in advance for the right answer. At the risk of sounding blunt, which isnt my intention...please dont post links to other pages. I am looking for someone who actually knows and can explain the answer clearly and understands it so I can learn. Chances are its one of the sites i've filled my evenings with and been to over the past 3 weeks anyways.1.7KViews1like10CommentsProblem backup from Symantec Backup Exec to HP Ultrium LTO tape
Dear Sir/Madam, We have an emergancy: Our backup Job notificate fails with Symantec Backup Exec 11d (version 11.0 Rev. 7170) " Job ended: woensdag 19 oktober 2011 at 10:48:54 Completed status: Failed Final error: 0xe00084ed - A hardware error occurred. Final error category: Backup Device Errors For additional information regarding this error refer to link V-79-57344-34029 Backup- D: Data Storage device "HP Ultrium 400" reported an error on a request to write data to media. Error reported: Kan de opdracht niet uitvoeren door een fout in een I/O-apparaat. V-79-57344-34029 - A hardware error occurred." The Server (DC) is a Windows Server 2003 Small Business ServerPremium R2. The Backup device is a HP Ultium 2-SCSI The system Event Log notifies (in order of sequence, first error 15, then information 7036 en then 3 times error 7, made anonymously "xxxx") , as listed below: Bythe way / and maybe connected to the problem: - Strangly we don't get notifications by mail although is is implied.. - Also if I place a cleaning cadrigde the Symantec Software still mention that there's no cleaning since 4 years orso. -We had toreplace the battery ofthe SCSI cache.We also replaced the cache itself -Later on, the backupdid function sometimes. - I've tried using less weared tapes, but the problem remained. - If I retry a backup (Run now a scheduled backup), the same amout of bytes are counted to the backuptape (43.280.832) - All lights on the front of the HP server are green (oké I'll guess) Type gebeurtenis:Fout Bron van gebeurtenis:hplto Categorie van gebeurtenis:Geen Gebeurtenis-id15 Datum:19-10-2011 Tijd:1:00:37 Gebruiker:n.v.t. Computer:xxxxDC Beschrijving: Kan apparaat \Device\Tape0 niet benaderen. Zie Help en ondersteuning op http://go.microsoft.com/fwlink/events.asp voor meer informatie. Gegevens: 0000: 0f 00 68 00 01 00 bc 00 ..h...¼. 0008: 00 00 00 00 0f 00 04 c0 .......À 0010: 04 01 00 00 9d 00 00 c0 ......À 0018: 00 00 00 00 00 00 00 00 ........ 0020: 00 00 00 00 00 00 00 00 ........ 0028: ab 43 2a 00 00 00 00 00 «C*..... 0030: ff ff ff ff 00 00 00 00 ÿÿÿÿ.... 0038: 40 00 00 0a 00 00 03 00 @....... 0040: fe 20 06 12 08 01 10 10 þ ...... 0048: 00 00 00 00 60 09 00 00 ....`... 0050: 00 00 00 00 b0 ad 17 8a ....°. 0058: 00 00 00 00 08 60 c3 89 .....`Ã 0060: 00 00 00 00 00 00 00 00 ........ 0068: 00 00 00 00 00 00 00 00 ........ 0070: 00 00 00 00 00 00 00 00 ........ 0078: 00 00 00 00 00 00 00 00 ........ 0080: 00 00 00 00 00 00 00 00 ........ 0088: 00 00 00 00 00 00 00 00 ........ Type gebeurtenis:Informatie Bron van gebeurtenis:Service Control Manager Categorie van gebeurtenis:Geen Gebeurtenis-id7036 Datum:19-10-2011 Tijd:1:03:35 Gebruiker:n.v.t. Computer:xxxxDC Beschrijving: De Volume Shadow Copy-service heeft nu de status Beëindigd. Zie Help en ondersteuning op http://go.microsoft.com/fwlink/events.asp voor meer informatie. Type gebeurtenis:Fout Bron van gebeurtenis:hplto Categorie van gebeurtenis:Geen Gebeurtenis-id7 Datum:19-10-2011 Tijd:1:04:14 Gebruiker:n.v.t. Computer:xxxxDC Beschrijving: Beschadigd blok in apparaat \Device\Tape0. Zie Help en ondersteuning op http://go.microsoft.com/fwlink/events.asp voor meer informatie. Gegevens: 0000: 0f 00 68 00 01 00 bc 00 ..h...¼. 0008: 00 00 00 00 07 00 04 c0 .......À 0010: 00 01 00 00 9c 00 00 c0 ......À 0018: 00 00 00 00 00 00 00 00 ........ 0020: 00 00 00 00 00 00 00 00 ........ 0028: 07 7a 2a 00 00 00 00 00 .z*..... 0030: ff ff ff ff 00 00 00 00 ÿÿÿÿ.... 0038: 40 00 00 84 02 00 03 00 @...... 0040: fe 20 06 12 08 01 00 00 þ ...... 0048: 00 00 00 00 60 09 00 00 ....`... 0050: 00 00 00 00 08 b0 6d 87 .....°m 0058: 00 00 00 00 08 d0 36 89 .....Ð6 0060: 00 00 00 00 00 00 00 00 ........ 0068: 11 03 00 00 00 00 00 00 ........ 0070: 00 00 00 00 00 00 00 00 ........ 0078: 70 00 03 00 00 00 00 10 p....... 0080: 00 00 00 00 14 00 00 00 ........ 0088: 50 90 00 00 00 00 00 00 P...... Type gebeurtenis:Fout Bron van gebeurtenis:hplto Categorie van gebeurtenis:Geen Gebeurtenis-id7 Datum:19-10-2011 Tijd:1:06:26 Gebruiker:n.v.t. Computer:xxxxDC Beschrijving: Beschadigd blok in apparaat \Device\Tape0. Zie Help en ondersteuning op http://go.microsoft.com/fwlink/events.asp voor meer informatie. Gegevens: 0000: 0f 00 68 00 01 00 bc 00 ..h...¼. 0008: 00 00 00 00 07 00 04 c0 .......À 0010: 00 01 00 00 9c 00 00 c0 ......À 0018: 00 00 00 00 00 00 00 00 ........ 0020: 00 00 00 00 00 00 00 00 ........ 0028: 00 9b 2a 00 00 00 00 00 .*..... 0030: ff ff ff ff 00 00 00 00 ÿÿÿÿ.... 0038: 40 00 00 84 02 00 03 00 @...... 0040: fe 20 06 12 08 01 00 00 þ ...... 0048: 00 00 00 00 60 09 00 00 ....`... 0050: 00 00 00 00 f0 81 8d 87 ....ð 0058: 00 00 00 00 08 2b eb 87 .....+ë 0060: 00 00 00 00 00 00 00 00 ........ 0068: 11 03 00 00 00 00 00 00 ........ 0070: 00 00 00 00 00 00 00 00 ........ 0078: 70 00 03 00 00 00 00 10 p....... 0080: 00 00 00 00 14 00 00 00 ........ 0088: 50 90 00 00 00 00 00 00 P...... Type gebeurtenis:Fout Bron van gebeurtenis:hplto Categorie van gebeurtenis:Geen Gebeurtenis-id7 Datum:19-10-2011 Tijd:1:08:38 Gebruiker:n.v.t. Computer:xxxxDC Beschrijving: Beschadigd blok in apparaat \Device\Tape0. Zie Help en ondersteuning op http://go.microsoft.com/fwlink/events.asp voor meer informatie. Gegevens: 0000: 0f 00 68 00 01 00 bc 00 ..h...¼. 0008: 00 00 00 00 07 00 04 c0 .......À 0010: 00 01 00 00 9c 00 00 c0 ......À 0018: 00 00 00 00 00 00 00 00 ........ 0020: 00 00 00 00 00 00 00 00 ........ 0028: f8 bb 2a 00 00 00 00 00 ø»*..... 0030: ff ff ff ff 00 00 00 00 ÿÿÿÿ.... 0038: 40 00 00 84 02 00 03 00 @...... 0040: fe 20 06 12 08 01 00 00 þ ...... 0048: 00 00 00 00 60 09 00 00 ....`... 0050: 00 00 00 00 e8 4c 5b 87 ....èL[ 0058: 00 00 00 00 e0 07 00 88 ....à.. 0060: 00 00 00 00 00 00 00 00 ........ 0068: 11 03 00 00 00 00 00 00 ........ 0070: 00 00 00 00 00 00 00 00 ........ 0078: 70 00 03 00 00 00 00 10 p....... 0080: 00 00 00 00 14 00 00 00 ........ 0088: 50 90 00 00 00 00 00 00 P...... Type gebeurtenis:Fout Bron van gebeurtenis:hplto Categorie van gebeurtenis:Geen Gebeurtenis-id7 Datum:19-10-2011 Tijd:1:10:50 Gebruiker:n.v.t. Computer:xxxxDC Beschrijving: Beschadigd blok in apparaat \Device\Tape0. Zie Help en ondersteuning op http://go.microsoft.com/fwlink/events.asp voor meer informatie. Gegevens: 0000: 0f 00 68 00 01 00 bc 00 ..h...¼. 0008: 00 00 00 00 07 00 04 c0 .......À 0010: 00 01 00 00 9c 00 00 c0 ......À 0018: 00 00 00 00 00 00 00 00 ........ 0020: 00 00 00 00 00 00 00 00 ........ 0028: f2 dc 2a 00 00 00 00 00 òÜ*..... 0030: ff ff ff ff 00 00 00 00 ÿÿÿÿ.... 0038: 40 00 00 84 02 00 03 00 @...... 0040: fe 20 06 12 08 01 00 00 þ ...... 0048: 00 00 00 00 60 09 00 00 ....`... 0050: 00 00 00 00 00 08 d8 87 ......Ø 0058: 00 00 00 00 40 84 0b 88 ....@. 0060: 00 00 00 00 00 00 00 00 ........ 0068: 11 03 00 00 00 00 00 00 ........ 0070: 00 00 00 00 00 00 00 00 ........ 0078: 70 00 03 00 00 00 00 10 p....... 0080: 00 00 00 00 14 00 00 00 ........ 0088: 50 90 00 00 00 00 00 00 P......1.7KViews1like7Comments