I have a client with a tough one here. They have a SQL server that was running for some time. After the So. Cal power outage they ran into problems with the server as a few drives have fried. They replaced those drives and since the Raid was toast freshly installed Windows 2003 and SQL server 2005. The server is setup with a C: partition of 20GB and the rest of the local drives E: partition of 466GB. They also have a SATA raid box that connects to the server as drive F of 4TB. This was used to get the backup files of the database they had on the server. Well I was going to help them restore the database but I noticed the size of the database backup .bak file alone is 3.6TB. NOt sure why this file is so large and how I can recover. Any thoughts?
3.6Tb sounds huge, but the backup job (maintenance plan) might have been set to append each backup to the same .bak file.
Suggest you run the restore wizard and see if you can select the latest backup.
If you use NetScaler you will want to see these guides. The NetScaler How To Guides show administrators how to get NetScaler up and configured by providing instructions for common scenarios and some not so common ones.
Established in 1997, Technology Architects has become one of the most reputable technology solutions companies in the country. TA have been providing businesses with cost effective state-of-the-art solutions and unparalleled service that is designed…