Michael
The MSEXCH:MB backs up the mailboxes.
The MSEXCH:PF backs up the pubic folders
The NetWorker admin guide for Exchange explains the operations well.
Regards
Richard
-----Original Message-----
From: Legato NetWorker discussion [mailto:NETWORKER AT LISTMAIL.TEMPLE DOT EDU]
On
Behalf Of Michael Brooks
Sent: Friday, 7 January 2005 10:50 a.m.
To: NETWORKER AT LISTMAIL.TEMPLE DOT EDU
Subject: Re: [Networker] Backing up Exchange...
scott- i agree that the MSEXCH:MB saveset saves the same info, but in a
more granular fashion. what does the MSEXCH:PF saveset imply? how is it
different than MSEXCH:MB?
michael brooks ........... michaelb AT sequoiains DOT com
Network Administrator .... 831.657.4539 (phone)
Sequoia Insurance ........ 831.657.4512 (fax)
"Flying is learning how to throw yourself at the ground and miss"
-----Original Message-----
From: Legato NetWorker discussion [mailto:NETWORKER AT LISTMAIL.TEMPLE DOT EDU]
On Behalf Of Brian O'Neill
Sent: Thursday, January 06, 2005 1:36 PM
To: NETWORKER AT LISTMAIL.TEMPLE DOT EDU
Subject: Re: [Networker] Backing up Exchange...
Scott Bingham wrote:
> Hello Brian et al,
>
> The essential saveset is MSEXCH:IS -- this will do a database backup
> of everything in the Exchange Server. Or MSEXCH: by itself will do
> the same operation. This will allow disaster recovery (i.e. disk
> crash). To recover individual items, this will allow you to recover
> databases to the RSG via Microsoft mechanisms, or to recover to a
scratch server.
>
> If you wish for an easier way to do individual item recoveries, you
> may opt to enable MSEXCH:MB or MSEXCH:PF backups. These will save the
> same information over again, in a different format, such that
> individual messages etc may be recovered without recovering the entire
> database. The industry standard term for this is a brick-level
> backup. This is a slower and more cumbersone operation, and would be
> useless for disaster recovery, but is quite useful if you're often
> approached by people who have inadvertently deleted important
messages.
>
> In summary: You must always do an IS backup to protect your
environment.
> You may elect to also do MB or PF if you would like that flexibility
> and have the resources. As others have noted, no additional licenses
> are required for this.
>
> Hope that this helps,
> _Scott
>
> -----Original Message-----
> From: Legato NetWorker discussion
> [mailto:NETWORKER AT LISTMAIL.TEMPLE DOT EDU]On Behalf Of Michael Brooks
> Sent: Thursday, January 06, 2005 7:11 AM
> To: NETWORKER AT LISTMAIL.TEMPLE DOT EDU
> Subject: Re: [Networker] Backing up Exchange...
>
>
> it is my understanding that you need two clients -- one for individual
> mailboxes, and one for database (IS). for individual mailboxes, the
> saveset is MSEXCH:MB, for database MSEXCH:
>
> and i concur with jeffrey that the license is per physical box
>
> michael brooks ........... michaelb AT sequoiains DOT com Network
> Administrator .... 831.657.4539 (phone) Sequoia Insurance ........
> 831.657.4512 (fax)
>
> "Flying is learning how to throw yourself at the ground and miss"
>
> -----Original Message-----
> From: Legato NetWorker discussion
> [mailto:NETWORKER AT LISTMAIL.TEMPLE DOT EDU]
> On Behalf Of Brian O'Neill
> Sent: Wednesday, January 05, 2005 2:52 PM
> To: NETWORKER AT LISTMAIL.TEMPLE DOT EDU
> Subject: Re: [Networker] Backing up Exchange...
>
> This is where I was confused by the documentation. It implied that
> MSEXCH: did not back up private mailboxes and public folders.
> Elsewhere it seems to imply MSEXCH:IS is what I want. Instead, it
> seems that I really want MSEXCH:, MSEXCH:MB, and MSEXCH:PF. Is this
> true? Why would I NOT want to back up some parts, unless it was to
> schedule them differently?
>
> I intend on using the same basic schedule as other clients - Full once
> a month, incremental daily - with some staggering of when the fulls
> take place. Does a different schedule make sense for Exchange?
>
> Leiss, Jeffrey wrote:
>
>>You only need 1 license per server, the number of clients you have of
>>that server is unimportant. If you want to backup all of Exchange,
>>MSEXCH: is sufficient, and nsrxchsv.exe needs to be added to the
>>backup command field under the remote tab in the settings of the
>
> client.
>
>>
>>-=-=-=
>>Jeffrey Leiss
>>Senior Infrastructure Analyst - ACS
>>jeff.leiss AT nwdc DOT net
>>503.466.6540
>>
>>
>>-----Original Message-----
>>From: Legato NetWorker discussion
>>[mailto:NETWORKER AT LISTMAIL.TEMPLE DOT EDU]
>>On Behalf Of Brian O'Neill
>>Sent: Wednesday, January 05, 2005 1:42 PM
>>To: NETWORKER AT LISTMAIL.TEMPLE DOT EDU
>>Subject: [Networker] Backing up Exchange...
>>
>>Just got a few questions to pass by the experts (I was one once.. :)
>>
>>I'm backing up 4 Exchange 2003 servers as clients to my Linux
>>Networker server. After reading the Exchange Module docs, I understand
>
>
>>that I need to create two "clients" for each. Will this count as 2
>>clients against the license? Or as long as I use the same client name,
>
> is it only 1?
>
>>As for setting up the client, if I want to back up all Exchange stuff,
>
>
>>is "MSEXCH:IS" the correct saveset? Also, will "nsrxchsv" by itself
>>sufficient?
>>
>>Does the "Skip M Drive" directive still apply to Exchange 2003?
>>
>>-Brian
>>
>>--
>>Note: To sign off this list, send a "signoff networker" command via
>>email to listserv AT listmail.temple DOT edu or visit the list's Web site at
>>http://listmail.temple.edu/archives/networker.html where you can also
>>view and post messages to the list. Questions regarding this list
>>should be sent to stan AT temple DOT edu
>>=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
>>
>>
>>
>>
>
>
> --
> Note: To sign off this list, send a "signoff networker" command via
> email to listserv AT listmail.temple DOT edu or visit the list's Web site at
> http://listmail.temple.edu/archives/networker.html where you can also
> view and post messages to the list. Questions regarding this list
> should be sent to stan AT temple DOT edu
> =*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
>
> --
> Note: To sign off this list, send a "signoff networker" command via
> email to listserv AT listmail.temple DOT edu or visit the list's Web site at
> http://listmail.temple.edu/archives/networker.html where you can also
> view and post messages to the list. Questions regarding this list
> should be sent to stan AT temple DOT edu
> =*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
>
> --
> Note: To sign off this list, send a "signoff networker" command via
> email to listserv AT listmail.temple DOT edu or visit the list's Web site at
> http://listmail.temple.edu/archives/networker.html where you can also
> view and post messages to the list. Questions regarding this list
> should be sent to stan AT temple DOT edu
> =*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
--
Note: To sign off this list, send a "signoff networker" command via
email to listserv AT listmail.temple DOT edu or visit the list's Web site at
http://listmail.temple.edu/archives/networker.html where you can also
view and post messages to the list. Questions regarding this list should
be sent to stan AT temple DOT edu
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
--
Note: To sign off this list, send a "signoff networker" command via email
to listserv AT listmail.temple DOT edu or visit the list's Web site at
http://listmail.temple.edu/archives/networker.html where you can
also view and post messages to the list. Questions regarding this list
should be sent to stan AT temple DOT edu
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
--
Note: To sign off this list, send a "signoff networker" command via email
to listserv AT listmail.temple DOT edu or visit the list's Web site at
http://listmail.temple.edu/archives/networker.html where you can
also view and post messages to the list. Questions regarding this list
should be sent to stan AT temple DOT edu
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
|
