Hi Steve,

The only difference in "snapdiff backup"  than any other remote file system
backup is that up front part.  With Snapdiff, we use 2 snapshots to
determine what has changed instead of traversing the remote filesystem.
Once we get past that, it is just like any other backup.  So, options like
RESOURCEUTIL which increases the number of sessions with the server (can be
read 'threads per volume') can be used.

resourceutil
http://www.ibm.com/support/knowledgecenter/SSGSG7_7.1.3/client/r_opt_resourceutilization.html

General Performance pointers can be found here.
https://www.ibm.com/developerworks/community/wikis/home?lang=en#!/wiki/Tivoli%20Storage%20Manager/page/Optimizing%20performance%20for%20servers%20and%20clients

Frank Ramke
IBM Spectrum Protect Development

"ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU> wrote on 03/10/2016
03:17:38 PM:

> From: "Schaub, Steve" <Steve_Schaub AT BCBST DOT COM>
> To: ADSM-L AT VM.MARIST DOT EDU
> Date: 03/10/2016 03:18 PM
> Subject: Can Snapdiff be multithreaded per volume?
> Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
>
> TSM Server 6.3
> TSM Client 7.1.3
>
> Does anyone know if snapdiff backups are single or multi-threaded?
> Specifically when we periodically run the full incremental (-
> createnewbase=yes).  From what I'm seeing, it looks like it is
> single threaded, but it would help if we could somehow make each vol
> multi-thread.
>
> To be clear, we are already running multiple snapdiff backup
> commands concurrently, but we have some volumes with mult-million
> files that are taking several days when we periodically force the
> full incremental.  Looking for some way to speed things up if possible.
>
>
> 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
>