Warm Standby with Windows Server 2003

We have a primary file server for our Windows Server 2003 (Standard Edition) domain. We're running active directory in a plain vanilla type environment. When we recently migrated from an old server to a new one, I set up a DNS entry as Files.OurDomain.local as an Alias (CNAME) to the real server name. I disabled Strict Name Checking (see MSDN link text). All client machines now refer to \\Files or \\Files.OurDomain.local to get to their files. No one ever uses RealServer.OurDomain.local. Printers also use an alias to get to their server.

I plan to use this setup in the event of a significant server problem to switch the dns alias to another server as a poor man's warm standby. Also it should make server migrations in the future very easy. I tried DFS but it didn't give me the comfort that I had exact control over where files were going. The default TTL (Time to Live) for the DNS entries is 1 hour. That's probably what it would take the tech staff to determine that the server had been lost and we would really need to switch to the backup.

Any concerns or problems (or even accolades) with this approach?

It seems like you're handicapping yourself by not just using DFS or Clustered File Sharing.

http://support.microsoft.com/kb/284838