Date: Thu, 17 Apr 2008 10:57:12 +0100
From: James Pattinson <jamesp AT hisser DOT org>
Subject: [Veritas-bu] Backup of exchange using "wrong" name
To: veritas-bu AT mailman.eng.auburn DOT edu
Message-ID: <48071EF8.5030405 AT hisser DOT org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Hi All
I'm backing up a customer's machine over a dedicated backup network with
our own naming convention, which doesn't always relate to the actual
name of the machine. This has been working OK for Filesystem and SQL
backups, but I am unable to get an exchange backup working in this way.
Example
Exchange server is called "exch"
We back it up as "cust-exch-b" and a filesystem backup works, but
exchange backup doesn't work, we get this in the bpbkar log:
10:26:37.515: [5140.964] <2> tar_backup_tfi::setupFileDirectives: TAR -
backup filename = Microsoft Information Store:\
10:26:37.530: [5140.5648] <4> tar_base::keepaliveThread: INF - keepalive
thread is active with an interval of 60 seconds
10:26:38.593: [5140.964] <2> ov_log::V_GlobalLog: INF - BEDS_Init()
Enter InitFlags:0x0
10:26:43.171: [5140.964] <2> ov_log::V_GlobalLog: INF - DumpDleInfo()
DLE Device Name: C:
10:26:43.171: [5140.964] <2> ov_log::V_GlobalLog: INF - DumpDleInfo()
DLE Device Name: D:
10:26:43.171: [5140.964] <2> ov_log::V_GlobalLog: INF - DumpDleInfo()
DLE Device Name: Microsoft Terminal Services
10:26:43.171: [5140.964] <2> ov_log::V_GlobalLog: INF - DumpDleInfo()
DLE Device Name: Microsoft Windows Network
10:26:43.171: [5140.964] <2> ov_log::V_GlobalLog: INF - DumpDleInfo()
DLE Device Name: Web Client Network
10:26:43.171: [5140.964] <2> ov_log::V_GlobalLog: INF - DumpDleInfo()
DLE Device Name: \\cust-exch-b\Microsoft Exchange Mailboxes
10:26:43.171: [5140.964] <2> ov_log::V_GlobalLog: INF - DumpDleInfo()
DLE Device Name: \\cust-exch-b\Microsoft Exchange Public Folders
10:26:43.171: [5140.964] <2> ov_log::V_GlobalLog: INF - DumpDleInfo()
DLE Device Name: Shadow?Copy?Components
10:26:43.171: [5140.964] <4> dos_backup::V_VerifyFileList: INF - unable
to determine UBS type for:Microsoft Information Store:
10:26:43.171: [5140.964] <4> dos_backup::V_VerifyFileList: INF - UBS
Local Type for 'Microsoft Information Store:\' --> 00000000
10:26:43.171: [5140.964] <4> dos_backup::V_Initialize: INF - Exchange
Backup - Disabling Open File Backups, Archive Bit processing, TIR and
Job Estimating.
10:26:43.171: [5140.964] <4> backup_create: INF - NetBackup Temp
Directory: 'D:\Program Files\Veritas\\NetBackup\Temp'
10:26:43.171: [5140.964] <2> tar_base::V_vTarMsgW: ERR - object not
found for file system backup: Microsoft Information Store:
So it looks like I'm missing a bit of configuration on the Exchange
agent to tell it to use a certain name when talking to Exchange...
Can anyone help?
Thanks!
James
------->
There are two peculiarities with MS Exchange Public Folder,
Mailbox and Information store backups that are not well documented, or
at least were not well documented in NetBackup 4.5 and 5.x. The first is
that the client name of your server in the Host Properties/Client
Properties/Client Name dialog for the Exchange server needs to be the
NetBIOS name for the server. If the NetBIOS name is not the same as the
FQDN then change it in this dialog box. In your case change the client
name to "exch". In the Host Properties/Client Properties/Universal
Settings dialog box change the "Use Specified Network Interface" to the
hostname or IP address of your backup subnet NIC.
The other thing that you need to do for Exchange backups and restores to
work properly is set the name of the mailbox for message level backups
and restores. This is set in Host Properties/Client Properties/Windows
Client/Exchange. You can also enable single instance backup for
attachments here which reduces the amount of data you back up by storing
a single instance of a message attachment and then for subsequent
mailbox backups that contain that attachment set a pointer to the
attachment. You'll have to have your local Exchange guru create this
mailbox on the Exchange server if it doesn't exist. (I'm lucky, I work
with a wicked smart Exchange/Mail/MS products guy who knew exactly what
to do as soon as he saw this dialog box.).
Another thing you can do when backing up mailboxes, and some people
might think that I'm completely insane for doing this, is use a wildcard
in your backup selections window on the policy and "allow multiple
streams". So in backup selections you might have an entry that looked
like this:
Microsoft Exchange Mailboxes:\*
Doing this causes NetBackup to spawn a separate job for each mailbox on
your Exchange server. I set this up after a couple of incidents where
NetBackup was backing up the MS-Exchange mailboxes, hit some weirdness
in one of the last mailboxes that needed to be backed up and decided to
choke, puke and fall all over itself. This caused the entire backup to
fail. Now if I have a mailbox with weirdness in it that NetBackup
doesn't like that mailbox backup fails without affecting the backups of
the other mailboxes and I can then have the Exchange guru I work with
take a look at that mailbox to find out what ails it.
I hope this helps.
Jamie Jamison
Network Systems Administrator
ZymoGenetics, Seattle WA
_______________________________________________
Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
|
