The primary enhancements in this release are:<\/p>\n
- \n
- Addressed reported issues in the Backup\/Restore Power Tool<\/li>\n
- Fleshed out the Windows Shell Extension for version control<\/li>\n
- Took the first step on the path to a bunch of new TFS Build Power Tools<\/li>\n<\/ul>\n
<\/p>\n
Backup\/Restore Power Tool<\/h3>\n
We released the backup\/restore Power Tool in the last Power Tools release and you can read about it in depth here: http:\/\/blogs.msdn.com\/b\/bharry\/archive\/2010\/08\/18\/backing-up-and-restoring-your-tfs-server.aspx<\/a> and here: http:\/\/blogs.msdn.com\/b\/bharry\/archive\/2010\/08\/19\/backing-up-your-tfs-server-with-sharepoint-and-reporting.aspx<\/a>.\u00a0 Unfortunately, we pretty quickly got feedback that there were enough bugs in it that it was not nearly as useful as we had imagined.\u00a0 In this new release, the experience is pretty much the same so I\u2019m not going to repeat all of the screen shots.\u00a0 The big difference is that we fixed just about every bug that was reported.\u00a0 We also put a ton more effort into testing it.\u00a0 This is probably the most involved Power Tool we have shipped today and it\u2019s clear that the standard Power Tool approach was not sufficient.\u00a0 We\u2019ve tried really hard to ensure that this is going to be a great solution for you.\u00a0 Of course, if you find any issues at all, please let us know and we\u2019ll get them fixed as quickly as we can.\u00a0 Here\u2019s a list of all of the bugs that we fixed:<\/p>\n
- \n
- The backup wizard window goes to the background when switching between windows<\/li>\n
- Support backup\/restore when SQLServer uses an international date format<\/li>\n
- Backup RS encryption key with reporting databases<\/li>\n
- Transactional backups only run for “interval” each day, instead of every “interval” for the entire day<\/li>\n
- Differential backups scheduled at different time than configured<\/li>\n
- The backup plan wizard cannot find Reporting Services databases when the report server is using an FQDN<\/li>\n
- The backup plan wizard fails with the message “Value does not fall within the expected range” on w2k3 if advanced schedule is used<\/li>\n
- Backup retention duration can\u2019t be set to less than 30 days<\/li>\n
- Backups timeout after 10 minutes<\/li>\n
- Backup plan should remove NO_TRUNCATE option so that the SQL log doesn’t grow indefinitely<\/li>\n
- Send admin warning emails when backups fail<\/li>\n
- Remove Sharepoint Marked Transactions from the backup plan to avoid putting Sharepoint in an unsupported state<\/li>\n
- Backup Wizard should not schedule TfsDeleteOldBackup task to start after (today + retention days) days<\/li>\n
- Restore Wizard: In the Sql Instances page , it is not possible to scroll down in order to select a single database to restore<\/li>\n
- The backup plan wizard configuration fails on w2k3 if task account is Network Service<\/li>\n
- Need to prevent scheduled tasks and backup plan configuration from running while installing SP1<\/li>\n
- Split “External Databases” page into “Reporting Instance” and “Sharepoint Databases”<\/li>\n
- Need to relocate ldf and mdf data files if they are already in use by another database<\/li>\n
- TfsEmailValidation task sometimes keeps running until it times out<\/li>\n
- Back up plan not created when reporting database is not selected<\/li>\n
- Failure to restore RS encryption key should not block TFS database restore<\/li>\n
- Validating email using task scheduler should be done after granting permissions<\/li>\n
- The size of the backup is not accurate in the restore wizard<\/li>\n
- During restore, we should not allow one database failure to block all others<\/li>\n
- Improve performance of listing backupsets in the restore wizard<\/li>\n
- Restore fails if running from start menu<\/li>\n
- Backup Plan Wizard needs to give a meaningful message in case of using multi-farms<\/li>\n
- Backup Plan Restore Wizard crashes when ConfigPT.xml files doesnt exist<\/li>\n
- On a clean\/unconfigured machine, the restore wizard fails to retrieve the backup extensions<\/li>\n
- Restore Wizard UI becomes unresponsive after loading and modifying backup path<\/li>\n
- Restore fails on a sql instance if it has non-reachable databases<\/li>\n
- Restore leaves the configuration db in a restoring state<\/li>\n
- Display Information about SQL Timeout in the backup plan wizard<\/li>\n
- DiskFreeSpace check is checking for too small a number to be valuable<\/li>\n
- Backup set size is calculating only trn sizes in some cases<\/li>\n
- When the restore wizard crashes it “resets” the ConfigPT.xml<\/li>\n
- The test db used to while creating a backup plan should be labeled with test or temp name instead of “TFS_Configuration_*”<\/li>\n
- Restore Wizard gives stack over flow exception when computing sizes<\/li>\n
- File contention issue on ConfigPT.xml between backup tasks and restore wizard<\/li>\n
- Process terminates with StackOverflowException when loading large backupset<\/li>\n
- Strong password for RS key does not accept all special characters<\/li>\n<\/ol>\n
Yeah, it\u2019s a long list, I know.\u00a0 I\u2019m really sorry about the issues in the first release and we appreciate your help in finding many of them.\u00a0 I really think you\u2019ll like this release.<\/p>\n
Windows Shell Extension<\/h3>\n
I\u2019m really excited to finally be getting back around to giving the shell extension some more love.\u00a0 It\u2019s been a long time.\u00a0 We focused on adding the most requested functionality to it and it\u2019s getting close to the point where most people won\u2019t have to run Team Explorer for version control if they don\u2019t want to.<\/p>\n
Here\u2019s a screen shot showing the new commands on the context menu.<\/p>\n
![\"Image](\"https:\/\/devblogs.microsoft.com\/bharry\/wp-content\/uploads\/sites\/8\/2011\/03\/6811.image_thumb_576B4FC7.png\")
<\/a><\/p>\n![\"Image](\"https:\/\/devblogs.microsoft.com\/bharry\/wp-content\/uploads\/sites\/8\/2011\/03\/4274.clip_image002_thumb_1F1CB2E2.jpg\")
<\/a><\/p>\n