I use 7.1. With /PREFERDAGPASSIVE set it correctly skips the mailboxes on
the active node but the return code is 1829.
Could this safely be ignored that is if the backup command has RC=1829 I
can force the script to return with RC=0?
Another thing, should /PREFERDAGPASSIVE not be used when doing
ADSM: Dist Stor Manager ADSM-L@vm.marist.edu wrote on 04/03/2014
08:49:45 AM:
From: Hans Christian Riksheim bull...@gmail.com
To: ADSM-L@vm.marist.edu,
Date: 04/03/2014 08:50 AM
Subject: TDP for Exchange error code
Sent by: ADSM: Dist Stor Manager ADSM-L
Hi to all
I have an exchange server Windows2003 (not in cluster) with TDP version 5.2.1 I
backup it at Sunday Tuesday Thursday full (at 23:00) and between 3 times a day
incremental (at 9 , 15 , 20).
The 3 incrementals after the full are running correctly but the second day I
got the
Hi Robert,
I recommend that you check the event logs and other system logs closely.
I think that there must be something else running (like another backup
type,
or a defrag, or something else) that is causing this situation to occur.
I know that you said that the exchange admin told you that the
-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Del Hoobler
Sent: Tuesday, August 29, 2006 3:52 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] TDP for exchange error
Hi Robert,
I recommend that you check the event logs and other system logs closely.
I think that there must
Hi Robert,
We are currently investigating a problem where the Data Protection
for Exchange 5.3.3 GUI is loading the restore screen without
clearing a previous query... so you may see duplicate entries.
This should not affect the operations.
Thanks,
Del
Hi to all
I just got an error message when I backup my exchange database (two storage group) . A
the beginning of this month I implant this backup running O.K till today.
Here the error I got:
07/23/2004 10:08:47 Retrying failed backups...
07/23/2004 10:08:51 Backup of storage group First
Robert,
This means that the Exchange Server thinks that an
Exchange backup is already being run on that storage group.
That could mean one of two things:
1. A backup is actually still running on that storage group.
...or...
2. A previous backup has hung or prematurely ended.
If a
Following is the TDP Schedule log file.
We are taking a full backup of the exchange database using TDP.
You can see that the TDP full backup was successful yesterday.But today
it got failed.There was no change done to the configuration.It is a
daily scheduled job which failed today with the error
Mohan,
Try reinstalling the TSM API Runtime feature from the Version 5.1.5
(or later) TSM Backup Archive client package. If it still fails,
uninstall... then reinstall the TSM Backup Archive client and the
Data Protection for Exchange client.
Thanks,
Del
Uninstalling and installing both Backup Archive client and TDP solved
the problem.
Thanks Del!
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Del Hoobler
Sent: Tuesday, January 06, 2004 5:09 PM
To: [EMAIL PROTECTED]
Subject: Re: TDP for exchange
11 matches
Mail list logo