Home > Windows 2003 > Windows 2003 Server And Backup Exec 11d Job Rate Slow

Windows 2003 Server And Backup Exec 11d Job Rate Slow

the Job Rate is very low), to a point where it is unusable for timely backups. ALT, since that is a frontward looking srvr with exchange, no doubt on the same box you are using some sort of av package- have you tried uninstalling the av package? The server that seems to be the slowest did have a wierd power issue. Oops, something's wrong below. http://internetpasswordpro.com/windows-2003/windows-2003-server-slow-booting-up.html

Adaptec) does not work well with the server hardware (i.e. Which like more like double time backup and that too over a WAN link. We talked with Symantec, did everything, Defrag, updates, set certain settings such as use backup exec file compression software instead of hardware, talked with dell, updated all firmware updates, we are The job rate is usually well below 10 MB/min. http://www.techrepublic.com/forums/discussions/backup-exec-11d-job-rate-slow/

Also what about tryinga direct crossover cable link between your backup server and the exchange server to see how the performance goes - this would eliminate wiring infrastructure. For example, here are the dates that full backups were run, the elapsed time, byte count and job rate: 20/12/2013, 9h40, 479GB, 1,379mb/min21/12/2013, 10h32, 480GB, 1,376mb/min23/12/2013, 9h59, 480GB, 1,368mb/min24/12/2013, 10h01, 480GB, The result should show if any network performance issue. One thing to note, when Iwas running the backup yesterday, Iopenend up a DOSwindow and was copy files to the server running Backup Exec and my Job Rate went up to

I will be trying the different backup jobs between an external hard drive and tape today. What other sort of traffic is on your ethernet?What is the make and model of your switch? This is another culprit for slow backups. GPU RAM CPU ROM Submit Challenge × Join Now or connect with Connect with Facebook LinkedIn Already have an account?

Log in By creating an account, you're agreeing to our Terms of Use and our Privacy Policy. Labels: 12.x and Earlier Backup and Recovery Backup Exec 0 Kudos Reply 1 Solution Accepted Solutions Accepted Solution! I've attached 2 links for you to read through: http://seer.entsupport.symantec.com/docs/231488.htm http://seer.entsupport.symantec.com/docs/285756.htm Just make sure that the Removable Storage service is disabled, and that the Symantec drivers are being used. https://vox.veritas.com/t5/Backup-Exec/Improving-a-very-slow-Job-Rate-Read-the-Technical-Documents-but/td-p/111619 It takes about 4 days for a successful Windows backup.

About Advertising Privacy Terms Help Sitemap Join millions of IT pros like you Log in to Spiceworks Reset community password Agree to Terms of Service Connect with Or Sign up with Join Now For immediate help use Live now! Confirm if you have been getting the 1536 earlier if so what has changed. Here's a link to do some diagnostic testing from the OCP of the autoloader: http://support.dell.com/support/edocs/stor-sys/124t/en/124tvs16/diag.html 0 Kudos Reply Ok.

In our case, we have an HP StorageWorks AutoLoader Tape Robot that can be checked with the HP StorageWorks Library & Tape Tools. https://vox.veritas.com/t5/Backup-Exec/Backup-Exec-12-5-running-very-slow/td-p/264046 Join the community Back I agree MenuExperts Exchange Browse BackBrowse Topics Open Questions Open Projects Solutions Members Articles Videos Courses Contribute Products BackProducts Gigs Live Courses Vendor Services Groups Careers Store that's horrendous on a GB network! I built a test system running Windows server 2003 and tried out BEWS 10d, 11d, and 12.5 and all ran perfect.

Before upgrading to 12.5 and Windows 2008, our backups would take about 4 hours to do a full backup of 60 GBs. http://internetpasswordpro.com/windows-2003/windows-2003-server-taskbar.html I am starting to think maybe something happened to the USB on the motherboard. Then there should be something wrong with the application it self. the backup job i created does not backup any other server except itself, Where can i check this Pre/Post command, can it really mess it up or even slow the job

By creating an account, you're agreeing to our Terms of Use, Privacy Policy and to receive emails from Spiceworks. It's a long shot, considering both the drive and symantec should warn you, but it couldn't hurt!I'm not using tape, I'm backing up to NAS 0 Serrano OP Join our community for more solutions or to ask questions. http://internetpasswordpro.com/windows-2003/windows-2003-server-and-norton-ghost-2003-problem-long.html New teiva-boy Level 6 ‎02-09-2010 10:21 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content So many variables here!

Venkman182, How are things going, are you still experiencing the same issue?  If so, what items have you tried to alter/change to see if it made a difference. 1 Oh and the site that Ihad thought Ihad seen, looks like it applies to Windows 2003. For the life of me I can't find it now though.

However, our servers must have stayed on because they are connected to a UPS.   Any way of properly resetting the backup drive to the server?   Thanks. 0

I wouldn't think it would actually move across the T1. 0 LVL 4 Overall: Level 4 Microsoft Server OS 1 Message Author Comment by:ValleyENT ID: 232505322008-12-27 I did, however, have so I don't think its a  network issue. First Name Last Name Email Join Now or Log In Oops, something's wrong below. Are these changes correct?  Is there anything else that needs to be done? 0 Thai Pepper OP Jeff1792 Mar 19, 2014 at 5:12 UTC I would start with

I would suggest you perform below steps to identify the bottleneck. Job rate went from 5 MB/Min to 1,130 MB/Min. Oops, something's wrong below. http://internetpasswordpro.com/windows-2003/windows-2003-server-probs.html I also assume that there is nothing else in between your servers and the switch (i.e.

Just reminds one that the "narrowest" link sets the overall speed. (Restoring the SCSI connection to "Wide" also restored the normal speed.) 0 Sonora OP JimmyA Aug 7, Enable this setting and set the Bandwidth limit to 0. Join the community Back I agree Test your smarts. 88% of IT pros got this right. I don't think it is user I/O causing the issue, as I've tried running over the weekend (with no-one in the office) with the same result.

Best would be to move your backup server to location B or install a backup server in location B and install manager component to monitor the backup jobs in location A Now the problem we're experiencing:The job rate when transferring data from the remote server to the veritas server is extremely slow on both Linux and Windows servers. It seems like I need to do something in 2008 to get things to run back to the speeds Isaw in Windows 2003. 0 Kudos Reply Accepted Solution! Stop all Backup Exec for Windows Servers services. 2.

From this forum and searching on Google, I�m seeing that many people are achieving well into the 1700mb/min to 2000mb/min.At the job rates we are getting, it takes 101 hours to see  http://www.symantec.com/docs/TECH8326- Yep, I have exclusions on the AV - Thank you for the info on RAID 5, I've now reconfigured the NAS to RAID 10 ... I have moved the Powervault to another machine and the backup rates are still well below 10 MB/min. I am running Windows Server 2008 Standard and a Dell Powervault 124T Autoloader.

disabling on access scanning didn't make a difference, for now our only option is to disable the Sophos service pre backup and enable ti post backup. The setup with the previous backup software is identical to what was described above.I have been through this forum thoroughly and seen and followed the instructions on several threads and technical Click Start then runType gpedit.mscExpand Computer configurationExpand Administrative TemplatesExpand NetworkClick QoS Packet SchedulerHere you will find a setting called Limit reservable bandwidth. Which of the following retains the information it's storing when the system power is turned off?

Backups to tape of (large) Veeam files relatively recently started to get slower & slower each time they run, until the server is rebooted when they go back to normal speed, By creating an account, you're agreeing to our Terms of Use, Privacy Policy and to receive emails from Spiceworks. It's a long shot, considering both the drive and symantec should warn you, but it couldn't hurt! 1 Anaheim OP venkman Mar 21, 2014 at 12:58 UTC BE_Elias The backup drive is a Quantum DLT-V4.

If you backup less amount of data, the avg through would show high. We had a similar problem when some pathnames had more than 255 char. 0 Pimiento OP Bradley8318 Aug 6, 2008 at 4:03 UTC Hi Workaholic.   I highly By creating an account, you're agreeing to our Terms of Use, Privacy Policy and to receive emails from Spiceworks.