Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
dhumphries
Starting Member
18 Posts |
 Posted - 2009-04-24 : 09:19:11
|
| We have a server we are migrating from SQL 2000 to 2005. Everything works fine save one problem. We backup our files to a SAN and this works fine for all databases on this server except for one database. The one database produces a backup that is 100 Gig + and after starting a backup it never moves past Executing. I let this backup run all night just to see if it would move and while in the am it indicated it was 90% done the backup file had not been written two at all and was still the file from a month ago. This works fine if you backup to a local drive but will not backup to the SAN. Any thoughts would be helpful. |
|
|
nr
SQLTeam MVY
12543 Posts |
Posted - 2009-04-25 : 07:55:16
|
| If other backups work then this sounds like a write isue. Maybe it's getting an error trying o writte data.What happens if you cpy afileof that size to the san.You can bakup locally then copy the file or maybe use a backup utility lie redgate tht will compress the file on backup.==========================================Cursors are useful if you don't know sql.DTS can be used in a similar way.Beer is not cold and it isn't fizzy. |
 |
|
|
|
|
|
Backup will not move past Executing