Windows Server Backup does NOT backup Ex2k7.

A little tidbit I gathered from studying W2k8:
W2k8 released a new backup technology named Windows Server Backup. Admittedly, client may not consider using this to backup critical Exchange data. However, a few may such as Windows SBS users or EBS users. Personally, I've used NTBackup to save my hide on several occasions specifically in clearing out the transaction logs and creating the CYA backup of a mailbox database.

It turns out that this technology doesn't support Exchange database backups as with W2k3 and previous versions of Windows. With EBS, I found the Exchange database is configured for circular logging by default. (I've heard from MS sources that this changed with the RTM edition of EBS but the Internet documentation hasn't caught up.) I expect SBS is as well.

The basic premise for this is the lack of VSS support for Exchange in W2k8. With third party solutions, an Exchange aware VSS writer? must be provided to send the VSS signals to Exchange to make it backup. Exchange doesn't come with it, nor does W2k8. However, I did find a blog post stating that MS announced they will develope on for the use with Windows Backup Server and release it later this year.

Here are a few links which reveal this:
http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=2787183&SiteID=17
http://blogs.technet.com/scottschnoll/archive/2008/06/15/back-from-teched-it-pro-north-america-2008.aspx
http://blog.crowe.co.nz/archive/2008/06/02/Windows-Server-2008--Exchange-Server-2007--NO-SUPPORTED.aspx

Comments

jaxdagger said…
Coming back to this blog topic... Exchange 2007 SP2 will have the "plug-in" to allow Window Server Backup to perform VSS backups along with log truncation. It will allow you to restore over existing databases and to a recovery storage group as well.
November 11, 2009 at 6:03 PM
Post a Comment

Popular posts from this blog

Robocopy Error 31 A device attached to the system is not functioning

I was migrating Windows file shares to NetApp CIFS shares using Robocopy. I was unable to copy owner information or NTFS Security (/COPY:DATSOU) without getting this Error: ERROR 31 (0x0000001F) Copying NTFS Security to Destination Directory F:\PATH A device attached to the system is not functioning. I thought it may be the zone information on may of these files. I used the Sysintenals Streams utility to remove that information. It did not help. In the end, I was forced to copy without NTFS information (/COPY:DATU) When I viewed the properties of any share, folder, or file, the length of time to enumerate and display the permissions was exceedingly slow. I tried disabling anti-virus, etc. In the end, I had to manually re-create the permissions after the initial data copy. File ownership information was lost. UPDATE: I ran a CHKDSK /F and following a reboot this robocopy functioned fine.
Read more

"The following factors also affect the level of access for" user with excess permissions

Image
I have a user that had access to site settings, all content, etc. I double checked her access and it was read only but the permissions check tool showed a panel beneath the site permissions that showed Allow for many categories. She had full control. "The following factors also affect the level of access for" She was added as a Site Collection Administrator. I don't know who would have added her there, but someone had. If you find this type of issue, that should be the first thing you check. You can also check the Web Application User Policy in Central Admin. That's the other area I find people or groups with elevated permissions.
Read more

Unknown server tag 'AdminControls:MigrationToolPromotionTip'. in Central Admin after installing SharePoint 2013 security update KB4482464

I installed KB4482464 on my sandbox server without issue so I moved to my development farm. Following the patch, Central Admin (CA) had an error: Unknown server tag 'AdminControls:MigrationToolPromotionTip'. I noticed that the sandbox environment CA had this banner: You can now use the SharePoint Migration Tool to migrate to OneDrive and SharePoint Online. It looks like that failed in the Dev farm. The Configuration Wizard GUI failed to successfully run. Solution: I ran PSCONFIG with these options on my primary APP server: psconfig.exe -cmd helpcollections -installall -cmd secureresources -cmd services -install -cmd installfeatures -cmd applicationcontent -install -cmd upgrade -inplace b2b -force -wait I ran PSCONFIG with these options on my remaining app, search and WFE servers: psconfig.exe -cmd upgrade -inplace b2b -wait -force I will exclude this update from my deployment on SCCM and run it manually.
Read more