itech

Hi, the WSUS DB (MSSQL Express 2005) of a customer won’t start after a hardware failure and bluescreen. Here are the steps which recovers the database back in an usable state. The SQL Server Instance logs errors like this "Could not redo log record (183366:6166:54), for transaction ID (0:117029942), on page (1:657511), database 'SUSDB' (database ID 5). Page: LSN = (183267:2976:260), type = 2. Log: OpCode = 2, context 3, PrevPageLSN: (183366:1717:287). Restore from a backup of the database, or repair the database." in  “C:\Windows\SYSMSI\SSEE\MSSQL.2005\MSSQL\LOG\ERRORLOG”  and the database is down. First connect to the DB Instance using a named pipe c:\> sqlcmd -S np:\\.\pipe\MSSQL$MICROSOFT##SSEE\sql\query and see state of the Database. Replace SUSDB with the Databasename of your DB. Try to repair the Database. The repair attempt fails… DBCC CHECKDB ('SUSDB') WITH NO_INFOMSGS, ALL_ERRORMSGS; go Error MEssage: Database ‘SUSDB’ cannot be opened

Move WSUS to another Hard Drive is a timely, yet fun little project First things first, let’s add another hard drive (if it’s virtualized, what you will want to do is add a Fixed disk for this, because you are using it as a database) For my scenario WSUS is for Several Hundred servers, so i will add a 300GB Fixed disk (you can add whatever size necessary for your environment) boot up the VM/Server and make sure the Disk Mounts (if not go into server manager, format, etc) Once created, make a new folder on the disk named “WSUS-Storage” Before proceeding, to make life easier, go ahead and run a WSUS cleanup on your server to remove all old updates (less updates to move,the less time it will take) from there open a handy command prompt on WSUS Server from there change folders cd c:/Program Files/Update Services/Tools from there issue the following command: wsusutil movecontent D:/WSUS-Storage D:/Move.log  wait a few minutes as your data is being moved to the