Backup Central

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
should be sent to stan < at > temple.edu

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.=20


-=3D-=3D-=3D
Jeffrey Leiss
Senior Infrastructure Analyst - ACS
jeff.leiss < at > nwdc.net
503.466.6540
=20

-----Original Message-----
From: Legato NetWorker discussion [mailto:NETWORKER < at > LISTMAIL.TEMPLE.EDU]
On Behalf Of Brian O'Neill
Sent: Wednesday, January 05, 2005 1:42 PM
To: NETWORKER < at > LISTMAIL.TEMPLE.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
view and post messages to the list. Questions regarding this list should
be sent to stan < at > temple.edu
=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D=
*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D

Note: To sign off this list, send a "signoff networker" command via email
should be sent to stan < at > temple.edu
=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D

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.net
503.466.6540


-----Original Message-----
From: Legato NetWorker discussion [mailto:NETWORKER < at > LISTMAIL.TEMPLE.EDU]
On Behalf Of Brian O'Neill
Sent: Wednesday, January 05, 2005 1:42 PM
To: NETWORKER < at > LISTMAIL.TEMPLE.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
view and post messages to the list. Questions regarding this list should
be sent to stan < at > temple.edu





Note: To sign off this list, send a "signoff networker" command via email
should be sent to stan < at > temple.edu

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:=20

and i concur with jeffrey that the license is per physical box

michael brooks ........... michaelb < at > sequoiains.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.EDU]
On Behalf Of Brian O'Neill
Sent: Wednesday, January 05, 2005 2:52 PM
To: NETWORKER < at > LISTMAIL.TEMPLE.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=20
that server is unimportant. If you want to backup all of Exchange,
MSEXCH: is sufficient, and nsrxchsv.exe needs to be added to the=20
backup command field under the remote tab in the settings of the
client.


-=3D-=3D-=3D
Jeffrey Leiss
Senior Infrastructure Analyst - ACS
jeff.leiss < at > nwdc.net
503.466.6540


-----Original Message-----
From: Legato NetWorker discussion=20
[mailto:NETWORKER < at > LISTMAIL.TEMPLE.EDU]
On Behalf Of Brian O'Neill
Sent: Wednesday, January 05, 2005 1:42 PM
To: NETWORKER < at > LISTMAIL.TEMPLE.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=20
Networker server. After reading the Exchange Module docs, I understand

that I need to create two "clients" for each. Will this count as 2=20
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=20
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=20
view and post messages to the list. Questions regarding this list=20
should be sent to stan < at > temple.edu=20
=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D=
*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D

Note: To sign off this list, send a "signoff networker" command via
view and post messages to the list. Questions regarding this list should
be sent to stan < at > temple.edu
=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D=
*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D

Note: To sign off this list, send a "signoff networker" command via email
should be sent to stan < at > temple.edu
=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D

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.EDU]On Behalf Of Michael Brooks
Sent: Thursday, January 06, 2005 7:11 AM
To: NETWORKER < at > LISTMAIL.TEMPLE.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.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.EDU]
On Behalf Of Brian O'Neill
Sent: Wednesday, January 05, 2005 2:52 PM
To: NETWORKER < at > LISTMAIL.TEMPLE.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.net
503.466.6540


-----Original Message-----
From: Legato NetWorker discussion
[mailto:NETWORKER < at > LISTMAIL.TEMPLE.EDU]
On Behalf Of Brian O'Neill
Sent: Wednesday, January 05, 2005 1:42 PM
To: NETWORKER < at > LISTMAIL.TEMPLE.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
view and post messages to the list. Questions regarding this list
should be sent to stan < at > temple.edu





Note: To sign off this list, send a "signoff networker" command via
view and post messages to the list. Questions regarding this list should
be sent to stan < at > temple.edu

Note: To sign off this list, send a "signoff networker" command via email
should be sent to stan < at > temple.edu

Note: To sign off this list, send a "signoff networker" command via email
should be sent to stan < at > temple.edu

Yes, thanks...this is much clearer now. I'm discussing with the client
how they intend to do the restores. I tested the MB backup - it was
attrociously slow.

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.EDU]On Behalf Of Michael Brooks
Sent: Thursday, January 06, 2005 7:11 AM
To: NETWORKER < at > LISTMAIL.TEMPLE.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.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.EDU]
On Behalf Of Brian O'Neill
Sent: Wednesday, January 05, 2005 2:52 PM
To: NETWORKER < at > LISTMAIL.TEMPLE.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.net
503.466.6540


