Re: Query performance issue
Thank you very much Erwann, but it does not help. There is no visible improvement. Grigori G. Solonovitch -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Erwann SIMON Sent: Sunday, August 21, 2011 4:20 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Query performance issue Hi Grigori, Try to first add a clause that limit the scope of the search to avoid calculation on the entire actlog table, something like "... where date(current_timestamp)=current_date and cast((current_timestamp-date_time)minutes as decimal)<3 ..." Best regards / Cordialement / مع تحياتي Erwann SIMON Le 21/08/2011 12:38, Grigori Solonovitch a écrit : > TSM Client 6.2.3.0& TSM Server 5.5.5. > > Is there any way to speed up next request? > > select msgno, severity, message, originator, nodename, ownername, schedname, > domainname, servername, sessid, session, process, date_time as > date_time >from actlog > where cast((current_timestamp-date_time)minutes as decimal)<3 > ORDER BY date_time DESC > > Thank you very much in advance. > > Grigori G. Solonovitch > > > CONFIDENTIALITY AND WAIVER: The information contained in this electronic mail > message and any attachments hereto may be legally privileged and > confidential. The information is intended only for the recipient(s) named in > this message. If you are not the intended recipient you are notified that any > use, disclosure, copying or distribution is prohibited. If you have received > this in error please contact the sender and delete this message and any > attachments from your computer system. We do not guarantee that this message > or any attachment to it is secure or free from errors, computer viruses or > other conditions that may damage or interfere with data, hardware or software. > > Please consider the environment before printing this Email. CONFIDENTIALITY AND WAIVER: The information contained in this electronic mail message and any attachments hereto may be legally privileged and confidential. The information is intended only for the recipient(s) named in this message. If you are not the intended recipient you are notified that any use, disclosure, copying or distribution is prohibited. If you have received this in error please contact the sender and delete this message and any attachments from your computer system. We do not guarantee that this message or any attachment to it is secure or free from errors, computer viruses or other conditions that may damage or interfere with data, hardware or software.
Re: Query performance issue
Working with timestamps can be onerous. One sometimes has to be wily to compensate for processing time. Try: select msgno, severity, message, originator, nodename, ownername, schedname, \ domainname, servername, sessid, session, process, date_time \ from actlog \ where DATE(DATE_TIME)=CURRENT_DATE and date_time >(current_timestamp - 3 minutes) Add Order By if you want. Richard Sims On Aug 22, 2011, at 3:08 AM, Grigori Solonovitch wrote: > Thank you very much Erwann, but it does not help. There is no visible > improvement. > > Grigori G. Solonovitch > > > -Original Message- > From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of > Erwann SIMON > Sent: Sunday, August 21, 2011 4:20 PM > To: ADSM-L@VM.MARIST.EDU > Subject: Re: [ADSM-L] Query performance issue > > Hi Grigori, > > Try to first add a clause that limit the scope of the search to avoid > calculation on the entire actlog table, something like "... where > date(current_timestamp)=current_date and > cast((current_timestamp-date_time)minutes as decimal)<3 ..." > > Best regards / Cordialement / مع تحياتي > Erwann SIMON > > > Le 21/08/2011 12:38, Grigori Solonovitch a écrit : >> TSM Client 6.2.3.0& TSM Server 5.5.5. >> >> Is there any way to speed up next request? >> >> select msgno, severity, message, originator, nodename, ownername, schedname, >>domainname, servername, sessid, session, process, date_time as >> date_time >> from actlog >> where cast((current_timestamp-date_time)minutes as decimal)<3 >> ORDER BY date_time DESC >> >> Thank you very much in advance. >> >> Grigori G. Solonovitch
Windows server rename causing full backups
We had an incident this morning that ended up being caused by a Windows server that was renamed (internally) and connected to a domain (previously standalone), thus initiating a full backup of an 8TB volume/space, since TSM now sees it as new filespaces. How do I handle this to avoid a full backup? Will simply renaming the filespaces take care of this or is there a more elegant solution? Zoltan Forray TSM Software & Hardware Administrator Virginia Commonwealth University UCC/Office of Technology Services 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
Renaming a Windows node - where does it get the nodename if no nodename statement?
Please correct me if I am wrong, but I was under the impression that if a Windows node does NOT have a NODENAME statement in it's dsm.opt, it simply asks the OS for the hostname and uses that. This value is also used for the filespace names. So, if this Windows node has been backing up without a NODENAME statement and then the hostname is changed, shouldn't this also change the nodename so when the node attempts to connect to the TSM server it will use the new hostname? Or does the scheduling process use the registry keys, not caring about the hostname changed? What is the sequence of checking for nodename statements, vs just using the hostname and/or registry key? This issue is causing waaayyy to much activity and inquires for a Monday! Zoltan Forray TSM Software & Hardware Administrator Virginia Commonwealth University UCC/Office of Technology Services 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: Query performance issue
Hi Richard, You're right, and I see a mistake in my statement. I should have written "date(date_time)=current_date" and not "date(current_timestamp)=current_date"... Best regards / Cordialement / مع تحياتي Erwann SIMON Le 22/08/2011 13:29, Richard Sims a écrit : Working with timestamps can be onerous. One sometimes has to be wily to compensate for processing time. Try: select msgno, severity, message, originator, nodename, ownername, schedname, \ domainname, servername, sessid, session, process, date_time \ from actlog \ where DATE(DATE_TIME)=CURRENT_DATE and date_time>(current_timestamp - 3 minutes) Add Order By if you want. Richard Sims On Aug 22, 2011, at 3:08 AM, Grigori Solonovitch wrote: Thank you very much Erwann, but it does not help. There is no visible improvement. Grigori G. Solonovitch -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Erwann SIMON Sent: Sunday, August 21, 2011 4:20 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Query performance issue Hi Grigori, Try to first add a clause that limit the scope of the search to avoid calculation on the entire actlog table, something like "... where date(current_timestamp)=current_date and cast((current_timestamp-date_time)minutes as decimal)<3 ..." Best regards / Cordialement / مع تحياتي Erwann SIMON Le 21/08/2011 12:38, Grigori Solonovitch a écrit : TSM Client 6.2.3.0& TSM Server 5.5.5. Is there any way to speed up next request? select msgno, severity, message, originator, nodename, ownername, schedname, domainname, servername, sessid, session, process, date_time as date_time from actlog where cast((current_timestamp-date_time)minutes as decimal)<3 ORDER BY date_time DESC Thank you very much in advance. Grigori G. Solonovitch
Re: Windows server rename causing full backups
-Zoltan Forray wrote: - >We had an incident this morning that ended up being caused by a >Windows server that was renamed (internally) and connected to a >domain (previously standalone), thus initiating a full backup of >an 8TB volume/space, since TSM now sees it as new filespaces. > >How do I handle this to avoid a full backup? Will simply renaming >the >filespaces take care of this or is there a more elegant >solution? We have occasionally renamed Windows TSM clients. Renaming file spaces for drive letters works fine in terms of avoiding full backups. I would not recommend renaming system state file spaces that incorporate the node name.
Re: Renaming a Windows node - where does it get the nodename if no nodename statement?
-Zoltan Forray wrote: - >Please correct me if I am wrong, but I was under the impression that >if a Windows node does NOT have a NODENAME statement in it's dsm.opt, >it simply asks the OS for the hostname and uses that. This value is >also used for the filespace names. The documented default is the Windows machine name. This is often the same as the IP host name, but it is possible for the two names to be different. [Material removed] >Or does the scheduling process use the registry keys, not caring >about the hostname changed? Our experience with renamed Windows nodes indicates that the scheduler service locks in the node name in effect at the time when dsmcutil was used to create the service. I don't know whether this behavior is documented. The service presumably uses the registry to store the node name. When a Windows node is renamed, we tell the system administrator do remove and recreate the service.
Re: Renaming a Windows node - where does it get the nodename if no nodename statement?
All you have to do is use the same "Wizard" that you used to create the "Service" and update instead of create. This let's you change the node name used by the service. David Longo >>> Thomas Denier 8/22/2011 12:27 PM >>> -Zoltan Forray wrote: - >Please correct me if I am wrong, but I was under the impression that >if a Windows node does NOT have a NODENAME statement in it's dsm.opt, >it simply asks the OS for the hostname and uses that. This value is >also used for the filespace names. The documented default is the Windows machine name. This is often the same as the IP host name, but it is possible for the two names to be different. [Material removed] >Or does the scheduling process use the registry keys, not caring >about the hostname changed? Our experience with renamed Windows nodes indicates that the scheduler service locks in the node name in effect at the time when dsmcutil was used to create the service. I don't know whether this behavior is documented. The service presumably uses the registry to store the node name. When a Windows node is renamed, we tell the system administrator do remove and recreate the service. # This message is for the named person's use only. It may contain private, proprietary, or legally privileged information. No privilege is waived or lost by any mistransmission. If you receive this message in error, please immediately delete it and all copies of it from your system, destroy any hard copies of it, and notify the sender. You must not, directly or indirectly, use, disclose, distribute, print, or copy any part of this message if you are not the intended recipient. Health First reserves the right to monitor all e-mail communications through its networks. Any views or opinions expressed in this message are solely those of the individual sender, except (1) where the message states such views or opinions are on behalf of a particular entity; and (2) the sender is authorized by the entity to give such views or opinions. #
Re: Renaming a Windows node - where does it get the nodename if no nodename statement?
Thomas, Thanks for both of your responses. You have confirmed what we are seeing. We rooted through the registry and see the keys with the old node name and encrypted password. The box was renamed and rebooted but the GUI was never bought up. As soon as we bought up the GUI, it grabbed the hostname and attempted (and failed) to connect to the TSM server since we kept the old nodename. Zoltan Forray TSM Software & Hardware Administrator Virginia Commonwealth University UCC/Office of Technology Services 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 From: Thomas Denier To: ADSM-L@VM.MARIST.EDU Date: 08/22/2011 12:47 PM Subject:Re: [ADSM-L] Renaming a Windows node - where does it get the nodename if no nodename statement? Sent by:"ADSM: Dist Stor Manager" -Zoltan Forray wrote: - >Please correct me if I am wrong, but I was under the impression that >if a Windows node does NOT have a NODENAME statement in it's dsm.opt, >it simply asks the OS for the hostname and uses that. This value is >also used for the filespace names. The documented default is the Windows machine name. This is often the same as the IP host name, but it is possible for the two names to be different. [Material removed] >Or does the scheduling process use the registry keys, not caring >about the hostname changed? Our experience with renamed Windows nodes indicates that the scheduler service locks in the node name in effect at the time when dsmcutil was used to create the service. I don't know whether this behavior is documented. The service presumably uses the registry to store the node name. When a Windows node is renamed, we tell the system administrator do remove and recreate the service.
Re: Renaming a Windows node - where does it get the nodename if no nodename statement?
Of course, even with a NODENAME statement and reworking the scheduler, the filespace names are still based on the hostname. We have renamed plenty of other servers that had nodename statements and the first backup was brand-new. Zoltan Forray TSM Software & Hardware Administrator Virginia Commonwealth University UCC/Office of Technology Services 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 From: David Longo To: ADSM-L@VM.MARIST.EDU Date: 08/22/2011 12:58 PM Subject:Re: [ADSM-L] Renaming a Windows node - where does it get the nodename if no nodename statement? Sent by:"ADSM: Dist Stor Manager" All you have to do is use the same "Wizard" that you used to create the "Service" and update instead of create. This let's you change the node name used by the service. David Longo >>> Thomas Denier 8/22/2011 12:27 PM >>> -Zoltan Forray wrote: - >Please correct me if I am wrong, but I was under the impression that >if a Windows node does NOT have a NODENAME statement in it's dsm.opt, >it simply asks the OS for the hostname and uses that. This value is >also used for the filespace names. The documented default is the Windows machine name. This is often the same as the IP host name, but it is possible for the two names to be different. [Material removed] >Or does the scheduling process use the registry keys, not caring >about the hostname changed? Our experience with renamed Windows nodes indicates that the scheduler service locks in the node name in effect at the time when dsmcutil was used to create the service. I don't know whether this behavior is documented. The service presumably uses the registry to store the node name. When a Windows node is renamed, we tell the system administrator do remove and recreate the service. # This message is for the named person's use only. It may contain private, proprietary, or legally privileged information. No privilege is waived or lost by any mistransmission. If you receive this message in error, please immediately delete it and all copies of it from your system, destroy any hard copies of it, and notify the sender. You must not, directly or indirectly, use, disclose, distribute, print, or copy any part of this message if you are not the intended recipient. Health First reserves the right to monitor all e-mail communications through its networks. Any views or opinions expressed in this message are solely those of the individual sender, except (1) where the message states such views or opinions are on behalf of a particular entity; and (2) the sender is authorized by the entity to give such views or opinions. #
Re: Query performance issue
Thank you very much, Richard. This query is much faster and gives the same result from data point of view. I have only question about period of time from 00:00:00 till 00:02:59. Is this query correct for mentioned period of time? Grigori G. Solonovitch -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Richard Sims Sent: Monday, August 22, 2011 2:30 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Query performance issue Working with timestamps can be onerous. One sometimes has to be wily to compensate for processing time. Try: select msgno, severity, message, originator, nodename, ownername, schedname, \ domainname, servername, sessid, session, process, date_time \ from actlog \ where DATE(DATE_TIME)=CURRENT_DATE and date_time >(current_timestamp - 3 minutes) Add Order By if you want. Richard Sims On Aug 22, 2011, at 3:08 AM, Grigori Solonovitch wrote: > Thank you very much Erwann, but it does not help. There is no visible > improvement. > > Grigori G. Solonovitch > > > -Original Message- > From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of > Erwann SIMON > Sent: Sunday, August 21, 2011 4:20 PM > To: ADSM-L@VM.MARIST.EDU > Subject: Re: [ADSM-L] Query performance issue > > Hi Grigori, > > Try to first add a clause that limit the scope of the search to avoid > calculation on the entire actlog table, something like "... where > date(current_timestamp)=current_date and > cast((current_timestamp-date_time)minutes as decimal)<3 ..." > > Best regards / Cordialement / مع تحياتي > Erwann SIMON > > > Le 21/08/2011 12:38, Grigori Solonovitch a écrit : >> TSM Client 6.2.3.0& TSM Server 5.5.5. >> >> Is there any way to speed up next request? >> >> select msgno, severity, message, originator, nodename, ownername, schedname, >>domainname, servername, sessid, session, process, date_time as >> date_time >> from actlog >> where cast((current_timestamp-date_time)minutes as decimal)<3 >> ORDER BY date_time DESC >> >> Thank you very much in advance. >> >> Grigori G. Solonovitch Please consider the environment before printing this Email. CONFIDENTIALITY AND WAIVER: The information contained in this electronic mail message and any attachments hereto may be legally privileged and confidential. The information is intended only for the recipient(s) named in this message. If you are not the intended recipient you are notified that any use, disclosure, copying or distribution is prohibited. If you have received this in error please contact the sender and delete this message and any attachments from your computer system. We do not guarantee that this message or any attachment to it is secure or free from errors, computer viruses or other conditions that may damage or interfere with data, hardware or software.
Backupset restore question - different server OS's
I am currently running TSM V5.5 on AIX. I am setting up a TSM V6.2 server on Linux at a new data center. I would like to use backup sets to transfer client data from the old to the new data centers. This backupset data will be used to populate the newly built clients - not as a backup data store. Both the old and new data centers have IBM TS1120 drives in their TS3500 libraries. I don't plan to attach each client to tape drives and would perform the backupset restore via TSM server. Does anyone know or have experienced creating a backup set on a TSM V5 server on AIX and then recovering that backup to a TSM V6 server on Linux? The Linux server would need to generate a TOC from the tape created by the AIX server. The TSM V6.2 server should be able to work with the backup set. It is the OS tape read/write compatibility that I am unsure of. I don't currently have a Linux box to play with and cannot test this scenario. Your comment is highly welcomed. 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. 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: Query performance issue
On Aug 22, 2011, at 2:17 PM, Grigori Solonovitch wrote: > Thank you very much, Richard. This query is much faster and gives the same > result from data point of view. > I have only question about period of time from 00:00:00 till 00:02:59. > Is this query correct for mentioned period of time? > > Grigori G. Solonovitch I had a hunch you would ask about that. The technique is an expedient to compensate for unfortunate overhead in a generalized query (despite DATE_TIME being an indexed field). It works where the Select is invoked on the same day as the pertinent records being queried. Consider midnight to be a boundary exception. In any case, you should be asleep in bed at that time. :-) Richard Sims
How to completely get rid of TSM6.2/DB2 on AIX
Hi, I've got a problem. An installation failed when creating an instance and I decided to uninstall and start over. I removed the installation using the uninstall script provided. But when I ran install.bin the next time it asked for the password of the instance owner and then failed. So it seems something is left behind after uninstall confusing the installer. Any idea what it might be? Expect reinstalling AIX of course. AIX61 TL03 Hans Chr.
Ang: [ADSM-L] How to completely get rid of TSM6.2/DB2 on AIX
The autonomous installler places files under /var/ibm that needs to be removed incase the installation fails. I'm not infront of a machine atm so I cant give you the exact path, but previously when installations failed, I made sure to remove the entire directory containing configuration files (telling the installer what is installed) and the log files. I believe there is also files under /etc that needs to be removed, but like I said, I'm at home and have no access to any production machines so I cant give you the exact path. Best Regards Daniel Sparrman Daniel Sparrman Exist i Stockholm AB Växel: 08-754 98 00 Fax: 08-754 97 30 daniel.sparr...@exist.se http://www.existgruppen.se Posthusgatan 1 761 30 NORRTÄLJE -"ADSM: Dist Stor Manager" skrev: - Till: ADSM-L@VM.MARIST.EDU Från: Hans Christian Riksheim Sänt av: "ADSM: Dist Stor Manager" Datum: 08/22/2011 20:41 Ärende: [ADSM-L] How to completely get rid of TSM6.2/DB2 on AIX Hi, I've got a problem. An installation failed when creating an instance and I decided to uninstall and start over. I removed the installation using the uninstall script provided. But when I ran install.bin the next time it asked for the password of the instance owner and then failed. So it seems something is left behind after uninstall confusing the installer. Any idea what it might be? Expect reinstalling AIX of course. AIX61 TL03 Hans Chr.
Ang: [ADSM-L] Backupset restore question - different server OS's
I've read through your question 3 times now and I'm still trying to figure out what you're doing :) You're mentioning creating backupsets. For me, a backupset is a way of restoring a client without having to transfer the data across the LAN. But you're also mentioning TSM servers placed on AIX and Linux respectively. Are you trying to move a TSM server from AIX to Linux? I've never heard of anyone transfering client data betweeen TSM servers using backupsets, I didnt even know it was possible. Did you mix it up and mean export tapes? Cant answer for AIX > Linux, but for example AIX > Windows wont work since the way the OS writes/reads labels of the tape isnt the same (tried it, didnt work for me, perhaps someone else was more lucky). Is there a reason you dont want to do a server-to-server export? Generally (and I'm only talking from my own experience) tapes, databases and normal volumes arent compatible between OS's. The way they handle tapes are just too different. If you try to explain what you're trying to accomplish, perhaps it's easier to help. Or it's just getting late and I'm too tired :) Best Regards Daniel Sparrman Daniel Sparrman Exist i Stockholm AB Växel: 08-754 98 00 Fax: 08-754 97 30 daniel.sparr...@exist.se http://www.existgruppen.se Posthusgatan 1 761 30 NORRTÄLJE -"ADSM: Dist Stor Manager" skrev: - Till: ADSM-L@VM.MARIST.EDU Från: "Strand, Neil B." Sänt av: "ADSM: Dist Stor Manager" Datum: 08/22/2011 20:25 Ärende: [ADSM-L] Backupset restore question - different server OS's I am currently running TSM V5.5 on AIX. I am setting up a TSM V6.2 server on Linux at a new data center. I would like to use backup sets to transfer client data from the old to the new data centers. This backupset data will be used to populate the newly built clients - not as a backup data store. Both the old and new data centers have IBM TS1120 drives in their TS3500 libraries. I don't plan to attach each client to tape drives and would perform the backupset restore via TSM server. Does anyone know or have experienced creating a backup set on a TSM V5 server on AIX and then recovering that backup to a TSM V6 server on Linux? The Linux server would need to generate a TOC from the tape created by the AIX server. The TSM V6.2 server should be able to work with the backup set. It is the OS tape read/write compatibility that I am unsure of. I don't currently have a Linux box to play with and cannot test this scenario. Your comment is highly welcomed. 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. 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.
