There is nothing you should need to do in regards to the
SQL Server to use multiple stripes. Data Protection for SQL
informs the SQL Server how many stripes it would like to use.
The SQL Server completely determines how the data is
fed to each striped session. Data Protection for SQL
will open a TSM API session for each stripe created,
plus one additional session for management.
You didn't mention it, so I cannot be sure, but you need
to tell Data Protection for SQL to use multiple stripes.
That is, something like this:
TDPSQLC BACKUP dbname FULL /STRIPES=3
It is probably a good idea to find out where your
maximum throughput rate is by running some backups
starting with a lower number of stripes, for example,
try 2, 3, and 4 stripes... before going to 8 stripes.
If you cannot get multiple stripes to work, please call
"ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU> wrote on 04/19/2004
> TSM server v220.127.116.11 running on IBM mainframe. OS is Z/OS 1.4
> TSM Client v18.104.22.168
> TDP version 2.2.1
> SQL Server 7.0
> I have a 20gb SQL database that takes slightly more than an hour to
> using TDP and a 200gb SQL database taking 15 hours to backup using TDP.
> I am considering using striping. I have read the redbook and the TSM/SQL
> installation and Users guide and have evrything setup, or so i thought.
> Collocation on FILESPACES
> Node MAXNUMMP set to 8 mount points
> Device Class set to Mount Limit 8
> TXNGROUPMAX set to 256
> The 20gb database is on one physical disk
> The 200gb database is spread across 3 physical volumes
> When i backup, it only uses a single thread, i.e. one mount point. Do i
> need to ask our Database Admin guys to put striping on the SQL database?
> The manuals were'nt clear about this
> Jeff White
> Senior Systems Programmer
> ICT Operations and Services
> 1st Floor
> Miller Street
> 0161 837 5020
> jeff.white AT cis.co DOT uk