-----Original Message-----
From: Legato NetWorker discussion
[mailto:NETWORKER < at > LISTMAIL.TEMPLE.EDU]
On Behalf Of Brian O'Neill
Sent: Wednesday, January 05, 2005 1:42 PM
To: NETWORKER < at > LISTMAIL.TEMPLE.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
view and post messages to the list. Questions regarding this list
should be sent to stan < at > temple.edu






--
Note: To sign off this list, send a "signoff networker" command via
view and post messages to the list. Questions regarding this list should
be sent to stan < at > temple.edu

--
Note: To sign off this list, send a "signoff networker" command via email
should be sent to stan < at > temple.edu

--
Note: To sign off this list, send a "signoff networker" command via email
should be sent to stan < at > temple.edu

Note: To sign off this list, send a "signoff networker" command via email
should be sent to stan < at > temple.edu

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.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.EDU]
On Behalf Of Brian O'Neill
Sent: Thursday, January 06, 2005 1:36 PM
To: NETWORKER < at > LISTMAIL.TEMPLE.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=20
of everything in the Exchange Server. Or MSEXCH: by itself will do=20
the same operation. This will allow disaster recovery (i.e. disk=20
crash). To recover individual items, this will allow you to recover=20
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=20
may opt to enable MSEXCH:MB or MSEXCH:PF backups. These will save the

same information over again, in a different format, such that=20
individual messages etc may be recovered without recovering the entire

database. The industry standard term for this is a brick-level=20
backup. This is a slower and more cumbersone operation, and would be=20
useless for disaster recovery, but is quite useful if you're often=20
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=20
and have the resources. As others have noted, no additional licenses=20
are required for this.

Hope that this helps,
_Scott

-----Original Message-----
From: Legato NetWorker discussion
[mailto:NETWORKER < at > LISTMAIL.TEMPLE.EDU]On Behalf Of Michael Brooks
Sent: Thursday, January 06, 2005 7:11 AM
To: NETWORKER < at > LISTMAIL.TEMPLE.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=20
saveset is MSEXCH:MB, for database MSEXCH:

and i concur with jeffrey that the license is per physical box

michael brooks ........... michaelb < at > sequoiains.com Network=20
Administrator .... 831.657.4539 (phone) Sequoia Insurance ........=20
831.657.4512 (fax)

"Flying is learning how to throw yourself at the ground and miss"

-----Original Message-----
From: Legato NetWorker discussion=20
[mailto:NETWORKER < at > LISTMAIL.TEMPLE.EDU]
On Behalf Of Brian O'Neill
Sent: Wednesday, January 05, 2005 2:52 PM
To: NETWORKER < at > LISTMAIL.TEMPLE.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.=20
Elsewhere it seems to imply MSEXCH:IS is what I want. Instead, it=20
seems that I really want MSEXCH:, MSEXCH:MB, and MSEXCH:PF. Is this=20
true? Why would I NOT want to back up some parts, unless it was to=20
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=20
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=20
that server is unimportant. If you want to backup all of Exchange,
MSEXCH: is sufficient, and nsrxchsv.exe needs to be added to the=20
backup command field under the remote tab in the settings of the

client.


-=3D-=3D-=3D
Jeffrey Leiss
Senior Infrastructure Analyst - ACS
jeff.leiss < at > nwdc.net
503.466.6540


-----Original Message-----
From: Legato NetWorker discussion
[mailto:NETWORKER < at > LISTMAIL.TEMPLE.EDU]
On Behalf Of Brian O'Neill
Sent: Wednesday, January 05, 2005 1:42 PM
To: NETWORKER < at > LISTMAIL.TEMPLE.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=20
Networker server. After reading the Exchange Module docs, I understand


that I need to create two "clients" for each. Will this count as 2=20
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=20
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=20
view and post messages to the list. Questions regarding this list=20
should be sent to stan < at > temple.edu=20
=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D=
*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D


--
Note: To sign off this list, send a "signoff networker" command via=20
view and post messages to the list. Questions regarding this list=20
should be sent to stan < at > temple.edu=20
=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D=
*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D

