Hi,

        It should be fine to run the parallel backup on different databases
that are not on the same LUN/volumes.
        For your problem, RC 418 means TSM API error, please check
dsmerror.log under baclient directory to see if there is any error
messages. Also you can contact support for help.

Best regards.
Tian Miao Liu


"ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU> wrote on 04/27/2016
08:58:20 AM:

> From: "Schaub, Steve" <Steve_Schaub AT BCBST DOT COM>
> To: ADSM-L AT VM.MARIST DOT EDU
> Date: 04/27/2016 09:01 AM
> Subject: [ADSM-L] How to backup Exchange full using multiple
> concurrent sessions
> Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
>
> TDP 6.4.1, moving to 7.1.4 very soon.
>
> We are having some single-stream throughput issues and while I wait
> for that resolution, I need to find a way to shrink my full Exchange
> database backup runtimes.
> So far, I have not found anything easy built in, for example the "/
> stripes=x" parm I can use for SQL Server.
> Barring that, testing scripting logic to run multiple concurrent
> databases has been problematic.
>
> I keep seeing this error, making me think the CAD is somehow
> limiting me from running multiple command line specific backups of
> different databases?
> Both CAD and the Remote Client Agent are installed & running.
>
> "ANS2619S The Client Acceptor Daemon was unable to start the Remote
> Client Agent."
>
> Using this command in powershell:
> & .\TDPEXCC BACKUP $myDatabase FULL /SkipIntegrityCheck /
> DAGNode=EXCHANGE2010 /BackupMethod=VSS /BackupDestination=TSM /
> LogFile=$myTsmSchedLog
>
> Looks like the first one in works, the one that tries to run next
> gets a rc=418
>
> What am I missing?
>
> Steve Schaub
> Systems Engineer II, Backup/Recovery
> Blue Cross Blue Shield of Tennessee
> 423-535-6574 (desk)
> 423-785-7347 (cell)
>
>
>
------------------------------------------------------------------------------

> Please see the following link for the BlueCross BlueShield of
> Tennessee E-mail disclaimer:  http://www.bcbst.com/email_disclaimer.shtm
>