Schrooten Robin
Mar 12, 2012 8:47:14 AM

Exchange 2007 -2010 support

Is there any plan in the roadmap, to support VSS based MS Exchange backups ( by using the exchange vss writer)


Ryan
Apr 10, 2012 1:16:36 AM

Exchange 2007 -2010 support

Bump! >Is there any plan in the roadmap, to support VSS based MS Exchange backups >(by using the exchange vss writer)


yeshpal
Apr 14, 2012 7:51:58 PM

Exchange 2007 -2010 support

>Is there any plan in the roadmap, to support VSS based MS Exchange backups ( by using >the exchange vss writer)


Daniel Paton
May 2, 2012 8:44:07 PM

Exchange 2007 -2010 support

will purchase isp license as soon as i can use it to backup exchange and sql. >Is there any plan in the roadmap, to support VSS based MS Exchange backups ( by using >the exchange vss writer)


Schrooten Robin
May 31, 2012 4:23:01 AM

Exchange 2007 -2010 support

Hello, I have tested VSS for creating a backup of Exchange, but this didn't work really well. The issue is that the Exchange database files (.MDB), do not change the timestamp, until a unmount/mount of the information store. Syncrify first checks the timestamp, and doesn't notice a difference here, so it doesn't perform a copy of the IS. However, it seems to start a VSS session, but it doesn't seem to close it. If you check the VSS writers (vssadmin list writers), the writers seem to be stuck in a waiting for completion state. This can be fixed by using somthing like Windows backup, to create a full backup of the system, so the writers a correctly closed. Also, Syncrify will create a temp file localy on the Exchange server, so you really have to keep an eye on your free storage on this server, as this temp file can really grow into a large file (depending on the amount of users/mails the server handles)


Schrooten Robin
May 31, 2012 4:26:48 AM

Exchange 2007 -2010 support

Instead of using VSS, I am using powershell commands, to first export the mailbox into a PST, and afterwards copying the PST files with Syncrify. This is really efficient, as the powershell command (export-mailbox) doesn't rebuild the PST, but only adds new mails into the pst. With the latest version, we can add pre and post commands to Syncrify, so we can use some powershell scripts here. However, It would be nice to have these scripts integrated into syncrify. To help out, I found some links about how to integrate Powershell into java (as this is what syncrify is wriiten in), and something that describes the requirements for exchange 2007 and 2010. An idea might also be to have an option to first create a local PST file and have syncrify copy this afterwards, or a direct copy to a remote PST file. The advantage will be that you will not require to have local free storage available, if you select the direct copy. Links: Powershell commands in java: https blogs.oracle.com/vaibhav/entry/not_as_easy_as_we some possible requirements: http blog.tyang.org/2010/08/13/mailbox-archive-tool-for-microsoft-exchange-servers/

Navigation

Social Media

Powered by 10MinutesWeb.com