Re: Deduplication question
On 06/09/11 22:40, Richard van Denzel wrote: Hi All, Just a question aboutn the internal dedup of TSM. When I dedup a storage pool and then backup the pool to a dedup copy pool, will the data in the storage pool backup be transferred deduped or will it get undeduped first, then transferred and then dedupped again? Richard. Richard, The chapter 'managing storage pools and volumes' in the TSM 6.1 Admin Guide has a decent section on deduplicating data. We are investigating server- and client-side dedupe but we haven't tried what you want to do in our test environment. However, the above document suggests in two places that the data will be copied/moved in its deduplicated 'state' rather than being rebuilt, copied and deduplicated again. Ian Smith Oxford University
Backupset encryption - quick question
Hi all I need to transport a backup set and need at least some basic encryption. Before I do a load of testing, I thought I'd ask the group Does anyone know if client side encryption include.encrypt works with backup sets, or rather, can you restore the stuff! I'll be restoring via a locally attach drive. Thanks Steven
Re: [adsm] Re: TSM v6.2 Diaster Recovery Restore
Thanks. The underlying problem turned out to be that I was trying to run the db restore as root instead of as the instance owner. That in turn created a log file in the instance directory that was owned by root that had to be corrected before the instance owner could do the restore. The V6 DRM restore script needs a LOT of work. David -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Lloyd Dieter Sent: Tuesday, September 06, 2011 7:03 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] [adsm] Re: TSM v6.2 Diaster Recovery Restore See: http://publib.boulder.ibm.com/infocenter/tsminfo/v6/index.jsp?topic=%2Fcom.ibm.itsm.tshoot.doc%2Fr_pdg_cmonerrsbkupdbrstordb.html A 106 seems to indicate a permissions problem. -Lloyd On 09/06/2011 10:44 AM, Ehresman,David E. wrote: I am trying to do a DR type restore of a TSM 6.2 DB onto a tsm instance on a different machine. After the DB backup tape mounts, I get a Database restore terminated. DB2 sqlcode: -2033. DB2 sqlerrmc: 106.. What are the DB2 codes trying to tell me? The restore is running on TSM 6.2.3.0 server level. The OS is AIX 6100-06-05-1115 -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Christian Svensson Sent: Monday, September 05, 2011 2:37 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] SV: TSM v6.2 Diaster Recovery Restore Hi David, Yes you can do that. Make sure you have backup the database to a media that both Instance Users can read/write and also copy Volhist/Devconfig and copy both of them in to your new instances home directory (same as dsmserv.opt) after you have configured the new instance. Best Regards Christian Svensson Cell: +46-70-325 1577 E-mail: christian.svens...@cristie.se Supported Platform for CPU2TSM:: http://www.cristie.se/cpu2tsm-supported-platforms Från: Ehresman,David E. [deehr...@louisville.edu] Skickat: den 2 september 2011 21:44 Till: ADSM-L@VM.MARIST.EDU Ämne: TSM v6.2 Diaster Recovery Restore Can I restore a TSM v6.2 database to a tsm instance with a different name? That is, could I restore a db backup from a tsm with a instance user id of libmgr1 to a new machine which has been configured with a instance user id of libmgr2?
Sql query problem in tsm 6.2
TSM folks, tsm server 6.2.2 on redhat enterprise linux 6.0 I submit the following file as a macro and recieve the errors below. This query works in tsm 5.5 file c:\tsmscripts\pl3 - select events.node_name, events.status, nodes.email_address from events, - nodes where events.node_name = nodes.node_name and - events.status != 'Completed' and - events.scheduled_start '2011-09-06 08:00:00' and - events.scheduled_start '2011-09-07 07:00:00' tsm screen cut below. tsm: TSM01macro c:\tsmscripts\pl3 ANS8000I Server command: 'select events.node_name, events.status, nodes.email_ ad dress from events, nodes where events.node_name = nodes.node_name and events.s ta tus != 'Completed' and events.scheduled_start '2011-09-06 08:00:00' and event s. scheduled_start '2011-09-07 07:00:00'' ANR0162W Supplemental database diagnostic information: -1:42S22:-206 ([ IBM][CLI Driver][DB2/LINUXX8664] SQL0206N NODES.NODE_NAME is not valid in the context where it is used. SQLSTATE=42703 ). ANR2940E The command 'select events.node_name , events.status , nodes.email_address from events , NODESVIEW where events.node_name = nodes.node_name and events.status != 'Completed' and events.scheduled_start ' 2011-09-06 08:00:00' and events.scheduled_start '2011-09-07 07:00:00' ' contains an unknown SQL column name. ANS8001I Return code 3. ANS8 29E Macro processing terminated. tsm: TSM01 Gary Lee Senior System Programmer Ball State University phone: 765-285-1310
Re: Sql query problem in tsm 6.2
Do select * from syscat.columns where tabname='NODES' and see if the column name is still NODE_NAME, or perhaps changed to NODENAME. Beyond that: There were a bunch of APARs involving TSM tables, such as IC70346, which may be impacting your attempted Select. Unfortunately, TSM version 6 has been chaotic. Richard Sims
Antwort: [ADSM-L] Sql query problem in tsm 6.2
Hi, use following Syntax: select ev.node_name, ev.status, no.email_address from events ev, - nodes no where ev.node_name = no.node_name and - ev.status != 'Completed' and - ev.scheduled_start '2011-09-06 08:00:00' and - ev.scheduled_start '2011-09-07 07:00:00' Thorsten Von:Lee, Gary D. g...@bsu.edu An: ADSM-L@VM.MARIST.EDU Datum: 07.09.11 15:07 Betreff:[ADSM-L] Sql query problem in tsm 6.2 Gesendet von: ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU TSM folks, tsm server 6.2.2 on redhat enterprise linux 6.0 I submit the following file as a macro and recieve the errors below. This query works in tsm 5.5 file c:\tsmscripts\pl3 - select events.node_name, events.status, nodes.email_address from events, - nodes where events.node_name = nodes.node_name and - events.status != 'Completed' and - events.scheduled_start '2011-09-06 08:00:00' and - events.scheduled_start '2011-09-07 07:00:00' tsm screen cut below. tsm: TSM01macro c:\tsmscripts\pl3 ANS8000I Server command: 'select events.node_name, events.status, nodes.email_ ad dress from events, nodes where events.node_name = nodes.node_name and events.s ta tus != 'Completed' and events.scheduled_start '2011-09-06 08:00:00' and event s. scheduled_start '2011-09-07 07:00:00'' ANR0162W Supplemental database diagnostic information: -1:42S22:-206 ([ IBM][CLI Driver][DB2/LINUXX8664] SQL0206N NODES.NODE_NAME is not valid in the context where it is used. SQLSTATE=42703 ). ANR2940E The command 'select events.node_name , events.status , nodes.email_address from events , NODESVIEW where events.node_name = nodes.node_name and events.status != 'Completed' and events.scheduled_start ' 2011-09-06 08:00:00' and events.scheduled_start '2011-09-07 07:00:00' ' contains an unknown SQL column name. ANS8001I Return code 3. ANS8 29E Macro processing terminated. tsm: TSM01 Gary Lee Senior System Programmer Ball State University phone: 765-285-1310 + 750 Jahre Knappschaft. Soziale Verantwortung zu jeder Zeit. www.750jahre.info +
Re: Sql query problem in tsm 6.2
Well, column name is still node_name. listed as column 0. Next to lookup the apar. Thanks for the help. This is disconcerting. Sure effects my reporting and error tracking. Gary Lee Senior System Programmer Ball State University phone: 765-285-1310 -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Richard Sims Sent: Wednesday, September 07, 2011 9:28 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Sql query problem in tsm 6.2 Do select * from syscat.columns where tabname='NODES' and see if the column name is still NODE_NAME, or perhaps changed to NODENAME. Beyond that: There were a bunch of APARs involving TSM tables, such as IC70346, which may be impacting your attempted Select. Unfortunately, TSM version 6 has been chaotic. Richard Sims
Re: Sql query problem in tsm 6.2
For some reason 6.2 does not like linking tables in the old way. You need to use aliases. Try this select statement: select ev.node_name, ev.status, nd.email_address from events ev, nodes nd where ev.node_name = nd.node_name and ev.status != 'Completed' and ev.scheduled_start '2011-09-06 08:00:00' and ev.scheduled_start '2011-09-07 07:00:00' Dan Fiske -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Lee, Gary D. Sent: Wednesday, September 07, 2011 9:02 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Sql query problem in tsm 6.2 TSM folks, tsm server 6.2.2 on redhat enterprise linux 6.0 I submit the following file as a macro and recieve the errors below. This query works in tsm 5.5 file c:\tsmscripts\pl3 - select events.node_name, events.status, nodes.email_address from events, - nodes where events.node_name = nodes.node_name and - events.status != 'Completed' and - events.scheduled_start '2011-09-06 08:00:00' and - events.scheduled_start '2011-09-07 07:00:00' tsm screen cut below. tsm: TSM01macro c:\tsmscripts\pl3 ANS8000I Server command: 'select events.node_name, events.status, nodes.email_ ad dress from events, nodes where events.node_name = nodes.node_name and events.s ta tus != 'Completed' and events.scheduled_start '2011-09-06 08:00:00' and event s. scheduled_start '2011-09-07 07:00:00'' ANR0162W Supplemental database diagnostic information: -1:42S22:-206 ([ IBM][CLI Driver][DB2/LINUXX8664] SQL0206N NODES.NODE_NAME is not valid in the context where it is used. SQLSTATE=42703 ). ANR2940E The command 'select events.node_name , events.status , nodes.email_address from events , NODESVIEW where events.node_name = nodes.node_name and events.status != 'Completed' and events.scheduled_start ' 2011-09-06 08:00:00' and events.scheduled_start '2011-09-07 07:00:00' ' contains an unknown SQL column name. ANS8001I Return code 3. ANS8 29E Macro processing terminated. tsm: TSM01 Gary Lee Senior System Programmer Ball State University phone: 765-285-1310
Re: Antwort: [ADSM-L] Sql query problem in tsm 6.2
Thanks all. Adding the alias names fixed it. Gary Lee Senior System Programmer Ball State University phone: 765-285-1310 -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Thorsten Burghardt Sent: Wednesday, September 07, 2011 9:36 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Antwort: [ADSM-L] Sql query problem in tsm 6.2 Hi, use following Syntax: select ev.node_name, ev.status, no.email_address from events ev, - nodes no where ev.node_name = no.node_name and - ev.status != 'Completed' and - ev.scheduled_start '2011-09-06 08:00:00' and - ev.scheduled_start '2011-09-07 07:00:00' Thorsten Von:Lee, Gary D. g...@bsu.edu An: ADSM-L@VM.MARIST.EDU Datum: 07.09.11 15:07 Betreff:[ADSM-L] Sql query problem in tsm 6.2 Gesendet von: ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU TSM folks, tsm server 6.2.2 on redhat enterprise linux 6.0 I submit the following file as a macro and recieve the errors below. This query works in tsm 5.5 file c:\tsmscripts\pl3 - select events.node_name, events.status, nodes.email_address from events, - nodes where events.node_name = nodes.node_name and - events.status != 'Completed' and - events.scheduled_start '2011-09-06 08:00:00' and - events.scheduled_start '2011-09-07 07:00:00' tsm screen cut below. tsm: TSM01macro c:\tsmscripts\pl3 ANS8000I Server command: 'select events.node_name, events.status, nodes.email_ ad dress from events, nodes where events.node_name = nodes.node_name and events.s ta tus != 'Completed' and events.scheduled_start '2011-09-06 08:00:00' and event s. scheduled_start '2011-09-07 07:00:00'' ANR0162W Supplemental database diagnostic information: -1:42S22:-206 ([ IBM][CLI Driver][DB2/LINUXX8664] SQL0206N NODES.NODE_NAME is not valid in the context where it is used. SQLSTATE=42703 ). ANR2940E The command 'select events.node_name , events.status , nodes.email_address from events , NODESVIEW where events.node_name = nodes.node_name and events.status != 'Completed' and events.scheduled_start ' 2011-09-06 08:00:00' and events.scheduled_start '2011-09-07 07:00:00' ' contains an unknown SQL column name. ANS8001I Return code 3. ANS8 29E Macro processing terminated. tsm: TSM01 Gary Lee Senior System Programmer Ball State University phone: 765-285-1310 + 750 Jahre Knappschaft. Soziale Verantwortung zu jeder Zeit. www.750jahre.info +
Comment about the TSM gui from a IBM conference
Interesting question/comment on the IBM Storage blog by Tony Pearsonat https://www.ibm.com/developerworks/mydeveloperworks/blogs/InsideSystemStorage/?lang=en In talking about events on Day 4 of the IBM Storage University, he describes a Question/Answer event with this Q+A . . . Q) The TSM GUI sucks! Are there any plans to improve it? A) Yes, we are aware that products like IBM XIV have raised the bar for what people expect for graphical user interfaces. We have plans to improve the TSM GUI. IBM's new GUI for the SAN Volume Controller and Storwize V7000 has been well-received, and wll be used as a template for the GUIs of other storage hardware and software products. The GUI uses the latest HTML5 Dojo widgets and AJAX technologies, eliminating Java dependencies on the client browser. Rick - The information contained in this message is intended only for the personal and confidential use of the recipient(s) named above. If the reader of this message is not the intended recipient or an agent responsible for delivering it to the intended recipient, you are hereby notified that you have received this document in error and that any review, dissemination, distribution, or copying of this message is strictly prohibited. If you have received this communication in error, please notify us immediately, and delete the original message.
confused about deduprequiresbackup
Hi, I'm a bit confused about this option. when I set it to no, reclamation on my primary dedup filepool works when set to yes, not. although all data is copied to a copypool. reclamaion on copypool works in both situations... could it have to do with the fact that the copypool is also file device (on a share) with deduplication activated? Regards, Alex Heindl smime.p7s Description: S/MIME Cryptographic Signature
Re: confused about deduprequiresbackup
Alex, I can't find the precise reference at the moment, but I think the copy backup must be to a non-deduplicated pool for this flag to be satisfied. Accordingly, I suspect reclamation, which is the process that deconstructs the duplicate data, is disabled until the flag setting is properly honoured. Ian Smith On 07/09/11 16:18, Alexander Heindl wrote: Hi, I'm a bit confused about this option. when I set it to no, reclamation on my primary dedup filepool works when set to yes, not. although all data is copied to a copypool. reclamaion on copypool works in both situations... could it have to do with the fact that the copypool is also file device (on a share) with deduplication activated? Regards, Alex Heindl
Re: confused about deduprequiresbackup
See page 286 in the AIX admin guide Quote: Attention: By default, the Tivoli Storage Manager server requires that you back up deduplication-enabled primary storage pools before volumes in the storage pool are reclaimed and before duplicate data is discarded. The copy storage pools and active-data pools to which you back up data and copy active data must not be set up for data deduplication. To prevent possible data loss, do not change the default. If you do change the default, reclamation criteria remains unchanged ... ... Attention: You can change the default setting to permit reclamation of primary storage pools that are not backed up. However, there is a remote possibility that changing the default can result in unrecoverable data loss if a data-integrity error occurs. To change the default and permit reclamation of primary sequential-access storage pools that are not backed up, set the value of the DEDUPREQUIRESBACKUP server option to NO. Changing the default does not change the reclamation criteria that you specified for a storage pool. The DEDUPREQUIRESBACKUP server option applies only to primary storage pools. The option does not apply to copy storage pools or active-data pools. Cheers, Thank you, Neil Strand Storage Engineer - Legg Mason Baltimore, MD. (410) 580-7491 Whatever you can do or believe you can, begin it. Boldness has genius, power and magic. From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Alexander Heindl Sent: Wednesday, September 07, 2011 11:19 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] confused about deduprequiresbackup Hi, I'm a bit confused about this option. when I set it to no, reclamation on my primary dedup filepool works when set to yes, not. although all data is copied to a copypool. reclamaion on copypool works in both situations... could it have to do with the fact that the copypool is also file device (on a share) with deduplication activated? Regards, Alex Heindl IMPORTANT: E-mail sent through the Internet is not secure. Legg Mason therefore recommends that you do not send any confidential or sensitive information to us via electronic mail, including social security numbers, account numbers, or personal identification numbers. Delivery, and or timely delivery of Internet mail is not guaranteed. Legg Mason therefore recommends that you do not send time sensitive or action-oriented messages to us via electronic mail. This message is intended for the addressee only and may contain privileged or confidential information. Unless you are the intended recipient, you may not use, copy or disclose to anyone any information contained in this message. If you have received this message in error, please notify the author by replying to this message and then kindly delete the message. Thank you.
Re: Comment about the TSM gui from a IBM conference
I've been ranting about that here for a while now. Yes, it sucks! And removing the dsmmfc native GUI client in 6.2 just added insult to injury. I did a benchmark of the Windows v6.1 java client versus the v6.1 native dsmmfc client on the same computer, and the java client took 10 times longer to initialize. TEN TIMES. It's so slow that when you ask it to do something, you find yourself frequently clicking again because nothing happened, but that sometimes causes malfunctions. I should submit a performance APAR against it. It's so bad that we are still distributing the v5.5 client to all our Windows users, despite the other improvements in 6.2 such as incremental system state backup. Until this improved and hopefully fast new client is developed with all that new technology, please update and return the dsmmfc client to distributions in v6.3, and make it the default. It was fast; THAT was the product that raised the bar for performance expectations for TSM client programs - TSM v5.5 dsmmfc, not XIV. Roger Deschner University of Illinois at Chicago rog...@uic.edu ==I have not lost my mind -- it is backed up on tape somewhere.= On Wed, 7 Sep 2011, Richard Rhodes wrote: Interesting question/comment on the IBM Storage blog by Tony Pearsonat https://www.ibm.com/developerworks/mydeveloperworks/blogs/InsideSystemStorage/?lang=en In talking about events on Day 4 of the IBM Storage University, he describes a Question/Answer event with this Q+A . . . Q) The TSM GUI sucks! Are there any plans to improve it? A) Yes, we are aware that products like IBM XIV have raised the bar for what people expect for graphical user interfaces. We have plans to improve the TSM GUI. IBM's new GUI for the SAN Volume Controller and Storwize V7000 has been well-received, and wll be used as a template for the GUIs of other storage hardware and software products. The GUI uses the latest HTML5 Dojo widgets and AJAX technologies, eliminating Java dependencies on the client browser. Rick - The information contained in this message is intended only for the personal and confidential use of the recipient(s) named above. If the reader of this message is not the intended recipient or an agent responsible for delivering it to the intended recipient, you are hereby notified that you have received this document in error and that any review, dissemination, distribution, or copying of this message is strictly prohibited. If you have received this communication in error, please notify us immediately, and delete the original message.
