If you are using Windows Server Backup to backup Exchange Server 2010 then you will want to configure a scheduled back task to automate the process. However, Windows Server Backup alone may not support the schedule that you want to create.
GFI has recently released two backup products, a free one for home users and a paid product for business users. I downloaded and tested the Business Edition to see if it was as easy to install and use as they claim.
Microsoft has announced that Service Pack 2 for Exchange Server 2007 will be released in Q3 of this year. The MS Exchange Team has listed some of the key new features in their blog post here. A welcome addition is the new volume snapshot backup plugin for Windows Server 2008. Currently Exchange Server 2007 cannot […]
You may encounter an issue with Backup Exec 11d performing backups of Exchange Server 2007 Mailbox Servers using Granular Restore Technology (GRT) when the backup job is targeted at tape media. The backup job fails with the following error: Backup- \SERVER.domain.localMicrosoft Information StoreFirst Storage Group V-79-57344-33928 – Access Denied. Cannot backup directory Mailbox Database and […]
Dan lets us know that the book Enterprise Systems Backup and Recovery: A Corporate Insurance Policy written by local guru Preston De Guise is available now. The book is a platform-agnostic guide to comprehensive backup and recovery systems and should be compulsory reading for IT decision makers. In the author’s own words: Instead of […]
Exchange Server 2007 has some very useful replication features such as Local Continuous Replication (in RTM and SP1) and Standby Continuous Replication (in SP1 only). These features can provide nice and simple disaster recovery options by replicating your storage group logs and databases to another location, be it another disk/LUN with LCR or another mailbox […]
On a Symantec Backup Exec 11d server that is backing up Microsoft SQL Server databases you may encounter failed backups with an error: The path for this database is invalid because it contains extra backslash characters. You must remove the extra backslash characters before the database can be backed up. The solution provided by Symantec […]