Thanks.
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Del
Hoobler
Sent: Tuesday, February 26, 2013 5:03 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] TSM TDP EXCHANGE INCREMENTAL BACKUP
If you are running with Data Protection for Exchange
If you are running with Data Protection for Exchange 6.3,
the latest is Data Protection for Exchange 6.3.1.
Here are the "requirements" for 6.3.1:
http://www-01.ibm.com/support/docview.wss?uid=swg21620061
You can also consider Data Protection for Exchange 6.4,
but it is not needed for this cu
Do you happen to know what the recommended sp level of exchange is?
And also the Recommended level of tdp?
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Del
Hoobler
Sent: Tuesday, February 26, 2013 4:18 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re
Thank you.
Will do.
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Del
Hoobler
Sent: Tuesday, February 26, 2013 4:18 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] TSM TDP EXCHANGE INCREMENTAL BACKUP
VSS_E_WRITERERROR means that the Exchang
VSS_E_WRITERERROR means that the Exchange Server is having an issue.
I recommend opening a PMR to take this to the next step.
Thanks,
Del
"ADSM: Dist Stor Manager" wrote on 02/26/2013
04:12:38 PM:
> From: Jeanne Bruno
> To: ADSM-L@vm.mari
Sorry, I meant to include the DSMerror.log.
I restarted Exchange Replication service first and then the schedule kicked
off. Still failed.
Dsmerror:
02/25/2013 15:07:21 ANS0361I DIAG: VssRequestor::checkWriterStatus:
VssRequestor::checkWriterStatus failed with hr=VSS_E_WRITERERROR_RETRYABLE
02
Hi Jeannie,
Did the problem still happen after restarting the
Microsoft Exchange Replication service?
... or are you waiting for the next schedule to run?
How about the DSMERROR.LOG file in the "baclient" directory?
What's in there? This file will have the best chance to
contain the error. Keep i
Hello. We are not using hardware for VSS.
I did a 'vssadmin list writer' and noticed there was a 'replication error', so
I restarted the Microsoft Exchange Replication service.
Vssadmis list writers showed no errors after that.
Errors from logs:
02/25/2013 15:09:01 ANS1909E The scheduled command
Hi,
we tried STA 5.5 on AIX with TSM Server 6.3.3.0 on AIX which is not working.
Minumum STA Level for TSM 6.3.3.0 Server is 6.1.
Regards,
Rainer
-Ursprüngliche Nachricht-
Von: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] Im Auftrag von
Huebner, Andy
Gesendet: Dienstag, 26. Febr
I have STA 5.4 running on a 6.2 server. Same spread on versions.
Andy Huebner
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of David
Rigaudiere
Sent: Tuesday, February 26, 2013 12:38 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] Storage Age
Jeannie,
What appears in the DSMERROR.LOG file for the
timestamps that the error occurs?
Also, does the Event Log show anything?
Thanks,
Del
"ADSM: Dist Stor Manager" wrote on 02/26/2013
01:17:00 PM:
> From: Jeanne Bruno
> To: ADSM-L@v
STA should be at same level as server.
Le 26 févr. 2013 à 19:31, Robert Ouzen a écrit :
> Hi to all
>
> Anybody now if Storage agent version 5.5.2 is working against a TSM server
> of 6.3.3.100 or needed a Storage agent of version 6+
>
> Regards Robert
Hi to all
Anybody now if Storage agent version 5.5.2 is working against a TSM server of
6.3.3.100 or needed a Storage agent of version 6+
Regards Robert
have you checked the dsierror.log for any hints? and... are all relevant VSS
services enabled (manual)? If you're using hardware based VSS snapshots, do you
actually have room on the box for the snapshot?
On 26 feb. 2013, at 19:17, Jeanne Bruno wrote:
> Hello. We are having a problem in doing
Hello. We are having a problem in doing incrementals backups on our TDP
Exchange server.
The TSM schedule kicks off the backup fine, but it fails with a snapshot
operation error.
We are using TDP v 6.3.0
And this is the command we are using in the excincr.cmd file:
tdpexcc backup * incr /EXCLUDE
Backing up livedump logical volume ..
dd read error: I/O error
Clean up on failed backup image from TSM server X successful.
FAILURE: System backup failed to complete.
Thanks in Advance!
+--
|This was sent by satish.vergh...
Thanks Guys!! It was very helpful.
+--
|This was sent by satish.vergh...@gmail.com via Backup Central.
|Forward SPAM to ab...@backupcentral.com.
+--
17 matches
Mail list logo