Networker

Re: [Networker] Backing up exchange 2007 running on windows server 2008?

2008-05-14 08:46:26
Subject: Re: [Networker] Backing up exchange 2007 running on windows server 2008?
From: MIchael Leone <Michael.Leone AT PHA.PHILA DOT GOV>
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Date: Wed, 14 May 2008 08:43:35 -0400
EMC NetWorker discussion <NETWORKER AT LISTSERV.TEMPLE DOT EDU> wrote on 
05/13/2008 11:20:49 PM:

> Hello Oscar,
> 
> Windows 2008 was not yet out when NMEx 5.1 was released, so it is not
> listed as supported, but it is being qualified, and it works -- mostly.
> If you wish to do brick-level mailbox backups, you will need a new MAPI
> support library from Microsoft, that they have not yet released.  Their
> current MAPI library does not work with Windows 2008.

I know when I used BackupExec, the prevailing wisdom was that brick-level 
mailbox backup was BAD. Much better to use the Dumpster, and proper 
message retention. However, I digress ....

> 
> Thanks,
> _Scott
> 
> -----Original Message-----
> From: EMC NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU] 
> On
> Behalf Of Oscar Olsson
> Sent: Tuesday, May 13, 2008 5:36 AM
> To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
> Subject: [Networker] Backing up exchange 2007 running on windows server
> 2008?
> 
> We need to back up exchange 2007 that is running on windows server 2008.
> 
> This has been more tricky than expected.
> 
> At first we figured it should work to just run the Networker module for 
> exchange 5.1, but that didn't seem to work. In the documentation, there
> is 
> no mention about windows 2008 support. My guess is that NME isn't 
> supported on windows server 2008, is this assumption correct?
> 
> Then I started investigating if we could use NMM instead. It does seem 
> that it should work, but according to the documentation they have not 
> implemented support for any other backup levels than full yet. So if we
> do 
> daily backups of exchange this way, the amount of storage needed on the 
> networker backup system will increase. Also, I guess we need a new
> license 
> to use the NMM?
> 
> Either way, this situation feels a bit unstatisfying if my suspicions
> are 
> true. Does anyone have more experience on this subject, and/or ideas on 
> how to solve this in a better way when it comes to licensing and storage
> 
> requirements?
> 
> //Oscar
> 
> Ps. Its fun to read networker documentation sometimes.
> In the NMM docs, they say "If NetWorker NMM client is
> installed, then the NetWorker Module for Exchange Client promotes its
> own
> incremental backup to a full backup to maintain the integrity of the 
> backup and prevent data loss." . I would translate this to:
> "We were too lazy to implement support for incremental
> backups so far."
> 
> To sign off this list, send email to listserv AT listserv.temple DOT edu and
> type "signoff networker" in the body of the email. Please write to
> networker-request AT listserv.temple DOT edu if you have any problems with 
> this
> list. You can access the archives at
> http://listserv.temple.edu/archives/networker.html or
> via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER
> 
> To sign off this list, send email to listserv AT listserv.temple DOT edu 
> and type "signoff networker" in the body of the email. Please write 
> to networker-request AT listserv.temple DOT edu if you have any problems 
> with this list. You can access the archives at http://listserv.
> temple.edu/archives/networker.html or
> via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER

To sign off this list, send email to listserv AT listserv.temple DOT edu and 
type "signoff networker" in the body of the email. Please write to 
networker-request AT listserv.temple DOT edu if you have any problems with this 
list. You can access the archives at 
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER