ADSM-L

Re: [ADSM-L] TDP for Exchange Failures

2014-06-10 11:21:58
Subject: Re: [ADSM-L] TDP for Exchange Failures
From: "Lepre, James" <james.lepre AT SOLIXINC DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Tue, 10 Jun 2014 15:20:06 +0000
Try resetting VSS.. 

Also Run on the exchange server  Get-MailboxDatabase -Server "ServerNAME" 
-Status |ft name,mounted,backupinprogress

If the BACKUPINPROGRESS is listed as true the exchange server needs to be 
rebooted
James Lepre
Infrastructure Support Specialist
Solix, Inc. | 30 Lanidex Plaza West | Parsippany, NJ 07054
T: 973.581.5362 | F: 973.599.6544
www.solixinc.com | Solix on Facebook | Solix on Twitter


-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of 
Leonard, Matthew
Sent: Tuesday, June 10, 2014 11:06 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] TDP for Exchange Failures

I have been working directly with the exchange admin and I'm an exchange admin 
myself and through the GUI it works fine.  It’s the scheduled backup as you 
could see the command I'm running below but it does seem to be a VSS issue 
using he scheduler.

Regards,

Matthew J. Leonard
Network Infrastructure Administrator
IT Network Operations
AtlasAir, Inc.
Matthew.Leonard AT AtlasAir DOT com
914-701-8042


-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of 
Francisco Javier
Sent: Tuesday, June 10, 2014 11:00 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] TDP for Exchange Failures

Try to make a backup with the assistance of the Exhange Admin and watch the 
actlog to check if there aren't more errors about it

regards



2014-06-10 9:54 GMT-05:00 Vandeventer, Harold [BS] <
Harold.Vandeventer AT ks DOT gov>:

> I don't know the details, but is this a VSS problem?   There is a command
> line to test that as I recall.  I don't manage our Exchange boxes, 
> just vaguely recall a command would test VSS functions.
>
> -----Original Message-----
> From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf 
> Of Francisco Javier
> Sent: Tuesday, June 10, 2014 9:38 AM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Re: [ADSM-L] TDP for Exchange Failures
>
> Since when did you saw it? Did you try to do one backup online since 
> TDP GUI, this working?
>
> Try to update the admin and doing a connection since de client dsmc 
> using the dsm.opt
>
> Regards
>
>
> 2014-06-10 6:32 GMT-05:00 Leonard, Matthew <Matthew.Leonard AT atlasair DOT 
> com>:
>
> > Hello All,
> >
> >
> >
> > I've been getting numerous failures with our Exchange Backups that 
> > are being executed via a scheduled command as shown below.  Server
> > Version: 6, Release 1, Level 4.5, TSM Client Version: 6.2.3.0, TDP
> Client Version:
> > 6.1.3.0 all running on Windows 2008 R2 and Exchange 2010 SP2 Rollup
> > 3 and we are running from a replica mailbox server with the 
> > Proxynode option set for this Mailbox server with the passive copies 
> > of the databases.  We have had no problems for years and nothing has 
> > changed besides growth but lately we have been getting tons of failures 
> > such as:
> >
> >
> >
> > Event Logs:
> >
> > Failure Executing Schedule EXCHANGE2010_4, RC=450.
> >
> > Failure Executing Schedule EXCHANGE2010_4, RC=418.
> >
> > VSS processing encountered error 'VSS_E_SNAPSHOT_SET_IN_PROGRESS' in 
> > the Volume Shadow Copy API 'StartSnapshotSet'.
> >
> >
> >
> > DSM Logs:
> >
> > ACN0519E The VSS operation failed with rc = 450.
> >
> > ANS1017E (RC-50)  Session rejected: TCP/IP connection failure
> >
> > ACN5060E A Tivoli Storage Manager API error has occurred.
> >
> >
> >
> > Again, The majority of our DB's backup but we get 3-6 failures a day 
> > and it's not the same ones every day.  One that was successful 
> > yesterday could fail tonight.  It's just very odd
> >
> >
> >
> >
> >
> > Command Running:
> >
> > tdpexcc backup " XDCExecStore1" full /BACKUPMETHOD=VSS 
> > /BACKUPDESTINATION=TSM /tsmoptfile=XDCCrewStore1.opt 
> > /logfile=C:\TSM\excsch_XDCCrewStore1.log >> 
> > C:\TSM\excfull_XDCCrewStore1.log
> >
> >
> >
> > Options File:
> >
> > NODename                        XDCExecStore1
> >
> > TCPServeraddress           sxdctsm01
> >
> > SCHEDMODE                      Prompted
> >
> > CLUSTERnode                    no
> >
> > COMPRESSIon                   no
> >
> > PASSWORDAccess           Generate
> >
> > COMMMethod                 TCPip
> >
> > TCPPort                                1500
> >
> > TCPWindowsize                63
> >
> > TCPBuffSize                        32
> >
> > COMPRESSALWAYS        no
> >
> > RESOURCEUTILIZATION     2
> >
> > ERRORLOGNAME             C:\TSM\dsmerror_XDCExecStore1.log
> >
> > SCHEDLOGNAME             C:\TSM\dsmsched_XDCExecStore1.log
> >
> > ERRORLOGRETENTION  7
> >
> > SCHEDLOGRETENTION   7
> >
> >
> >
> >
> >
> > Regards,
> >
> >
> >
> > Matthew J. Leonard
> >
> > Network Infrastructure Administrator
> >
> > IT Network Operations
> >
> > AtlasAir, Inc.
> >
> > Matthew.Leonard AT AtlasAir DOT com<mailto:Matthew.Leonard AT AtlasAir DOT 
> > com>
> >
> > 914-701-8042
> >
>
> [Confidentiality notice:]
> **********************************************************************
> * This e-mail message, including attachments, if any, is intended for 
> the person or entity to which it is addressed and may contain 
> confidential or privileged information.  Any unauthorized review, use, 
> or disclosure is prohibited.  If you are not the intended recipient, 
> please contact the sender and destroy the original message, including 
> all copies, Thank you.
> **********************************************************************
> *
>

  
  
---------------------------------------------------------------
Confidentiality Notice: The information in this e-mail and any attachments 
thereto is intended for the named recipient(s) only.  This e-mail, including 
any attachments, may contain information that is privileged and confidential  
and subject to legal restrictions and penalties regarding its unauthorized 
disclosure or other use.  If you are not the intended recipient, you are hereby 
notified that any disclosure, copying, distribution, or the taking of any 
action or inaction in reliance on the contents of this e-mail and any of its 
attachments is STRICTLY PROHIBITED.  If you have received this e-mail in error, 
please immediately notify the sender via return e-mail; delete this e-mail and 
all attachments from your e-mail  system and your computer system and network; 
and destroy any paper copies you may have in your possession. Thank you for 
your cooperation.