Dear List,
it seems, it is solved:
On 12/12/2012 03:54 PM, Thomas Denier wrote:
...
> Are you using the style of script that does the following?
>
> * Store the process ID in a specific file after a successful
> start.
> * Delete the ID file after stopping dsmc.
> * Refuse a request to start ds
Multiple stanza's are quite normal to use, think about TDP's.
Did you tried a different client port number for each scheduler?
Regards,
Maurice van 't Loo
http://mvantloo.nl/
2012/12/12 Ethan Günther
> Dear List,
>
> for a client with large filespaces, we would like to split the backup up
> in
esday, December 12, 2012 1:43 AM
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] Multiple stanzas unusable: "/usr/bin/dsmc already running."
Dear List,
for a client with large filespaces, we would like to split the backup up into
several nodes in order to balance the load. On the basis of
-Ethan Günther wrote: -
>for a client with large filespaces, we would like to split the backup
>up
>into several nodes in order to balance the load. On the basis of the
>TSM-client documentation we created several stanzas in the dsm.sys
>file
>with different servername entries. In the init
Dear List,
for a client with large filespaces, we would like to split the backup up
into several nodes in order to balance the load. On the basis of the
TSM-client documentation we created several stanzas in the dsm.sys file
with different servername entries. In the init-script several dsmc
proces
