Moved SQL Server to different server

Our techs moved sql server over to a different server thats solely for sql and now the backups wont work right, they check for the consistency but wont back up the data. Can anyone give some suggestions pleaseWhat is the path they are trying to back up to?

What is the error you are getting?|||He says he is trying to backup from gcfs01 drive to gcsql drive and the error message he is getting is Device cannot be found|||Sounds to me like he is trying to back up to a network drive that is not connected to the new server.

Backing up to a network drive is a bad idea, in my opinion. You should backup to a local drive, and then copy the resulting files to a network drive or to tape for archiving.|||he is putting SQL on to a server all its own, so he is moving it from gcfs01 server to gcsql server. Its been functioning and backing up to the gcfs01 server with no problems|||So what do you think is the issue there

How are you doing blindman? btw|||Doing fine, thank you.

He needs to open up windows exporer and make sure he can access both those drives under SQL Agent's account.

Again, you should backup your databases to a local drive, referenced by the drive letter. I do not understand what you mean by "he is trying to backup from gcfs01 drive to gcsql drive".|||If you are trying to move the backup off the server, then backup locally, zip the file and then move the file. You will only need enough free space as large as the biggest backup+the zip file. Backing up to a network drive is much much slower and not as stable as backing up locally.

I backup all of my databases, zip them, and have them copied to my machine nightly. That way when I come in in the morning I have everything I need to recreate all my databases on my machine.

Just my opinion.|||Just my opinion...and the opinion of every other experienced dba. I don't know of anybody who would recommend backing up directly to a network drive.|||...and the opinion of every other experienced dba. I don't know of anybody who would recommend backing up directly to a network drive.Its Ok with me for a few manual "one off" situations, particularly in actual process of migrating to a new machine. I wouldn't recommend it for an ongoing practice, especially not an automated one.

-PatP|||You guys are such a great I really appreciate it :)

No I was just reiterating what I said earlier, I didnt know if explained correctly or anything. Let me tell him what you guys are saying

YOUR THE BEST|||so blind what your saying is instead of backing it up to the server, back it up to a local drive instead??

says hes getting error messages from the backup tapes..hmm|||I have a scheduled job the backs up the databases to disk in separate subdirectories, maintaining five days of historical data on the local drive. A second step then uses robocopy to archive the new files off to a network drive, where our network administrator uses veritas to back them up to tape.

You should not backup to a network drive, because you do not want database recoverability to fail due to network failure. Plus, as was mentioned, it is slow.|||Our Tech is actually going to try it out, hes going to take your advice...HOORAY!!!!!!!!!!!