Re: [ADSM-L] ANR2033E Command failed - lock conflict
2015-07-07 20:08:42
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 only ever create two streams.
If you have two volumes, one 100GB and one 1TB and you want to do a
backup storge pool after, you have to wait for the largest to finish.
We never saw it in 6.3 that we ran for 18 months or more. We have seen
it every time in 7.1.1.300. We have to keep retrying until it works.
Grant
On 08/07/15 00:22, Nick Marouf wrote:
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
|
|
|