SV: Linux Backup - restore image
Hi, Talk to your IBM Tivoli rep about this. IBM has a tool called CBMR that is an 3rd part software for TSM that do this for all your platforms. That mean you will have the same software and documentation for both Windows and Linux. Thanks Christian -Ursprungligt meddelande- Från: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] För Bogdan Stoica Skickat: den 10 november 2006 21:41 Till: ADSM-L@VM.MARIST.EDU Ämne: Linux Backup - restore image Hi I'm a new user in tivoli, I need to make a full backup linux server (redhat 4.4) that can be full restored to an empty computer like in windows (asr) or in a way that can be used in the shortest time but i don't know how For my test i use a blade system. Can you help me? Thanks a lot
Restore Times
Hi all; I have 2 TSM machines - both - TSM 5.3 Level 4.0. I have about 55 Tb on each. We are getting a netapp machine which will have about 70 Tb on it. My boss is concerned that if I just add the netapp data to one of the machines, enstead of getting a third machine that it will cause the restore times to increase. Is that really the case, or won't it matter? I want to add all of the 70 Tb to just one machine, because I also want to get some new tape drives and then convert the current data on it to the new tape drives. Lawrence McMahon Senior Programmer Analyst 341 Computing Center, North Campus SUNY at Buffalo 645-3579
Linux Backup - restore image
Hi I'm a new user in tivoli, I need to make a full backup linux server (redhat 4.4) that can be full restored to an empty computer like in windows (asr) or in a way that can be used in the shortest time but i don't know how For my test i use a blade system. Can you help me? Thanks a lot
Reporting anomaly - EST CAPACITY for sequential storage pools?
Well, I'm confused. TSM 5.3.3.0 on Windows. One of my TSM servers has 3 primary sequential pools on disk. (Devclass type = FILE). The volumes are preallocated files created with DEFINE VOLUME, so MAXSCRATCH=0 for the pool. There have been no volumes added/deleted for weeks. One of the pools is 254 GB, one is 7142 GB, one is 25TB (actual bytes, calculated by summing up values for each file from Windows Properties). Can anybody tell me how the ESTIMATED CAPACITY for the pool is calculated? All three are coming up with Estimated Capacity of MORE GB than are actually available in the pool. I get the same results from Q STGPOOL, or from SELECT * from STGPOOLS. For example, Q STGPOOL shows the 1st pool as 257 GB, the second as 7551 GB. None of the hits I found on ibm.com seemed to address this, and all should have been fixed at 5.3.3.0. Anybody else figured this out? Wanda Prather "* I/O, I/O, It's all about I/O *" -(me)
Re: Data unavailable to Server
On Nov 10, 2006, at 2:21 PM, Anders St¦hlbom wrote: Repair volume. What is the result? It does not even mount the copy pool volume volume. I think you mean the Restore Volume and Restore Stgpool commands. They are simple to use and work fine - providing that a Backup Stgpool had secured a copy of the file(s) in question, and that the copypool tape is available at restoral time. You can verify if all of a primary tape's data got copied via the 'Query CONTent ... COPied=No' command. Copying would fail if the original primary pool tape had a defect where the backup file had been written. You may want to perform 'Query Volume ... Format=Detailed' on a sampling of some tapes to see if read/write errors are accumulating on your tapes - which is to say that this may not be the only tape with problems. All in a day's administration. If you do have to perform a Restore Volume, do a Move Data first, to greatly reduce the overall amount of time (mounts). Richard Sims
Windows LAN-free client HBA replacement
The Windows 2003 LAN-free client has been configured and working properly for some time now. It uses Gresham/ACSLS to share an STK library and drives with our TSM servers. TSM client, storage agent and server versions are all 5.3.2.0. So the client's HBA that connects to the tape drives went kablooey yesterday and had to be replaced. After the storage folks rezoned the new HBA's WWN to the drives in the SAN, Windows discovered them as it should. So far, so good. Naturally, the drives all came back with different names than they used to have. No big deal, I have spreadsheets telling me which ACSLS drives have which WWN's, so looking in the Management Console gives me the information I need to update the elm.cnf file so Gresham can tell TSM which drive ACSLS is mounting its tape in. But the Device Names are all different from the TSM Names in the Management Console. The TSM names look like "mt.3.0.0.3", and the Device Names look like "\\.\Tape0". Oh yeah, that means that the drives are all using the default STK drivers - I need to go into Device Manager and update the drivers that the tape drives use to the TSMSCSI driver. And here's where I run into problems. When I try to apply that driver (which appears to be loaded on the system, and used to work fine before the HBA replacement) to a drive, the icon for that drive gets the error marker on it, and the Device Status window in the Properties for the drive shows "This device is not working properly because Windows cannot load the drivers required for this device. (Code 31)". When I run tsmdlst, it tells me that my TSMSCSI driver is running: C:\TSM\storageagent>tsmdlst Tivoli Storage Manager -- Device List Utility Licensed Materials - Property of IBM 5697-TSM (C) Copyright IBM Corporation 2000, 2005. All rights reserved. U.S. Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corporation. Computer Name: WIN2003LANFREECLIENT OS Version: 5.2 OS Build #: 3790 TSM Device Driver: TSMScsi - Running .. (boring HBA and drive information, which all looks kosher) Have I neglected to do something critical that will allow the TSM tape driver to work on these drives? Do I need to get the TSMSCSI driver reloaded on that system? Is this something that (this being Windows) a simple reboot will fix? I would prefer not to hear "maybe" or even "probably", because a reboot for this server is a non-trivial event, business-wise, so if that's what I ask for, it had better work. Thanks in advance for any responses! Robben Leaf [EMAIL PROTECTED] -- Electronic Privacy Notice. This e-mail, and any attachments, contains information that is, or may be, covered by electronic communications privacy laws, and is also confidential and proprietary in nature. If you are not the intended recipient, please be advised that you are legally prohibited from retaining, using, copying, distributing, or otherwise disclosing this information in any manner. Instead, please reply to the sender that you have received this communication in error, and then immediately delete it. Thank you in advance for your cooperation. ==
Re: TSM Admin Console on VmWare server
Not much, in terms of network load. For the "health check" function, the admin center periodically sends some queries to the TSM server (like Q DB, Q LOG, Q PATH), I think it's every 30 minutes. Other than that, it's only the responses to your queries or commands when you are working with it. No backup/client data goes throught the ISC. Wanda Prather "I/O, I/O, It's all about I/O" -(me) -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Lamb, Charles P. Sent: Friday, November 10, 2006 2:14 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: TSM Admin Console on VmWare server Hi. Can anyone tell me how much network activity there is between TSM Admin Center on an Intel server and the main TSM storage manager on a RISC server?? My network group is asking the question. We will have both servers on the same Vlan subnet here at work. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Keith Arbogast Sent: Friday, November 10, 2006 12:09 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] TSM Admin Console on VmWare server We have TSM Admin Center running on a virtual machine under ESX 2.5.2. Since I also support ESX, I gave it two 2.2 ghz cpus and 3.6 GB of RAM. It has been in service for only a few weeks, but to date has had no performance problems or other issues. In the (at least) three years we have been using virtual machines in production there have been extremely few problems traced back to the Vmware itself. Keith Arbogast Indiana University
Data unavailable to Server
Hi, I got "Data unavailable to server" message in the client and from actlog this: 2006-11-10 19:54:29 ANR0548W Retrieve or restore failed for session 26 for node NODE11 (WinNT) processing file space \\NODE11\g$ 6 for file \MSSQL\BACKUP\AXDB\ AXDB_DB_200610211619.BAK stored as Backup - error detected.(SESSION: 26) OK fine I will repair the original volume in tapepool but it simply don't work. I have tried to: Repair volume. What is the result? It does not even mount the copy pool volume volume. Repair stgpool. Same result I have done an audit volume fix=no got this 2006-11-10 20:14:41 ANR2317W Audit Volume found damaged file on volume NMF926L2: Node NODE11, Type Backup (Inactive), File space \\NODE11\g$, fsId 6, File name \MSSQL\BACKUP\AXDB\ AXDB_DB_200610211619.BAK is number 1 of 1 versions.(SESSION: 4, PROCESS: 1) I have done an audit volume fix=yes then the content off the volume was deleted and I had to rollback the database I read the Administrators guide and I can't say it was advicing me a clear way to make a restore off the actual tape volume in the primary pool. Ideas? Thanks in advance /Anders
Re: TSM Admin Console on VmWare server
Hi. Can anyone tell me how much network activity there is between TSM Admin Center on an Intel server and the main TSM storage manager on a RISC server?? My network group is asking the question. We will have both servers on the same Vlan subnet here at work. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Keith Arbogast Sent: Friday, November 10, 2006 12:09 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] TSM Admin Console on VmWare server We have TSM Admin Center running on a virtual machine under ESX 2.5.2. Since I also support ESX, I gave it two 2.2 ghz cpus and 3.6 GB of RAM. It has been in service for only a few weeks, but to date has had no performance problems or other issues. In the (at least) three years we have been using virtual machines in production there have been extremely few problems traced back to the Vmware itself. Keith Arbogast Indiana University
Re: Days Since Last Access
I generate a report once a month that shows me all the filesystems that have not been backed up in more than 30 days. I can look through the list and pick out the hosts that I know should be backing up. Here is the select statement I use (likely borrowed from this forum). select node_name, Filespace_name, (current_timestamp-backup_end)days as "days_since_backup" from filespaces where cast((current_timestamp-backup_start) days as decimal) >=30 order by "days_since_backup" Ben -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Jeremy Cloward Sent: Friday, November 10, 2006 11:36 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: Days Since Last Access Yeah, I am in the same boat, I have too many nodes that do not backup, anbd no way to know unless I look in the failure report that gets e mailed out. Best thing to do is check the filesystem and see the last time It was accessed and backed up, the hitting the server info means meta data was sent and the system said yeah Im here, its the filesystem that tells you what is really going on. Jeremy Friday, November 10, 2006 1:32 PM To: ADSM-L@VM.MARIST.EDU cc: From: "Kauffman, Tom" <[EMAIL PROTECTED]> Subject: Re: [ADSM-L] Days Since Last Access We had a system that was connecting to the server 4 times a day, so last access was always less than 1. I crashed and burned, got rebuilt -- and the most recent backup was 15 months old. And I *still* can't get the NT admins to check the logs on any regular basis. Tom Kauffman NIBCO, Inc -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Prather, Wanda Sent: Friday, November 10, 2006 12:17 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: Days Since Last Access "Days since last access" just tells you the last time there was communication between the client and the server. It doesn't tell you anything about whether the client was backed up, or not. The communication could have been a single restore; or it could be the client scheduler just checking for a backup time. Or you could have a client backup that started, but did not complete successfully. To verify whether the client has been successfully backed up, look at q filespace nodename f=d Look for the "last backup end" date for each client filesystem to see when it last backed up. Wanda Prather "I/O, I/O, It's all about I/O" -(me) -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Avy Wong Sent: Friday, November 10, 2006 11:52 AM To: ADSM-L@VM.MARIST.EDU Subject: Days Since Last Access hello, When I do a q node to find out what nodes are being backed up, I see that "<1" means it is being backed up properly. But at times I see "1" , "2", "3" .." some big number " without "<" attached to it , my question is what is the definitive number to say it is still being backed up without digging through the details I have been told that "1" .. up to "3" is still ok. Thank you for clarifying. Node Name Platform Policy Domain Days Since Days Since Locked? Name Last Access Password Set - -- --- --- DAT03TEST WinNTSTANDARD <1 235No EOSNOTE1WinNTSTANDARD1 240 No ESSMOC04 WinNTSTANDARD 653 855 No Avy Wong Business Continuity Administrator Mohegan Sun 1 Mohegan Sun Blvd Uncasville, CT 06382 ext 28164 ** The information contained in this message may be privileged and confidential and protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution, or copy of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to the message and deleting it from your computer. ** CONFIDENTIALITY NOTICE: This email and any attachments are for the exclusive and confidential use of the intended recipient. If you are not the intended recipient, please do not read, distribute or take action in reliance upon this message. If you have received this in error, please notify us immediately by return email and promptly delete this message and its attachments from your computer system. We do not waive attorney-client or work product privilege by the transmission of this message.
Re: Days Since Last Access
Yeah, I am in the same boat, I have too many nodes that do not backup, anbd no way to know unless I look in the failure report that gets e mailed out. Best thing to do is check the filesystem and see the last time It was accessed and backed up, the hitting the server info means meta data was sent and the system said yeah Im here, its the filesystem that tells you what is really going on. Jeremy Friday, November 10, 2006 1:32 PM To: ADSM-L@VM.MARIST.EDU cc: From: "Kauffman, Tom" <[EMAIL PROTECTED]> Subject: Re: [ADSM-L] Days Since Last Access We had a system that was connecting to the server 4 times a day, so last access was always less than 1. I crashed and burned, got rebuilt -- and the most recent backup was 15 months old. And I *still* can't get the NT admins to check the logs on any regular basis. Tom Kauffman NIBCO, Inc -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Prather, Wanda Sent: Friday, November 10, 2006 12:17 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: Days Since Last Access "Days since last access" just tells you the last time there was communication between the client and the server. It doesn't tell you anything about whether the client was backed up, or not. The communication could have been a single restore; or it could be the client scheduler just checking for a backup time. Or you could have a client backup that started, but did not complete successfully. To verify whether the client has been successfully backed up, look at q filespace nodename f=d Look for the "last backup end" date for each client filesystem to see when it last backed up. Wanda Prather "I/O, I/O, It's all about I/O" -(me) -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Avy Wong Sent: Friday, November 10, 2006 11:52 AM To: ADSM-L@VM.MARIST.EDU Subject: Days Since Last Access hello, When I do a q node to find out what nodes are being backed up, I see that "<1" means it is being backed up properly. But at times I see "1" , "2", "3" .." some big number " without "<" attached to it , my question is what is the definitive number to say it is still being backed up without digging through the details I have been told that "1" .. up to "3" is still ok. Thank you for clarifying. Node Name Platform Policy Domain Days Since Days Since Locked? Name Last AccessPassword Set - -- --- --- DAT03TEST WinNTSTANDARD <1 235No EOSNOTE1WinNTSTANDARD1 240 No ESSMOC04 WinNTSTANDARD 653 855 No Avy Wong Business Continuity Administrator Mohegan Sun 1 Mohegan Sun Blvd Uncasville, CT 06382 ext 28164 ** The information contained in this message may be privileged and confidential and protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution, or copy of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to the message and deleting it from your computer. ** CONFIDENTIALITY NOTICE: This email and any attachments are for the exclusive and confidential use of the intended recipient. If you are not the intended recipient, please do not read, distribute or take action in reliance upon this message. If you have received this in error, please notify us immediately by return email and promptly delete this message and its attachments from your computer system. We do not waive attorney-client or work product privilege by the transmission of this message.
Re: Days Since Last Access
We had a system that was connecting to the server 4 times a day, so last access was always less than 1. I crashed and burned, got rebuilt -- and the most recent backup was 15 months old. And I *still* can't get the NT admins to check the logs on any regular basis. Tom Kauffman NIBCO, Inc -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Prather, Wanda Sent: Friday, November 10, 2006 12:17 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: Days Since Last Access "Days since last access" just tells you the last time there was communication between the client and the server. It doesn't tell you anything about whether the client was backed up, or not. The communication could have been a single restore; or it could be the client scheduler just checking for a backup time. Or you could have a client backup that started, but did not complete successfully. To verify whether the client has been successfully backed up, look at q filespace nodename f=d Look for the "last backup end" date for each client filesystem to see when it last backed up. Wanda Prather "I/O, I/O, It's all about I/O" -(me) -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Avy Wong Sent: Friday, November 10, 2006 11:52 AM To: ADSM-L@VM.MARIST.EDU Subject: Days Since Last Access hello, When I do a q node to find out what nodes are being backed up, I see that "<1" means it is being backed up properly. But at times I see "1" , "2", "3" .." some big number " without "<" attached to it , my question is what is the definitive number to say it is still being backed up without digging through the details I have been told that "1" .. up to "3" is still ok. Thank you for clarifying. Node Name Platform Policy Domain Days Since Days Since Locked? Name Last AccessPassword Set - -- --- --- DAT03TEST WinNTSTANDARD <1 235No EOSNOTE1WinNTSTANDARD1 240 No ESSMOC04 WinNTSTANDARD 653 855 No Avy Wong Business Continuity Administrator Mohegan Sun 1 Mohegan Sun Blvd Uncasville, CT 06382 ext 28164 ** The information contained in this message may be privileged and confidential and protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution, or copy of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to the message and deleting it from your computer. ** CONFIDENTIALITY NOTICE: This email and any attachments are for the exclusive and confidential use of the intended recipient. If you are not the intended recipient, please do not read, distribute or take action in reliance upon this message. If you have received this in error, please notify us immediately by return email and promptly delete this message and its attachments from your computer system. We do not waive attorney-client or work product privilege by the transmission of this message.
Re: TSM Admin Console on VmWare server
We have TSM Admin Center running on a virtual machine under ESX 2.5.2. Since I also support ESX, I gave it two 2.2 ghz cpus and 3.6 GB of RAM. It has been in service for only a few weeks, but to date has had no performance problems or other issues. In the (at least) three years we have been using virtual machines in production there have been extremely few problems traced back to the Vmware itself. Keith Arbogast Indiana University
Re: Days Since Last Access
"Days since last access" just tells you the last time there was communication between the client and the server. It doesn't tell you anything about whether the client was backed up, or not. The communication could have been a single restore; or it could be the client scheduler just checking for a backup time. Or you could have a client backup that started, but did not complete successfully. To verify whether the client has been successfully backed up, look at q filespace nodename f=d Look for the "last backup end" date for each client filesystem to see when it last backed up. Wanda Prather "I/O, I/O, It's all about I/O" -(me) -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Avy Wong Sent: Friday, November 10, 2006 11:52 AM To: ADSM-L@VM.MARIST.EDU Subject: Days Since Last Access hello, When I do a q node to find out what nodes are being backed up, I see that "<1" means it is being backed up properly. But at times I see "1" , "2", "3" .." some big number " without "<" attached to it , my question is what is the definitive number to say it is still being backed up without digging through the details I have been told that "1" .. up to "3" is still ok. Thank you for clarifying. Node Name Platform Policy Domain Days Since Days Since Locked? Name Last AccessPassword Set - -- --- --- DAT03TEST WinNTSTANDARD <1 235No EOSNOTE1WinNTSTANDARD1 240 No ESSMOC04 WinNTSTANDARD 653 855 No Avy Wong Business Continuity Administrator Mohegan Sun 1 Mohegan Sun Blvd Uncasville, CT 06382 ext 28164 ** The information contained in this message may be privileged and confidential and protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution, or copy of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to the message and deleting it from your computer. **
Re: Days Since Last Access
Careful, access and backup are not synonymous here. For instance, a locked node still on a schedule will access TSM, but no backup takes place. At 11:52 AM 11/10/2006 -0500, you wrote: hello, When I do a q node to find out what nodes are being backed up, I see that "<1" means it is being backed up properly. But at times I see "1" , "2", "3" .." some big number " without "<" attached to it , my question is what is the definitive number to say it is still being backed up without digging through the details I have been told that "1" .. up to "3" is still ok. Thank you for clarifying. Node Name Platform Policy Domain Days Since Days Since Locked? Name Last AccessPassword Set - -- --- --- DAT03TEST WinNTSTANDARD <1 235No EOSNOTE1WinNTSTANDARD1 240 No ESSMOC04 WinNTSTANDARD 653 855 No Avy Wong Business Continuity Administrator Mohegan Sun 1 Mohegan Sun Blvd Uncasville, CT 06382 ext 28164 ** The information contained in this message may be privileged and confidential and protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution, or copy of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to the message and deleting it from your computer. ** Fred Johanson ITSM Administrator University of Chicago 773-702-8464
Days Since Last Access
hello, When I do a q node to find out what nodes are being backed up, I see that "<1" means it is being backed up properly. But at times I see "1" , "2", "3" .." some big number " without "<" attached to it , my question is what is the definitive number to say it is still being backed up without digging through the details I have been told that "1" .. up to "3" is still ok. Thank you for clarifying. Node Name Platform Policy Domain Days Since Days Since Locked? Name Last AccessPassword Set - -- --- --- DAT03TEST WinNTSTANDARD <1 235No EOSNOTE1WinNTSTANDARD1 240 No ESSMOC04 WinNTSTANDARD 653 855 No Avy Wong Business Continuity Administrator Mohegan Sun 1 Mohegan Sun Blvd Uncasville, CT 06382 ext 28164 ** The information contained in this message may be privileged and confidential and protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution, or copy of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to the message and deleting it from your computer. **
Re: JR- listof files/mgmt class used for a node from TSM admin console
select node_name, hl_name, ll_name, class_name from backups where
node_name in('NODE1','NODE2') and ll_name like '%.MDB'
Note:
The backups table is the largest table you have; you will get much
better performance for this query if you do it for 1 nodename at a time,
because the table is indexed by node name:
e.g.: where node_name='NODE1'
The "%" is a wildcard for any number of characters.
The nodenames must be specified in upper case.
File ane path names must also be specified in upper case, for Windows
clients.
If you want to restrict the query further to just one directory, the
path is in hl_name, so you could add:
and hl_name like '%JDOE%'
Wanda Prather
"I/O, I/O, It's all about I/O" -(me)
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
JR Trimark
Sent: Friday, November 10, 2006 10:56 AM
To: ADSM-L@VM.MARIST.EDU
Subject: JR- listof files/mgmt class used for a node from TSM admin
console
I can run the following command to list out what mgmt class was used for
files ending in mbd, how do I do this from the TSM admin console for
more
than 1 client?
q backup -detail -subdir=yes userdata:\home\jdoe\*.mdb
I am trying to confirm what mgmt class was used to backup the mdb files
since my clients use at least 2 mgmt class for files.
Thanks
JR- listof files/mgmt class used for a node from TSM admin console
I can run the following command to list out what mgmt class was used for files ending in mbd, how do I do this from the TSM admin console for more than 1 client? q backup -detail -subdir=yes userdata:\home\jdoe\*.mdb I am trying to confirm what mgmt class was used to backup the mdb files since my clients use at least 2 mgmt class for files. Thanks
Re: Archive Slowness
Tom - You'll likely have to do the standard analysis to isolate the problem. The best first approach is to watch the session from the server, via repeated Query SEssion, and see what's happening during it. (You can get some sense of where waits were occurring in past sessions by reviewing TSM accounting log data.) If the problem is constant on one or two files, perform a cp of the file to /dev/null and see if that takes far longer than it should, which would point to file system issues. Whereas you say that other archives from that client run at good speed, then it's probably not a network configuration issue. If still stumped, run a client trace. Richard Sims
Archive Slowness
I have a problem with a few archives running extremely long/slow. We just migrated this client to a new machine and AIX version. The problem did not exist before. TSM 5.2.2.5 server running on AIX 5.1. TSM 5.2.2.0 client running on AIX 5.3. P590, 4 cpus, 32 Gig memoy, etherchannel made up of two GigE ethernets >From TSM server activity log: 11/10/06 00:48:08 ANR0406I Session 300086 started for node EUHAIX08 (AIX) ( Tcp/Ip euhaix08(40714)). (SESSION: 300086) 11/10/06 06:08:48 ANR0403I Session 300086 ended for node EUHAIX08 (AIX). (S ESSION: 300086) 11/10/06 06:08:49 ANR0406I Session 303402 started for node EUHAIX08 (AIX) ( Tcp/Ip euhaix08(42100)). (SESSION: 303402) 11/10/06 06:08:49 ANE4952I (Session: 303402, Node: EUHAIX08) Total number of objects inspected:2(SESSION: 303402) 11/10/06 06:08:49 ANE4953I (Session: 303402, Node: EUHAIX08) Total number of objects archived: 2(SESSION: 303402) 11/10/06 06:08:49 ANE4958I (Session: 303402, Node: EUHAIX08) Total number of objects updated: 0(SESSION: 303402) 11/10/06 06:08:49 ANE4960I (Session: 303402, Node: EUHAIX08) Total number of objects rebound: 0(SESSION: 303402) 11/10/06 06:08:49 ANE4957I (Session: 303402, Node: EUHAIX08) Total number of objects deleted: 0(SESSION: 303402) 11/10/06 06:08:49 ANE4970I (Session: 303402, Node: EUHAIX08) Total number of objects expired: 0(SESSION: 303402) 11/10/06 06:08:49 ANE4959I (Session: 303402, Node: EUHAIX08) Total number of objects failed: 0(SESSION: 303402) 11/10/06 06:08:49 ANE4961I (Session: 303402, Node: EUHAIX08) Total number of bytes transferred: 1.95 GB(SESSION: 303402) 11/10/06 06:08:49 ANE4963I (Session: 303402, Node: EUHAIX08) Data transfer time:17,046.90 sec(SESSION: 303402) 11/10/06 06:08:49 ANE4966I (Session: 303402, Node: EUHAIX08) Network data transfer rate: 120.26 KB/sec(SESSION: 303402) 11/10/06 06:08:49 ANE4967I (Session: 303402, Node: EUHAIX08) Aggregate data transfer rate:106.54 KB/sec(SESSION: 303402) 11/10/06 06:08:49 ANE4968I (Session: 303402, Node: EUHAIX08) Objects compr essed by:0%(SESSION: 303402) 11/10/06 06:08:49 ANE4964I (Session: 303402, Node: EUHAIX08) Elapsed proce ssing time:05:20:42(SESSION: 303402) Other archives running from this same machine, during the same time complete with normal timeframes, IE, pretty fast. On this one (and a few similar on this machine) it is like the priority of the session goes to zero and is not processed at all. The data connection does not time out, and the archive finishes, just in a HUGE amount of wall clock time. I see no errors on the etherchannel device, and no errors in the errlog. The client is still the 32bit version, have not upgraded it to the 64bit version to match the newly migrated to machine and O/S. Any thoughts? -Tom
unsubscribe
This communication is for use by the intended recipient and contains information that may be privileged, confidential or copyrighted under law. If you are not the intended recipient, you are hereby formally notified that any use, copying or distribution of this e-Mail, in whole or in part, is strictly prohibited. Please notify the sender by return e-Mail and delete this e-Mail from your system. Unless explicitly and conspicuously stated in the subject matter of the above e-Mail, this e-Mail does not constitute a contract offer, a contract amendment, or an acceptance of a contract offer. This e-Mail does not constitute consent to the use of sender's contact information for direct marketing purposes or for transfers of data to third parties. This email has been scanned for all viruses by the MessageLabs service.
Re: Client Acces Definition @ TSM DB
On Nov 10, 2006, at 2:57 AM, Oliver Martin wrote: I define at the client side an access for another node. Can someone tell me where this definition is saved ? I think at the TSM server DB but I was not able to find in wich tabel it is stored. Can someone tell me where to look ? Oliver - As noted in ADSM QuickFacts, the Set Access information is stored in the TSM database. There is no SQL table provided for querying that info from the server side: it must be performed from the client. Richard Sims