--
Note: To sign off this list, send a "signoff networker" command via=20
view and post messages to the list. Questions regarding this list=20
should be sent to stan < at > temple.edu=20
=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D=
*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D

--
Note: To sign off this list, send a "signoff networker" command via=20
view and post messages to the list. Questions regarding this list=20
should be sent to stan < at > temple.edu=20
=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D=
*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D

Note: To sign off this list, send a "signoff networker" command via
view and post messages to the list. Questions regarding this list should
be sent to stan < at > temple.edu
=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D=
*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D

Note: To sign off this list, send a "signoff networker" command via email
should be sent to stan < at > temple.edu
=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D

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.EDU] On
Behalf Of Michael Brooks
Sent: Friday, 7 January 2005 10:50 a.m.
To: NETWORKER < at > LISTMAIL.TEMPLE.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.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.EDU]
On Behalf Of Brian O'Neill
Sent: Thursday, January 06, 2005 1:36 PM
To: NETWORKER < at > LISTMAIL.TEMPLE.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.EDU]On Behalf Of Michael Brooks
Sent: Thursday, January 06, 2005 7:11 AM
To: NETWORKER < at > LISTMAIL.TEMPLE.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.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.EDU]
On Behalf Of Brian O'Neill
Sent: Wednesday, January 05, 2005 2:52 PM
To: NETWORKER < at > LISTMAIL.TEMPLE.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.net
503.466.6540


-----Original Message-----
From: Legato NetWorker discussion
[mailto:NETWORKER < at > LISTMAIL.TEMPLE.EDU]
On Behalf Of Brian O'Neill
Sent: Wednesday, January 05, 2005 1:42 PM
To: NETWORKER < at > LISTMAIL.TEMPLE.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
view and post messages to the list. Questions regarding this list
should be sent to stan < at > temple.edu






--
Note: To sign off this list, send a "signoff networker" command via
view and post messages to the list. Questions regarding this list
should be sent to stan < at > temple.edu

--
Note: To sign off this list, send a "signoff networker" command via
view and post messages to the list. Questions regarding this list
should be sent to stan < at > temple.edu

--
Note: To sign off this list, send a "signoff networker" command via
view and post messages to the list. Questions regarding this list
should be sent to stan < at > temple.edu

Note: To sign off this list, send a "signoff networker" command via
view and post messages to the list. Questions regarding this list should
be sent to stan < at > temple.edu

Note: To sign off this list, send a "signoff networker" command via email
should be sent to stan < at > temple.edu

Note: To sign off this list, send a "signoff networker" command via email
should be sent to stan < at > temple.edu

Hello Scott - I thank you also for the explanations.

Regarding the so called brick-level backups using MSEXCH:MB (for all) or
MSEXCH:MB/Username or MSEXCH:MB (then specifying the mailboxes in an
input file). We have been struggling with this on a Windows
2000/Exchange Cluster and I logged a call with Legato support.

One answer from Legato support was that if you were running Windows
2003/Exchange, then you don't need to perform the MSEXCH:MB option at
all. Going through some steps for the restores you'll be able to perform
individual mailbox restores after backing up the MSEXCH:IS saveset.

As we are, just today, turning on a Windows 2003/Exchange cluster to
migrate to, I would like verification that we will indeed be able to do
individual mailboxes from the MSEXCH:IS saveset. We'll be testing this
tomorrow with some throw away test mailboxes.

Thanks again,
Randy



-----Original Message-----
From: Legato NetWorker discussion
[mailto:NETWORKER < at > LISTMAIL.TEMPLE.EDU]
On Behalf Of Scott Bingham
Sent: Thursday, January 06, 2005 1:59 PM
To: NETWORKER < at > LISTMAIL.TEMPLE.EDU
Subject: Re: [Networker] Backing up Exchange...

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.EDU]On Behalf Of Michael Brooks
Sent: Thursday, January 06, 2005 7:11 AM
To: NETWORKER < at > LISTMAIL.TEMPLE.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.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.EDU]
On Behalf Of Brian O'Neill
Sent: Wednesday, January 05, 2005 2:52 PM
To: NETWORKER < at > LISTMAIL.TEMPLE.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.net
503.466.6540


