Re: [ADSM-L] ANR2033E Command failed - lock conflict
2015-07-07 12:24:53
I have been running 4 streams in parallel against a single NAS server. There
are parameters within the NAS server that specified how many background tasks
that can be started. I use a single master script that in parallel start 4
other scripts that run sequentially. I am not at 7.1.1.300 yet, but I am
running 7.1.0.0.
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Nick Marouf
Sent: Tuesday, July 07, 2015 7:22 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: ANR2033E Command failed - lock conflict
Hi Grant,
I've been interested in pursing NDMP backups in parallel, How does it work
overall?
Is this lock conflict something that you have experienced specifically with
the new version of tsm, and not with version 6.3?
Thanks,
-Nick
On Tue, Jul 7, 2015 at 12:41 AM, Grant Street <Grant.Street AT al.com DOT au>
wrote:
> Hi All
>
> We are running some NDMP backups in parallel using the PARALLEL
> functionality in a TSM script.
>
> Since moving to 7.1.1.300 from 6.3 we have noticed that we are getting
>
> ANR2033E BACKUP NODE: Command failed - lock conflict.
>
> Has anyone else seen this? or have some advice?
>
> We can't change it to a single stream as it will take close to a week in
> order to do the backup....
>
> Thanks in advance
>
> Grant
>
|
|
|