Re: Backup specific folder only
Try the following. Add Exclude.dir e:\dir1 Exclude.dir e:\dir2 . . . For each major tree on the e: drive. This will keep tsm from traversing the trees at all. More administration, but the only thing I can think of. Exclude.dir is processed before standard excludes, therefore you cannot exclude.dir e:\ then include what you wanted. Hope this helps. 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 Gibin Sent: Monday, July 18, 2011 2:26 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Backup specific folder only Thanks Paul ,Made the changes in the server dsm.opt DOMAIN E: Exclude "E:\...\*" Include "E:\Oracle\...\*" 3mth_grp2_MC Now only files/folders from "E:\Oracle" get backed up.But i noticed a problem when using the mentioned include/exclude , all the sub folders from all the other excluded folders get backed up as well.This i feel can cause unnecessary TSM DB growth .As each file/folder backed up consumes 4KB of TSM database space. Is there some way to avoid TSM backing up the sub folder structure from all the other excluded directories...?? +-- |This was sent by gibi...@gmail.com via Backup Central. |Forward SPAM to ab...@backupcentral.com. +--
Re: Backup specific folder only
Another solution is to use a customized schedule for this node that targets the desired directory: DEFINE SCHEDULE domain schedname OBJECTS=E:\Oracle\ OPTIONS=-SUBDIR=YES And keep the INCLUDE statement in dsm.opt: Include "E:\Oracle\...\*" 3mth_grp2_MC Best regards, Andy Raibeck IBM Software Group Tivoli Storage Manager Client Product Development Level 3 Team Lead Internal Notes e-mail: Andrew Raibeck/Hartford/IBM@IBMUS Internet e-mail: stor...@us.ibm.com IBM Tivoli Storage Manager support web page: http://www.ibm.com/support/entry/portal/Overview/Software/Tivoli/Tivoli_Storage_Manager "ADSM: Dist Stor Manager" wrote on 2011-07-18 07:25:48: > From: "Lee, Gary D." > To: ADSM-L@vm.marist.edu > Date: 2011-07-18 07:33 > Subject: Re: Backup specific folder only > Sent by: "ADSM: Dist Stor Manager" > > Try the following. > > Add > > Exclude.dir e:\dir1 > Exclude.dir e:\dir2 > . . . > > For each major tree on the e: drive. This will keep tsm from > traversing the trees at all. > More administration, but the only thing I can think of. > Exclude.dir is processed before standard excludes, therefore you > cannot exclude.dir e:\ then include what you wanted. > > Hope this helps. > > > > 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 Gibin > Sent: Monday, July 18, 2011 2:26 AM > To: ADSM-L@VM.MARIST.EDU > Subject: [ADSM-L] Backup specific folder only > > Thanks Paul ,Made the changes in the server dsm.opt > > > DOMAIN E: > Exclude "E:\...\*" > Include "E:\Oracle\...\*" 3mth_grp2_MC > > > Now only files/folders from "E:\Oracle" get backed up.But i noticed > a problem when using the mentioned include/exclude , all the sub > folders from all the other excluded folders get backed up as > well.This i feel can cause unnecessary TSM DB growth .As each file/ > folder backed up consumes 4KB of TSM database space. > > > Is there some way to avoid TSM backing up the sub folder structure > from all the other excluded directories...?? > > +-- > |This was sent by gibi...@gmail.com via Backup Central. > |Forward SPAM to ab...@backupcentral.com. > +--
Re: Backup specific folder only
Indeed just using the EXCLUDE as I specified will grab the directory tree still. It's a longer story, but the Reader's Digest version is that doing so ensure's the TSM BA client GUI can drill down to any given directory to find files you may have backed up. You can't use EXCLUDE.DIR on the "E:\" directory, otherwise you won't get the Oracle directory either for the reasons I specified previously. You could use the EXCLUDE.DIR on all the other directories in E: as suggested by Gary, but then (also as he suggested) you'll have more administrative overhead as you need to check periodically to ensure that all the dirctories in the E: drive are still being excluded - if someone adds a dir to the E: drive afterwards without telling you, it'll get backed up. Andy's suggestion for doing a separate schedule that targets the directory is actually pretty good, you'd get only the directory you want and don't risk someone doing something on the server to inadvertently cause you to start backing up unwanted data. However then you're maintaining a separate schedule (not really a big deal). As far as fear of the DB growing, I would ask you this - do you really have that many subdirectories in the Oracle dir that you're going to see any kind of noticable db growth as a result? Even if you have a hundred or a few hundred other directories there, it is not going to impact your db in any way that you could ever notice. If you had thousands of subdirs in there, then yes, I might be a bit concerned, though I'd be less concerned about the size of the db growth and more concerned about how long it takes to traverse the directories unnecessarily. In general, though, I've found that it hasn't been any kind of a super negative impact. I would also re-ask the question - are you really, really sure you don't want to backup anything else on this server, especially the OS? As I mentioned previously, in most TSM installations, the size difference that backing up the rest of the data/OS will make to the total storage is small, and having the ability to restore the odd file here or there if someone mucks up is worth it's weight in gold Paul On Mon, Jul 18, 2011 at 6:04 AM, Andrew Raibeck wrote: > Another solution is to use a customized schedule for this node that targets > the desired directory: > > DEFINE SCHEDULE domain schedname OBJECTS=E:\Oracle\ OPTIONS=-SUBDIR=YES > > And keep the INCLUDE statement in dsm.opt: > > Include "E:\Oracle\...\*" 3mth_grp2_MC > > Best regards, > > Andy Raibeck > IBM Software Group > Tivoli Storage Manager Client Product Development > Level 3 Team Lead > Internal Notes e-mail: Andrew Raibeck/Hartford/IBM@IBMUS > Internet e-mail: stor...@us.ibm.com > > IBM Tivoli Storage Manager support web page: > > http://www.ibm.com/support/entry/portal/Overview/Software/Tivoli/Tivoli_Storage_Manager > > "ADSM: Dist Stor Manager" wrote on 2011-07-18 > 07:25:48: > > > From: "Lee, Gary D." > > To: ADSM-L@vm.marist.edu > > Date: 2011-07-18 07:33 > > Subject: Re: Backup specific folder only > > Sent by: "ADSM: Dist Stor Manager" > > > > Try the following. > > > > Add > > > > Exclude.dir e:\dir1 > > Exclude.dir e:\dir2 > > . . . > > > > For each major tree on the e: drive. This will keep tsm from > > traversing the trees at all. > > More administration, but the only thing I can think of. > > Exclude.dir is processed before standard excludes, therefore you > > cannot exclude.dir e:\ then include what you wanted. > > > > Hope this helps. > > > > > > > > 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 > Gibin > > Sent: Monday, July 18, 2011 2:26 AM > > To: ADSM-L@VM.MARIST.EDU > > Subject: [ADSM-L] Backup specific folder only > > > > Thanks Paul ,Made the changes in the server dsm.opt > > > > > > DOMAIN E: > > Exclude "E:\...\*" > > Include "E:\Oracle\...\*" 3mth_grp2_MC > > > > > > Now only files/folders from "E:\Oracle" get backed up.But i noticed > > a problem when using the mentioned include/exclude , all the sub > > folders from all the other excluded folders get backed up as > > well.This i feel can cause unnecessary TSM DB growth .As each file/ > > folder backed up consumes 4KB of TSM database space. > > > > > > Is there some way to avoid TSM backing up the sub folder structure > > from all the other excluded directories...?? > > > > +-- > > |This was sent by gibi...@gmail.com via Backup Central. > > |Forward SPAM to ab...@backupcentral.com. > > +-- >
Re: Backup specific folder only
Correction to my previous message - I asked if you really have that many directories in the Oracle dir, when I meant to say do you really have that many other directories on the E: drive? Paul On Mon, Jul 18, 2011 at 8:54 AM, Paul Fielding wrote: > Indeed just using the EXCLUDE as I specified will grab the directory tree > still. It's a longer story, but the Reader's Digest version is that doing so > ensure's the TSM BA client GUI can drill down to any given directory to find > files you may have backed up. > > You can't use EXCLUDE.DIR on the "E:\" directory, otherwise you won't get > the Oracle directory either for the reasons I specified previously. > > You could use the EXCLUDE.DIR on all the other directories in E: as > suggested by Gary, but then (also as he suggested) you'll have more > administrative overhead as you need to check periodically to ensure that all > the dirctories in the E: drive are still being excluded - if someone adds a > dir to the E: drive afterwards without telling you, it'll get backed up. > > Andy's suggestion for doing a separate schedule that targets the directory > is actually pretty good, you'd get only the directory you want and don't > risk someone doing something on the server to inadvertently cause you to > start backing up unwanted data. However then you're maintaining a separate > schedule (not really a big deal). > > As far as fear of the DB growing, I would ask you this - do you really have > that many subdirectories in the Oracle dir that you're going to see any kind > of noticable db growth as a result? Even if you have a hundred or a few > hundred other directories there, it is not going to impact your db in any > way that you could ever notice. If you had thousands of subdirs in there, > then yes, I might be a bit concerned, though I'd be less concerned about the > size of the db growth and more concerned about how long it takes to > traverse the directories unnecessarily. In general, though, I've found > that it hasn't been any kind of a super negative impact. > > I would also re-ask the question - are you really, really sure you don't > want to backup anything else on this server, especially the OS? As I > mentioned previously, in most TSM installations, the size difference that > backing up the rest of the data/OS will make to the total storage is small, > and having the ability to restore the odd file here or there if someone > mucks up is worth it's weight in gold > > Paul > > > On Mon, Jul 18, 2011 at 6:04 AM, Andrew Raibeck wrote: > >> Another solution is to use a customized schedule for this node that >> targets >> the desired directory: >> >> DEFINE SCHEDULE domain schedname OBJECTS=E:\Oracle\ OPTIONS=-SUBDIR=YES >> >> And keep the INCLUDE statement in dsm.opt: >> >> Include "E:\Oracle\...\*" 3mth_grp2_MC >> >> Best regards, >> >> Andy Raibeck >> IBM Software Group >> Tivoli Storage Manager Client Product Development >> Level 3 Team Lead >> Internal Notes e-mail: Andrew Raibeck/Hartford/IBM@IBMUS >> Internet e-mail: stor...@us.ibm.com >> >> IBM Tivoli Storage Manager support web page: >> >> http://www.ibm.com/support/entry/portal/Overview/Software/Tivoli/Tivoli_Storage_Manager >> >> "ADSM: Dist Stor Manager" wrote on 2011-07-18 >> 07:25:48: >> >> > From: "Lee, Gary D." >> > To: ADSM-L@vm.marist.edu >> > Date: 2011-07-18 07:33 >> > Subject: Re: Backup specific folder only >> > Sent by: "ADSM: Dist Stor Manager" >> > >> > Try the following. >> > >> > Add >> > >> > Exclude.dir e:\dir1 >> > Exclude.dir e:\dir2 >> > . . . >> > >> > For each major tree on the e: drive. This will keep tsm from >> > traversing the trees at all. >> > More administration, but the only thing I can think of. >> > Exclude.dir is processed before standard excludes, therefore you >> > cannot exclude.dir e:\ then include what you wanted. >> > >> > Hope this helps. >> > >> > >> > >> > 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 >> Gibin >> > Sent: Monday, July 18, 2011 2:26 AM >> > To: ADSM-L@VM.MARIST.EDU >> > Subject: [ADSM-L] Backup specific folder only >> > >> > Thanks Paul ,Made the changes in the server dsm.opt >> > >> > >> > DOMAIN E: >> > Exclude "E:\...\*" >> > Include "E:\Oracle\...\*" 3mth_grp2_MC >> > >> > >> > Now only files/folders from "E:\Oracle" get backed up.But i noticed >> > a problem when using the mentioned include/exclude , all the sub >> > folders from all the other excluded folders get backed up as >> > well.This i feel can cause unnecessary TSM DB growth .As each file/ >> > folder backed up consumes 4KB of TSM database space. >> > >> > >> > Is there some way to avoid TSM backing up the sub folder structure >> > from all the other excluded directories...?? >> > >> > +-- >> > |This was sent by gibi...@gmail.
How to script commands at startup
Hello, We are running version 6.2.2.3(0) on an AIX 6.1 server. We are experiencing issues as described in https://www-304.ibm.com/support/entdocview.wss?uid=swg1IC76984 and have been given three commands that need to be issued right after the TSM server is restarted (they are only good for the life of the server). Does anyone know how to write a script, or can point me to something that will issue TSM commands from an administrator session shortly after the server is restarted? Any help would be appreciated. Thank you, Pam Pam Pagnotta EES, LLC, Contractor to the United States Department of Energy 1000 Independence Avenue, SW Washington, DC 20585 Office: 301 903-5508 Mobile: 301 326-7296 Email: pam.pagno...@hq.doe.gov
Re: How to script commands at startup
>> On Mon, 18 Jul 2011 11:16:18 -0400, "Pagnotta, Pam (CONTR)" >> said: > Does anyone know how to write a script, or can point me to something > that will issue TSM commands from an administrator session shortly > after the server is restarted? There are several possibilities, none of them particularly delightful. + You can define an administrative credential which has the power to do the stuff you want done, stick the password in a script file somewhere, and run the command with e.g. dsmadmc -id=[whatever] -password=[whatever] (-server=whatever?) run [SCRIPT NAME] + You can define a schedule inside the server that runs, say, every hour; this schedule will run your script. Call this SCHED-1 Then you define _another_schedule to run every hour. This one does two things: looks to see if it's been less than (say) two hours since the server started. If so, it should activate SCHED-1. If it's been _more_ than two hours, then it should _de_activate SCHED-1. There are probably other ways to handle this too but these are the ones I've contemplated in the past. - Allen S. Rout
Re: snapdiff advice
We're running 8.0.1P3 on an n6210 gateway, in front of an SVC. The error we get is: >tsm> incr -snapdiff Y: > >Incremental by snapshot difference of volume 'Y:' >ANS2840E Incremental backup using snapshot difference is not supported for Data >ONTAP file server version '0.0.0'. Upgrade the file server 'x.x.x.x' to Dat >a ONTAP version '7.3' or later in order to perform incremental backup >operations > using snapshot difference. >ANS2832E Incremental by snapshot difference failed for >\\10.16.78.101\test_cifs. > Please see error log for details. >ANS5283E The operation was unsuccessful. I'll be opening an ETR on this, but if anyone has any ideas, let me know. Thanks! Note that TSM thinks the ONTAP version is '0.0.0' for some reason. ..Paul At 01:31 PM 7/15/2011, Frank Ramke wrote: >Hi Paul, > >8.0.1 should work. Ensure the NetApp user id has sufficient capabilities >and that it's password is not expired. > > >Frank Ramke > > > >From: Paul Zarnowski >To: ADSM-L@vm.marist.edu >Date: 07/15/2011 12:10 PM >Subject:Re: snapdiff advice >Sent by:"ADSM: Dist Stor Manager" > > > >David, > >Did you get this working with 8.0.1? We're getting this error: > >>tsm> incremental -snapdiff Y: -diffsnapshot=latest >> >>Incremental by snapshot difference of volume 'Y:' >>ANS2840E Incremental backup using snapshot difference is not supported >for Data >>ONTAP file server version '0.0.0'. Upgrade the file server '10.16.78.101' >to Dat >>a ONTAP version '7.3' or later in order to perform incremental backup >operations >> using snapshot difference. >>ANS2832E Incremental by snapshot difference failed for >\\10.16.78.101\test_cifs. >> Please see error log for details. >>ANS5283E The operation was unsuccessful. > > >At 03:41 PM 6/29/2011, David Bronder wrote: >>Clark, Margaret wrote: >>> >>> Back in March, I watched a recorded presentation about DB2 reorgs >>> within TSM server 6.2.2.0, and discovered that OnTap will only allow >>> snapdiff backups to work correctly with releases 7.3.3 and 8.1, NOT >>> 8.0. Apparently OnTap 7.3.3 and 8.1 contain the File Access Protocol >>> (FAP), but 8.0 does not, so snapdiff would fail. - Margaret Clark >> >>My understanding is that it's more convoluted than that, but the FAP >>and Unicode support for ONTAP 8 came with version 8.0.1, not 8.1. >>So I should be good to go on my array running 8.0.1P5 with a 6.2.2.0 >>or newer TSM client. (My NFS testing is on an older array at 7.3.2, >>but that should still be OK if there are no Unicode filenames. Even >>if there were, it should fail in a different way than I'm seeing.) >> >>-- >>Hello World.David Bronder - Systems >Admin >>Segmentation Fault ITS-EI, Univ. of >Iowa >>Core dumped, disk trashed, quota filled, soda warm. >david-bron...@uiowa.edu > > >-- >Paul ZarnowskiPh: 607-255-4757 >Manager, Storage Services Fx: 607-255-8521 >719 Rhodes Hall, Ithaca, NY 14853-3801Em: p...@cornell.edu -- Paul ZarnowskiPh: 607-255-4757 Manager, Storage Services Fx: 607-255-8521 719 Rhodes Hall, Ithaca, NY 14853-3801Em: p...@cornell.edu
Re: Reporting and BIRT in TSM 6.2
Thanks Christian.. I solved 24 hours in arrears by adjusting the collection and warehouse intervals to more frequent occurrence. Collecting at 15 minutes and warehousing at 1 hour. Your suggestion to go directly to the TSM db2 is good, ALL of the data is there and timely. We sometimes use the node contact name, which doesn't seem to appear in the WAREHOUS schema. I found a couple of errors in the BIRT rtp library as delivered on the TSM 6 package. It wasn't correctly identifying failed schedules on the summary chart and node listing. Solved the chart by editing the SchedulesSummary Data Set. Similar edit on the SchedulesMissed data set returns totally incorrect result. Also haven't figured out how to get a "July 11, 2011 6:00 PM" string out of the "111071118000" string value. It appears the leading 1 and trailing 000 are extraneous. I'll be skinning my knees a few times learning to ride this new bicycle. Harold Vandeventer Systems Programmer State of Kansas - DISC harold.vandeven...@da.ks.gov (785) 296-0631 -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Christian Svensson Sent: Sunday, July 17, 2011 1:51 PM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] SV: Reporting and BIRT in TSM 6.2 Hi Harold, I have been working a little bit with BIRT. One thing you need to remember about the Warehouse database is that it is 24 hours behind the real world. You need to open the TSM DB2 database to be accessible direct from TCR and then write reports direct to the TSM Server to be able to get 20 hours backup status. 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: Vandeventer, Harold [BS] [harold.vandeven...@da.ks.gov] Skickat: den 15 juli 2011 18:47 Till: ADSM-L@VM.MARIST.EDU Ämne: Re: Reporting and BIRT in TSM 6.2 I will first admit that I'm a TSM admin, not a "report writer" but we have to come up with a replacement for the reporting component on the TSM 5.x servers. Finally got BIRT Report Designer configured to query the TCR WAREHOUS schema. When previewing a report in BIRT Report Design the schedule start displays as '1110714180036000'. That is somehow to be July 14th, 2011 at 6:00 PM. Running the similar report in Administration Center (Reporting > Common Reporting) properly displays the "Jul 14, 2011 6:00 PM" format. The data is defined as CHAR in Birt, not a date/time as I would expect. I don't know enough DB2 yet to look at the properties in WAREHOUS. Anyone out there working, successfully, with BIRT? At least a few of you are holding out for Cognos in a future release. Thanks...
Filespaces appearing for nodes that have never backed up
Recently, I was asked to delete 2-nodes that were accidentally defined and never used. When I tried to remove the node, it said "filespaces exist" When I do a "q filespace", it returns info for a completely different node: 1:12:27 PM SUN : q filespace persimmon.vcu.edu Node Name Filespace FSID Platform Filespace Is Files-Capacity Pct Name Typepace (MB) Util Unicode? --- --- - - --- - PERSIMMON.VCU.- WALNUT.DOM-1 (?) API:Domi-No 0.0 0.0 EDU DBS noData This has me concerned that I have some kind of database corruption? To further feed my paranoia, when I d a query on the node, I get: 1:15:08 PM SUN : q node persimmon.vcu.edu f=d Node Name: PERSIMMON.VCU.EDU Platform: (?) Client OS Level: (?) Client Version: (?) Policy Domain Name: NOTES Last Access Date/Time: 04/11/2011 11:39:48 Days Since Last Access: 98 Password Set Date/Time: 04/11/2011 11:42:52 Days Since Password Set: 98 Invalid Sign-on Count: 0 Locked?: No Contact: Marie Scott Compression: Client Archive Delete Allowed?: Yes Backup Delete Allowed?: Yes Registration Date/Time: 04/11/2011 11:39:48 Registering Administrator: ZFORRAY Last Communication Method Used: Bytes Received Last Session: 0 Bytes Sent Last Session: 0 Duration of Last Session: 0.00 Pct. Idle Wait Last Session: 0.00 Pct. Comm. Wait Last Session: 0.00 Pct. Media Wait Last Session: 0.00 Optionset: URL: Node Type: Client Password Expiration Period: 0 Day(s) Keep Mount Point?: No Maximum Mount Points Allowed: 1 Auto Filespace Rename : No Validate Protocol: No TCP/IP Name: TCP/IP Address: Globally Unique ID: Transaction Group Max: 0 Data Write Path: ANY Data Read Path: ANY Session Initiation: ClientOrServer High-level Address: 128.172.184.1 Low-level Address: 1501 Collocation Group Name: Proxynode Target: Proxynode Agent: Node Groups: Email Address: Deduplication: ServerOnly Client OS Name: Client Processor Architecture: Client Target Version: (?) Note that almost everything is blank, as it should be. However, the "High-level Address" is not a valid IP address/not assigned to anything. So where did it get this info from? Any ideas what could be going on? This is a 6.2.2.0 server on RH Linux. 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
Determing how much of a tsm server's data is active
Tsm server 5.5.4. running on Suse linux sles9. I am being asked for how much of my server's data is active data. I have seen the type=allactive and preview=yes in the export node command. Is there a better way? Maybe something like A query to sum file_size in contents for each active object? Not sure how to construct such a query. Just a pointer in the right direction will do. Thanks for the help. Gary Lee Senior System Programmer Ball State University phone: 765-285-1310
Re: Filespaces appearing for nodes that have never backed up
I believe I've seen similar when the node was renamed. At least in a Windows environment. The filespaces were ID'd with the former name. Maybe a backup did run? Harold Vandeventer Systems Programmer State of Kansas - DISC harold.vandeven...@da.ks.gov (785) 296-0631 -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Zoltan Forray/AC/VCU Sent: Monday, July 18, 2011 12:21 PM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Filespaces appearing for nodes that have never backed up Recently, I was asked to delete 2-nodes that were accidentally defined and never used. When I tried to remove the node, it said "filespaces exist" When I do a "q filespace", it returns info for a completely different node: 1:12:27 PM SUN : q filespace persimmon.vcu.edu Node Name Filespace FSID Platform Filespace Is Files-Capacity Pct Name Typepace (MB) Util Unicode? --- --- - - --- - PERSIMMON.VCU.- WALNUT.DOM-1 (?) API:Domi-No 0.0 0.0 EDU DBS noData This has me concerned that I have some kind of database corruption? To further feed my paranoia, when I d a query on the node, I get: 1:15:08 PM SUN : q node persimmon.vcu.edu f=d Node Name: PERSIMMON.VCU.EDU Platform: (?) Client OS Level: (?) Client Version: (?) Policy Domain Name: NOTES Last Access Date/Time: 04/11/2011 11:39:48 Days Since Last Access: 98 Password Set Date/Time: 04/11/2011 11:42:52 Days Since Password Set: 98 Invalid Sign-on Count: 0 Locked?: No Contact: Marie Scott Compression: Client Archive Delete Allowed?: Yes Backup Delete Allowed?: Yes Registration Date/Time: 04/11/2011 11:39:48 Registering Administrator: ZFORRAY Last Communication Method Used: Bytes Received Last Session: 0 Bytes Sent Last Session: 0 Duration of Last Session: 0.00 Pct. Idle Wait Last Session: 0.00 Pct. Comm. Wait Last Session: 0.00 Pct. Media Wait Last Session: 0.00 Optionset: URL: Node Type: Client Password Expiration Period: 0 Day(s) Keep Mount Point?: No Maximum Mount Points Allowed: 1 Auto Filespace Rename : No Validate Protocol: No TCP/IP Name: TCP/IP Address: Globally Unique ID: Transaction Group Max: 0 Data Write Path: ANY Data Read Path: ANY Session Initiation: ClientOrServer High-level Address: 128.172.184.1 Low-level Address: 1501 Collocation Group Name: Proxynode Target: Proxynode Agent: Node Groups: Email Address: Deduplication: ServerOnly Client OS Name: Client Processor Architecture: Client Target Version: (?) Note that almost everything is blank, as it should be. However, the "High-level Address" is not a valid IP address/not assigned to anything. So where did it get this info from? Any ideas what could be going on? This is a 6.2.2.0 server on RH Linux. 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: Filespaces appearing for nodes that have never backed up
On Jul 18, 2011, at 1:21 PM, Zoltan Forray/AC/VCU wrote: > ... >High-level Address: 128.172.184.1 > Low-level Address: 1501 > ... > Note that almost everything is blank, as it should be. However, the > "High-level Address" is not a valid IP address/not assigned to anything. > So where did it get this info from? Possibly, came from Set SERVERHladdress and Set SERVERLladdress values related to defining the client to perform storage agent functions, in LAN-free operations. You may find more info in logs on the Persimmon machine. Richard Sims
Re: Determing how much of a tsm server's data is active
If your clients are doing unfettered incremental backups of file systems, then the following would yield a MB approximation, very quickly: SELECT SUM(CAPACITY*PCT_UTIL/100) FROM FILESPACES which is based upon TSM's information about the file system as gotten from the last client operation. By definition, the files on the client represent all the Active files in TSM storage where the activity is incremental backups. Richard Sims
Re: Filespaces appearing for nodes that have never backed up
No Storage Agents. Not doing LAN-free. The PERSIMMON server is a Windoz box. The IP address shown is part of a block of reserved addresses not in use. We don't set HLA/LLA when defining nodes. The other server (WALNUT) whose Domino/TDP backups it is listing, IP address is 128.172.14.87 - whole different part of the university, subnet-wise. I doubt if I will ever find out what has happened. Hopefully it is not damage to the DB. Thanks for the ideas! From: Richard Sims To: ADSM-L@VM.MARIST.EDU Date: 07/18/2011 02:33 PM Subject: Re: [ADSM-L] Filespaces appearing for nodes that have never backed up Sent by: "ADSM: Dist Stor Manager" On Jul 18, 2011, at 1:21 PM, Zoltan Forray/AC/VCU wrote: > ... >High-level Address: 128.172.184.1 > Low-level Address: 1501 > ... > Note that almost everything is blank, as it should be. However, the > "High-level Address" is not a valid IP address/not assigned to anything. > So where did it get this info from? Possibly, came from Set SERVERHladdress and Set SERVERLladdress values related to defining the client to perform storage agent functions, in LAN-free operations. You may find more info in logs on the Persimmon machine. Richard Sims
Scalar 50 support TSM 6.2?
Hi all Scalar 50 tape drives is supported for TSM 6.2 ? thanks in advance, velavan +-- |This was sent by rvela...@gmail.com via Backup Central. |Forward SPAM to ab...@backupcentral.com. +--
Re: Scalar 50 support TSM 6.2?
http://www-01.ibm.com/software/sysmgmt/products/support/IBM_TSM_Supported_Devices_for_AIXHPSUNWIN.html and more specifically: https://www-304.ibm.com/support/docview.wss?rs=663&uid=swg21273206 On Mon, Jul 18, 2011 at 9:59 PM, lavan wrote: > Hi all > > Scalar 50 tape drives is supported for TSM 6.2 ? > > thanks in advance, > velavan > > +-- > |This was sent by rvela...@gmail.com via Backup Central. > |Forward SPAM to ab...@backupcentral.com. > +-- >
Re: Determing how much of a tsm server's data is active
with a side-note that this figure includes data that may be excluded from backup. As long as you don't exclude too much, that would be ok. If you have many databases, and/or long exclude lists YMMV. On 18 jul 2011, at 20:42, Richard Sims wrote: > If your clients are doing unfettered incremental backups of file systems, > then the following would yield a MB approximation, very quickly: > SELECT SUM(CAPACITY*PCT_UTIL/100) FROM FILESPACES > which is based upon TSM's information about the file system as gotten from > the last client operation. By definition, the files on the client represent > all the Active files in TSM storage where the activity is incremental backups. > > Richard Sims -- Met vriendelijke groeten/Kind Regards, Remco Post r.p...@plcs.nl +31 6 248 21 622
