- 843Views4likes3Comments
NIC Teaming Slow Throughput, any ideas?
Hey guys, We currently have 2Gig set up through NIC teaming for our backup exec setup.When we have backups running, it barely reaches 35-40% of the bandwith. I am using Backup Exec 2010. Has anyone else here set up NIC teaming before? What are some things that might cause slow performance? Are there any specific settings in Backup Exec that may help? Thanks!5.1KViews3likes9CommentsMajor Data loss situations - OSX Mavericks + WD drive software + external Hard drives
Please be aware that there are serious data loss issues ongoing with Mac OSX Maverics and Western Digital drive sofware. Both the Apple support and WD forums have mutiple customer reports of total external drive data loss. The data loss is not limited to systems activly using the WD software and drives, other vendor external hard drives are being lost. Personally I just lost 1TB of Time machine backups on a Iomega external drive. I did have a WD myBook for a while about 2 years ago but was not aware the WD drive software was still active on this machine. Current advice from Western Digital is to uninstall the WD drive software before going to Mavericks. Uninstaller is here ..... http://support.wdc.com/product/download.asp?groupid=126&sid=214&lang=en This situation as already caused a lot of digital pain, loss of data and as a techincal person makes me sad in so many ways. Clive467Views2likes0Commentsbackup 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.9KViews2likes8CommentsSymantec System Recovery (IOCTL_VSNAP_VDIFF_STOP) failed
We are currently using Symantec System Recovery 2011 to backup a database of image files. It has worked perfectly for some time now. But about two weeks ago I started getting the following error..... Error EC8F17B7: Cannot create recovery points for job: Drive Backup of Storage (E:\). Error E7B70001: Win32/Win64 API DeviceIoControl(IOCTL_VSNAP_VDIFF_STOP) failed. Error EBAB03F1: The device does not recognize the command. (UMI:V-281-3215-6071) Nothing has been updated since I think this product was abandond by Symantec it hasn't seen an update since it was installed. The disk appears to be running fine and error free. I have no idea why this started or how to fix it. A google turned up no results which I don't think has ever happend. Any input would be greatly appreciated.1.5KViews2likes10CommentsNot following mount points, junction points message!
Hi, I am using a Dell Poweredge R710 connected to a Drobo 800i SAN that has the Deduplication drive configured to 4TB. I'm in the process of configuring BUE 2012 on all of our servers. When I am going through the job logs I noticed that even though I am getting reports showing completed and "Successful" backups to the Dedupe drive I get the following message on every "successful" job: Checkpoint restart cannot be applied to the following resource(s): System?StateBackup Exec will not follow mount points, junction points, and symbolic links when the Simplified Disaster Recovery indicator is ON. Drive and media mount requested: 1/22/2013 11:00:08 PM No appendable media could be mounted. Switching to overwrite operation on scratch media. 1) I want to use SRD on my Dedupe backups 2) Drobo is a recognized media for BUE - confirmed with Symantec and Drobo I have searched for answers (noticed someoen else getting told off for that in regards to this question- which was never answered.) I am also getting this error on other backup configured drives that are 1TB in size. Please note- the only other references I found references to tape and robotic media- and I do not use either. How do I eleiminate this error without eliminating the SRD? Thank you Ken1.8KViews2likes6CommentsRestores queuing for 60+ minutes before beginning execution, Netbackup 7.5.0.3
We have just upgraded from 7.0 to 7.5.0.3 on our master and media servers. They are running on Sun Solaris version 10. Previously we had no issues with restores, but now it seems that most of our restores are remaining in a queued state after being submited fromanywhere from 30 to 60 or minutes before they begin execution. Once they begin running, they restore fine with normal transfer rates and complete successfully. Has anyone every come across this issue before and do you have any suggestions on where to look to reduce the "queued" time ? The backups seem to run as they did prior to the upgrade, it seems to only be a problem with the restores.1.6KViews2likes6CommentsDoes More than one Techn work at Symantec?????
1. NO ONE IS ANSWERING THE PHONE ANYWHERE AT SYMANTEC 2. YOUR PHONE SYSTEM IS REPORTING 1 MIN THEN OVER AN HOUR 3. I WAS ON HOLD OVER TWO HOURS 4. I HAVE ANOTHER ISSUE WITH BACKUP EXEC 5. EVEN YOUR SYMANTEC OPERATORS CANT GET THROUGH TO SUPPORT 6. MY ONLINE SUPPORT IS IN AN ORIENTAL LANGUAGE 7. YOUR ONLINE CHAT SUPPORT DOESNT WORK. NOONE IS THERE EITHER I've been on hold all morning. Don't listen to "The Customer Hold the Longest. is X min. It goes up and down and noone ever answers.2KViews2likes7CommentsNeed help in restoring a file from an Imported Tape.
I am using Netbackup 7.0. Master server is linux / Client is Windows Server 2008. I restored a file from an imported Tape, but it does not appear in the folder. 15:50:05 9/21/2015: Restore Started 15:50:10 (610.xxx) Restore job id 610 will require 1 image. 15:50:10 (610.xxx) Media id P00580 is needed for the restore. 15:50:10 (610.xxx) Media id P00426 is needed for the restore. 15:50:14 (610.001) Restoring from image created Sun Jul 5 01:08:33 2015 15:50:14 (610.001) INF - If Media id P00426 is not in a robotic library administrative interaction may be required to satisfy this mount request. 15:50:41 (610.001) INF - Waiting for mount of media id P00426 on server utbak1.solint.net for reading. 15:52:10 (610.001) INF - Waiting for positioning of media id P00426 on server utbak1.solint.net for reading. 15:53:00 (610.001) INF - Beginning restore from server utbak1.solint.net to client utbak1.solint.net. 15:53:02 (610.001) /telecom/b9/17/85/512306.crexendo.com/storage/recordings/f72434ed-6b43-47c8-8d3c-2d27948211d4-1434058444168.aac 15:53:02 (610.001) Changed /telecom/b9/17/85/512306.crexendo.com/storage/recordings/f72434ed-6b43-47c8-8d3c-2d27948211d4-1434058444168.aac to /E/jimmy/f72434ed-6b43-47c8-8d3c-2d27948211d4-1434058444168.aac 15:53:02 (610.001) (610.001) INF - TAR EXITING WITH STATUS = 0 15:53:02 (610.001) (610.001) INF - TAR RESTORED 1 OF 1 FILES SUCCESSFULLY 15:53:02 (610.001) (610.001) INF - TAR KEPT 0 EXISTING FILES 15:53:02 (610.001) (610.001) INF - TAR PARTIALLY RESTORED 0 FILES 15:53:02 (610.001) Status of restore from image created Sun Jul 5 01:08:33 2015 = the requested operation was successfully completed 15:53:03 (610.xxx) INF - Status = the requested operation was successfully completed.Solved808Views1like2Comments