Hmm, that's the same firmware build that I'm running. I'm about to head out the door to a tech rehearsal and the machine that backs up to that network drive isn't the one that I'm typing from right now, but I will double check when I get home this evening that it is backing up correctly to that NAS 220.

I know you're mad busy, ND, and weekends don't really exist, but if you do get a chance to see if my setup differs, I'd be very grateful.

There's another kind of help I'm beseeching. I need to write a guggle to zatch testing strategy. Normally, I write them in slices--performance testing strategy, UAT strategy, etc. But we're migrating a platform from physical servers to virtual servers, and there's a credibility issue, and I need to come at this thoroughly.

So far, I'm looking at it with these facets:

• stability testing (smoke, stress, etc)
• performance testing (acceptable response times)
• functionality testing (use cases)

Performance testing is pretty much taken care of, and functionality testing is a matter of resurrecting what we did when we first installed the system, but we don't normally do any sort of stability testing here. And this system? REALLY needs to pass these tests, because people think it sucks.

One of my problems is that I don't have the technical knowledge to design an appropriate smoke test for this platform, but I also am not familiar with the scope of tests that one does in order to assure (because that always works) stability. Smoke tests are just general "this won't fall over" tests, right? If I had general principles, then maybe I could work out how to translate it for this app.

My first deliverable is an overarching test strategy document. Does anyone know of good online resources for that sort of thing?

I'm not sure what I am doing differently but it's definitely still working on my end. My MacBook Air, and K's Air both use the Black Armor 220 for time machine. I'm watching my air run a backup now.

I see a BA_Backup share as an option for a backup disk and it's working like a charm. The Air is running OS 10.7.4.

I need to write a guggle to zatch testing strategy. Normally, I write them in slices

I am rarely lost in this thread, but this could be a Lewis Carroll poem from my perspective.

Sits with Gris on this one.

So, anyone know how to view the communications between Microsoft Access 2007 and SQL Server 2008? Using ODBC and TCP/IP.

Or does anyone have a good rec for a packet-sniffer?

What version of firmware is your NAS on, ND? I can see BA_Backup, but when I select it, that's the error I get.

That's not Lewis Carroll, it's James Thurber. Sheesh, people.

ita, silly question with your backup problems... Not 100% familiar with the set up, as I don't have one, but, the NAS is connected via cable to the airport?? Could you have a bad cable??? Hey, sometimes it's the simple things.

This is what the web interface to the NAS reports:

2000.1231
Built on Fri, 19 Aug 2011

The NAS is connected to a router, omnis. And I can copy files to and from it just fine. I just can't:

• use Time Machine
• resolve symbolic links in a Photoshop Elements save dialog (they resolve fine in a PSE open dialog, and all the other apps I've tried so far)

I can certainly try swapping cables, but that would be some of the weirdest ethernet behaviour I've ever seen.

Of course, ND having the same version of OS and firmware as mine isn't really comforting. Hmm. What are the other variables? Must ponder.