-----Original Message-----
From: Legato NetWorker discussion
[mailto:NETWORKER < at > LISTMAIL.TEMPLE.EDU]
On Behalf Of Brian O'Neill
Sent: Wednesday, January 05, 2005 1:42 PM
To: NETWORKER < at > LISTMAIL.TEMPLE.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
at
also
view and post messages to the list. Questions regarding this list
should be sent to stan < at > temple.edu





--
Note: To sign off this list, send a "signoff networker" command via
view and post messages to the list. Questions regarding this list
should
be sent to stan < at > temple.edu

--
Note: To sign off this list, send a "signoff networker" command via
email
should be sent to stan < at > temple.edu

--
Note: To sign off this list, send a "signoff networker" command via
email
should be sent to stan < at > temple.edu

Note: To sign off this list, send a "signoff networker" command via email
should be sent to stan < at > temple.edu

You will have to restore the database to a seperate server in a seperate
Exchange Org but, yes you can get back individual mailboxes. You need =
to
read the Microsoft Exchange Disaster Recovery whitepapers.

-----Original Message-----
From: Legato NetWorker discussion
[mailto:NETWORKER < at > LISTMAIL.TEMPLE.EDU]On Behalf Of Randy Doering
Sent: Thursday, January 06, 2005 5:56 PM
To: NETWORKER < at > LISTMAIL.TEMPLE.EDU
Subject: Re: [Networker] Backing up Exchange...


Hello Scott - I thank you also for the explanations.

Regarding the so called brick-level backups using MSEXCH:MB (for all) or
MSEXCH:MB/Username or MSEXCH:MB (then specifying the mailboxes in an
input file). We have been struggling with this on a Windows
2000/Exchange Cluster and I logged a call with Legato support.

One answer from Legato support was that if you were running Windows
2003/Exchange, then you don't need to perform the MSEXCH:MB option at
all. Going through some steps for the restores you'll be able to perform
individual mailbox restores after backing up the MSEXCH:IS saveset.

As we are, just today, turning on a Windows 2003/Exchange cluster to
migrate to, I would like verification that we will indeed be able to do
individual mailboxes from the MSEXCH:IS saveset. We'll be testing this
tomorrow with some throw away test mailboxes.

Thanks again,
Randy



-----Original Message-----
From: Legato NetWorker discussion
[mailto:NETWORKER < at > LISTMAIL.TEMPLE.EDU]
On Behalf Of Scott Bingham
Sent: Thursday, January 06, 2005 1:59 PM
To: NETWORKER < at > LISTMAIL.TEMPLE.EDU
Subject: Re: [Networker] Backing up Exchange...

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.EDU]On Behalf Of Michael Brooks
Sent: Thursday, January 06, 2005 7:11 AM
To: NETWORKER < at > LISTMAIL.TEMPLE.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.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.EDU]
On Behalf Of Brian O'Neill
Sent: Wednesday, January 05, 2005 2:52 PM
To: NETWORKER < at > LISTMAIL.TEMPLE.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.


-=3D-=3D-=3D
Jeffrey Leiss
Senior Infrastructure Analyst - ACS
jeff.leiss < at > nwdc.net
503.466.6540


-----Original Message-----
From: Legato NetWorker discussion
[mailto:NETWORKER < at > LISTMAIL.TEMPLE.EDU]
On Behalf Of Brian O'Neill
Sent: Wednesday, January 05, 2005 1:42 PM
To: NETWORKER < at > LISTMAIL.TEMPLE.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
at
also
view and post messages to the list. Questions regarding this list
should be sent to stan < at > temple.edu
=
=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D=
*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D

--
Note: To sign off this list, send a "signoff networker" command via
view and post messages to the list. Questions regarding this list
should
be sent to stan < at > temple.edu
=
=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D=
*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D

--
Note: To sign off this list, send a "signoff networker" command via
email
should be sent to stan < at > temple.edu
=
=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D=
*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D

--
Note: To sign off this list, send a "signoff networker" command via
email
should be sent to stan < at > temple.edu
=
=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D=
*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D

Note: To sign off this list, send a "signoff networker" command via =
email
should be sent to stan < at > temple.edu
=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D=
*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D

Note: To sign off this list, send a "signoff networker" command via email
should be sent to stan < at > temple.edu
=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D

