Jump to content

derek500

Members
  • Content count

    102
  • Joined

  • Last visited

  • Days Won

    3

Everything posted by derek500

  1. Hi, I frequently get 519 errors on a certain client. I'm using Retro Server 6.1.126 with RDU 6.1.2.102 on a 10.3.9 client PowerMac G4 to AIT-2 tape via SCSI. The Client is OS X Server 10.4.5 on a Dual G4 XServe with client 6.1.107. The Xserve is running Kerio email server and a few minor services, nothing else. The mail store is on an Xserve RAID. Nightly the mail server creates it's own backup of the email store to .zip files. The mail server backs up 'full' weekly, and 'differentially' the rest of the week. The backup files being backed up are also on the RAID, only the static zip files are backed up - not the live mail store. The zip files total about 60 GB for the full, 1-2 GB for the differential files. The config in the email server limits the size of each zip file to 2 GB, so the mail backup consists of about 30 2GB files. It's usually when backing up the main weekly backup files that the -519 errors occur. I never have any problems backing up the Xserve's local HD. The Xserve has a gigabit connection to our LAN, the Retrospect Server only has a 100 MB connection. They are both connected to the same switch, an Asante GX5-424W Gigabit switch. I don't see any packet collision happening. Performance is reasonable for the zip files, around 350 Mb/Sec to the tape drive. If I restart a failed backup sometimes it will complete, sometimes it -519s again. If I restart it again, same thing - sometimes it completes, sometimes not. Eventually it will complete. The speeds stay relatively good up until the failure. Where do I start troubleshooting? It's the only volume I have problems backing up out of 80 clients, so I don't see this being a SCSI problem although the hardware compression stinks. I know copy speeds from the RAID are good, and it performs well as a mail server. Finder copy speeds of those same zip files to the backup server are reasonable and the finder copy doesn't fail. I can reproduce this error for most (but not all) full backup from the Retrospect server, and after most (but not all) Full backups that Kerio makes of it's mail store. The failure point is usually anywhere between 20-30 GB of data. Thanks -Derek Cunningham
  2. Yep, I've read both of those documents and that's kind of where I'm at. When we moved to OS X on our backup servers I upgraded to the ATTO UL3S and haven't had any problems with it, and ATTO's support has been excellent. I got burned when Apple moved to PCIe and didn't leave any legacy PCI ports. Now I am ready to roll out my CPU upgrade and can't figure out how to find any qualified SCSI cards to use. I was very surprised when I tried to install my UL3S into my G5 and couldn't do so. How can ATTO list the UL5D as a qualified card when EMC/Retrospect doesn't list it? I guess I'll have to take my chances with Retrospect's support, given that ATTO will support it. Retrospect, if you do support this card please hear the sarcasm in this statement. If there is a list of qualified SCSI cards please publish it somewhere findable! Russ, thanks for the advice. -Derek
  3. Hi, I am having trouble finding a list of qualified PCIe scsi cards for a new PowerMac G5. Can someone link to the list I need or recommend any cards? The only card I know of is the ATTO UL5D which is very expensive, and someone else mentioned in a recent post that it wasn't listed under qualified hardware. Thanks for any advice. -Derek
  4. "The Client is OS X Server 10.4.5 on a Dual G4 XServe with client 6.1.107" These were the latest updates we had available when we started watching this problem closely. I've seen a few minor issues reported after Server 10.4.6, so I'm waiting a bit on that update. I see that they recently released some client updates as well, I can certainly try that but I don't see our issues mentioned in the new client documentation, so I'm not very hopeful. Can you update the onboard NIC drivers separately?
  5. I'm still having the same problem. I watched the packet count in the switch and there are no lost packets or collisions reported. Performance is decent until it quits. What do I do next? Here's what it looks like in the log: - 5/8/2006 7:22:09 PM: Copying Kerio Backups on Mailserver Trouble reading files, error 519 (network communication failed). 5/8/2006 9:28:56 PM: Execution incomplete. Remaining: 15 files, 27.0 GB Completed: 18 files, 35.9 GB Performance: 306.2 MB/minute Duration: 02:06:47 (00:06:50 idle/loading/preparing) Thanks for any assistance! -Derek
  6. Thanks for the suggestion. Unfortunately, no. Definitely no link encryption. No problems last night and it backed up 40 GB from that client. I'm sure next Monday I'll see the same problem again though. Any other suggestions? THanks -Derek Cunningham
  7. Thanks for the help so far. I reset the switch counters yesterday, and last night the same thing - 21.9 GB into a 40 GB backup a -519 error. No packet losses to any port on the switch. Switch speeds are negotiated correctly (1 GB full on the XServe, 100 MB Full on the Retro Server's G4) What's the next troubleshooting step? Thanks, -Derek
  8. Hi Lennart, I did see some lost packets in the switch for those ports, but it was not very many, and the counters hadn't been reset in ages. I reset the counters and I'll look there after the next failed backup. Thanks for the advice. If there are lost packets happening during the backup, what can I do about it? Does it only take 1 lost packet to bring up the -519? Thanks, -Derek
  9. Hi, The subject pretty much says it all. For a new PowerMac to use with Retrospect Server should I get ECC or non-ECC RAM? Does it matter to Retrospect? I have to justify the added price, or I can save money by getting the standard RAM. Don't see this mentioned in system requirements anywhere. Thanks -Derek Cunningham
  10. Hi, I am using Retrospect 6 Server on Mac OS X 10.3.6 running Backup Server 24/7. I have one windows client that keeps giving me trouble. The client machine is Windows 2000 with no special firewall software installed, it has two NICs, one wired, one wireless. Every couple of weeks the client stops backing up and won't respond to the Retrospect server. I cannot configure the client, I cannot add the client if I forget it. I add clients by name, not IP address. Everything else on that machine seems normal. While the computer is in-house, the wireless card is turned off. I have had the client restart several times (with the wireless card off before the restart). I can ping the machine, etc. The only way I have been able to fix the problem is to reinstall the client software, then forget/add the client on the server. I can reinstall the client again and I'm sure the problem will be gone for a couple of weeks, but I want to figure out why this is happening. What are my troubleshooting options here? Thanks, -Derek Cunningham
  11. I'm looking at updating/upgrading one of my Retrospect systems and wanted to run this config past you folks. Right now the system has a LVD SCSI AIT-2 drive and runs Backup Server watching our network for laptops, and backs up to tape. I have it set to back up every machine every 3 days. We cycle the backup set every two weeks, with 6 tape sets in rotation, so we have 12 weeks of backup at any given time. I would like to do the back up to disk instead of tape, but we are still required to do the set rotation, so I was thinking of this solution: Configure a new PowerMac with some additional RAM (the lowest cost is a dual 2 GHz G5; that with 1 GB of ram should be more than enough machine), then I can re-use the SCSI card and tape drive from the old system (it's an ATTO UL3S, please speak up if that won't work in the new PowerMacs). Then I install the OS and Retrospect on the primary drive (160 GB internal drive). For the backup storage, I'm thinking I can install myself two 400 GB internal SATA hard drives and use Disk Utility to create a RAID 0 800 GB storage area. Once every other week, dump the backup to tape and take the tapes offsite and recycle the disk space. The two week backup sets tend to run about 120 GB, not quite filling two AIT-2 tapes. Any thoughts on this? Things I'm interested in... Hard Drive Cache: I see a lot of different cache sizes available. If I remember right, Retrospect really doesn't want any cache at all, right? So is this irrelevant? How do I ensure that the cache isn't used? RPMs: 7200 seems sufficient, especially with a RAID 0 in effect? Is it worth 10,000 RPM drives? Tape Speed and Capacity: I'm going to have to do the offload to tape manually (right?), so it would be nice to have happen as fast as possible. I could probably spring for the AIT-3 drive if there's a significant speed gain, but otherwise I'd rather not spend it if I don't need to. Disk to Disk to Tape: I've got plenty of experience making backup sets on disk, and making backup sets on tape, but I've never moved a backup set from one to the other. Is that the duplicate function? What is the best approach for this? Backup to File? Backup to Disk? Can a File span multiple volumes if needed? Physical storage: Is it possible to have 3 internal hard drives in a powermac G5? Am I wasting my time installing internal disks? Is this all doable using external firewire drives? It seems to me that using internal drives will cost less than externals (no enclosures needed) and by directly connecting with SATA will be faster, more reliable, etc. The drives would be controllable by disk utility and I could RAID them, etc. That part of the idea sounds difficult to do with external drives... ... Ideally I would try this stuff out to see how it goes, but I don't really have the available systems or time to play with. Any thoughts would be appreciated. I'm hoping the Disk to Tape part is as easy as it sounds. Any thoughts are much appreciated. Thanks, -Derek Cunningham
  12. The clapping hands that appeared to me should be 3 colons in a row, NOT ":hands "
  13. From the RetroTALK mailing list, July 19, 2004, posted by Derek Chee (that isn't me even though we have the same first name): Awhile back, I asked about rotating the Retrospect log files. I rolled my own rotating scripts based on the ones in Mac OS X 10.3. I thought somebody might find them useful. Add to /etc/daily.local and change ownership and privileges to root:wheel and rwxr-xr-x, respectively : daily.local : #!/bin/sh - # # @(#)daily 8.2 (Berkeley) 1/25/94 # PATH=/bin:/usr/bin:/sbin:/usr/sbin:/usr/local/bin echo "" echo -n "Rotating log files:" cd /var/log for i in retropds.log; do if [ -f "${i}" ]; then echo -n " ${i}" if [ -x /usr/bin/gzip ]; then gzext=".gz"; else gzext=""; fi if [ -f "${i}.6${gzext}" ]; then mv -f "${i}.6${gzext}" "${i}.7${gzext}"; fi if [ -f "${i}.5${gzext}" ]; then mv -f "${i}.5${gzext}" "${i}.6${gzext}"; fi if [ -f "${i}.4${gzext}" ]; then mv -f "${i}.4${gzext}" "${i}.5${gzext}"; fi if [ -f "${i}.3${gzext}" ]; then mv -f "${i}.3${gzext}" "${i}.4${gzext}"; fi if [ -f "${i}.2${gzext}" ]; then mv -f "${i}.2${gzext}" "${i}.3${gzext}"; fi if [ -f "${i}.1${gzext}" ]; then mv -f "${i}.1${gzext}" "${i}.2${gzext}"; fi if [ -f "${i}.0${gzext}" ]; then mv -f "${i}.0${gzext}" "${i}.1${gzext}"; fi if [ -f "${i}" ]; then mv -f "${i}" "${i}.0" && if [ -x /usr/bin/gzip ]; then gzip -9 "${i}.0"; fi; fi touch "${i}" && chmod 640 "${i}" && chown root:admin "${i}" fi done echo "" Add to /etc/monthly.local and change ownership and privileges to root:wheel and rwxr-xr-x, respectively : monthly.local : #!/bin/sh - # # @(#)monthly 8.2 (Berkeley) 1/25/94 # PATH=/bin:/usr/bin:/sbin:/usr/sbin:/usr/local/bin echo "" echo -n "Rotating log files:" cd /var/log for i in retroclient.log; do if [ -f "${i}" ]; then echo -n " ${i}" if [ -x /usr/bin/gzip ]; then gzext=".gz"; else gzext=""; fi if [ -f "${i}.6${gzext}" ]; then mv -f "${i}.6${gzext}" "${i}.7${gzext}"; fi if [ -f "${i}.5${gzext}" ]; then mv -f "${i}.5${gzext}" "${i}.6${gzext}"; fi if [ -f "${i}.4${gzext}" ]; then mv -f "${i}.4${gzext}" "${i}.5${gzext}"; fi if [ -f "${i}.3${gzext}" ]; then mv -f "${i}.3${gzext}" "${i}.4${gzext}"; fi if [ -f "${i}.2${gzext}" ]; then mv -f "${i}.2${gzext}" "${i}.3${gzext}"; fi if [ -f "${i}.1${gzext}" ]; then mv -f "${i}.1${gzext}" "${i}.2${gzext}"; fi if [ -f "${i}.0${gzext}" ]; then mv -f "${i}.0${gzext}" "${i}.1${gzext}"; fi if [ -f "${i}" ]; then mv -f "${i}" "${i}.0" && if [ -x /usr/bin/gzip ]; then gzip -9 "${i}.0"; fi; fi touch "${i}" && chmod 640 "${i}" && chown root:admin "${i}" fi done echo "" -- Derek At 6:59 PM -0700 5/26/04, I asked the list: I just noticed that the retropds.log file in /var/log has grown to over 90MB. Has Dantz considered adding rotation of the retropds.log to the Mac OS X daily/weekly/monthly log rotation scripts? Has anybody else added their own rotation scripts? If so, would you be willing to post what and where you dropped the scripts? I'm leery of modifying the system scripts as on OS X upgrade later, my customized scripts will be wiped. -- Derek _______________________________________________ Retro-Talk mailing list List Address: Retro-Talk@list.dantz.com Retro-Talk settings and archive: http://list.dantz.com/mailman/listinfo/retro-talk Dantz Support: http://www.dantz.com/support
  14. Quote: Are there lots of small files on these server machines? Large files back up _much_ more quickly than many small ones. There are a lot of files on both machines. The dual G4's RAID is 76 GB and 649,465 files. The G5's RAID has 207 GB and 606,144 files. The dual G4 has the most files and the smaller files, it is our email server. It makes sense that it has the slowest backup rate. The G5 acts as our file server with years of data and many users. The log claims the backup rate of the G5 raid at 400 MB/Min average between copy and compare, but apparently this does not factor in the overhead time needed for multiple files.
  15. I apologize in advance for the long post. I have tried to include all relevant information about my problem here. I also searched the Dantz knowledgebases for anything similar to this problem we are seeing, please point out if I missed a KB article or forum post that addresses this issue. I have two Xserves with RAIDs attached via Fibre channel. When I back up these machines to my backup server (PowerMac G4), I get very different backup speeds, depending on if it is the internal hard drive of the Xserve, or the Xserve RAID volume. Each Xserve RAID is connected with Apple Fibre channel cards, and have no problem moving large amounts of data at high speeds to network destinations via afp or smb. The first Xserve (our email server) is a dual G4 and backs up at between 300 and 400 MB/min for the internal hard drive. Our last Full backup happened at 318.6 MB/Min (according to the report) for ~13GB. The last incremental ran 414 MB/Min. (1.5 GB) It's RAID volume is the email store. It is configured as RAID level 5 and currently holds approximately 75 GB of data. The RAID volume is selected in the Xserve's retrospect client on the server. Data transfer during the last Full backup was 21.6 MB/Min taking over 10 hours. This seems like a lot of time for 75 GB. The second Xserve (our file sharing server) is a single G5 and the internal hard drive backs up at 200 MB/Min for Full backups. This Xserve controls the file share of it's RAID and some authentication duties (only relative to the RAID access). The G5 Xserve's RAID volume is also RAID 5 and stores about 200 GB of data. The backup transfer rate was 53.8 MB/Min on the last Full backup, taking 16 hours. Better than the first set, but still slow! Mostly both servers are reasonably idle except for occasional file transfers, except that the mail server always has a light steady stream of activity. The full backups start every other Friday night to make use of the light weekends. For confirmation, I copied a 1.6 GB file through finder from the local volume of the G5 Xserve and from that Xserve's RAID. Performance of both file copies was superb, taking 2.8 minutes from the Xserve's local drive and 2.77 min from the RAID. Needless to say, we were concerned to find out the discrepancy of data transfer with the retro client. At afp transfer rates, 200 GB should take under 120 minutes to copy, and that again to verify, that's 4 hours, not 16. Why does Retrospect take so long when afp does not? What can we do about it? I understand that the backup is more than just copying - I should allow some extra time for matching, comparing, spanning multiple tapes (performed by an auto-loading library), so even 5-6 hours seems reasonable here. The backup server is a 400 MHz G4 PowerMac with 1.5 GB of RAM, AIT-2 tape drive and ATTO UL3S SCSI card. Our network is a mix of gigabit and 10/100 switches. The Xserves and the Retro server are all on the same gigabit switch (although the PowerMac does not have a Gig network card, it runs correctly at 100 MB with no errors). The best performance of the backup comes from the second drive internal local to the Retro server, it runs at 600 MB/Min to the tape drive, so I know the capacity of data flow to the tape drive is sufficient. Backup Server is 10.3.6 client with Retrospect Server 6.0.204 with RDU 6.0.103. Both Xserves run 10.3.4 Server with Retro Client 6.0.108. Thanks for any ideas. We would really like to speed up the backups of the RAID volumes! P.S. Please feel free to correct my math if I have made a mistake here - the 1.64 GB file copy took 2 minutes, 48 seconds, which I figured is 2.8 minutes. 1.64 GB / 2.8 minutes is .58 GB/min. At this rate, 200 GB should take 116 minutes?
  16. Hi Nate, According to the ATTO config tool, it is driver version 3.1.0. Should we upgrade it? It is also running flash version 1.6.6f0. These are the settings I left it at after a long battle with -206 errors and a call to ATTO tech support. Other than the speed from the Xserve RAID, it seems to work very well. Since we are seeing 600+ MB/Min from the internal hard drive, I thought I had ruled out SCSI communication as an issue... Thanks -Derek
  17. We are backing up to a SCSI AIT-2 Sony SDX-500C in a Qualstar 4212 Library.
  18. (1/7/02) The setup worked flawlessly for two weeks straight, until yesterday. I start a new backup set every two weeks and last friday was the day for me to start a new set. It ran over the weekend but I recieved the -206 error again yesterday. The alarming thing for me is that last night I recieved the -206 error on my second retrospect system where the Tape Library I mentioned in earlier posts sits immediately next to my APS Tech tape drive. I again suspect some sort of electrical interference being thrown from the single AIT-2 Drive but have no way of confirming this. Can anyone suggest a way to get an idea for electrical noise in a specific area? Would it help if I posted the exact error from my log? It contains a 16 numbered hexidecimal looking code that somebody might be able to de-code for me. ? Thanks, -Derek
  19. Hi, I originally posted this on the OS 9 board, but I am re-posting it to the OS X board because we have moved the machine having the problem to OS X and I plan on solving the problem within OS X. Please continue to read, there are a few posts as I added information to the situation. Thanks in advance for any help, this has been an extrememely frustrating problem. -Derek Cunningham
  20. Hi all, I have re-posted this issue on the OS X discussion board, I'm determined to resolve this problem under OS X, so there it goes. Please don't reply to this thread anymore. Thanks, -Derek
  21. Hi, I am looking for some help here. We are getting very frustrated and don't know where to go from here. (and yes, I have used a cleaning tape! Several times!) We have two seperate retrospect systems running. One is a B&W G3 running OS 8.6, retro 4.3 (ADK 1.8 and RDU 2.2) with a Qualstar 4212 loader to a sony SDX-500C drive and an adaptec 29160 SCSI card. It runs a scheduled backup of about 60 clients, mac OS 8.6 through 9.2 and several windows clients, Win98 through 2000. This system _was_ running flawlessly for a year and a half. I'll get into it's problems in a minute. The other system started out as a beige desktop G3, OS 9.1, Retro 4.3, Adaptec AHA-2940UW SCSI card, APS Tech AIT-2 single tape drive (sony SDX-500C also). It runs backup server all the time for our laptop windows and mac clients. I'll give it's problems first. The Desktop G3 was running for months with no problems. We moved the system from one building to another and began experiencing the -206 errors. I called APS Tech, the drive is still under warranty, so they took it back and replaced the drive. I got the drive back, got the same -206 error again and called back. They suggested possible electrical interference from an external source. I described our server room to them (hanging overhead power strips and twin ceiling mounted HVAC units). The G3 and tape drive was on an upper shelf, maybe 5-6 feet below the power cabling. The A/C unit was also within 8 feet. The tech I spoke with at APS suggested moving the entire setup, suspecting possible electrical interference from the overhead items. I brought the G3 and tape drive into my office, set it all on a shelf and let it run for a couple days there. I recieved the same -206 error a few times there, each about 2 days apart. This eliminated the server room as a potential cause, so back to the server room it went. I contacted APS again, they said send the drive back. This time they replaced the drive mechanism and the internal controller board of the drive. I got the drive back, hooked it all up and in a few days got the -206 error AGAIN. Grrr. now this is frustrating. The last diagnostic from APS: Try a different computer, scsi card, etc. I built a G4, OS X 10.1.5, Adaptec 39160 and Retro 5. I had it on the top shelf in our server room. I got the -206 error after 4 days of operation. This time I figured, okay, maybe it IS the electrical interference. I moved it down to the lower shelf (right next to the 1st system I talked described). The first night it was there, I got a -206 error on my B&W/Qualstar system! Now THIS leads to something (I suspect). It must be the power supply in the APS tech drive. The APS Tech drive was right next to the qualstar loader so that must be it, right? I contacted APS Tech again. Described what happened. They said to send the single drive back and this time they would replace the drive, the board AND the power supply. They still have my drive, but then today I came in and found the -206 error on my qualstar system again. This NEVER gave me any problems before. I have been using the B&W G3 for about 1-1/2 years with this setup and other than one bad tape I never recieved any errors from this system. I am at my wits end here. We have re-used old tapes, taken new tapes right out of the box (we use Sony SDX2-50C tapes), it doesn't seem to matter. What can I try from here? I'm open to any suggestions. Is there such a thing as an electrical interference meter? Thank you for taking the time to read this horendously long post and still take the time to think about my problem. -Derek Cunningham
  22. (12/31/02) Well, I recieved the error again after replacing the drive. In a bout of frustration and hope I upgraded the machine to 10.2.3, added the new Adaptec 39160 drivers and RDU, and haven't seen the error in a week. Keeping my fingers crossed... -Derek
  23. Update (12/18/02): I heard back from APS Tech yesterday and they can find nothing wrong with the drive I sent them. I am getting it back again, I'll update again when it is in and running... Thanks for the help, -Derek
  24. Hi, I am looking for some help here. We are getting very frustrated and don't know where to go from here. (and yes, I have used a cleaning tape! Several times!) We have two seperate retrospect systems running. One is a B&W G3 running OS 8.6, retro 4.3 (ADK 1.8 and RDU 2.2) with a Qualstar 4212 loader to a sony SDX-500C drive and an adaptec 29160 SCSI card. It runs a scheduled backup of about 60 clients, mac OS 8.6 through 9.2 and several windows clients, Win98 through 2000. This system _was_ running flawlessly for a year and a half. I'll get into it's problems in a minute. The other system started out as a beige desktop G3, OS 9.1, Retro 4.3, Adaptec AHA-2940UW SCSI card, APS Tech AIT-2 single tape drive (sony SDX-500C also). It runs backup server all the time for our laptop windows and mac clients. I'll give it's problems first. The Desktop G3 was running for months with no problems. We moved the system from one building to another and began experiencing the -206 errors. I called APS Tech, the drive is still under warranty, so they took it back and replaced the drive. I got the drive back, got the same -206 error again and called back. They suggested possible electrical interference from an external source. I described our server room to them (hanging overhead power strips and twin ceiling mounted HVAC units). The G3 and tape drive was on an upper shelf, maybe 5-6 feet below the power cabling. The A/C unit was also within 8 feet. The tech I spoke with at APS suggested moving the entire setup, suspecting possible electrical interference from the overhead items. I brought the G3 and tape drive into my office, set it all on a shelf and let it run for a couple days there. I recieved the same -206 error a few times there, each about 2 days apart. This eliminated the server room as a potential cause, so back to the server room it went. I contacted APS again, they said send the drive back. This time they replaced the drive mechanism and the internal controller board of the drive. I got the drive back, hooked it all up and in a few days got the -206 error AGAIN. Grrr. now this is frustrating. The last diagnostic from APS: Try a different computer, scsi card, etc. I built a G4, OS X 10.1.5, Adaptec 39160 and Retro 5. I had it on the top shelf in our server room. I got the -206 error after 4 days of operation. This time I figured, okay, maybe it IS the electrical interference. I moved it down to the lower shelf (right next to the 1st system I talked described). The first night it was there, I got a -206 error on my B&W/Qualstar system! Now THIS leads to something (I suspect). It must be the power supply in the APS tech drive. The APS Tech drive was right next to the qualstar loader so that must be it, right? I contacted APS Tech again. Described what happened. They said to send the single drive back and this time they would replace the drive, the board AND the power supply. They still have my drive, but then today I came in and found the -206 error on my qualstar system again. This NEVER gave me any problems before. I have been using the B&W G3 for about 1-1/2 years with this setup and other than one bad tape I never recieved any errors from this system. I am at my wits end here. We have re-used old tapes, taken new tapes right out of the box (we use Sony SDX2-50C tapes), it doesn't seem to matter. What can I try from here? I'm open to any suggestions. Is there such a thing as an electrical interference meter? Thank you for taking the time to read this horendously long post and still take the time to think about my problem. -Derek Cunningham
  25. Well, I recieved the error again after replacing the drive. In a bout of frustration and hope I upgraded the machine to 10.2.3, added the new Adaptec 39160 drivers and RDU, and haven't seen the error in a week. Keeping my fingers crossed... -Derek
×