Re: TSM Storage Pool Hierarchy Question
Curt, The hierarchy will eventually look like this: Remote Server (RS) Disk Cache -Main Server (MS) Disk Cache -MS Tape Pool -MS Offsite Copy Pool Questions I have: 1) Is this possible? Yes, no problems - you create a DEVCLASS of type SERVER, then a storage pool that uses that DEVCLASS. Primary backup goes to your local DISK storage pool, with the NEXT storage pool as the one with the devclass of type server. Keep in mind, that the MS will see these as ARCHIVES (and will be unaware of the contents of the archives), so make sure your management class is set appropriately (for the storage hierarchy) - and doesnt expire them. Leave the expiration responsibility to RS. Run Reconcile Volumes (help reconcile volumes to see what it does) frequently, to make sure things are in sync - and investigate why remote volumes are out of sync (if they become that way). 2) Can I do this without the DR module? Yes 3) How does the RS backup it's database - because it won't backup to the local disk? You can send your RS backups to the DEVCLASS (of type server), so that they are stored there as well. Make sure you keep a CURRENT copy of your VOLHIST backup file (backup volhistory) - so that if you need it, you can recover those volumes. (Remember the MS wont have any idea of the contents of the backups from RS - it only sees them as archive blobs.). 3b) Should the RS backup it's DB directly to tape? and if so, how is it possible to share the tape library with no NAS? Either to tape if you can, or to a FILE devclass and ship them off somewhere, so that they are easily accessible. (EG: Backup to devclass FILE, which might be C:\TSM\FILECLASS, then have a FTP job that collects them and moves them somewhere else, for DR availability.) Sharing the tape library does require a SAN or shared SCSI connections and depends on the library - I have no first hand experience, so I'm sure somebody else will comment. 4) Should I just break down and put some tape drives out there to handle the DBs? No, you can use your network and other tools (ftp, etc) to save you on the cost of the drives, and the tape jockey (to make sure that the correct tape is loaded, etc). Make sure you have the process right though, and TEST IT - you dont want to test it when a DR is in progress! ...deon --- Have you looked at the A/NZ Tivoli User Group website? http://www.tuganz.org Deon George, IBM Tivoli Software Engineer, IBM Australia Office: +61 3 9626 6058, Fax: +61 3 9626 6622, Mobile: +61 412 366 816, IVPN +70 66058 mailto:[EMAIL PROTECTED], http://www.ibm.com/tivoli
Re: Online DB Reorg
I did this for a subset of our clients, mainly the Unix clients, because they were more copperative than the Intel clients. Andy Carlson|\ _,,,---,,_ Senior Technical Specialist ZZZzz /,`.-'`'-. ;-;;,_ BJC Health Care|,4- ) )-,_. ,\ ( `'-' St. Louis, Missouri '---''(_/--' `-'\_) Cat Pics: http://andyc.dyndns.org/animal.html On Sat, 18 Oct 2003, Talafous, John G. wrote: I too will some day in the future need to reorg a TSM database. I am currently working to split our 122GB database into two TSM instances. I will be doing the same as Andy!!! Andy, Do I understand correctly that you simply pointed clients to the new server and did a full backup and some time later deleted the old node from the old server? Remco, Would you be willing to share your SQL query that reports on DB fragmentation? Thanks to all, John G. Talafous IS Technical Principal The Timken CompanyGlobal Software Support P.O. Box 6927 Data Management 1835 Dueber Ave. S.W. Phone: (330)-471-3390 Canton, Ohio USA 44706-0927 Fax : (330)-471-4034 [EMAIL PROTECTED] http://www.timken.com
DsmLabel problem
Good morning, I´m on 5.1.7.0 on w2k SP3 and DLT7000 drives in STK9710. I used dsmlabel 'dsmlabel -library=lb0.0.0.8 -drive=mt3.0.0.4,1032 -drive=mt4.0.0.4,1033 -drive=mt5.0.0.6,1034 -drive=mt8.0.0.6,1035 -keep -overwrite -barcode'. All went fine, then I used 'checkin libv stk9710 search=yes checkl=barcode status=scratch' and added all new tapes to my scratch pool. And now when TSM try to use thoose tapes grr. 10/17/2003 16:48:30 ANR8337I DLT volume 02 mounted in drive DRIVE4 (mt5.0.0.6). 10/17/2003 16:48:30 ANR1340I Scratch volume 02 is now defined in storage pool 9710COLLO. 10/17/2003 16:48:30 ANR1411W Access mode for volume 02 now set to read-only due to write error. 10/17/2003 16:48:35 ANR1341I Scratch volume 02 has been deleted from storage pool 9710COLLO. 10/17/2003 16:49:05 ANR8468I DLT volume 02 dismounted from drive DRIVE4 (mt5.0.0.6) in library STK9710. I did a Checkout of my dsmlabled tapes and issued 'label libv stk9710 search=bulk labels=barcode checkin=scartch overwrite=yes'. It works! The reason why I first used dsmlable was the tapes that I got from another site was already labled with with same volumenames that existed in my TSM server. So I had to scatch the volumename and define new. Any thought why dsmlabel didnt work i.e. why did I have to use 'label libv' too? //Henrik --- The information contained in this message may be CONFIDENTIAL and is intended for the addressee only. Any unauthorised use, dissemination of the information or copying of this message is prohibited. If you are not the addressee, please notify the sender immediately by return e-mail and delete this message. Thank you.
Re: Clock Change
Besides that on 5.2 aix server worry if your libc version is lower than stated. We are now patching a lot of servers -Original Message- From: David Longo [mailto:[EMAIL PROTECTED] Sent: Saturday, October 18, 2003 9:33 PM To: [EMAIL PROTECTED] Subject: Re: Clock Change I think this was something that popped up in AIX 4.3.3 somewhere around Maint Level 9 - 10 or so. We had that last Fall here. David B. Longo System Administrator Health First, Inc. 3300 Fiske Blvd. Rockledge, FL 32955-4305 PH 321.434.5536 Pager 321.634.8230 Fax:321.434.5509 [EMAIL PROTECTED] [EMAIL PROTECTED] 10/18/03 11:58AM IF you are running AIX, you should heed the following warning emailed by IBM. More than just ITSM can become loused up. In a nutshell, type echo $TZ and if there are two trailing commas, worry! Roger Deschner University of Illinois at Chicago [EMAIL PROTECTED] = Time is nature's way of making sure == === that everything doesn't happen at once. On Fri, 17 Oct 2003, Herkenrath, Wolfgang wrote: Hi everybody, does anyone know wether I have to do something before clock change on October, 25. I have a TSM-Server on OS/390 and one on Unix. TSM-Version 5.1.6.2. TIA Gruß, Herkenrath forwarded note below -- From [EMAIL PROTECTED] Sat Oct 18 10:49:40 2003 Date: Thu, 16 Oct 2003 10:56:39 AM CST From: [EMAIL PROTECTED] Subject: SPECIAL NOTICE: Technical Support Bulletin [IMAGE] [IMAGE] [IMAGE] You have received this email because [EMAIL PROTECTED] is subscribed to support bulletins for selected topics. Following are updates for one or more of the topics you requested. System clock may become incorrect during daylight savings time changes. IBM recommends you take immediate action. Customers running AIX 4.3 or AIX 5.1 need to read ITEM 1. Customers running AIX 5.2 need to read both ITEM 1 and ITEM 2. The information in this bulletin is not available for viewing via the web. If this information is important to you, please retain this email. ITEM 1 IBM released fixes in 2002 for AIX 4.3, AIX 5.1, and AIX 5.2 but some customers may not have applied the fixes. We recommend you verify all your AIX systems have the fix applied. Without the fix applied, the daylight savings time change may not occur properly which could cause time sensitive applications to malfunction. Run lslpp -L bos.rte.date and compare the output with the following list. The fileset should be at or above the level in this list. AIX 4.3.3 bos.rte.date 4.3.3.77 AIX 5.1 bos.rte.date 5.1.0.26 AIX 5.2 bos.rte.date 5.2.0.1 The fixes are available for immediate downloading at the AIX Fix Delivery Center located at https://techsupport.services.ibm.com/server/aix.fdc IMPORTANT The fix corrects the programs that created the error but does not fix the variable setting itself. After applying the fix you must take the following actions. Action 1 Reset the time zone variable TZ if echo $TZ output includes one or more commas. To reset the variable, run smitty chtz. Action 2 If you reset the time zone variable because it included one or more commas, then either refresh the cron daemon and restart all applications that read the time zone environment variable -or- reboot the system. Reference information: 4.3 APAR IY34798 SMITTY CHTZ APPENDING 2 COMMAS AFTER TZ 5.1 APAR IY34203 SMITTY CHTZ APPENDING 2 COMMAS AFTER TZ 5.2 APAR IY35629 SMITTY CHTZ APPENDING 2 COMMAS AFTER TZ ITEM 2 IBM relased a fix in March 2003 for AIX 5.2 but some customers may not have applied the fix. We recommend you verify all your AIX systems have the fix applied. Without the fix applied, systems that use daylight savings time offsets may not properly change time at the correct time. This could cause time sensitive applications to malfunction. An offset in DST is not widely used. You do not need to apply the fix if you do not use a DST offset. Run lslpp -L bos.rte.libc and compare the output with the following list. The fileset should be at or above the level in this list. AIX 5.2 bos.rte.libc 5.2.0.10 The fixes are available for immediate downloading at the AIX Fix Delivery Center located at https://techsupport.services.ibm.com/server/aix.fdc IMPORTANT After applying the fix you must take the following action. Action 1 Restart all applications -or- reboot the system. Reference information: 5.2 APAR IY39159 DEFAULT DST TZ SETTINGS WITH AN OFFSET FAILS TO RETURN TO STD IBM, eServer and pSeries are trademarks or registered trademarks of International Business Machines Corporation in the United States or other countries, or both. ## This message is for the named person's use only. It may contain confidential, proprietary, or legally privileged information. No confidentiality or privilege is
Re: SQL select problems
Well you have to be at the right levels of client and server code for the summary table to provide accurate information. I am still at 4.2 for the majoriity of mine so it does not work for me either, but I get what I want by pulling the data out of the activity log into a file ie. QUERY AC BEGIND=TODAY-1 BEGINT=08:00 ENDD=TODAY ENDT=08:00 ORIGINATOR=CLIENT I then parse that file to pull out the detail and summary information I want John Simeon Johnston [EMAIL PROTECTED]@vm.marist.edu on 10/20/2003 09:51:32 PM Please respond to ADSM: Dist Stor Manager [EMAIL PROTECTED] Sent by:ADSM: Dist Stor Manager [EMAIL PROTECTED] To:[EMAIL PROTECTED] cc: Subject:SQL select problems I'm trying to run some select statements and get a summary of the bytes transferred during a backup. No matter what I use, the bytes transferred always = 0. In the msi GUI it all looks good, but the dsmadmc select queries come up w/ 0. Is this a known problem or am I doing something wrong? Why does it always say 0? Is there another table other than 'summary' that will give me a better idea of bytes transferred? I'm slightly worried right now... Basically, WTF is going on? sim ** The information in this E-Mail is confidential and may be legally privileged. It may not represent the views of Scottish and Southern Energy plc. It is intended solely for the addressees. Access to this E-Mail by anyone else is unauthorised. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful. Any unauthorised recipient should advise the sender immediately of the error in transmission. Scottish Hydro-Electric, Southern Electric, SWALEC and S+S are trading names of the Scottish and Southern Energy Group. **
Re: SQL select problems
I'm trying to run some select statements and get a summary of the bytes transferred during a backup. No matter what I use, the bytes transferred always = 0. In the msi GUI it all looks good, but the dsmadmc select queries come up w/ 0. Is this a known problem or am I doing something wrong? Why does it always say 0? Is there another table other than 'summary' that will give me a better idea of bytes transferred? I'm slightly worried right now... Basically, WTF is going on? Two recommendations: 1. When posting, include your client/server levels so we can ascertain whether a given fix may or may not be on your system. 2. Search the mailing list archives for gross problems, as it's almost guaranteed that the issue has been pored over in the past. Indeed, if you search www.adsm.org for summary table, you will see numerous postings referring to the Summary Table as historically unreliable, and that it was broken again in 5.1, fixed via APAR IC33455. See also http://people.bu.edu/rbs/ADSM.QuickFacts Richard Sims, BU
HELP!! . Return code is: 127
hi all,
my problem is the code: 127
after running my postschedule the code error 127 is registered in my
dsmsched.log
look below:
TSM SERVER V4.2.2.0 (Win2k)
TSM Client V4.2.1.0 (Red Hat Linux release 6.2)
- file DSMSCHED.LOG
--
10/21/03 04:43:08 --- SCHEDULEREC STATUS BEGIN
10/21/03 04:43:08 Total number of objects inspected: 118,610
10/21/03 04:43:08 Total number of objects backed up:1,750
10/21/03 04:43:08 Total number of objects updated: 0
10/21/03 04:43:08 Total number of objects rebound: 0
10/21/03 04:43:08 Total number of objects deleted: 0
10/21/03 04:43:08 Total number of objects expired: 1
10/21/03 04:43:08 Total number of objects failed: 0
10/21/03 04:43:08 Total number of bytes transferred:38.86 GB
10/21/03 04:43:08 Data transfer time:3,684.83 sec
10/21/03 04:43:08 Network data transfer rate:11,060.34 KB/sec
10/21/03 04:43:08 Aggregate data transfer rate: 9,530.66 KB/sec
10/21/03 04:43:08 Objects compressed by:0%
10/21/03 04:43:08 Elapsed processing time: 01:11:16
10/21/03 04:43:08 --- SCHEDULEREC STATUS END
10/21/03 04:43:08 --- SCHEDULEREC OBJECT END BKP_SERVER1 10/21/03
03:30:00
10/21/03 04:43:08
Executing Operating System command or script:
remove_files.sh
10/21/03 04:43:08 Finished command. Return code is:
127
10/21/03 04:43:08 Scheduled event 'BKP_SERVER1' completed
successfully.
10/21/03 04:43:08 Sending results for scheduled event 'BKP_SERVER1'.
10/21/03 04:43:08 Results sent to server for scheduled event
'BKP_SERVER1'.
CONFIG
DSM.SYS
* Sample Client System Options file for UNIX (dsm.sys.smp) *
* This file contains the minimum options required to get started
* using TSM. Copy dsm.sys.smp to dsm.sys. In the dsm.sys file,
* enter the appropriate values for each option listed below and
* remove the leading asterisk (*) for each one.
* If your client node communicates with multiple TSM servers, be
* sure to add a stanza, beginning with the SERVERNAME option, for
* each additional server.
SERVERNAME SERVER_A
PASSWORDACCESS generate
COMMmethod TCPip
TCPPort1500
TCPServeraddress 100.100.100.1
NODENAME server1
ERRORLOGRETENTION3
SCHEDLOGRETENTION3
ERRORLOGNAME /opt/tivoli/tsm/client/ba/bin/dsmerror.log
SCHEDLOGNAME /opt/tivoli/tsm/client/ba/bin/dsmsched.log
DOMain ALL-LOCAL
INCLUDE /
INCLUDE /backup
INCLUDE /boot
INCLUDE /home
INCLUDE /usr
INCLUDE /var
POSTSCHEDULECMD remove_files.sh
PRESCHEDULECMD
the file remove_files.sh it is the same directory of dsm.exe
description of remove_files.sh
cd /backup/oracle/server1/redo_logs/
find . -mtime +2 -type f -exec rm {} \; | tee
/opt/tivoli/tsm/client/ba/bin/remove_files_success
Best Regards,
Elenara
Elenara Geraldo
Senior TSM Administrator
Phone : 55 41 381 7588
Cellular: 55 41 91035796
Re: DsmLabel problem
I used dsmlabel 'dsmlabel -library=lb0.0.0.8 -drive=mt3.0.0.4,1032 -drive=mt4.0.0.4,1033 -drive=mt5.0.0.6,1034 -drive=mt8.0.0.6,1035 -keep -overwrite -barcode'. ... Any thought why dsmlabel didnt work i.e. why did I have to use 'label libv' too? Henrik - My first thought would be that you seem to have given an outside utility (dsmlabel) direction to use drives which may simultaneously in use by the TSM server, resulting in errors, as warned by the Admin Ref manual. This may have resulted in a conflict and possible failure of some of the dsmlabel operations. I'd advise sticking with 'label libv' for preparing tapes when your TSM server is up. Richard Sims, BU
Re: Moving from NT TSM to AIX TSM
This is not going to work due to different byte ordering within the word between Windows and AIX!!! Zlatko Krastev IT Consultant Crawford, Lindy [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] 17.10.2003 18:18 Please respond to ADSM: Dist Stor Manager To: [EMAIL PROTECTED] cc: Subject:Moving from NT TSM to AIX TSM Hi TSMers, We are busy trying to test our dr procedures. At the one site we have an Window NT server with TSM 4.2 server and on the other site we have an Aix server with TSM 5.1 server. We want to restore the tsm database from the Windows TSM server to the Aix tsm server. Is this possible to do...??? How can I go about thisany ideas Thank you in advance. Lindy Crawford Information Technology Nedbank Corporate - Property Asset Finance *+27-31-3642185 +27-31-3642946 [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] This email and any accompanying attachments may contain confidential and proprietary information. This information is private and protected by law and accordingly if you are not the intended recipient you are requested to delete this entire communication immediately and are notified that any disclosure copying or distribution of or taking any action based on this information is prohibited. Emails cannot be guaranteed to be secure or free of errors or viruses. The sender does not accept any liability or responsibility for any interception corruption destruction loss late arrival or incompleteness of or tampering or interference with any of the information contained in this email or for its incorrect delivery or non-delivery for whatsoever reason or for its effect on any electronic device of the recipient. If verification of this email or any attachment is required please request a hard-copy version
dsmserv restore db error
Dear listers, Getting some strange behavior when I want to restore a db backup. After formating the log and mounting the database tape dsmserv gives me the following error. anrd icstrame.c bla bla invalid record header found in input stream, magic=0087 Anyone seent - solved this. I am running on w2k sp 3 tsm 5151 lto1 3583lib. throw a dog a bone... thnx. Koen _ Help STOP SPAM with the new MSN 8 and get 2 months FREE* http://join.msn.com/?page=features/junkmail
Re: Database fragmentation formula (was Re: Online DB Reorg)
... Isn't this getting a little off the mark though? Last I checked, almost every database on the planet (yes even pervasive sql) when allocating pages/extents, left an amount of space unutilized at the end. In fact, if you do a reorg in SQL server, it specifically asks how much space you want to remain free in each page. Now why would you want that? So that when you add a row to a table with a clustered index (ie. A primary key, where the table is physically ordered the same as the index) the database does not have to add an extent at the end of the space to house the new row. This cuts down on logical fragmentation which is a far larger killer of databases than the fragmentation that these formulas show. By these formuls, every signle one of my SQL database is 25% fragmented (why, because every Sunday they do online reorgs to fix their logical fragmentation). Logical fragmentation turns large sequential reads into large random reads. ... Indeed, Michael. Distributed free space is a good thing in a random-access structure where inserts are performed. Some may believe that reorganization of a database always packs its contents closely together, yielding excellent adjacency and seek times. But the reload phase of a reorganization has to proceed according to the architecture and algorithms under which the database operates. In a B-tree type database, as the TSM db principally is, the reload insertions may result in a lot of splits and half-occupied pages. As customers have reported in ADSM-L postings, a reload may require twice as much space as their original database size. (This is summarized under topic ADSM DATABASE STRUCTURE AND DUMPDB/LOADDB in http://people.bu.edu/rbs/ADSM.QuickFacts .) It takes exceptional circumstance to justify doing such an unload-reload, and then the effects are typically short-lived. Richard Sims, BU
Re: Database fragmentation formula (was Re: Online DB Reorg)
Thank you for the response, If what you say is true, then I will forgo the Reorg concept, as it appears to be a waste of time. -Original Message- From: Richard Sims [mailto:[EMAIL PROTECTED] Sent: Tuesday, October 21, 2003 7:44 AM To: [EMAIL PROTECTED] Subject: Re: Database fragmentation formula (was Re: Online DB Reorg) ... Isn't this getting a little off the mark though? Last I checked, almost every database on the planet (yes even pervasive sql) when allocating pages/extents, left an amount of space unutilized at the end. In fact, if you do a reorg in SQL server, it specifically asks how much space you want to remain free in each page. Now why would you want that? So that when you add a row to a table with a clustered index (ie. A primary key, where the table is physically ordered the same as the index) the database does not have to add an extent at the end of the space to house the new row. This cuts down on logical fragmentation which is a far larger killer of databases than the fragmentation that these formulas show. By these formuls, every signle one of my SQL database is 25% fragmented (why, because every Sunday they do online reorgs to fix their logical fragmentation). Logical fragmentation turns large sequential reads into large random reads. ... Indeed, Michael. Distributed free space is a good thing in a random-access structure where inserts are performed. Some may believe that reorganization of a database always packs its contents closely together, yielding excellent adjacency and seek times. But the reload phase of a reorganization has to proceed according to the architecture and algorithms under which the database operates. In a B-tree type database, as the TSM db principally is, the reload insertions may result in a lot of splits and half-occupied pages. As customers have reported in ADSM-L postings, a reload may require twice as much space as their original database size. (This is summarized under topic ADSM DATABASE STRUCTURE AND DUMPDB/LOADDB in http://people.bu.edu/rbs/ADSM.QuickFacts .) It takes exceptional circumstance to justify doing such an unload-reload, and then the effects are typically short-lived. Richard Sims, BU
Re: TSM Storage Pool Hierarchy Question
1. It is possible 2. No, you need the DRM license (part of Extended Edition) to have server-to-server virtual volumes 3. To the virtual volumes device class, i.e. to a file stored in MS server 3b. Yes, it depends on the destination setting of the MS server copygroup 4. See the answers to q.3 3b. 999. No matter of the setup or version :-) You just need enough RS disks and rather good pipe to MS. Zlatko Krastev IT Consultant Curt Watts [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] 21.10.2003 02:41 Please respond to ADSM: Dist Stor Manager To: [EMAIL PROTECTED] cc: Subject:TSM Storage Pool Hierarchy Question Alright, time to ask the experts! Essentially, I'm trying to have our remote TSM servers (satellite locations) utilize the main TSM server as the next storage pool in it's hierarchy. The hierarchy will eventually look like this: Remote Server (RS) Disk Cache -Main Server (MS) Disk Cache -MS Tape Pool -MS Offsite Copy Pool Questions I have: 1) Is this possible? 2) Can I do this without the DR module? 3) How does the RS backup it's database - because it won't backup to the local disk? 3b) Should the RS backup it's DB directly to tape? and if so, how is it possible to share the tape library with no NAS? 4) Should I just break down and put some tape drives out there to handle the DBs? Current setup: MS: W2k sp4, TSM v4.3.2, IBM 3853 w/ 54 slots 2 LTO drives. RS: W2k sp4, TSM v5.2.0 Thanks everyone. Curt Watts ___ Curt Watts Network Analyst, Capilano College [EMAIL PROTECTED]
What to do with archives when deleting a client
We have systems where we have archived data where I can see the life of the archive data will far out lasting the client system itself. So, say you have a client system that is being removed from service. It's ok to delete all backups for the client and remove the client from TSM. But, the client has archive files that you want to keep. Q) Short of restoring the archives and re-archiving from a different client, is there anyway within TSM to move the archives to a different client? It funny, but I've often thought that there should be a way to archive data so that it isn't attached to any particular client system . . . .maybe there is . . . . Thanks! Richard Rhodes - The information contained in this message is intended only for the personal and confidential use of the recipient(s) named above. If the reader of this message is not the intended recipient or an agent responsible for delivering it to the intended recipient, you are hereby notified that you have received this document in error and that any review, dissemination, distribution, or copying of this message is strictly prohibited. If you have received this communication in error, please notify us immediately, and delete the original message.
Re: dsmserv restore db error
Hi Koen! Are you trying to restore an older (non 5.1) database? I so, you're probably running into APAR IC33690. If I ready the APAR correctly it's not supported to restore an older database on a 5.1 server: http://www-1.ibm.com/support/docview.wss?rs=203context=SWJ00q=invalid+reco rd+header+found+in+input+streamuid=swg1IC33690loc=en_UScs=utf-8lang=en It's suggested to restore the database under the old TSM server level and upgrade that installation by applying the 5.1 release. Kindest regards, Eric van Loon KLM Royal Dutch Airlines -Original Message- From: Koen Willems [mailto:[EMAIL PROTECTED] Sent: Tuesday, October 21, 2003 14:39 To: [EMAIL PROTECTED] Subject: dsmserv restore db error Dear listers, Getting some strange behavior when I want to restore a db backup. After formating the log and mounting the database tape dsmserv gives me the following error. anrd icstrame.c bla bla invalid record header found in input stream, magic=0087 Anyone seent - solved this. I am running on w2k sp 3 tsm 5151 lto1 3583lib. throw a dog a bone... thnx. Koen _ Help STOP SPAM with the new MSN 8 and get 2 months FREE* http://join.msn.com/?page=features/junkmail ** For information, services and offers, please visit our web site: http://www.klm.com. This e-mail and any attachment may contain confidential and privileged material intended for the addressee only. If you are not the addressee, you are notified that no part of the e-mail or any attachment may be disclosed, copied or distributed, and that any other action related to this e-mail or attachment is strictly prohibited, and may be unlawful. If you have received this e-mail by error, please notify the sender immediately by return e-mail, and delete this message. Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its employees shall not be liable for the incorrect or incomplete transmission of this e-mail or any attachments, nor responsible for any delay in receipt. **
Re: Database fragmentation formula (was Re: Online DB Reorg)
Please don't throw the concept out. Like all tools it has it's place. For example, we are thinking about reorg'ing one of our TSM databases. Why? 1) I ran a test reorg of one of our TSM databases on a test system. The db was 80gb in size with 72gb used. It shrunk to 40gb used. As discussed - it won't stay there very long, BUT . . . 2) We are changing our policies to cut down the versions we retain. After things settle down, I would like to run another test reorg. It MAY be worth our while to do a reorg, or maybe not . . . we'll see . . . Rick Hart, Charles [EMAIL PROTECTED]To: [EMAIL PROTECTED] TRONIC.COM cc: (bcc: Richard L. Rhodes/OE/FirstEnergy) Sent by: ADSM: Subject: Re: Database fragmentation formula (was Re: Online DB Dist Stor Reorg) Manager [EMAIL PROTECTED] .EDU 10/21/2003 09:12 AM Please respond to ADSM: Dist Stor Manager Thank you for the response, If what you say is true, then I will forgo the Reorg concept, as it appears to be a waste of time. -Original Message- From: Richard Sims [mailto:[EMAIL PROTECTED] Sent: Tuesday, October 21, 2003 7:44 AM To: [EMAIL PROTECTED] Subject: Re: Database fragmentation formula (was Re: Online DB Reorg) ... Isn't this getting a little off the mark though? Last I checked, almost every database on the planet (yes even pervasive sql) when allocating pages/extents, left an amount of space unutilized at the end. In fact, if you do a reorg in SQL server, it specifically asks how much space you want to remain free in each page. Now why would you want that? So that when you add a row to a table with a clustered index (ie. A primary key, where the table is physically ordered the same as the index) the database does not have to add an extent at the end of the space to house the new row. This cuts down on logical fragmentation which is a far larger killer of databases than the fragmentation that these formulas show. By these formuls, every signle one of my SQL database is 25% fragmented (why, because every Sunday they do online reorgs to fix their logical fragmentation). Logical fragmentation turns large sequential reads into large random reads. ... Indeed, Michael. Distributed free space is a good thing in a random-access structure where inserts are performed. Some may believe that reorganization of a database always packs its contents closely together, yielding excellent adjacency and seek times. But the reload phase of a reorganization has to proceed according to the architecture and algorithms under which the database operates. In a B-tree type database, as the TSM db principally is, the reload insertions may result in a lot of splits and half-occupied pages. As customers have reported in ADSM-L postings, a reload may require twice as much space as their original database size. (This is summarized under topic ADSM DATABASE STRUCTURE AND DUMPDB/LOADDB in http://people.bu.edu/rbs/ADSM.QuickFacts .) It takes exceptional circumstance to justify doing such an unload-reload, and then the effects are typically short-lived. Richard Sims, BU - The information contained in this message is intended only for the personal and confidential use of the recipient(s) named above. If the reader of this message is not the intended recipient or an agent responsible for delivering it to the intended recipient, you are hereby notified that you have received this document in error and that any review, dissemination, distribution, or copying of this message is strictly prohibited. If you have received this communication in error, please notify us immediately, and delete the original message.
Re: Database fragmentation formula (was Re: Online DB Reorg)
Good point for reducing size, other than normal growth why would it not last long, is ther other reasons? Thank you. -Original Message- From: Richard Rhodes [mailto:[EMAIL PROTECTED] Sent: Tuesday, October 21, 2003 8:44 AM To: [EMAIL PROTECTED] Subject: Re: Database fragmentation formula (was Re: Online DB Reorg) Please don't throw the concept out. Like all tools it has it's place. For example, we are thinking about reorg'ing one of our TSM databases. Why? 1) I ran a test reorg of one of our TSM databases on a test system. The db was 80gb in size with 72gb used. It shrunk to 40gb used. As discussed - it won't stay there very long, BUT . . . 2) We are changing our policies to cut down the versions we retain. After things settle down, I would like to run another test reorg. It MAY be worth our while to do a reorg, or maybe not . . . we'll see . . . Rick Hart, Charles [EMAIL PROTECTED]To: [EMAIL PROTECTED] TRONIC.COM cc: (bcc: Richard L. Rhodes/OE/FirstEnergy) Sent by: ADSM: Subject: Re: Database fragmentation formula (was Re: Online DB Dist Stor Reorg) Manager [EMAIL PROTECTED] .EDU 10/21/2003 09:12 AM Please respond to ADSM: Dist Stor Manager Thank you for the response, If what you say is true, then I will forgo the Reorg concept, as it appears to be a waste of time. -Original Message- From: Richard Sims [mailto:[EMAIL PROTECTED] Sent: Tuesday, October 21, 2003 7:44 AM To: [EMAIL PROTECTED] Subject: Re: Database fragmentation formula (was Re: Online DB Reorg) ... Isn't this getting a little off the mark though? Last I checked, almost every database on the planet (yes even pervasive sql) when allocating pages/extents, left an amount of space unutilized at the end. In fact, if you do a reorg in SQL server, it specifically asks how much space you want to remain free in each page. Now why would you want that? So that when you add a row to a table with a clustered index (ie. A primary key, where the table is physically ordered the same as the index) the database does not have to add an extent at the end of the space to house the new row. This cuts down on logical fragmentation which is a far larger killer of databases than the fragmentation that these formulas show. By these formuls, every signle one of my SQL database is 25% fragmented (why, because every Sunday they do online reorgs to fix their logical fragmentation). Logical fragmentation turns large sequential reads into large random reads. ... Indeed, Michael. Distributed free space is a good thing in a random-access structure where inserts are performed. Some may believe that reorganization of a database always packs its contents closely together, yielding excellent adjacency and seek times. But the reload phase of a reorganization has to proceed according to the architecture and algorithms under which the database operates. In a B-tree type database, as the TSM db principally is, the reload insertions may result in a lot of splits and half-occupied pages. As customers have reported in ADSM-L postings, a reload may require twice as much space as their original database size. (This is summarized under topic ADSM DATABASE STRUCTURE AND DUMPDB/LOADDB in http://people.bu.edu/rbs/ADSM.QuickFacts .) It takes exceptional circumstance to justify doing such an unload-reload, and then the effects are typically short-lived. Richard Sims, BU - The information contained in this message is intended only for the personal and confidential use of the recipient(s) named above. If the reader of this message is not the intended recipient or an agent responsible for delivering it to the intended recipient, you are hereby notified that you have received this document in error and that any review, dissemination, distribution, or copying of this message is strictly prohibited. If you have received this communication in error, please notify us immediately, and delete the original message.
/ /OREF:CPTB7E3A deleting volumes
We need to run manual deletion of 6 volumes. i.e. delete volume volume_name discarddata=yes It needs to run synchronously i.e. command runs, finishes and the next command runs. How could I do this in batch mode i.e. via a command line script? Any help appreciated... Cecily Hewlett
Re: / /OREF:CPTB7E3A deleting volumes
try adding wait=yes. Regard, Karel -Oorspronkelijk bericht- Van: Cecily Hewlett [mailto:[EMAIL PROTECTED] Verzonden: dinsdag 21 oktober 2003 15:52 Aan: [EMAIL PROTECTED] Onderwerp: / /OREF:CPTB7E3A deleting volumes We need to run manual deletion of 6 volumes. i.e. delete volume volume_name discarddata=yes It needs to run synchronously i.e. command runs, finishes and the next command runs. How could I do this in batch mode i.e. via a command line script? Any help appreciated... Cecily Hewlett
Re: HELP!! . Return code is: 127
hi,
i think you should play with your rm-script.
Why do you use the ' |tee ' ?
What about the user-rights of the script.
The scheduler seem to work right, because tsm tells no error.
Michael Kinderman
Wuerzburg/Germany
Am Dienstag, 21. Oktober 2003 13:44 schrieb T_MML:
hi all,
my problem is the code: 127
after running my postschedule the code error 127 is registered in my
dsmsched.log
look below:
TSM SERVER V4.2.2.0 (Win2k)
TSM Client V4.2.1.0 (Red Hat Linux release 6.2)
- file DSMSCHED.LOG
--
10/21/03 04:43:08 --- SCHEDULEREC STATUS BEGIN
10/21/03 04:43:08 Total number of objects inspected: 118,610
10/21/03 04:43:08 Total number of objects backed up:1,750
10/21/03 04:43:08 Total number of objects updated: 0
10/21/03 04:43:08 Total number of objects rebound: 0
10/21/03 04:43:08 Total number of objects deleted: 0
10/21/03 04:43:08 Total number of objects expired: 1
10/21/03 04:43:08 Total number of objects failed: 0
10/21/03 04:43:08 Total number of bytes transferred:38.86 GB
10/21/03 04:43:08 Data transfer time:3,684.83 sec
10/21/03 04:43:08 Network data transfer rate:11,060.34 KB/sec
10/21/03 04:43:08 Aggregate data transfer rate: 9,530.66 KB/sec
10/21/03 04:43:08 Objects compressed by:0%
10/21/03 04:43:08 Elapsed processing time: 01:11:16
10/21/03 04:43:08 --- SCHEDULEREC STATUS END
10/21/03 04:43:08 --- SCHEDULEREC OBJECT END BKP_SERVER1 10/21/03
03:30:00
10/21/03 04:43:08
Executing Operating System command or script:
remove_files.sh
10/21/03 04:43:08 Finished command. Return code is:
127
10/21/03 04:43:08 Scheduled event 'BKP_SERVER1' completed
successfully.
10/21/03 04:43:08 Sending results for scheduled event 'BKP_SERVER1'.
10/21/03 04:43:08 Results sent to server for scheduled event
'BKP_SERVER1'.
CONFIG
DSM.SYS
* Sample Client System Options file for UNIX (dsm.sys.smp) *
* This file contains the minimum options required to get started
* using TSM. Copy dsm.sys.smp to dsm.sys. In the dsm.sys file,
* enter the appropriate values for each option listed below and
* remove the leading asterisk (*) for each one.
* If your client node communicates with multiple TSM servers, be
* sure to add a stanza, beginning with the SERVERNAME option, for
* each additional server.
SERVERNAME SERVER_A
PASSWORDACCESS generate
COMMmethod TCPip
TCPPort1500
TCPServeraddress 100.100.100.1
NODENAME server1
ERRORLOGRETENTION3
SCHEDLOGRETENTION3
ERRORLOGNAME /opt/tivoli/tsm/client/ba/bin/dsmerror.log
SCHEDLOGNAME /opt/tivoli/tsm/client/ba/bin/dsmsched.log
DOMain ALL-LOCAL
INCLUDE /
INCLUDE /backup
INCLUDE /boot
INCLUDE /home
INCLUDE /usr
INCLUDE /var
POSTSCHEDULECMD remove_files.sh
PRESCHEDULECMD
the file remove_files.sh it is the same directory of dsm.exe
description of remove_files.sh
cd /backup/oracle/server1/redo_logs/
find . -mtime +2 -type f -exec rm {} \; | tee
/opt/tivoli/tsm/client/ba/bin/remove_files_success
Best Regards,
Elenara
Elenara Geraldo
Senior TSM Administrator
Phone : 55 41 381 7588
Cellular: 55 41 91035796
Re: What to do with archives when deleting a client
Why remove the client node definition? You don't have to license nodes that you aren't backing up. (How many processors does that node have? Zero). [EMAIL PROTECTED] 10/21/2003 9:30:06 AM We have systems where we have archived data where I can see the life of the archive data will far out lasting the client system itself. So, say you have a client system that is being removed from service. It's ok to delete all backups for the client and remove the client from TSM. But, the client has archive files that you want to keep. Q) Short of restoring the archives and re-archiving from a different client, is there anyway within TSM to move the archives to a different client? It funny, but I've often thought that there should be a way to archive data so that it isn't attached to any particular client system . . . .maybe there is . . . . Thanks! Richard Rhodes - The information contained in this message is intended only for the personal and confidential use of the recipient(s) named above. If the reader of this message is not the intended recipient or an agent responsible for delivering it to the intended recipient, you are hereby notified that you have received this document in error and that any review, dissemination, distribution, or copying of this message is strictly prohibited. If you have received this communication in error, please notify us immediately, and delete the original message.
Re: dsmserv restore db error
anrd icstrame.c bla bla invalid record header found in input stream, magic=0087 Koen - When restoring a TSM server, it is starting out from nothing and needs to be accurately told what its devices (devclasses) are, which is the role of the devconfig file. Check that the one you are using is accurate, so that TSM can proceed to properly process its restoral data: that is a common foible in this situation. Richard Sims, BU
Re: Database fragmentation formula (was Re: Online DB Reorg)
Good point for reducing size, other than normal growth why would it not last long, is ther other reasons? Charles - Normal daily TSM activity makes for a lot of db updating which rather rapidly returns the db to a condition akin to that before the db reorg. Entropy, and all that. Richard Sims, BU
Re: What to do with archives when deleting a client
No, there isn't any way to archive data so that it isn't attached to a particular client. And there isn't really any reason you can't leave the archives attached to the old node name; once the old node name has been idle for 30 days, it will drop from your license count, it doesn't cost you anything just to let it sit there. If you really want to move the data to another client, there is a hokey way to do it, requiring some work: Assume the client that is going away is called SOURCE, and the client you are keeping is called TARGET. 1) If SOURCE and TARGET aren't in the same domain, make sure that TARGET has the same management class names (for archives) as the SOURCE domain. 2) On the TSM server, rename node TARGET to OTHER. 3) On the TSM server, rename node SOURCE to TARGET. 4) EXPORT the archive data from what is now TARGET: EXPORT NODE TARGET FILEDATA=ARCHIVE ... 5) Rename everybody back to their original names. You now have SOURCE=SOURCE, and TARGET=TARGET, but the archive data from SOURCE was exported under the name TARGET. 6) IMPORT the data. That will work if the TARGET machine doesn't already have archives with the same filespace names. If it DOES already have archives with the same filespace names, you have to play the same games with the filespace names before doing the EXPORT. -Original Message- From: Richard Rhodes [mailto:[EMAIL PROTECTED] Sent: Tuesday, October 21, 2003 9:30 AM To: [EMAIL PROTECTED] Subject: What to do with archives when deleting a client We have systems where we have archived data where I can see the life of the archive data will far out lasting the client system itself. So, say you have a client system that is being removed from service. It's ok to delete all backups for the client and remove the client from TSM. But, the client has archive files that you want to keep. Q) Short of restoring the archives and re-archiving from a different client, is there anyway within TSM to move the archives to a different client? It funny, but I've often thought that there should be a way to archive data so that it isn't attached to any particular client system . . . .maybe there is . . . . Thanks! Richard Rhodes - The information contained in this message is intended only for the personal and confidential use of the recipient(s) named above. If the reader of this message is not the intended recipient or an agent responsible for delivering it to the intended recipient, you are hereby notified that you have received this document in error and that any review, dissemination, distribution, or copying of this message is strictly prohibited. If you have received this communication in error, please notify us immediately, and delete the original message.
TSM Downward Scaleability
The organization that I work for deploys TSM quite sucessfully at its large main sites that serve some +4000 nodes. It is very apparent that TSM scales upwardly very well but I believe that scaling down is something else. MY question is this:How can similar services be delivered to sites where there are less than ten nodes, limited bandwidth, no system administrators and, most importantly, tiny budgets. The organization can comfortably absorb the price of software and TSM licensing for these sites but there';s no budget to equip each site with a dual tape drive library. What are the alternatives? An autoloader, for example.?? __ Post your free ad now! http://personals.yahoo.ca
Re: TSM Downward Scaleability
Actually there are some 2-drive tiny LTO and AIT libraries that are very affordable; that's the best alternative. If you can't do that, consider backing up over the WAN. Whether it's practical depends on the type size of the remote clients, but if they aren't huge, it's possible. The initial backup will take a long time (so what, do it on the weekend). But If you use client compression AND enable subfile backup, the daily backups may be very manageable. That will give your remote sites the ability to do ad hoc restores, usually, with no problem. And your site becomes their vault, so disaster recovery is taken care of. That leaves the big problem to be LARGE restores - e.g., suppose a hard disk dies on the remote client and requires 30GB to be restored. If you are lucky enough to have a fairly homogenous client population, for this case you could consider keeping a spare server at your main site; rebuild it locally and then fed-ex it out to the remote site instead of taking days to restore with limited bandwidth. If they need rebuilds faster than that - they gotta get budgets for local tape! -Original Message- From: Douglas Currell [mailto:[EMAIL PROTECTED] Sent: Tuesday, October 21, 2003 10:54 AM To: [EMAIL PROTECTED] Subject: TSM Downward Scaleability The organization that I work for deploys TSM quite sucessfully at its large main sites that serve some +4000 nodes. It is very apparent that TSM scales upwardly very well but I believe that scaling down is something else. MY question is this:How can similar services be delivered to sites where there are less than ten nodes, limited bandwidth, no system administrators and, most importantly, tiny budgets. The organization can comfortably absorb the price of software and TSM licensing for these sites but there';s no budget to equip each site with a dual tape drive library. What are the alternatives? An autoloader, for example.?? __ Post your free ad now! http://personals.yahoo.ca
Re: Database fragmentation formula (was Re: Online DB Reorg)
I have to ask one thing about all this higher math - Does it matter? That is, what can you do about it, or what should you do about it? I think the answer is that, even if these competing formulae are correct and you discover your database is fragmented, there is practically nothing you can or should actually do. Except in the case where a TSM system is being deliberately shrunk, such as by removing a bunch of nodes, there is nothing you should attempt to do about database fragmentation. Fragmentation occurs at three levels, as far as I can tell. But any speculation on my part as to what those three levels are is just that - speculation. And conjecture from external observation. I do know that there is fragmentation within TSM's storage units, and then there is fragmentaiton of TSM's units within the OS file system's storage units. Measuring or fixing the former involves the lengthly and risky unload/reload procedure which I do not ever recommend. I suspect I can see the latter, by comparing the amount of free space shown by Q DBVOL F=D, and the amount of free space shown by Q DB. I could correct fragmentation at that level with DELETE DBVOL, which is easier than unload/reload, but it still won't achieve much and the effect still won't last. So all this mathematics still does not give me much to go on, in terms of how to make my TSM system run better in the long term. I ran that first SELECT published in this thread on my system and came up with -0.04% fragmented. Obviously a flawed formula. I know my database is fragmented, simply because it is old and big. But what you can do, that will help, is to just give it enough room and let it spread itself out far enough that it can usually get contiguous space, at all levels including the physical level, when it wants to write something that is large enough to span multiple units, whatever those units are. A full, fragmented database will defragment itself to a degree after it has been run with additional space for a while. Throw more disk drives at the problem. An 80% full database of any kind WILL run faster than a 98% full database. Of that I am very, very certain. Roger Deschner University of Illinois at Chicago [EMAIL PROTECTED] Have you ever, like, tried to put together a bicycle in public? Or a grill? Astronauts David Wolf and Piers Sellers, explaining the difficulties encountered in attaching equipment to the Space Station
Re: TSM Downward Scaleability
Hi Doug, I agree with Wanda entirely. This very debate arose within out organization when we deployed TSM a couple of years ago. We have about a dozen remote offices which have no TSM server at their local site. We implemented our configuration almost precisely as Wanda described, minus the sub-file backups. Our business requirements are such that we have one day to restore a down server in these remote offices. Thus, we have installed DDS4 tape drives in each remote server as well as one on our TSM servers. Should failure occur, we generate a backupset (about 2-3 hours), travel to the remote office (1-6 hours), repair the server(?? hours) and then restore from the backupset 2-3 hours). This solution has worked well for us as we have used it to recover several servers, and was cheap to implement! Hope that helps! Chris Murphy IT Network Analyst Idaho Dept. of Lands Office: (208) 334-0293 [EMAIL PROTECTED] -Original Message- From: Prather, Wanda [mailto:[EMAIL PROTECTED] Sent: Tuesday, October 21, 2003 9:11 AM To: [EMAIL PROTECTED] Subject: Re: TSM Downward Scaleability Actually there are some 2-drive tiny LTO and AIT libraries that are very affordable; that's the best alternative. If you can't do that, consider backing up over the WAN. Whether it's practical depends on the type size of the remote clients, but if they aren't huge, it's possible. The initial backup will take a long time (so what, do it on the weekend). But If you use client compression AND enable subfile backup, the daily backups may be very manageable. That will give your remote sites the ability to do ad hoc restores, usually, with no problem. And your site becomes their vault, so disaster recovery is taken care of. That leaves the big problem to be LARGE restores - e.g., suppose a hard disk dies on the remote client and requires 30GB to be restored. If you are lucky enough to have a fairly homogenous client population, for this case you could consider keeping a spare server at your main site; rebuild it locally and then fed-ex it out to the remote site instead of taking days to restore with limited bandwidth. If they need rebuilds faster than that - they gotta get budgets for local tape! -Original Message- From: Douglas Currell [mailto:[EMAIL PROTECTED] Sent: Tuesday, October 21, 2003 10:54 AM To: [EMAIL PROTECTED] Subject: TSM Downward Scaleability The organization that I work for deploys TSM quite sucessfully at its large main sites that serve some +4000 nodes. It is very apparent that TSM scales upwardly very well but I believe that scaling down is something else. MY question is this:How can similar services be delivered to sites where there are less than ten nodes, limited bandwidth, no system administrators and, most importantly, tiny budgets. The organization can comfortably absorb the price of software and TSM licensing for these sites but there';s no budget to equip each site with a dual tape drive library. What are the alternatives? An autoloader, for example.?? __ Post your free ad now! http://personals.yahoo.ca
Re: TSM Downward Scaleability
The organization that I work for deploys TSM quite sucessfully at its large main sites that serve some +4000 nodes. It is very apparent that TSM scales upwardly very well but I believe that scaling down is something else. MY question is this:How can similar services be delivered to sites where there are less than ten nodes, limited bandwidth, no system administrators and, most importantly, tiny budgets. It's not realistic to have server systems of any kind at a site where there is no technical administration: someone has to be knowledgeable about the systems in order to minimally inspect them visually when there is a problem. Clerical people simply can't serve in that capacity. Remote administration is a feasible concept, but when hardware stops working, knowledgable eyes and experienced hands must be at the site. Such a responsibility might be contracted to an outside company, which can feasibly attend to disparate physical sites. Consider also that while unattended backup, by various means by products of different scales, is not difficult, the backups are done because of the prospect of the need for a restoral, which can involve a full-down computer, and that is beyond the capabilities of clerical people to address: someone has to know what to do, particularly where a collection of office computers will seldom be uniform. TSM is an enterprise product, intended for larger installations, which is to say those where there are concentrated server facilities and network access. As Wanda suggests, backup by remote offices over a WAN is the method of choice where TSM or like backup/restore product are involved. Again, the backup is easy, but restoral can be problematic. Advanced planning is necessary to cover all aspects of backup/restoral needs, which in turn is just a part of a company's larger disaster recovery plan. Richard Sims, BU
Re: TSM Storage Pool Hierarchy Question
Answering only your questions 3, 3b, and 4... For the remote database backups at least, your RS can become a client of the MS, and can back up its database to the MS. From the MS perspective, the RS is just a regular backup/archive client doing an archive operation on a rather big file. The MS stores those DB backups in its storage pool heirarchies just like any other archive files for a client node, including expiring them when they're no longer needed. It's actually better to back up your DB to another TSM system, rather than backing it up to local tape, because it uses far fewer tape volumes by stacking multiple DB backups on a single tape. This setup is fairly well described in the TSM Admin Guide. Evaluate it, however, in terms of disaster recovery - you cannot lose both TSM servers at once, so the two should not be in the same location. I know I am still leaving your first 2 questions unanswered. Roger Deschner University of Illinois at Chicago [EMAIL PROTECTED] On Mon, 20 Oct 2003, Curt Watts wrote: Alright, time to ask the experts! Essentially, I'm trying to have our remote TSM servers (satellite locations) utilize the main TSM server as the next storage pool in it's hierarchy. The hierarchy will eventually look like this: Remote Server (RS) Disk Cache -Main Server (MS) Disk Cache -MS Tape Pool -MS Offsite Copy Pool Questions I have: 1) Is this possible? 2) Can I do this without the DR module? 3) How does the RS backup it's database - because it won't backup to the local disk? 3b) Should the RS backup it's DB directly to tape? and if so, how is it possible to share the tape library with no NAS? 4) Should I just break down and put some tape drives out there to handle the DBs? Current setup: MS: W2k sp4, TSM v4.3.2, IBM 3853 w/ 54 slots 2 LTO drives. RS: W2k sp4, TSM v5.2.0 Thanks everyone. Curt Watts ___ Curt Watts Network Analyst, Capilano College [EMAIL PROTECTED]
Re: What to do with archives when deleting a client
Richard, You might be able to use the mergefilespaces=yes option on the import to avoid the filespace name juggling Wanda mentioned in her caveat. Alex Paschal Freightliner, LLC (503) 745-6850 phone/vmail -Original Message- From: Prather, Wanda [mailto:[EMAIL PROTECTED] Sent: Tuesday, October 21, 2003 7:30 AM To: [EMAIL PROTECTED] Subject: Re: What to do with archives when deleting a client No, there isn't any way to archive data so that it isn't attached to a particular client. And there isn't really any reason you can't leave the archives attached to the old node name; once the old node name has been idle for 30 days, it will drop from your license count, it doesn't cost you anything just to let it sit there. If you really want to move the data to another client, there is a hokey way to do it, requiring some work: Assume the client that is going away is called SOURCE, and the client you are keeping is called TARGET. 1) If SOURCE and TARGET aren't in the same domain, make sure that TARGET has the same management class names (for archives) as the SOURCE domain. 2) On the TSM server, rename node TARGET to OTHER. 3) On the TSM server, rename node SOURCE to TARGET. 4) EXPORT the archive data from what is now TARGET: EXPORT NODE TARGET FILEDATA=ARCHIVE ... 5) Rename everybody back to their original names. You now have SOURCE=SOURCE, and TARGET=TARGET, but the archive data from SOURCE was exported under the name TARGET. 6) IMPORT the data. That will work if the TARGET machine doesn't already have archives with the same filespace names. If it DOES already have archives with the same filespace names, you have to play the same games with the filespace names before doing the EXPORT. -Original Message- From: Richard Rhodes [mailto:[EMAIL PROTECTED] Sent: Tuesday, October 21, 2003 9:30 AM To: [EMAIL PROTECTED] Subject: What to do with archives when deleting a client We have systems where we have archived data where I can see the life of the archive data will far out lasting the client system itself. So, say you have a client system that is being removed from service. It's ok to delete all backups for the client and remove the client from TSM. But, the client has archive files that you want to keep. Q) Short of restoring the archives and re-archiving from a different client, is there anyway within TSM to move the archives to a different client? It funny, but I've often thought that there should be a way to archive data so that it isn't attached to any particular client system . . . .maybe there is . . . . Thanks! Richard Rhodes - The information contained in this message is intended only for the personal and confidential use of the recipient(s) named above. If the reader of this message is not the intended recipient or an agent responsible for delivering it to the intended recipient, you are hereby notified that you have received this document in error and that any review, dissemination, distribution, or copying of this message is strictly prohibited. If you have received this communication in error, please notify us immediately, and delete the original message.
Upgrade TSM 5.1.7 to 5.2.0 - how long should upgradedb take?
Hi all, Today we started our upgrade of TSM 5.1.7 to 5.2.0. Our TSM server is HP-UX 11i, TSM database is 112GB, about 80% used. After the install of the TSM product, the 'dsmserv -upgradedb' command is run during server reboot (that's how it is done on HP-UX the startup screen says Configuring all unconfigured software filesets). At this point, the system is not responding to pings... we suspect it is performing the upgradedb in single-user mode, or maybe just hasn't started network processes yet. The system has been in this state for over three hours is this normal? I don't recall the upgrade from 4.1 to 5.1 taking this long. Thanks for any tips... Robin Sharpe Berlex Labs
restoring multiple versions of the same file
Greetings, We have a customer that wants to restore all 10 versions of a file (1 active and 9 inactive) that TSM has stored. Is there a way to restore all of them at once, or is he going to need to run 10 separate restores and rename the file once it's on the box? I don't see how Windows is going to let multiple copies of the same file name exist, but I figured if anybody would know a trick it would be this crowd! thanks, -- Jim Kirkman AIS - Systems UNC-Chapel Hill 966-5884
Re: restoring multiple versions of the same file
The way I have done this type of request is to restore to the same directory a re-directed restore to a directory like RESTOREmmdd where the mmdd are the year month and date of the backup into that sub-directory. This way the user had an 'opportunity' to be involved and understand what they are getting. In short, you are right. Windows does not allow multiple versions of the same file name to exist concurrently at the same place in a directory tree.. -Original Message- From: Jim Kirkman [SMTP:[EMAIL PROTECTED] Sent: Tuesday, October 21, 2003 2:17 PM To: [EMAIL PROTECTED] Subject: restoring multiple versions of the same file Greetings, We have a customer that wants to restore all 10 versions of a file (1 active and 9 inactive) that TSM has stored. Is there a way to restore all of them at once, or is he going to need to run 10 separate restores and rename the file once it's on the box? I don't see how Windows is going to let multiple copies of the same file name exist, but I figured if anybody would know a trick it would be this crowd! thanks, -- Jim Kirkman AIS - Systems UNC-Chapel Hill 966-5884
Patch or upgrade
Hi, I am in 4.2.1.9 / NT 4.0. I have a problem in restoring SAP DATA after backing up using LAN-FREE (storage Agent on NT). To resolve this, i think i have to apply patch 9 and above or to upgrade to 5.1. Any Idea?? Thanks
TDP For Exchange Performance Question
Folks, I am trying to gather some performance thru-put numbers on what the rest of you are seeing on TDP for Exchange. I have a cluster environment running LAN free and am only getting about 20GB per hour. The drives are LTO gen2. I am just trying to find out what I should/might be able to expect, understanding of course that their are alot of factors that would need to be considered. Thanks in advance for your feedback. Regards, Mike Hedden reply Description: null
Informix TDP restore to another server
We're running Informix TDP 4.1, TSM client 5.1 on AIX 4.3.3 trying to restore to another client running same O/S and TDP/TSM version. Our TSM server version is at 5.1 on AIX 4.3.3. The cross-server restore is failing because it is trying to log in as the INFORMIX node... which doesnt exist. I have set the virtualnodename in the api dsm.opt file and also changed the nodename in the api dsm.sys file. We can do normal TDP backup and restores to/from the same server and it uses the right name and works fine. Any idea why now its trying to use a different nodename (its the name of the user running the process) and how to overcome it? Thanks Steve
TSM Device Driver on Windows XP?
I am running v5.11 on a Compaq Evo laptop with Windows XP. We have a need for a mobile tsm solution from time to time. I am trying to talk to a single, manual, ADIC LTO200D drive. I had communications with the tape drive natively through windows, but even after I disable the media changer through the O/S, I can't get TSM to talk with the drive. I am using the IBM Ultrium drivers for the tape drive, but it is not working. This configuration has worked for us in the past on a Thinkpad running Windows 2000 Professional. I believe this is a device driver issue with Windows XP. Is there anyway I can make the device driver work with Windows XP so I can move data to the ADIC drive or should I look for an Ultrium driver that works on XP or 2003 since 2003 has similarities to XP. This email has been scanned for all viruses by the MessageLabs SkyScan service.___ Note: Please update your email address for this user to reflect the new MeadWestvaco Corporation. MeadWestvaco employee email addresses are in the format of [EMAIL PROTECTED] This electronic message contains information from MeadWestvaco Corporation or subsidiary companies, which may be confidential, privileged or otherwise protected from disclosure. The information is intended to be used solely by the recipient(s) named. If you are not an intended recipient, be aware that any review, disclosure, copying, distribution or use of this transmission or its contents is prohibited. If you have received this transmission in error, please notify MeadWestvaco immediately at [EMAIL PROTECTED] ___
Re: TSM Storage Pool Hierarchy Question
On Tuesday 21 October 2003 07:41, Curt Watts wrote: Alright, time to ask the experts! Essentially, I'm trying to have our remote TSM servers (satellite locations) utilize the main TSM server as the next storage pool in it's hierarchy. The hierarchy will eventually look like this: Remote Server (RS) Disk Cache -Main Server (MS) Disk Cache -MS Tape Pool -MS Offsite Copy Pool Questions I have: 1) Is this possible? Yes, everything you describe is possible. Though some features would require DRM licensing, and network performance may be an issue. See below for details. 2) Can I do this without the DR module? Yes and no. What you describe is migrating primary pool data, from RS disk to RS virtual volumes - that happen to be stored remotely on the MS server. You can do this without DRM. The DRM module is required when sending any DR related data across the server-to-server communications. Thus, you will need to license DRM if you wish to send copy pool data, TSM database backups, or prepare output via server-to-server communications. There are a couple of practical considerations too. :) First, when RS stores primary data on virtual volumes on the MS server, it needs to access those virtual volumes during reclamation. This causes significant network traffic during reclamation, as the virtual volumes need to be copied _back_ to the RS server, reclaimed, then sent _back_ to the MS server. This is not such an issue with copy pool virtual volumes. Also, the MS server stores these virtual volumes as archive objects, typically in the default management class of whatever policy domain the RS server's client account resides. Thus you might want to create a new policy domain for the RS server's client account, and a management class with (only) an archive copy group. The MS server ignores *all* the archive copy group parameters, except the storage pool destination. Thus you don't have to worry about the MS server expiring the RS server's data, it will _never_ expire the data (until the RS server says too...) And finally, since both the RS and MS server's need to retain the virtual volumes, the potential exists that they get out of sync. Therefore you should consider scheduling reconcile volumes to run occassionally to fix any problems. 3) How does the RS backup it's database - because it won't backup to the local disk? As I stated in (2), you will require DRM if you wish to backup the TSM database directly to the remote TSM server. Perhaps you could backup up the database to the local RS disk, then copy the resultant file across the network, or even use the B/A client to backup the file to the remote TSM server. 3b) Should the RS backup it's DB directly to tape? and if so, how is it possible to share the tape library with no NAS? ( I think you mean, no SAN?) Again, as I state in (2), you need DRM to do this. Assuming that you don't use DRM, and instead backup to the local disk and then use the B/A client to backup to the remote server - then due to the size of the database backup, I'd probably want to send it directly to tape. 4) Should I just break down and put some tape drives out there to handle the DBs? That's probably not necessary; If you have the bandwidth to consider sending storage pool data between sites electonically, then copying the TSM database should be easy. :) Regards, Steven P. -- Steven Pemberton Senior Enterprise Management Consultant IBK, Senetas Group Mobile: +61/0 418 335 136 | Phone: +61/3 9820 5811 | Fax: +61/3 9820 9907 Level 1, 11 Queens Road, Melbourne, Victoria, 3004, Australia http://www.senetas.com.au | http://www.ibk.com.au | http://www.datum.com.au
Re: HELP!! . Return code is: 127
From: T_MML [mailto:[EMAIL PROTECTED] after running my postschedule the code error 127 is registered in my dsmsched.log This return code is coming from the operating system running your shell script remove_files.sh Refer to RedHat docs to find what this code means. -- Mark Stapleton ([EMAIL PROTECTED])
Re: TSM Storage Pool Hierarchy Question
I asked this question a while back but didn't get a reply. A migration process from disk to tape will normally handle only one client's data per migration process and hence only use one tape drive. Since the virtual volumes on MS appear to come from a single client (RS), then this data will also be limited to a single process and drive. I have a situation where my inter-site san link may disappear and I'll be forced to use server-to-server for electronic vaulting. Is migration limited in this way, and, if so, is there any circumvention for the problem? Steve Harris Queensland Health, Brisbane Australia [EMAIL PROTECTED] 22/10/2003 10:35:56 On Tuesday 21 October 2003 07:41, Curt Watts wrote: Alright, time to ask the experts! Essentially, I'm trying to have our remote TSM servers (satellite locations) utilize the main TSM server as the next storage pool in it's hierarchy. The hierarchy will eventually look like this: Remote Server (RS) Disk Cache -Main Server (MS) Disk Cache -MS Tape Pool -MS Offsite Copy Pool Questions I have: 1) Is this possible? Yes, everything you describe is possible. Though some features would require DRM licensing, and network performance may be an issue. See below for details. 2) Can I do this without the DR module? Yes and no. What you describe is migrating primary pool data, from RS disk to RS virtual volumes - that happen to be stored remotely on the MS server. You can do this without DRM. The DRM module is required when sending any DR related data across the server-to-server communications. Thus, you will need to license DRM if you wish to send copy pool data, TSM database backups, or prepare output via server-to-server communications. There are a couple of practical considerations too. :) First, when RS stores primary data on virtual volumes on the MS server, it needs to access those virtual volumes during reclamation. This causes significant network traffic during reclamation, as the virtual volumes need to be copied _back_ to the RS server, reclaimed, then sent _back_ to the MS server. This is not such an issue with copy pool virtual volumes. Also, the MS server stores these virtual volumes as archive objects, typically in the default management class of whatever policy domain the RS server's client account resides. Thus you might want to create a new policy domain for the RS server's client account, and a management class with (only) an archive copy group. The MS server ignores *all* the archive copy group parameters, except the storage pool destination. Thus you don't have to worry about the MS server expiring the RS server's data, it will _never_ expire the data (until the RS server says too...) And finally, since both the RS and MS server's need to retain the virtual volumes, the potential exists that they get out of sync. Therefore you should consider scheduling reconcile volumes to run occassionally to fix any problems. 3) How does the RS backup it's database - because it won't backup to the local disk? As I stated in (2), you will require DRM if you wish to backup the TSM database directly to the remote TSM server. Perhaps you could backup up the database to the local RS disk, then copy the resultant file across the network, or even use the B/A client to backup the file to the remote TSM server. 3b) Should the RS backup it's DB directly to tape? and if so, how is it possible to share the tape library with no NAS? ( I think you mean, no SAN?) Again, as I state in (2), you need DRM to do this. Assuming that you don't use DRM, and instead backup to the local disk and then use the B/A client to backup to the remote server - then due to the size of the database backup, I'd probably want to send it directly to tape. 4) Should I just break down and put some tape drives out there to handle the DBs? That's probably not necessary; If you have the bandwidth to consider sending storage pool data between sites electonically, then copying the TSM database should be easy. :) Regards, Steven P. -- Steven Pemberton Senior Enterprise Management Consultant IBK, Senetas Group Mobile: +61/0 418 335 136 | Phone: +61/3 9820 5811 | Fax: +61/3 9820 9907 Level 1, 11 Queens Road, Melbourne, Victoria, 3004, Australia http://www.senetas.com.au | http://www.ibk.com.au | http://www.datum.com.au *** This email, including any attachments sent with it, is confidential and for the sole use of the intended recipients(s). This confidentiality is not waived or lost, if you receive it and you are not the intended recipient(s), or if it is transmitted/received in error. Any unauthorised use, alteration, disclosure, distribution or review of this email is prohibited. It may be subject to a statutory duty of confidentiality if it relates to health service matters. If you are not the intended recipients(s), or if you have received this e-mail in error,
Re: TSM Device Driver on Windows XP?
From: Royce E Johnson [mailto:[EMAIL PROTECTED] I am running v5.11 on a Compaq Evo laptop with Windows XP. We have a need for a mobile tsm solution from time to time. I am trying to talk to a single, manual, ADIC LTO200D drive. I had communications with the tape drive natively through windows, but even after I disable the media changer through the O/S, I can't get TSM to talk with the drive. I am using the IBM Ultrium drivers for the tape drive, but it is not working. This configuration has worked for us in the past on a Thinkpad running Windows 2000 Professional. I believe this is a device driver issue with Windows XP. Is there anyway I can make the device driver work with Windows XP so I can move data to the ADIC drive or should I look for an Ultrium driver that works on XP or 2003 since 2003 has similarities to XP. In answer to your question as to why W2KPro works and XP doesn't, check the server requirements page at http://www-1.ibm.com/support/docview.wss?rs=663context=SSGSG7q=windowsuid=swg21064234loc=en_UScs=utf-8lang=en -- Mark Stapleton ([EMAIL PROTECTED])
