Skip to main content
Start a Conversation

Unsolved

This post is more than 5 years old

PeterBen

120 Posts

722

February 9th, 2009 02:00

how to define Exchange mailbox database backup

helo
i can backup the storage group by specifying the saveset
MSEXCH:IS/Storage Group 2

anyway i want to split the backup to maibox databases which is supported according the documentation

but if i specify it like this
MSEXCH:IS/Storage Group 2/SG2-Mbx 1
MSEXCH:IS/Storage Group 2/SG2-Mbx 2
MSEXCH:IS/Storage Group 2/SG2-Mbx 3
MSEXCH:IS/Storage Group 2/SG2-Mbx 4

i receive
..exited with return code 5.

the mailbox databases names are the same that are displayed in the networker user for exchange server when trying to backup manually via gui.

any idea how the mailbox database save set should be entered?

PeterBen

120 Posts

February 9th, 2009 04:00

i will answer myself

it has to be like MSEXCH:IS/Storage Group 2/SG2-Mbx 1 (virtual server name)

DeaconZ28-2015

252 Posts

February 9th, 2009 06:00

Thanks for the info.

But I must ask, as an Exchange and Networker admin myself, why would you want to break it out that far?

I have found that I get the best Exchange I/O performance by only having MAX 2 databases per storage group per LUN (each set of logs also on separate LUN).

I'm backing up about 250GB in one hour just using MSEXCH:IS saveset.

Are you trying to achieve more parallel streams to your backup media?

What is the performance difference between doing it your way and the just using MSEXCH:IS?

amediratta

2 Intern

 • 

2K Posts

February 9th, 2009 10:00

Mailbox backup save set is set using MSEXCH:MB. You can use MSEXCH:MB/Mailbox1, MSEXCH:MB/Mailbox2 etc if you want to. Apart from that you need a user with sufficient priviledges on the mailboxes to take the mailbox level backup. The client side Remote Execution services need to be started by that user. IF Exchange 2007, backup command also changes to nsrmbxchsv. Admin guide would have more details.

amediratta

2 Intern

 • 

2K Posts

February 9th, 2009 10:00

I have observed a great performance difference between backing up using MSEXCH:IS or MSEXCH:IS/IS1, MSEXCH:IS/IS2 etc.

When you mention multiple IS by there names, you get more parallel streams of data coming in and get faster performance. When I did this into 4 save sets, my backup window of 8-10 hours reduced to around 4 hours. Parallel data streams definetely improve performance.

ble1

4 Operator

 • 

14.3K Posts

February 10th, 2009 06:00

They do improve performance of backup at expanse of restore performance. Ask yourself what is more important.

PeterBen

120 Posts

February 11th, 2009 00:00

i am doing it for several reasons:
1. if you specify only MSEXCH:IS and you have multiple storage groups you are not able to see the backup status in the console after the first (MSEXCH:IS which is the first storage group in fact so it is misleading info in the database then) SG completes. you will see in the console only "contacting client" while the backup will be running ok. if you have the environment managed by multiple persons it leads to nothing good...

2. if you have problems with an exchange backup (as i have now) it will allow you to isolate the problem to a specific mailbox database (at least i hope so. we will see)

3. you will get more successfull backups because if it is defined only as a whole SG and it fails at some point you will not be able to restore any other mailbox database

Was this post helpful?

View All

Top