Hello Randy,

With Exchange 2003, you will be able to use the RSG (Recovery Storage Group)
instead of needing a separate server. RSGs are like a little recovery
sandbox within the production server.

You will still need to recover the entire database to do this, then use
Microsoft's ExMerge utility to copy from the RSG to your user's mailbox.
The MB backups would allow you to recover items directly to the users's
mailbox without going through the RSG/ExMerge steps. Thus MB backups do
still add value, for those who prefer that option.

Most experienced Exchange Admins prefer not to do brick-level backups. Some
perform MB backups only on senior managament mailboxes, etc.

Thanks,
_Scott

-----Original Message-----
From: Legato NetWorker discussion
[mailto:NETWORKER < at > LISTMAIL.TEMPLE.EDU]On Behalf Of Narkinsky, Brian
Sent: Thursday, January 06, 2005 3:00 PM
To: NETWORKER < at > LISTMAIL.TEMPLE.EDU
Subject: Re: [Networker] Backing up Exchange...


You will have to restore the database to a seperate server in a seperate
Exchange Org but, yes you can get back individual mailboxes. You need to
read the Microsoft Exchange Disaster Recovery whitepapers.

-----Original Message-----
From: Legato NetWorker discussion
[mailto:NETWORKER < at > LISTMAIL.TEMPLE.EDU]On Behalf Of Randy Doering
Sent: Thursday, January 06, 2005 5:56 PM
To: NETWORKER < at > LISTMAIL.TEMPLE.EDU
Subject: Re: [Networker] Backing up Exchange...


Hello Scott - I thank you also for the explanations.

Regarding the so called brick-level backups using MSEXCH:MB (for all) or
MSEXCH:MB/Username or MSEXCH:MB (then specifying the mailboxes in an
input file). We have been struggling with this on a Windows
2000/Exchange Cluster and I logged a call with Legato support.

One answer from Legato support was that if you were running Windows
2003/Exchange, then you don't need to perform the MSEXCH:MB option at
all. Going through some steps for the restores you'll be able to perform
individual mailbox restores after backing up the MSEXCH:IS saveset.

As we are, just today, turning on a Windows 2003/Exchange cluster to
migrate to, I would like verification that we will indeed be able to do
individual mailboxes from the MSEXCH:IS saveset. We'll be testing this
tomorrow with some throw away test mailboxes.

Thanks again,
Randy



-----Original Message-----
From: Legato NetWorker discussion
[mailto:NETWORKER < at > LISTMAIL.TEMPLE.EDU]
On Behalf Of Scott Bingham
Sent: Thursday, January 06, 2005 1:59 PM
To: NETWORKER < at > LISTMAIL.TEMPLE.EDU
Subject: Re: [Networker] Backing up Exchange...

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.EDU]On Behalf Of Michael Brooks
Sent: Thursday, January 06, 2005 7:11 AM
To: NETWORKER < at > LISTMAIL.TEMPLE.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.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.EDU]
On Behalf Of Brian O'Neill
Sent: Wednesday, January 05, 2005 2:52 PM
To: NETWORKER < at > LISTMAIL.TEMPLE.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.net
503.466.6540


-----Original Message-----
From: Legato NetWorker discussion
[mailto:NETWORKER < at > LISTMAIL.TEMPLE.EDU]
On Behalf Of Brian O'Neill
Sent: Wednesday, January 05, 2005 1:42 PM
To: NETWORKER < at > LISTMAIL.TEMPLE.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
at
also
view and post messages to the list. Questions regarding this list
should be sent to stan < at > temple.edu





--
Note: To sign off this list, send a "signoff networker" command via
view and post messages to the list. Questions regarding this list
should
be sent to stan < at > temple.edu

--
Note: To sign off this list, send a "signoff networker" command via
email
should be sent to stan < at > temple.edu

--
Note: To sign off this list, send a "signoff networker" command via
email
should be sent to stan < at > temple.edu

Note: To sign off this list, send a "signoff networker" command via email
should be sent to stan < at > temple.edu

Note: To sign off this list, send a "signoff networker" command via email
should be sent to stan < at > temple.edu

Note: To sign off this list, send a "signoff networker" command via email
should be sent to stan < at > temple.edu

Michael Brooks wrote:
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:


