Re: [ADSM-L] ANR2033E Command failed - lock conflict
2015-07-07 20:52:19
Grant,
To tackle your problem of multiple backups
at the same time you can carve up your NAS server (as long as you are using
volumes and directories and NOT volumes and Trees) using virtualmountpoint
Using the virtualmountpoint option to
identify a directory within a file system provides a direct path to the
files you want to back up, saving processing time. It is more efficient
to define a virtual mount point within a file system than it is to define
that file system using the domain option, and then to use the exclude option
in your include-exclude options list to exclude the files that you do not
want to back up.
Use the virtualmountpoint option to
define virtual mount points for multiple file systems, for local and remote
file systems, and to define more than one virtual mount point within the
same file system. Virtual mount points cannot be used in a file system
handled by automounter.
You can use the virtualmountpoint option
to back up unsupported file systems, with certain limitations.
After you define a virtual mount point,
you can specify the path and directory name with the domain option in either
the default client options file or on the incremental command to include
it for incremental backup services. When you perform a backup or archive
using the virtualmountpoint option, the query filespace command lists the
virtual mount point in its response along with other file systems. Generally,
directories that you define as virtual mount points are treated as actual
file systems and require that the virtualmountpoint option is specified
in the dsm.sys file to restore or retrieve the data.
After the creation of your virtualmountpoints,
you would create a NAS datamover for each virtualmountpoint, and each NAS
Datamover would be assigned to a schedule (could be the same schedule or
separate schedules). This would allow you to have multiple backups of your
NAS Server running at the same time. I have not used this configuration
with the NAS Appliance controlling the data storage pools, but this works
fine when TSM is setup to control the data (Normally called a 3-way setup).
This allows the NAS data to be treated that same as any other data that
TSM manages, sending it to disk storage pools, tape storage pools, making
copies for offsite requirements and such.
Best Regards,
_________________________________________________________
email: ron.delaware AT us.ibm DOT com
From:
Grant Street <Grant.Street AT AL.COM DOT AU>
To:
ADSM-L AT VM.MARIST DOT EDU
Date:
07/07/15 17:08
Subject:
Re: [ADSM-L]
ANR2033E Command failed - lock conflict
Sent by:
"ADSM:
Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
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
>>
|
|
|