ADSM-L

[ADSM-L] Exchange Backup return codes

2014-09-18 07:37:46
Subject: [ADSM-L] Exchange Backup return codes
From: Steven Harris <steve AT STEVENHARRIS DOT INFO>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Thu, 18 Sep 2014 21:35:31 +1000
Hi All

I'm setting up TSM for exchange (7.1.0.1) with Exchange 2013.  Servers
are 6.2.6.0 on AIX 7.1

I have 2 DAGs, 8 databases per DAG and each DAG is comprised of two
windows boxes.

I thought I'd use the new facilities so I run

tdpexcc backup * full /preferdagpassive /minimumbackupinterval=60

And do this 30 minutes apart on each of the nodes in the DAG.

The issue is that I get RC 418 or 1848 (that may be wrong I'm sending
this from home) because a database is excluded from backup by either
the /preferdagpassive or /minimumbackupinterval switches.  This
indicates an error where I think it should not, since I asked for this
behaviour.

As batch commands are quite difficult to program, I looked at the
powershell versions of the backup command.  If I read it right you'll
get an array of error objects for any errors encountered, but you'd
have to process the whole array to see which were real errors and
which were not. Powershell is not yet a strength.

Has anyone come up with a solution they'd be willing to share? Any ideas?

While I have your attention, there are two more issues.

I'd like to backup different databases on different days,
programmatically determined, so I can run the same script and have it
produce different results.  In order to do that I would need to
interrogate exchange and filter on mailbox name, since the dbname
supplied to the backup command is either * or something specific, not
accpting wildcards. Any pointers on what I have to do within powershell
to access the exchange cmdlets?

Finally,  I'd like to turn on client compression.  The manual says to
do this  at the VSS provider, i.e. the windows BA client node.  It
does not seem to be working for me.  I'd also like to have
include.compression statements that are specific to exchange so that
normal OS files are not compressed, and there is not a lot of guidance
on that. Has anyone cracked that problem?

Thanks

Steve

Steven Harris
TSM Admin
Canberra Australia

<Prev in Thread] Current Thread [Next in Thread>