This is true, IF you wish to backup at mailbox level, although this is
not necessarily the case. Backing up MSEXCH: still backs up everything,
and allows you to restore the whole Exchange database. If you choose to
backup mailboxes as well you will be backing up everything twice, but
will then be able to restore a single mailbox if necessary. Backing up
MSEXCH:MB will take a LONG time on a large system, much much longer than
just MSEXCH:. The reason for this is that the backup uses the Microsoft
API which is slow and inefficient for the reason that in order to backup
a mailbox it first needs to export it to a PST file which is then backed
up. Many admins choose to backup only a selected number of mailboxes
this way, perhaps high profile users.

Note: To sign off this list, send a "signoff networker" command via email
should be sent to stan < at > temple.edu

Many admins choose to backup only a selected number of mailboxes this
way, perhaps high profile users.

this is interesting and many have said this. do you need several clients
to accomplish this? or do you just define many savesets w/in a client
w/another syntax? MSEXCH:<mailbox> for instance?


michael brooks ........... michaelb < at > sequoiains.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: Davina Treiber [mailto:Treiber < at > hotpop.com]=20
Sent: Friday, January 07, 2005 2:44 AM
To: Legato NetWorker discussion; Michael Brooks
Subject: Re: [Networker] Backing up Exchange...

Michael Brooks wrote:
it is my understanding that you need two clients -- one for individual

mailboxes, and one for database (IS). for individual mailboxes, the=20
saveset is MSEXCH:MB, for database MSEXCH:
=20

This is true, IF you wish to backup at mailbox level, although this is
not necessarily the case. Backing up MSEXCH: still backs up everything,
and allows you to restore the whole Exchange database. If you choose to
backup mailboxes as well you will be backing up everything twice, but
will then be able to restore a single mailbox if necessary. Backing up
MSEXCH:MB will take a LONG time on a large system, much much longer than
just MSEXCH:. The reason for this is that the backup uses the Microsoft
API which is slow and inefficient for the reason that in order to backup
a mailbox it first needs to export it to a PST file which is then backed
up. Many admins choose to backup only a selected number of mailboxes
this way, perhaps high profile users.

Note: To sign off this list, send a "signoff networker" command via email
should be sent to stan < at > temple.edu
=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D

Hello Michael,

Here is an example of the syntax:

MSEXCH:MB/Michael Brooks/
MSEXCH:MB/Scott Bingham/

These can be put as saveset names into one client entry, or can be managed
through an Input File.

Thanks,
_Scott

-----Original Message-----
From: Legato NetWorker discussion
[mailto:NETWORKER < at > LISTMAIL.TEMPLE.EDU]On Behalf Of Michael Brooks
Sent: Friday, January 07, 2005 7:30 AM
To: NETWORKER < at > LISTMAIL.TEMPLE.EDU
Subject: Re: [Networker] Backing up Exchange...


Many admins choose to backup only a selected number of mailboxes this
way, perhaps high profile users.

this is interesting and many have said this. do you need several clients
to accomplish this? or do you just define many savesets w/in a client
w/another syntax? MSEXCH:<mailbox> for instance?


michael brooks ........... michaelb < at > sequoiains.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: Davina Treiber [mailto:Treiber < at > hotpop.com]
Sent: Friday, January 07, 2005 2:44 AM
To: Legato NetWorker discussion; Michael Brooks
Subject: Re: [Networker] Backing up Exchange...

Michael Brooks wrote:
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:


This is true, IF you wish to backup at mailbox level, although this is
not necessarily the case. Backing up MSEXCH: still backs up everything,
and allows you to restore the whole Exchange database. If you choose to
backup mailboxes as well you will be backing up everything twice, but
will then be able to restore a single mailbox if necessary. Backing up
MSEXCH:MB will take a LONG time on a large system, much much longer than
just MSEXCH:. The reason for this is that the backup uses the Microsoft
API which is slow and inefficient for the reason that in order to backup
a mailbox it first needs to export it to a PST file which is then backed
up. Many admins choose to backup only a selected number of mailboxes
this way, perhaps high profile users.

Note: To sign off this list, send a "signoff networker" command via email
should be sent to stan < at > temple.edu

Note: To sign off this list, send a "signoff networker" command via email
should be sent to stan < at > temple.edu