Re: New personal best.
And finally it finished... Total number of objects inspected: 10,304,027 Total number of objects backed up: 9,434,146 Total number of objects updated: 0 Total number of objects rebound: 5 Total number of objects deleted: 0 Total number of objects expired: 1,990,721 Total number of objects failed: 319 Total number of bytes transferred:30.71 TB Data transfer time:374,917.27 sec Network data transfer rate:87,965.08 KB/sec Aggregate data transfer rate: 50,048.12 KB/sec Objects compressed by:0% Elapsed processing time: 183:02:38 Regards, Ibán. Roger Deschner wrote: I tried this for a while, forcing large client files directly to tape, but those big files are so awful to back up directly to tape that we bought more disks. When a client session gets a tape drive for backup, the network and the client (more often than not, some underpowered Mac that some dork has filled with video files) can almost never pump enough data down the wire to keep the tape drive streaming. So it stops and starts - shoeshining. This really wears out your tapes. They say that DLT and LTO tapes are good for some huge number of passes in the millions, but once you start shoeshining you can reach those numbers real quick. To add insult to injury, when a slow client is backing up a huge file to a tape drive, your TSM Server Log is pinned. We had a log-full server crash this way. The only way to positively prevent shoeshining and resulting full log crashes is to buy more disks, and insure that all tape writing is done via TSM Migration from local server disk. Set the file size limits the same in the primary (disk) and secondary (tape) Storage Pools so that client backup sessions never mount a tape. The cost of a little more disk space is really worth it here, in terms of both overall performance, and tape wear. Another way to reduce shoeshining is to use a reclamation storage pool. During reclamation, the output tape has to stop while the input tape is skipping past the already-expired files. In your situation, set RESOURCEUTULIZATION to 10 in the client options file so that it uses 5 sessions to back up at once. This can really help with a lot of small files like you have. That old rule of thumb that you should have enough Storage Pool disk for one normal day of backups still applies, especially when backing up a monster like this. Then you should migrate to tape using as many migration processes as you have tape drives. Roger Deschner University of Illinois at Chicago [EMAIL PROTECTED] = Things are more like they are now than they have ever been before. = --Dwight D. Eisenhower On Thu, 12 Apr 2007, Skylar Thompson wrote: I have tried virtualmountpoint without chance (or without experience)... I meant that I have one TSM for one FS (8.000.000- today, 16.000.000 of files- future // 10 versions) This FS is represented by one node... the first stage is disk... so when I migrate to tape, I only have one process... :'( :'( And creating more than one node with virtual mount points seems to me so tedious to restore... do you disk at first stage ¿? Or are you backing up to tape directly ¿? My solution has been to force big files (1GB at our site) to tape, but spool small files on disk. You can do this with the MAXSIZE parameter on your disk storage pool. -- -- Skylar Thompson ([EMAIL PROTECTED]) -- Genome Sciences Department, System Administrator -- Foege Building S048, (206)-685-7354 -- University of Washington School of Medicine
revision and licensing info
hi all, just got inquiry from kpmg about our b/a environment, one of the questions is do you use multi-core processors on any of your tsm b/a servers just to let you know
AW: [ADSM-L] RAC backups
We backup a 4-node Linux RAC 10G-R2 without any problems. TSM BA client and API as well as TDP for Oracle was installed on every node. Backups are triggered by RMAN and work fine. I would be glad to answer any further questions you have. Thomas Rupp -Ursprüngliche Nachricht- Von: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Im Auftrag von Alexander Verkooijen Gesendet: Dienstag, 24. April 2007 07:41 An: ADSM-L@VM.MARIST.EDU Betreff: Re: [ADSM-L] RAC backups I spent the last two months installing TSM on a two node RAC cluster (Linux, not AIX). It was a very unpleasant experience. There is very little documentation (at least that I could find). I can back up now and a few weeks ago I had to restore a corrupt datafile. For some reason it took RMAN hours and I had to copy archived logs manually from one node to another node but in the end the datafile was restored. There is one advise I can give you: Make sure your archived logs (if you're running your database in archive log mode) are on some kind of shared storage like ASM so all the nodes can access them. Regards, Alexander On Monday 23 April 2007 16:18, Thomas, Matthew wrote: Guys, Does anyone have any guidance on using TSM scheduled TDP backups with Oracle RAC multi-node grids? We're due to implement a 4-way RAC cluster (on AIX) and ultimately we'll need the database(s) to be backed up and restored via any of the 4 nodes in the grid. Any advice would be appreciated. TIA Matt Thomas This e-mail is only for the above addressees. It may contain confidential or privileged information. If you are not an addressee you must not copy, distribute, disclose or use any of the information in it or any attachments. If you have received it in error please notify the sender and delete it immediately. Lloyds TSB Bank plc. Registered office: 25 Gresham Street, London EC2V 7HN. Registered in England and Wales, number 2065. Telephone: 020 7626 1500. Lloyds TSB Scotland plc. Registered office: Henry Duncan House, 120 George Street, Edinburgh EH2 4LH. Registered in Scotland, number 95237. Telephone: 0131 225 4555. Cheltenham Gloucester plc. Registered office: Barnett Way, Gloucester GL4 3RL. Registered in England and Wales, number 2299428. Telephone: 01452 372372. Lloyds TSB Bank plc, Lloyds TSB Scotland plc and Cheltenham Gloucester plc are authorised and regulated by the Financial Services Authority and are signatories to the Banking Codes. Lloyds TSB Bank plc and Lloyds TSB Scotland plc represent only the Scottish Widows and Lloyds TSB Marketing Group for life assurance, pensions and investment business. Cheltenham Gloucester plc acts as an introducer only for life assurance, pensions and investment business. Lloyds TSB Group plc. Registered office: Henry Duncan House, 120 George Street, Edinburgh EH2 4LH. Registered in Scotland, number 95000. Telephone: 0131 225 4555.
Re: New Library/Retire Old Library
Hi Doug Thanks to all of you for your opinion and advice. I have successfully migrated 2 sites to their new libraries, without a single problem, simply following a methodical, and systematic approach. Thanks again Adrian Compton From: ADSM: Dist Stor Manager on behalf of Doug Fox Sent: Fri 2007/04/20 04:32 PM To: ADSM-L@vm.marist.edu Subject: Re: [ADSM-L] New Library/Retire Old Library Easiest way IMO is to set the new library's storage pools as the nextmigration pool for your old stuff. You can then kick off migration and let it move stuff over for you. So updating your old 'offsite' pool to include the new 'offsite' pool as the next migration pool. Make sense? Then manually kick off migration and wait till its done. On 4/20/07, adrian_compton [EMAIL PROTECTED] wrote: Hi In a previous post I ask for advice on retiring an old library and commissioning a new library in its place. I have reached a point where I am not too sure on the direction to follow. I have migrated all my storage pools (sequential) to the new library, and they are working fine. I created a new devclass pointing to the new library. I have created a new Offsite Copy Pool for my DR offsite tapes, and this is in use. My old Offsite Copy Pool is no longer being used on the old library 3310 is the new library 3583 is the old library LTO3DEVCL is the old devclass pointing to the 3583 LTO3310DEVCL is the new devclass pointing to the 3310 Storage DeviceEstimated Pct Pct High Low Next Storage Pool NameClass Name Capacity Util Migr Mig Mig Pool Pct Pct --- --- - - --- --- ARCHPOOLLTO3310DE- 40,960 G 0.0 2.0 90 70 VCL DISKPOOLDISK1,500 G 53.4 53.4 98 30 OVERFLOW LEGACY LTO3310DE-0.0 M0.0 0.0 90 70 VCL MONTHPOOL LTO3310DE- 81,920 G0.2 1.0 90 70 VCL OFFSITE LTO3DEVCL 94,184 G 20.4 OFFSITE_33- LTO3310DE-132,595 G6.9 10 VCL OVERFLOWLTO3310DE-115,721 G1.7 2.0 90 70 VCL TAPEPOOLLTO3DEVCL 128,347 G 12.9 19.0 90 70 TAPEPOOL_3- LTO3310DE- 81,920 G1.7 2.0 90 70 310 VCL YEARPOOLLTO3310DE- 81,920 G0.0 2.0 90 70 VCL Library Name LibraryACS Category -- --- --- 3310LIBSCSI 3583LIBSCSI Library Name Drive Name Device Type On-Line --- --- 3310LIB LTO3DR3 LTO Yes 3310LIB LTO3DR4 LTO Yes 3310LIB LTO3DR5 LTO Yes 3583LIB LTO3DR1 LTO Yes 3583LIB LTO3DR2 LTO Yes Further Questions. 1. Is it possible to move the old offsite pool (OFFSITE) to the new one. I was told to just leave it and it will diminish to nothing over time with reclamation which I agree and understand. Not sure why, but it would look better and have all media in one logical group. 2. My TAPEPOOL is 19 tapes, and migration will take forever to the new TAPEPOOL_3310. Is there a way to check the tapes out and then check in to the new library or is migration the only way to go. 3. Should I change my old devclass to point to the new library i.e LTO3DEVCL to point to 3310LIB instead of 3583LIB Thanks in advance Adrian Compton Aspen Pharmacare
Hunny Kershaw/San Jose/IBM is on maternity leave
I will be out of the office starting 04/23/2007 and will not return until 06/04/2007. During my absense, please contact o Himanshu Madhani at [EMAIL PROTECTED] on device related issues or device certification requests o Ken Law at [EMAIL PROTECTED] on device certification status o or my manager Jim Riehl at [EMAIL PROTECTED] on other issues or urgent matters. Regards, Hunny..
Re: Collocation
With regards to the Move Nodedata command, is this something which can be stopped and started (i.e. if we were to kick off the process can we stop it and then resume from where it left off)? Richard Sims [EMAIL PROTECTED] 20/04/2007 17:12 On Apr 20, 2007, at 11:16 AM, William Kyndt wrote: ... 1. When enabling collocation for a group of servers, does a full backup of the servers occur to group the data on as few volumes as possible followed by incremental backups? Or do incremental backups still occur as normal and are simply grouped on pre defined volumes? William - There is no change in Incremental backup behavior because of collocation: if an object is in the target storage pool already, it will not be backed up again, regardless of how the storage pool is arranged. 2. Is there a way to collocate data already backed up onto fewer volumes? All subsequent data movement within the storage pool (reclamation, Move Data, Move Nodedata) will observe the collocation rule. The Admin Guide has good info on this. Richard Sims Sr. Systems Programmer at Boston University, Office of Information Technology ** The Miller Group Limited Registered in Scotland - SC018135 Miller Homes Limited Registered in Scotland - SC255429 Miller Construction (UK) Limited Registered in Scotland - SC209666 Miller Developments Limited Registered in Scotland - SC178108 2 Lochside View Edinburgh Park Edinburgh EH12 9DH Disclaimer: The Information in this e-mail is confidential and for use by the addressee(s) only. It may also be privileged. If you are not the intended recipient please notify us immediately on +44 (0) 870 336 5060 and delete the message from your computer: you may not copy or forward it, or use or disclose its contents to any other person. We do not accept any liability or responsibility for: (1) changes made to this email after it was sent, or (2) viruses transmitted through this email or any attachment.
Re: AW: [ADSM-L] RAC backups
We are building our first RAC. Due to the requirements of the vendor's product, we are building a 3-way RAC cluster (on Win2k3-64bit). We usually use BMC's SQLBacktrack for all of our databases, but BMC has released a client supporting RAC on Windows, yet. Right now we are using RMAN to output a flat-file and having TSM BAclient pick that up. I'd like to try TDP to a separate TSM node for the database filespace. I'd appreciate any advice, also... TIA, Troy Troy Barnhart, Sr. Systems Programmer [EMAIL PROTECTED] Regional Health, Inc. 353 Fairmont Boulevard Rapid City, South Dakota 57701 PH: 605-716-8352 / FAX: 605-716-8302 -Original Message- From: Thomas Rupp [mailto:[EMAIL PROTECTED] Sent: Tuesday, April 24, 2007 3:35 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] AW: [ADSM-L] RAC backups We backup a 4-node Linux RAC 10G-R2 without any problems. TSM BA client and API as well as TDP for Oracle was installed on every node. Backups are triggered by RMAN and work fine. I would be glad to answer any further questions you have. Thomas Rupp On Monday 23 April 2007 16:18, Thomas, Matthew wrote: Guys, Does anyone have any guidance on using TSM scheduled TDP backups with Oracle RAC multi-node grids? We're due to implement a 4-way RAC cluster (on AIX) and ultimately we'll need the database(s) to be backed up and restored via any of the 4 nodes in the grid. Any advice would be appreciated. TIA Matt Thomas ***Note: The information contained in this message, including any attachments, may be privileged, confidential, and protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify the Sender immediately by a reply to sender only message and destroy all electronic or paper copies of the communication, including any attachments.
Re: API queries
Hi, if i use tha API can i use queries like select cast(v.volume_name as char(9))as volume,cast(v.status as char(7))as status,cast(v.access as char(9))as access,cast(v.stgpool_name as char (9))as stgpool,cast(v.est_capacity_mb/1024 as decimal(5,2)) as GB,cast(pct_utilized as decimal(4,1))as util from libvolumes as l,volumes as v where l.volume_name=v.volume_name order by stgpool,status,util or SELECT AVAIL_SPACE_MB,PCT_UTILIZED,CACHE_HIT_PCT, LAST_BACKUP_DATE FROM DB? Tanks in advance, Amilcar
Update stgp devclass (Was Re: [ADSM-L] partitioning 3583)
Wanda, Thanks for the info, i appreciate it. I did see in the operator guide that the configurations are fixed, but i can deal with that. I partitioned the library and put the two LTO-3 drives in Lib A. The four LTO-1 drives in Lib B. The old device class was '3583'. I created a new devclass called '3583L3'. Then created new libraries and checked LTO3 cartridges into Lib A, LTO1's into Lib B. Now here's my problem: I have a storage pool and LTO-3 volumes that are still device class '3583'. But they're now in the Lib A LTO3 library. Is there a way to change the devclass on the storage pool or the volumes to '3583L3'?? Whenever the storage pool needs one of the L3 volumes, it does a mount request thinking the volume needs to be checked into Lib B (and of course the LTO-1 drives in Lib B can't read the LTO-3 cartridge). Of course i could wait for most of the data to naturally expire, but i think there may be some long retention on some of the data. Thanks for any ideas. ray On 4/23/07, Prather, Wanda [EMAIL PROTECTED] wrote: Been there done that, all though it was quite a while ago. You are correct that - There is nothing in TSM code that will prevent TSM from trying to mount an LTO3 cartridge in an LTO1 drive, if they are defined to the same TSM library. If you dig around in the books and web site you can find that documented, but I agree it isn't intuitively obvious. - The partitioning of the 3583 is limited to the FIXED configurations described in the 3583 Setup Operator Guide topic multipath library configurations. One place in the book sorta implies some flexibility, but I checked with our regional tape specialist, and the configurations shown in the book are the only ones available. (There are also restrictions on how the slots are divided up per logical library - if you have the 12-slot I/O door, the 6 slots below the door ALWAYS go with lib A, for example.) -Looks to me like you are correct that you will have 2 LTO3 drives in lib A and the other 4 LTO1 drives in lib B, which means you will have to move things around. -In addition to creating the partitions, you must assign a CONTROL PATH to the new logical library. (Every logical library must have at least 1 drive assigned as the control path.) See in the book add control paths. Then when you run cfgmgr, you should see a new /dev/smcx device. -Everything else you have looks right. Partition the library, reboot it, run config mgr. Make sure the devices show up in AIX like you expect. Then for TSM you just create a new library, drives, paths in TSM on the new /dev/smcx device, check the tapes in to that library. Update the paths/drives in the old library defined on /dev/smc0. TSM thinks it's 2 real, physically separate libraries. Things to check on: --Early releases of the 3583 didn't have the multipath feature, which means you can't partition. If you don't find the right virtual buttons on your front panel, you probably need to upgrade the microcode, although I'm pretty sure you have to be reasonably current since you are running LTO3's. (I'd recommend getting up to date on the microcode, anyway.) -Make sure you are using a reasonably up-to-date version of the Setup Operator guide. Once you get past the frustration of having to use the fixed partitions you get, it works like a champ. W From: ADSM: Dist Stor Manager on behalf of Ray Sent: Mon 4/23/2007 3:18 PM To: ADSM-L@VM.MARIST.EDU Subject: partitioning 3583 All, Through a little confusion and lack of research, we have a 3583 library where we have mixed LTO1 and LTO3 media. Apparently we read that TSM and the 3583 supports mixed-media with LTO and didn't read the fine print, thinking it would just work. The drives and cartridges are in a single device class (format=drive) all in the same storage pool. Surprisingly this has been working fine for a few months. I have 4 LTO-1 drives in slots 1-4, and 2 LTO-3 drives in slots 5-6. After a backup failure, i noticed TSM trying to mount an LTO3 cartridge in an LTO1 drive. Further research showed that our setup should not work at all haha. I've determined the best course of action now is to partition into 2 logical libraries. One library for LTO-1 media, one for LTO-3 media. Having never done this before, i have a few questions. 1. Are the 3583 partitioning configurations fixed? I don't see a way to assign a particular drive to a particular partition. If it is a fixed config, then according to the operator guide, when you define 2 logical libaries, drive slots 1 and 2 are in library A, and slots 3-6 are in library B. If this is true, i'll have to physically move the LTO-3 drives to slots 1 and 2. Am i following this correctly? 2. Library is connected to a p5-570 running AIX 5.3. Right now the library is /dev/smc0. After partitioning, will i get a smc0 and an smc1? Should i run cfgmgr after partitioning? 3. What is the best procedure to do the
Re: API queries
On Apr 24, 2007, at 12:00 PM, Amilcar Infante wrote: Hi, if i use tha API can i use queries like select ... The one and only TSM API is a client type API, only for storing data into TSM server storage pools and later retrieving it. The use of Select statements requires Administrative interaction with the server, as via dsmadmc. What you may be thinking of is the ODBC driver for Windows: information about that is found in the Admin Guide manual, and the TSM 5.1 Technical Guide redbook. Richard Sims
Re: Collocation
On Apr 24, 2007, at 8:41 AM, William Kyndt wrote: With regards to the Move Nodedata command, is this something which can be stopped and started (i.e. if we were to kick off the process can we stop it and then resume from where it left off)? Yes; that should work fine. In general, you can cancel and later reinvoke for completion, any command whose unit of operation is fine-grained, as where a Move command works on a Physical File at a time, as opposed to amalgam operations such as Export. Richard Sims
Re: revision and licensing info
Yes I do! Pablo Arzuaga Ticket Pop Networks Network Analyst Cel. 787-458-9063 [EMAIL PROTECTED] www.ticketpop.com -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of goc Sent: Tuesday, April 24, 2007 4:12 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] revision and licensing info hi all, just got inquiry from kpmg about our b/a environment, one of the questions is do you use multi-core processors on any of your tsm b/a servers just to let you know
Problems trying to use ISC Admin Center
Hello Everyone, I have just upgraded our TSM server to 5.3.4.2 and I was trying to add the server to ISC. I went to Storage Devices, Server, Add a Connection to an IBM TSM Server, but when I put the Administrator name, passwork, Server address and server port I received a message that an API error occurred while processing the request and check the Problem Determination guide to resolve the issue. I cannot seem to figure out what admin name I should be adding in order to add a server? Do I add my own TSM admin name? Or is this something else? If anyone has any suggestions on how to get this set up properly I would really appreciate it Thanks in advance! Joni Moyer Highmark Storage Systems, Senior Systems Programmer Phone Number: (717)302-9966 Fax: (717) 302-9826 [EMAIL PROTECTED]
TSM only reads from COPY1 during DB backup
Has anyone else observed that TSM only reads from COPY1 of a db volume mirror pair during DB backup? Orville L. Lantto Glasshouse Technologies, Inc.
Re: Collocation
Unclear whether it resumes where it left off, but since some files are already moved from the source stg, it picks up where it feels most efficient. Unless, a big unless, the target stg is the same as the source. Then all the oreviously moved will be moved again. Original message Date: Tue, 24 Apr 2007 13:41:42 +0100 From: William Kyndt [EMAIL PROTECTED] Subject: Re: [ADSM-L] Collocation To: ADSM-L@VM.MARIST.EDU With regards to the Move Nodedata command, is this something which can be stopped and started (i.e. if we were to kick off the process can we stop it and then resume from where it left off)? Richard Sims [EMAIL PROTECTED] 20/04/2007 17:12 On Apr 20, 2007, at 11:16 AM, William Kyndt wrote: ... 1. When enabling collocation for a group of servers, does a full backup of the servers occur to group the data on as few volumes as possible followed by incremental backups? Or do incremental backups still occur as normal and are simply grouped on pre defined volumes? William - There is no change in Incremental backup behavior because of collocation: if an object is in the target storage pool already, it will not be backed up again, regardless of how the storage pool is arranged. 2. Is there a way to collocate data already backed up onto fewer volumes? All subsequent data movement within the storage pool (reclamation, Move Data, Move Nodedata) will observe the collocation rule. The Admin Guide has good info on this. Richard Sims Sr. Systems Programmer at Boston University, Office of Information Technology * * The Miller Group Limited Registered in Scotland - SC018135 Miller Homes Limited Registered in Scotland - SC255429 Miller Construction (UK) Limited Registered in Scotland - SC209666 Miller Developments Limited Registered in Scotland - SC178108 2 Lochside View Edinburgh Park Edinburgh EH12 9DH Disclaimer: The Information in this e-mail is confidential and for use by the addressee(s) only. It may also be privileged. If you are not the intended recipient please notify us immediately on +44 (0) 870 336 5060 and delete the message from your computer: you may not copy or forward it, or use or disclose its contents to any other person. We do not accept any liability or responsibility for: (1) changes made to this email after it was sent, or (2) viruses transmitted through this email or any attachment. Fred Johanson
