Re: Issues with Client Acceptor on 2012 server
Passed on to the Windows admin and the response was: The service is being run as a domain account. Believe it or not, that did the trick. Simple, yet I overlooked it. The domain account was not a member of the local Administrator group. Thank You! On Tue, Jul 7, 2015 at 1:20 PM, Rick Adamson rickadam...@segrocers.com wrote: Zoltan, Asking the obviousare you running the CLI as Administrator ? -Rick Adamson -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Zoltan Forray Sent: Tuesday, July 07, 2015 12:01 PM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Issues with Client Acceptor on 2012 server A Windows admin just installed the 7.1.2.0 client (fresh install, not an upgrade) on a 2012 server and has this problem. Upon Attempting to start the CIFS1-VCUCC TSM Client Acceptor she got this error: *Error message* “Windows could not start the CIFS1-VCUCC TSM Client Acceptor service on Local Computer. Error 6712: The requested propagation protocol was not registered as a CRM.” *Application Log – Event ID 4099* “Error Opening/Creating Registry Path ‘Software\IBM\ADSM\CurrentVersion\EnterpriseMgmtClients\Services” She found an old document talking about similar issues with really old clients. She continues with: *I manually created the EnterpriseMgmtClients key but no luck. I tried uninstalling 7.1.2.1 – removed all remnants of the registry and remaining folders after the uninstall. I installed 7.1.1.4, however, the same issue exist. I then repeated the uninstall process and installed 6.4.2.1 – no luck. So needless to say, I have uninstall, rebooted, deleted only to have the server back to TSM version 7.1.2.1. * *I just realized 7.1.2.2 was available today (7/7). I stopped the TSM service and installed this version. However, the same Error 6712 message occurs*. This is being done using the Administrator client. Any thoughts/suggestions? -- *Zoltan Forray* TSM Software Hardware Administrator Xymon Monitor Administrator Virginia Commonwealth University UCC/Office of Technology Services www.ucc.vcu.edu zfor...@vcu.edu - 804-828-4807 Don't be a phishing victim - VCU and other reputable organizations will never use email to request that you reply with your password, social security number or confidential personal information. For more details visit https://urldefense.proofpoint.com/v2/url?u=http-3A__infosecurity.vcu.edu_phishing.htmld=AwIFaQc=AzgFQeXLLKhxSQaoFCm29Ar=eqh5PzQPIsPArLoI_uV1mKvhIpcNP1MsClDPSJjFfxwm=Y7f5yznDODX65PJyR9um0V9ov34Re8GxSLGqB-u66aUs=8WrTXoKDuV1SrnHIUpAAWhyJoaz7ABgDznIXs0L8V9ce= -- *Zoltan Forray* TSM Software Hardware Administrator Xymon Monitor Administrator Virginia Commonwealth University UCC/Office of Technology Services www.ucc.vcu.edu zfor...@vcu.edu - 804-828-4807 Don't be a phishing victim - VCU and other reputable organizations will never use email to request that you reply with your password, social security number or confidential personal information. For more details visit http://infosecurity.vcu.edu/phishing.html
Re: ANR2033E Command failed - lock conflict
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@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 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.str...@al.com.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
Re: Issues with Client Acceptor on 2012 server
Zoltan, Asking the obviousare you running the CLI as Administrator ? -Rick Adamson -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Zoltan Forray Sent: Tuesday, July 07, 2015 12:01 PM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Issues with Client Acceptor on 2012 server A Windows admin just installed the 7.1.2.0 client (fresh install, not an upgrade) on a 2012 server and has this problem. Upon Attempting to start the CIFS1-VCUCC TSM Client Acceptor she got this error: *Error message* “Windows could not start the CIFS1-VCUCC TSM Client Acceptor service on Local Computer. Error 6712: The requested propagation protocol was not registered as a CRM.” *Application Log – Event ID 4099* “Error Opening/Creating Registry Path ‘Software\IBM\ADSM\CurrentVersion\EnterpriseMgmtClients\Services” She found an old document talking about similar issues with really old clients. She continues with: *I manually created the EnterpriseMgmtClients key but no luck. I tried uninstalling 7.1.2.1 – removed all remnants of the registry and remaining folders after the uninstall. I installed 7.1.1.4, however, the same issue exist. I then repeated the uninstall process and installed 6.4.2.1 – no luck. So needless to say, I have uninstall, rebooted, deleted only to have the server back to TSM version 7.1.2.1. * *I just realized 7.1.2.2 was available today (7/7). I stopped the TSM service and installed this version. However, the same Error 6712 message occurs*. This is being done using the Administrator client. Any thoughts/suggestions? -- *Zoltan Forray* TSM Software Hardware Administrator Xymon Monitor Administrator Virginia Commonwealth University UCC/Office of Technology Services www.ucc.vcu.edu zfor...@vcu.edu - 804-828-4807 Don't be a phishing victim - VCU and other reputable organizations will never use email to request that you reply with your password, social security number or confidential personal information. For more details visit https://urldefense.proofpoint.com/v2/url?u=http-3A__infosecurity.vcu.edu_phishing.htmld=AwIFaQc=AzgFQeXLLKhxSQaoFCm29Ar=eqh5PzQPIsPArLoI_uV1mKvhIpcNP1MsClDPSJjFfxwm=Y7f5yznDODX65PJyR9um0V9ov34Re8GxSLGqB-u66aUs=8WrTXoKDuV1SrnHIUpAAWhyJoaz7ABgDznIXs0L8V9ce=
Issues with Client Acceptor on 2012 server
A Windows admin just installed the 7.1.2.0 client (fresh install, not an upgrade) on a 2012 server and has this problem. Upon Attempting to start the CIFS1-VCUCC TSM Client Acceptor she got this error: *Error message* “Windows could not start the CIFS1-VCUCC TSM Client Acceptor service on Local Computer. Error 6712: The requested propagation protocol was not registered as a CRM.” *Application Log – Event ID 4099* “Error Opening/Creating Registry Path ‘Software\IBM\ADSM\CurrentVersion\EnterpriseMgmtClients\Services” She found an old document talking about similar issues with really old clients. She continues with: *I manually created the EnterpriseMgmtClients key but no luck. I tried uninstalling 7.1.2.1 – removed all remnants of the registry and remaining folders after the uninstall. I installed 7.1.1.4, however, the same issue exist. I then repeated the uninstall process and installed 6.4.2.1 – no luck. So needless to say, I have uninstall, rebooted, deleted only to have the server back to TSM version 7.1.2.1. * *I just realized 7.1.2.2 was available today (7/7). I stopped the TSM service and installed this version. However, the same Error 6712 message occurs*. This is being done using the Administrator client. Any thoughts/suggestions? -- *Zoltan Forray* TSM Software Hardware Administrator Xymon Monitor Administrator Virginia Commonwealth University UCC/Office of Technology Services www.ucc.vcu.edu zfor...@vcu.edu - 804-828-4807 Don't be a phishing victim - VCU and other reputable organizations will never use email to request that you reply with your password, social security number or confidential personal information. For more details visit http://infosecurity.vcu.edu/phishing.html
Re: TSM server V7.1.1.300
Robert, We upgrade our servers from 7.1.1.108 to 7.1.1.301 about 2 weeks ago, without incident or the side effects that others have seen. Our expiration runs in the same time as it did prior to the upgrade. I do seem to recall that sometimes when upgrading DB2, it can take while for the indexes to be optimized (or whatever) and until that happens performance may be sluggish. We noticed this when we first upgraded from v5 to v6. We did not notice it for this minor upgrade. Our server is not error free - we are seeing more tape errors recently, but we have no reason to suspect they are related to the server software upgrade. More likely related to some new drives and/or tapes that we recently purchased. ..Paul At 03:00 AM 7/7/2015, Robert Ouzen wrote: Hello all Consider to upgrade my TSM servers to version 7.1.1.300 , want to know if someone already did it and have any issues ? Best Regards Robert Ouzen -- Paul ZarnowskiPh: 607-255-4757 Assistant Director for Storage Services Fx: 607-255-8521 IT at Cornell / InfrastructureEm: p...@cornell.edu 719 Rhodes Hall, Ithaca, NY 14853-3801
TSM server V7.1.1.300
Hello all Consider to upgrade my TSM servers to version 7.1.1.300 , want to know if someone already did it and have any issues ? Best Regards Robert Ouzen
Re: TSM server V7.1.1.300
On Tuesday 07 July 2015 07:00:42 you wrote: Hello all Consider to upgrade my TSM servers to version 7.1.1.300 , want to know if someone already did it and have any issues ? I did an upgrade last week and as a result, expire inventory never ends. We have to halt and restart the TSM server daily. Stef
ANR2033E Command failed - lock conflict
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
Re: TSM server V7.1.1.300
On 07/07/15 17:00, Robert Ouzen wrote: Hello all Consider to upgrade my TSM servers to version 7.1.1.300 , want to know if someone already did it and have any issues ? Best Regards Robert Ouzen I did find that upgrading from 6.3, trying to do a restore straight after the install took ages eg 30mins instead of 1 min. The db2 processes were going nuts during the restore. This was repeatable but resolved itself by the next morning. I'm guessing that it was still re-initializing indexes etc or some other housekeeping task. Apart from that no issues Grant
Re: ANR2033E Command failed - lock conflict
Cheers I might see if redoing the master script to spawn sub scripts will help Grant On 08/07/15 02:20, Gee, Norman wrote: 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@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 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.str...@al.com.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
Re: ANR2033E Command failed - lock conflict
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.str...@al.com.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
Re: ANR2033E Command failed - lock conflict
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 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.str...@al.com.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
Re: ANR2033E Command failed - lock conflict
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.delaw...@us.ibm.com From: Grant Street grant.str...@al.com.au 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 ADSM-L@VM.MARIST.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.str...@al.com.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
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.str...@al.com.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
