: ron.delaw...@us.ibm.com
From: Grant Street
To: ADSM-L@VM.MARIST.EDU
Date: 07/07/15 17:08
Subject:Re: [ADSM-L] ANR2033E Command failed - lock conflict
Sent by:"ADSM: Dist Stor Manager"
Hi Nick
It is a bit cumbersome to do parallel backups, but it does work.
Essen
Sorry.. to clarify
"If you only have two volumes you can only ever create a maximum of two
streams."
On 08/07/15 10:07, Grant Street wrote:
Hi Nick
It is a bit cumbersome to do parallel backups, but it does work.
Essentially you run a backup node process per NAS "volume" depending on
your N
, 2015 7:22 AM
To: ADSM-L@VM.MARIST.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
Hi Nick
It is a bit cumbersome to do parallel backups, but it does work.
Essentially you run a backup node process per NAS "volume" depending on
your NAS's definition of "volume".
This is tricky when you have few volumes or volumes that vary greatly in
size. If you only have two volumes you can o
, but I am
running 7.1.0.0.
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Nick
Marouf
Sent: Tuesday, July 07, 2015 7:22 AM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: ANR2033E Command failed - lock conflict
Hi Grant,
I've been interested in pu
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
wrote:
> Hi
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
