Re: VTL's and D2D solutions
- All physical media (tapes/disk drives/CDs/etc) are tagged, tracked and audited every quarter - No physical media (tapes/disk drives/CDs/etc) leaves the site - Malfunctioning media is marked for destruction collected in a safe - When enough media marked for destruction has been collected, a vendor brings a on-site shredder to the site and shreds the media following rigorous audit procedures - If media must be shipped, it is essentially done using armed guards, sealed containers and GPS monitoring, using three different vendors, two of which are decoys. Paranoia is another's reality. -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Shawn Drew Sent: Monday, July 02, 2012 4:53 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] VTL's and D2D solutions If someone pulls a disk out of the array, (replacing a bad disk, etc), you can't tell a regulator/auditor that it was encrypted. A purely bureaucratic reason, but still valid. Regulations pop up all the time without actual technical consideration. (I want to punch anyone who says the words 7 years to me!) The OP's email address sounds like he's involved in the health care industry. They have the worst of it. Almost as bad as the financial industry. Regards, Shawn Shawn Drew Internet dplafla...@gmail.com Sent by: ADSM-L@VM.MARIST.EDU 07/02/2012 05:35 PM Please respond to ADSM-L@VM.MARIST.EDU To ADSM-L cc Subject Re: [ADSM-L] VTL's and D2D solutions On Jul 2, 2012, at 9:35 AM, Kevin Boatright wrote: We are currently looking at adding a Disk to Disk backup solution. Our current solution has a 3584 tape library with LTO-5 drives using TKLM. We have looked at Exagrid and Data Domain. Also, I believe HP has a solution. We will need to have encryption on the device and the ability to replicate between the two disk units. Why do you have to have encryption on the device? No, that wasn't a sarcastic question. If someone pulls a disk out of your DataDomain RAID, what can they do with it? Your data is striped across many drives, in chunks that are admittedly large enough to have a whole mailing address on it. Is someone afraid that someone else will steal one or more drives and then read unstructured streams of data looking for PII? Really? There's no chance that a tape will fall off a truck as you ship your backups off site. Sure, encrypt the VPN between sites, or use a dedicated network. But that doesn't mean you have to encrypt your data on the appliance, unless you're more paranoid than I am (or answer to people who are more paranoid than I am). At this point, I start worrying more about debacles from poor implementation or management of encryption than I do about loss of unencrypted data. Anyone have any comments or recommendations? Besides DataDomain, HP, and IBM, I'm sure the rest of EMC, Oracle, and even small brands like Coraid would propose different solutions. For example, why not replicate cheap disk, on top of which you build FILE devices? Do you need the cost of a DataDomain or ProtecTier front-end, or do you just replicate unduplicated data? Oracle and Coraid will sell you large arrays of cheap disk with ZFS front-ends that could replicate data if you need it and could deduplicate the data as justified. I'm not saying I'd want to bet my job on Coraid, but others find there cost advantage over DataDomain attractive. Thanks, Kevin Nick This message and any attachments (the message) is intended solely for the addressees and is confidential. If you receive this message in error, please delete it and immediately notify the sender. Any use not in accord with its purpose, any dissemination or disclosure, either whole or partial, is prohibited except formal approval. The internet can not guarantee the integrity of this message. BNP PARIBAS (and its subsidiaries) shall (will) not therefore be liable for the message if modified. Please note that certain functions and services for BNP Paribas may be performed by BNP Paribas RCC, Inc.
Re: RMAN - Oracle Deletes
This is the script I use: ASSUMPTIONS: RMAN is backing-up using the node name ORACLE-NODE-BU select NODE_NAME,cast(BACKUP_DATE as date) as BACKUP_DATE,STATE,cast(DEACTIVATE_DATE as date) as DEACTIVATE_DATE, HL_NAME,LL_NAME from BACKUPS where NODE_NAME='ORACLE-NODE-BU' order by BACKUP_DATE /tmp/ORACLE-NODE-BU.bulist.txt Thanks, H. Milton Johnson -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Hart, Charles A Sent: Friday, November 21, 2008 9:59 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] RMAN - Oracle Deletes Hope everyone is well in these trying times. Does anyone know if there's a way other than tracking occupancy to see if RMAN is passing deletes to TSM for Oracle TDP clients? We've had many challenges with our Oracle group and their delete backup script not working. Thank you Have a great day! Charles This e-mail, including attachments, may include confidential and/or proprietary information, and may be used only by the person or entity to which it is addressed. If the reader of this e-mail is not the intended recipient or his or her authorized agent, the reader is hereby notified that any dissemination, distribution or copying of this e-mail is prohibited. If you have received this e-mail in error, please notify the sender by replying to this message and delete this e-mail immediately.
Re: Seeking thoughts/experiences on backing up large amounts (say 50 Petabytes) of data
Quite a project. Sepaton has customers that store Petabytes of data on their VTLs. Sepaton claims performance of: * 9600 MB/sec per VTL * 1.2 Petabytes per VTL (without compression) * RAID 6 protection Obviously you need more information on the requirements. Good luck! Thanks, Milton Johnson -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Bob Talda Sent: Wednesday, January 23, 2008 2:16 PM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Seeking thoughts/experiences on backing up large amounts (say 50 Petabytes) of data Folks: Our group has been approached by a customer who asked if we could backup/archive 50 petabytes of data. And yes, they are serious. We've begun building questions for the customer, but as this is roughly 1000 times the current amount of data we backup, we are on unfamiliar turf here. At a high level, here are some of the questions we are asking: 1) Is the 50 Petabytes an initial, or envisioned data size? If envisioned, how big is the initial data load and how fast will it grow? 2) What makes up the data: databases, video/audio files, other? (subtext: how many objects are involved? What are the opportunities to compress/deduplicate?) 3) how is the data distributed - over a number of systems or from a supercluster? 4) Is the data static, or changing slowly or changing rapidly? (subtext: is it a backup or archive scenario) 5) What are the security requirments? 6) What are the restore (aka RTO) requirements? We are planning on approaching vendors to get some sense of the probable data center requirements (cooling, power, footprint). If anyone in the community has experience with managing petatybes of backup data, we'd appreciate any feedback we could incorporate. Thanks in advance!
Re: Sizing virtual tapes
Here is my response to an earlier question on sizing a VTL. I have been using a 10GB tape volume size for a couple of years and have not seen a reason to change. I originally chose 10GB because ISM recommended that size when using sequential file devices. Yes that is an approach that will work. I used: (Total_Bytes_in_Primary_STG + ((Max_Daily_Amt_Backed-up X (ReuseDelay + 2))) X Growth_factor I then let the compression factor be my fudge factor. However give some thought to the size (native capacity) of your virtual tape volumes. In the physical world you have little control over this (we generally use the largest size cartridge we can get to have the greatest capacity [volume size times fixed number of cartridge slots = total capacity online]). In the VTL world things are different, you total capacity is fixed (determined by the disk space you purchased) but YOU can determine the volume size and the number cartridge slots equals the total capacity divided by the size of your virtual tape volumes. This said, what can you do with it? I went with a small tape size (10GB) and have the following benefits: A) If I need a file at the end of the tape I spin through 10GB not 100GB of data (ignoring compression). B) No matter what reclamation threshold you use, you will have tapes that are 1% short of being reclaimed. Small tapes in this state waste less space then large tapes in that state. One gotcha is deciding which physical library you are emulating. When I first brought my VTL up, TSM choked. Why? Because TSM knew that the library I was emulating could not have 1,415 physical tape slots. I changed the emulation to an ADIC Scalar 10K and the problem was solved. Sorry I don't remember the original library emulation. Just a thought, think outside the physical box, it's all virtual. Thanks, H. Milton Johnson -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of David E Ehresman Sent: Thursday, November 29, 2007 8:01 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Sizing virtual tapes How large are you making the max size of your virtual tapes? Why? I let my TS7520 emulating 3592E tapes default to a max size of 460GB but I'm starting to think a smaller size would make more sense. The median size of occupancy for my nodes is around 40GB so I'm thinking that might be a better max size to facilicate reclamination. David
Re: How to view Oracle TDP files from TSM server
Try: select NODE_NAME,cast(BACKUP_DATE as date) as BACKUP_DATE,STATE,cast(DEACTIVATE_DATE as date) as DEACTIVATE_DATE,HL_NAME,LL_NAME from BACKUPS where NODE_NAME='YOUR_TDP_NODE_NAME' order by BACKUP_DATE Milton Johnson -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Nicholas Rodolfich Sent: Thursday, September 20, 2007 11:21 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] How to view Oracle TDP files from TSM server Hello All, Thanks for your help!! Is there a way to verify or list of particular files from Oracle TDP backups on the server. I am caught in a chasm in DBA land. I don't fully understand the TDP and the DBA doesn't understand TSM or the TDP. Does anyone know any tricks or how I can find out more information than just the standard q occ? Nicholas IMPORTANT NOTICE: This message and any included attachments are from East Jefferson General Hospital, and is intended only for the addressee(s), and may include Protected Health (PHI) or other confidential information. If you are the intended recipient, you are obligated to maintain it in a secure and confidential manner and re-disclosure without additional consent or as permitted by law is prohibited. If you are not the intended recipient, use of this information is strictly prohibited and may be unlawful. Please promptly reply to the sender by email and delete this message from your computer. East Jefferson General Hospital greatly appreciates your cooperation.
Re: FW: Somewhat OT: Sizing a VTL solution
Yes that is an approach that will work. I used: (Total_Bytes_in_Primary_STG + ((Max_Daily_Amt_Backed-up X (ReuseDelay + 2))) X Growth_factor I then let the compression factor be my fudge factor. However give some thought to the size (native capacity) of your virtual tape volumes. In the physical world you have little control over this (we generally use the largest size cartridge we can get to have the greatest capacity [volume size times fixed number of cartridge slots = total capacity online]). In the VTL world things are different, you total capacity is fixed (determined by the disk space you purchased) but YOU can determine the volume size and the number cartridge slots equals the total capacity divided by the size of your virtual tape volumes. This said, what can you do with it? I went with a small tape size (10GB) and have the following benefits: A) If I need a file at the end of the tape I spin through 10GB not 100GB of data (ignoring compression). B) No matter what reclamation threshold you use, you will have tapes that are 1% short of being reclaimed. Small tapes in this state waste less space then large tapes in that state. One gotcha is deciding which physical library you are emulating. When I first brought my VTL up, TSM choked. Why? Because TSM knew that the library I was emulating could not have 1,415 physical tape slots. I changed the emulation to an ADIC Scalar 10K and the problem was solved. Sorry I don't remember the original library emulation. Just a thought, think outside the physical box, it's all virtual. Thanks, H. Milton Johnson -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of wanda.prather Sent: Thursday, June 21, 2007 2:35 PM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] FW: Somewhat OT: Sizing a VTL solution I agree! That's the method I would use. TSM thinks the VTL is a tape library, and processes it as such. So you need to look at how many volumes you are using, not just how much space. If the numbers you see for volume usage don't square with your occupancy, better find out why! In most customers, I find their overall tape utilization is at best around 65% full (because there are tapes in FILLING status, DB backup tapes, EXPORT tapes, scratch tapes, tapes that are below the reclaim threshold, etc.) And as far as I can tell, if you set your reclaim threshold to 50%, over time you can, quite by accident, end up with hundreds of tapes sitting at 49% that never reclaim without manual intervention. You can be more aggressive about running reclaims in a VTL. But you still have to account for un-reclaimed tapes and volumes that never fill (like DB backups). Now I know some VTL's will allocate their physical storage in chunks (say 5G for example) as a tape is written/appended to. So if your virtual volumes are 100G, but your DB backup only needs 20G, you will only be using 20G of the backstore. But if your DB backup needs 21G, you will be using 25G of the backstore. SO it is possible to get away with creating more virtual volumes than you actually have space to support. But I'm very leery of attempting to overcommit volumes in the VTL, given that TSM tries its best to create full volumes. What I would like to know is if anyone has good ideas on what level of overcomittment you can get away with? Or is it better just not to go there? W _ From: ADSM: Dist Stor Manager on behalf of Andy Huebner Sent: Thu 6/21/2007 2:21 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: Somewhat OT: Sizing a VTL solution The approach I used worked very well. I counted all of the tapes that would be kept on the VTL and multiplied that by the capacity of the tapes. I then calculated the growth rate of the tape pool and added that to the total, in my case 6 months out. That is the number I used. The assumption is that compression will be similar on both. If you calculate off of occupancy there is a greater uncertainty because you do not really know how much compression you will get. Calculating off of tape counts will be inaccurate because of filling tapes, but this error is in the admins favor. Filling tapes can be factored in to reduce the error. Andy Huebner -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of William Boyer Sent: Thursday, June 21, 2007 1:03 PM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Somewhat OT: Sizing a VTL solution Has anyone just gone through sizing a VTL solution for a library replacement? Is it as simple as taking your current occupancy/retention, applying for some compression and using that figure for the amount of storage behind the VTL? Or maybe I'm just trying to make something harder than it is. Wouldn't be the first time! :-) TIA. Bill Boyer Select * from USERS where CLUE0 0 rows returned This e-mail (including any attachments) is confidential and may be legally privileged. If you are not an intended recipient or an authorized representative of
Re: Fw: How to Incorporate a CDL into TSM environment?
2) Sepaton does hardware compression so as far as I can tell it performs like compression on physical drives, I imagine other vendors may also use hardware compression. Besides what's important to me is that my TSM clients and TSM server are not taking a performance hit from doing compression because compression has been off loaded to the VTL. Even if the VTL performs slower when compressing vs not compressing, it's not an issue unless your TSM server can over whelm your VTL. Any time your TSM server or TSM client is doing compression, your backup session performance is impacted. 3) This is an area that merits actual testing which is one reason I expressed it as a personal opinion. This seems to me that the results would be very dependent upon the exact hardware configuration being tested. At the least, using a VTL would off-load the file system management activities from the TSM server to the VTL freeing up TSM CPU cycles to pump data from the input stream to the output stream. 4) Read the article by Curtis Preston (referenced in the Just how does a VTL work? thread) for a discussion on in-band versus out-of band de-dup and the effect on performance. I agree this technology does not have a long track record and due diligence in progressing on this, and other new backup technologies, is strongly advised. As I stated I have not used this as of yet. 5) If your VTL must run FSCK against 100TB, yes you do have a problem but: 5A) At least your TSM server is up. 5B) Your TSM server is a much more complex system compared to a VTL. Hence is most likely more susceptible to crashing. Thanks, H. Milton Johnson -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Josef Weingand Sent: Sunday, June 17, 2007 2:58 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Fw: How to Incorporate a CDL into TSM environment? 1.) yes 2.) pls give me vendor / machine type of VTLs which does compression without performance impacts. physical tape drives gets performance improvements of compression, but VTL gets normally much slower performance if compression is enabled 3.) you need compare the same technology. You need compare a FC Disk Subsystems, like DS4000, with a VTL, then you get the same performance (maybe even more) from a File Device Type as from a VTL. 4.)current de-dups does not bring enough performance for most of the environments, and in addition, most vendors have just announced it, but does not have it ready for GA yet. 5.)what happens if the VTL crashed Mit freundlichen Grüßen / Kind regards Josef Weingand Senior IT Specialist Technical Sales Systems Storage Mobil +49 171 55 26 783 - Homeoffice Tel. +49 8845 757421 Fax +49 171 13 5526783 email: [EMAIL PROTECTED] SMS/eMail: [EMAIL PROTECTED] IBM Deutschland GmbH Vorsitzender des Aufsichtsrats: Hans Ulrich Maerki Geschäftsführung: Martin Jetter (Vorsitzender), Rudolf Bauer, Christian Diedrich, Christoph Grandpierre, Matthias Hartmann, Thomas Fell, Michael Diemer Sitz der Gesellschaft: Stuttgart Registergericht: Amtsgericht Stuttgart, HRB 14562 WEEE-Reg.-Nr. DE 99369940 Johnson, Milton [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU 15.06.2007 21:08 Please respond to ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU To ADSM-L@VM.MARIST.EDU cc Subject Re: [ADSM-L] Fw: How to Incorporate a CDL into TSM environment? Why a VTL vs FILE devclass volumes on local drives? 1) With a VTL you can do LAN free backups. 2) Data Compression: 2A) TSM Client does compression: Big performance hit on the client, slower backups/restores 2B) TSM server does compression (FILE devclass volumes on compressed file systems): Big performance hit on server, slower backups/reclaims/restores 2C) VTL does compression: No performance hits (just as with using physical drives with compression) 3) I doubt the TSM server could write large amounts of data simultaneously streaming in from 30 different clients to 30 different FILE devclasses volumes as fast as it can write that data to a fibre channel adapter. 3A) 30 input streams means 30 mounted FILE devclass volumes 3B) The drive heads would always be out of position for the next write. 4) Data Reduction/Data Deduplication/Content Aware Compression: What ever the VTL vendor calls it, you don't have that available with FILE devclass volumes. (I realize that from previous posts you are not comfortable with this technology, I myself have not used it.) 5) Do you really want to manage an AIX system with a 25TB, 50TB or a 100TB file system? After a system crash how long will a FSCK of 100Tb take? Thanks, H. Milton Johnson -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Allen S. Rout Sent: Thursday, June 14, 2007 3:22 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Fw: How to Incorporate a CDL into TSM environment? On Wed, 13 Jun 2007 08:43:43 -0400, Johnson, Milton [EMAIL
Re: non visible RMAN backups ...
You usually do not use RMAN to create a backup file locally on the client and then back up that file to TSM. Instead, via the TDPO api, RMAN: 1) connects to the TSM server 2) generates a file name 3) checks to see if that file name is currently in use 4) sends a stream of data to the TSM server to be stored in a file using the generated file name. I would not want RMAN to store a 200GB backup file locally on the client. It would consume too much space and the disk i/o would be a performance hit. (RMAN is usually used for hot backups.) RMAN should have complete control over how long a backup is retained on the TSM server. RMAN maintains a catalogue database to keep track of which files are required to restore a database. When RMAN tells TSM to delete a file, it deletes that file from the catalogue database. At that point the file is useless as far as restoring the database goes because it has been dropped from the catalogue database. The ability to restore previous versions of a database is a logical concept RMAN maintains using the catalogue database. So once RMAN tells TSM to delete a file, there is no need to hang on to it. Thanks, H. Milton Johnson -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of goc Sent: Monday, June 18, 2007 9:25 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] non visible RMAN backups ... hi all, is there any idea why don't i see RMAN backup files on client machine IBM Tivoli Storage Manager Command Line Backup/Archive Client Interface Client Version 5, Release 4, Level 0.0 Client date/time: 06/18/07 16:16:43 (c) Copyright by IBM Corporation and other(s) 1990, 2007. All Rights Reserved. Node Name: DSS25_TDPO Please enter your user id DSS25_TDPO: Please enter password for user id DSS25_TDPO: Session established with server TSM01: AIX-RS/6000 Server Version 5, Release 3, Level 4.0 Server date/time: 06/18/07 16:17:13 Last access: 06/18/07 16:14:27 tsm q ba /adsmorc/ ANS1092W No files matching search criteria were found tsm q filespace # Last Incr Date TypeFile Space Name --- -- --- 1 06/18/07 12:43:28 API:ORACLE /adsmorc tsm tsm tsm tsm but on server i can see them with no problem at all DSS25_TDPO/adsmorc 1ACTIVE_VERSION FILE//BACK_DSS25.50ikit- 552389757 2007-06-18 oracleDEFAULT h5_1_1 09:49:54.00 DSS25_TDPO/adsmorc 1ACTIVE_VERSION FILE//BACK_DSS25.50ikit- 552389759 2007-06-18 oracleDEFAULT v5_1_1 09:57:23.00 DSS25_TDPO/adsmorc 1ACTIVE_VERSION FILE//BACK_DSS25.52ikj7- 552394310 2007-06-18 oracleDEFAULT la_1_1 12:42:48.00 DSS25_TDPO/adsmorc 1ACTIVE_VERSION FILE//CTRL_DSS25.4pik5u- 550133859 2007-06-13 oracleDEFAULT 8a_1_1 11:42:33.00 DSS25_TDPO/adsmorc 1ACTIVE_VERSION FILE//CTRL_DSS25.4rik61- 550133951 2007-06-13 oracleDEFAULT ob_1_1 12:42:17.00 DSS25_TDPO/adsmorc 1ACTIVE_VERSION FILE//CTRL_DSS25.4vikit- 552389756 2007-06-18 oracleDEFAULT h1_1_1 09:49:51.00 DSS25_TDPO/adsmorc 1ACTIVE_VERSION FILE//CTRL_DSS25.4vikit- 552389758 2007-06-18 oracleDEFAULT v1_1_1 09:57:19.00 DSS25_TDPO/adsmorc 1ACTIVE_VERSION FILE//CTRL_DSS25.51ikj7- 552394309 2007-06-18 oracleDEFAULT l6_1_1 12:42:43.00 another tought question ... :-) why are recommended values for mgmt class 1-0-0-0 and not 0-0-0-0 since RMAN should do deletions of backups ? thanks in advance. goran tsm5.3.4 on aix with all kind of clients
Re: How to Incorporate a CDL into a TSM environment?
If you are in a pure TSM environment, meaning the VTL is exclusively used by TSM, how useful is truncating scratch tapes and returning that space to the VTL's pool of free space? Unless you use co-location all volumes are going to be quickly written to their define maximum native capacity. The only exception to that would be TSM db backup volumes. For me, the VTL's short mount/dismount times and using a small size (10GB) for the defined maximum native capacity has meant I do not require co-location. Since my volumes are small even a TSM db backup would not produce much wasted space. So while it is an interesting behavior, in the above environment, how relevant is it? Thanks, H. Milton Johnson -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Curtis Preston Sent: Friday, June 15, 2007 4:19 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] How to Incorporate a CDL into a TSM environment? John Schneider said: I can't speak for everybody's product out there, but the EMC CDL (EDL) releases the used pages from the virtual volume as soon as you begin to overwrite the virtual volume from the beginning. One thing that does this is a Label Libvolume. This is the way they all work. And you're right. All you have to do is find new tapes in the scratch pool and label them, and voila!. OR... You can just wait for the tape to get reused by TSM, at which point all its space will get erased then replaced with whatever you write to it next.
Re: Fw: How to Incorporate a CDL into TSM environment?
Why a VTL vs FILE devclass volumes on local drives? 1) With a VTL you can do LAN free backups. 2) Data Compression: 2A) TSM Client does compression: Big performance hit on the client, slower backups/restores 2B) TSM server does compression (FILE devclass volumes on compressed file systems): Big performance hit on server, slower backups/reclaims/restores 2C) VTL does compression: No performance hits (just as with using physical drives with compression) 3) I doubt the TSM server could write large amounts of data simultaneously streaming in from 30 different clients to 30 different FILE devclasses volumes as fast as it can write that data to a fibre channel adapter. 3A) 30 input streams means 30 mounted FILE devclass volumes 3B) The drive heads would always be out of position for the next write. 4) Data Reduction/Data Deduplication/Content Aware Compression: What ever the VTL vendor calls it, you don't have that available with FILE devclass volumes. (I realize that from previous posts you are not comfortable with this technology, I myself have not used it.) 5) Do you really want to manage an AIX system with a 25TB, 50TB or a 100TB file system? After a system crash how long will a FSCK of 100Tb take? Thanks, H. Milton Johnson -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Allen S. Rout Sent: Thursday, June 14, 2007 3:22 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Fw: How to Incorporate a CDL into TSM environment? On Wed, 13 Jun 2007 08:43:43 -0400, Johnson, Milton [EMAIL PROTECTED] said: The VTL is a Sepaton S2100-ES and yes it is disk only. I don't see the benefit that a tape backed system would bring, how does that really differ from a physical tape ATL with TSM providing a DISKPOOL front end? Well, exactly. :) But the distinction I wanted to make clear was: if you've decided to store all your data on disk, then TSM has all the primitives necessary to make that disk manageable, and you can discard the intermediate appliance that makes the disk pretend to be a bunch of tape drives. That's what everyone's getting at when they talk about FILE devclasses. So if you bought 23 TB of slow disk plus a pretend-im-tape-box, then the tape box was a waste, if you're using TSM. If you're using something without TSM's volume primitives, it could be extremely important. - Allen S. Rout
Re: Fw: How to Incorporate a CDL into TSM environment?
The VTL is a Sepaton S2100-ES and yes it is disk only. I don't see the benefit that a tape backed system would bring, how does that really differ from a physical tape ATL with TSM providing a DISKPOOL front end? Fewer tape-head-hours: I understand your confusion, there was no way to reduce the required tape-head-hours, but with a VTL if I need 30 physical tape drives then I configure the VTL as having 45 virtual drives, more than enough. There is no price difference for configuring my VTL as having 1 tape drive or 64 tape drives. Off topic: Configuration Based Pricing: I pray Sepaton will not start, and other vendors will not continue, a pricing scheme based up how you configure the software you PURCHASED. What's next, you have to may extra to your OS vendor for each file system you create? Thanks, H. Milton Johnson -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Allen S. Rout Sent: Tuesday, June 12, 2007 3:41 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Fw: How to Incorporate a CDL into TSM environment? On Tue, 12 Jun 2007 12:16:27 -0400, Johnson, Milton [EMAIL PROTECTED] said: Why a VTL? With us we found that when we out grew our physical library we would have to have to buy over 30 physical drives in order to be able to do backups, restores, cut off-site tapes and reclaim on/off site tapes in the time allowed. That amounted to some serious money, more than our VTL costs. I'm interested in the details on this. The VTL is disk-only, or is it tape backed? I'm confused about how you need fewer tape-head-hours when you virtualize processes. - Allen S. Rout
Re: Fw: How to Incorporate a CDL into TSM environment?
As I see it, there are two areas where you get performance hits when restoring from non-collocated volumes: 1) Tapes Mounts: In my experience my VTL makes this problem insignificant. 2) Spinning Sequential Media: Yes, VTL volumes are sequential and if you define your tapes as 50GB native and then with compression get 100GB written to the tape, you may have to spin through 99.9GB of data to retrieve a 0.1Gb file. However if you define 10GB volumes you only have to spin through 1/5 of the data to reach your 0.1GB file. Also with smaller volumes you are more likely to get natural collocation because a client that writes directly to tape is more likely to fill up a tape. Obviously if you define smaller and smaller volumes at some point you will have a tape mount bottle neck. Just one way to manage the trade offs. H. Milton Johnson -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Nicholas Cassimatis Sent: Monday, June 11, 2007 12:45 PM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Fw: How to Incorporate a CDL into TSM environment? A couple of comments about what Wanda said about collocation and VTL's: At some point, you do have a finite number of mount points defined for your VTL. Even if virtual tape mounts are near instant, there is still some overhead. A large number of clients mounting virtual tape after virtual tape after virtual tape will have some sort of negative effect on the overall throughput of their sessions. I'm not saying it will be significant, but it could get there, depending on the VTL technology. A few milliseconds here, a few there, and a controller that gets bogged down under the mount request queue, you could cause yourself some issues. And don't forget that virtual tapes are the same as physical tapes in one major factor - they're sequential! So non-collocated storage pools could have multiple clients asking for the same virtual tape, so there would be a wait queue for the virtual tape. A VTL doesn't resolve this type of contention, as it's at the TSM level. I would argue that the cost of creating collocated volumes in a VTL is negligible, and still has benefits on the restore side. To echo a number of others comments in the thread - if you don't plan it out right, it's not going to work. That goes for just about anything, from vacations to VTL's! Nick Cassimatis - Forwarded by Nicholas Cassimatis/Raleigh/IBM on 06/11/2007 01:33 PM - And you don't have to collocate in a VTL, since there is zero effective tape mount time.
Re: How to Incorporate a CDL into a TSM environment?
VTL and over subscription as I understand it. Definition: When (tape volume size) X (number of defined volumes) native capacity of VTL you have over subscribed. If you try to fill-up all your defined volumes to their defined native capacity you will fail as you will run out of space on your VTL. Why would one want to over subscribe? If you define a large tape volume size (i.e. 100GB), and only want to write 10GB to a tape then yes it would be neat if the VTL only allocated the actual space written to virtual tape volume (i.e. 10GB). When would this be beneficial in the TSM application? 1) TSM DB backups: Why waste a 100GB volume for one 20GB backup? 2) Using Collocation: If you collocate a client with 50GB of space then why waste a 100GB volume on the client? But the problem is as you point out, when you move a tape from pending to scratch the getting the VTL to reclaim the space previously allocated to the virtual tape volume involves: A) Checking out the scratch volume from TSM (so it will not attempt to use it during the following steps) B) Delete the volume from the VTL (this returns the space to the VTL) C) Redefining tape volume to the VTL D) Checking in and labeling the redefined volume into TSM (I imagine that a VTL could replace steps B C by truncating a volume, but you would still have to get TSM to rewrite the truncated label.) This is not a procedure I wanted to manage in a manual or automated manner, so I chose the following: 1) Define small virtual tape volumes (i.e. 10GB) 2) Do not use collocation 3) Do not over subscribe I have found tape mount time to be insignificant and the smaller virtual tape sizes to makes collocation unnecessary. This is just my way of managing the trade offs. Thanks, H. Milton Johnson -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Neil Schofield Sent: Monday, June 11, 2007 5:50 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] How to Incorporate a CDL into a TSM environment? Hi there We too are in the throes of a debate about virtual vs. physical tape libraries. On the VTL side, much is made of the ability to over-provision the disk capacity - eg a 100Gb virtual tape will only occupy as much space on disk as has been written to it. As a result, so the theory goes, we need only consider the occupancy when sizing the VTL. In a TSM environment, this seems to be wrong on a number of counts. - We still need to take into account the overhead of the reclaimable space on a virtual tape. This can be managed by varying the reclamation thresholds, but not eliminated. - A pending delete volume will still occupy an underlying disk capacity equivalent to its size. - Since the conversion of a pending delete volume to a scratch tape takes place purely in the TSM database, a virtual scratch tape will also occupy the full disk space on the VTL. until it is re-used. So am I correct in thinking that in the whole scratch, filling, full, reclaim, pending, delete, scratch lifecycle of a storage pool volume, the only time that we get the benefit of the over-provisioning is when it's filling? In our current physical tape environment (with collocation at the node level), only about 20% of volumes are filling. Ignoring de-dupe for now, does it seem reasonable to base the sizing for a replacement on the total physical tape capacity of the existing library and some estimates of expected growth. Regards Neil Schofield Yorkshire Water Services Ltd. - Are you a cactus or a sponge? Go to the on-line quiz at http://www.yorkshirewater.com/becool to find out how water efficient you are. Only available in Yorkshire. YORKSHIRE WATER - WINNER OF THE UTILITY OF THE YEAR AWARD 2004, 2005 AND 2006 The information in this e-mail is confidential and may also be legally privileged. The contents are intended for recipient only and are subject to the legal notice available at http://www.keldagroup.com/email.htm Yorkshire Water Services Limited Registered Office Western House Halifax Road Bradford BD6 2SZ Registered in England and Wales No 2366682
Re: Fw: How to Incorporate a CDL into TSM environment?
Yes a virtual tape volume can be accessed only by one client at a time and if two processes/clients try to access the same volume at the same time one process/client must wait. Again smaller volume sizes decreases the chance that a contention would happen and also decrease the contention duration. Why a VTL? With us we found that when we out grew our physical library we would have to have to buy over 30 physical drives in order to be able to do backups, restores, cut off-site tapes and reclaim on/off site tapes in the time allowed. That amounted to some serious money, more than our VTL costs. When you also take into account the costs of the much larger DISKPOOL a physical tape library requires, growing a physical tape library in a TSM environment is not cheap. The VTL footprint is also smaller which also should considered in the total cost of ownership. Sorry, but we had to justify our VTL purchase. Thanks, H. Milton Johnson -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Nicholas Cassimatis Sent: Tuesday, June 12, 2007 10:55 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Fw: How to Incorporate a CDL into TSM environment? I'm not looking at the spinning through the volume to find the file, I'm focused on the fact that a volume can only be accessed by one client at a time. You have to read the data to be restored, which takes time. If you have one client reading the volume, any other access to that volume has to queue up. With a slow client (or a fast one pulling a large file), you can develop some access contention, which is a bottleneck that collocation resolves. That's why I still see collocation playing with VTL's. It all comes back to Why do you want a VTL? which is another way of asking, What problem are you trying to solve/avoid? I'm sure there are people who are getting VTL's because they have to spend their budget or they lose it - and the rest of us are jealous of them for that! But, as with most other technologies, implementing a VTL just moves the bottleneck/weakest link to another spot, which may not be the best solution for a given environment. Nick Cassimatis - Forwarded by Nicholas Cassimatis/Raleigh/IBM on 06/12/2007 11:41 AM - ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU wrote on 06/12/2007 11:13:30 AM: As I see it, there are two areas where you get performance hits when restoring from non-collocated volumes: 1) Tapes Mounts: In my experience my VTL makes this problem insignificant. 2) Spinning Sequential Media: Yes, VTL volumes are sequential and if you define your tapes as 50GB native and then with compression get 100GB written to the tape, you may have to spin through 99.9GB of data to retrieve a 0.1Gb file. However if you define 10GB volumes you only have to spin through 1/5 of the data to reach your 0.1GB file. Also with smaller volumes you are more likely to get natural collocation because a client that writes directly to tape is more likely to fill up a tape. Obviously if you define smaller and smaller volumes at some point you will have a tape mount bottle neck. Just one way to manage the trade offs. H. Milton Johnson
WinTel Bare Metal Restore
Due to the lack of recent religious wars on this forum, I'm forced to ask: What is the best method to back-up and perform a reliable and successful Bare Metal Restore of a WinTel platform (Windows NT/Server 2000/2003/XP/etc.) using a TSM AIX server? Methods requiring a third party solution are acceptable. Solutions allowing a BMR to dis-similar hardware are preferable. Personally I view the need to do a BMR on a WinTel platform as an opportunity to bring up another AIX server, but that is yet another religious war. Thanks, Milton
Re: for those using VTL
1. Sepaton 2. Yes 3. No 4. No 5. No It's just a fast library. Eliminates the need for collocation. Thanks, Milton Johnson -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Gill, Geoffrey L. Sent: Thursday, March 29, 2007 4:06 PM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] for those using VTL We have a number of vendors coming in with their wares and I was wondering if those who use a VTL might pass on some info. As you all know when you're in these types of sales pitches you always hear how great theirs are and that nobody else can do what they do. My questions are below. 1. What VTL did you choose? 2. Is it all they said it would be? 3. If you do it over again would you choose differently and if so which one? This could also relate to wishing a current product was out at the time you made your decision. 4. Is anyone using their VTL in a multi-system environment where you have either more than 1 TSM server and/or both TSM 'AND' Netbackup? 5. Is anyone replicating their VTL to a DR site? If so are you experiencing any issues there? I understand there is going to be many answers here but I'd prefer to get the lowdown on how things work from those that are using them and not from someone who tells me how it's going to work. Geoff Gill TSM Administrator PeopleSoft Sr. Systems Administrator SAIC M/S-G1b (858)826-4062 Email: [EMAIL PROTECTED]
Re: Shrinking scratch pools - tips?
Unfortunately there are many reasons why an Oracle backup does not get deleted. My point was to examine your nodes backing up via TDP. A 100GB database that is deleting old back ups can eat up a TB fairly quickly. Thanks, Milton Johnson -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Rainer Holzinger Sent: Wednesday, March 28, 2007 11:54 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Shrinking scratch pools - tips? Hi Milton, one reason, 'old' TDPO/RMAN backups will not be expired anymore could be that your Oracle DBA's are using a different RMAN recovery catalog now. So every TDPO/RMAN backup which would be part of the 'old' RMAN recovery catalog wouldn't be expired anymore. Another reason could be that your Oracle databases are having a different DBID now for some reason. This is most likely if an Oracle database has been 'cloned' from another one. I have noticed both situations a couple of times in our installation. best regards, Rainer RHo-Consulting Alter Bahnhof 13 D-93093 Donaustauf phone: +49 9403 969174 mobile: +49 162 2807 888 email:[EMAIL PROTECTED] CONFIDENTIALITY NOTICE: This e-mail is confidential and may also be privileged. If you are not the intended recipient, please notify the sender IMMEDIATELY; you should not copy the e-mail or use it for any purpose or disclose its contents to any other person. VIRUSES: Although there have been taken steps to ensure that this e-mail and attachments are free from any viruses, the recipient should at its sole discretion take the necessary measures to ensure that the received messages are actually virus free -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Johnson, Milton [CCC-OT_IT] Sent: Wednesday, March 28, 2007 11:23 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Shrinking scratch pools - tips? I frequently find the culprit to be Oracle backups made via TDP/RMAN (but it could be any backup made via TDP). Something happens and they stop deleting old backups. I look at likely candidates using: set sqldisplaymode wide select NODE_NAME,cast(BACKUP_DATE as date) as BACKUP_DATE,STATE,cast(DEACTIVATE_DATE as date) \ as DEACTIVATE_DATE,HL_NAME,LL_NAME from BACKUPS where NODE_NAME='Client's Node Name' order by BACKUP_DATE If it shows old backups then I have the DBAs correct the problem and use tdposync to remove the old backups. Milton Johnson -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Bell, Charles (Chip) Sent: Friday, March 23, 2007 9:41 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Shrinking scratch pools - tips? Since this a GREAT place for info, etc., I though I would ask for tips/how-to's on tracking down why my scratch pools are dwindling, for LTO/LTO2/VTL. My guess is I have a couple of clients that are sending out a vast amount of data to primary/copy. But without a good reporting tool, how can I tell? Expiration/reclamation runs fine, and I am going to run a check against my Iron Mountain inventory to see if there is anything there that should be here. What else would you guys/gals look at? :-) Thanks in advance! God bless you!!! Chip Bell Network Engineer I IBM Tivoli Certified Deployment Professional Baptist Health System Birmingham, AL - Confidentiality Notice: The information contained in this email message is privileged and confidential information and intended only for the use of the individual or entity named in the address. If you are not the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this information is strictly prohibited. If you received this information in error, please notify the sender and delete this information from your computer and retain no copies of any of this information.
Re: Shrinking scratch pools - tips?
I frequently find the culprit to be Oracle backups made via TDP/RMAN (but it could be any backup made via TDP). Something happens and they stop deleting old backups. I look at likely candidates using: set sqldisplaymode wide select NODE_NAME,cast(BACKUP_DATE as date) as BACKUP_DATE,STATE,cast(DEACTIVATE_DATE as date) \ as DEACTIVATE_DATE,HL_NAME,LL_NAME from BACKUPS where NODE_NAME='Client's Node Name' order by BACKUP_DATE If it shows old backups then I have the DBAs correct the problem and use tdposync to remove the old backups. Milton Johnson -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Bell, Charles (Chip) Sent: Friday, March 23, 2007 9:41 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Shrinking scratch pools - tips? Since this a GREAT place for info, etc., I though I would ask for tips/how-to's on tracking down why my scratch pools are dwindling, for LTO/LTO2/VTL. My guess is I have a couple of clients that are sending out a vast amount of data to primary/copy. But without a good reporting tool, how can I tell? Expiration/reclamation runs fine, and I am going to run a check against my Iron Mountain inventory to see if there is anything there that should be here. What else would you guys/gals look at? :-) Thanks in advance! God bless you!!! Chip Bell Network Engineer I IBM Tivoli Certified Deployment Professional Baptist Health System Birmingham, AL - Confidentiality Notice: The information contained in this email message is privileged and confidential information and intended only for the use of the individual or entity named in the address. If you are not the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this information is strictly prohibited. If you received this information in error, please notify the sender and delete this information from your computer and retain no copies of any of this information.
Re: VTL Sepaton vs SUN/STK(FalconStor)
We have been using Sepaton for almost two years with no regrets. Sepaton has excellent in-house knowledge of TSM, and configuring both the VTL and TSM to use the VTL are very straight forward and simple. Their support has been top-notch and never disappointed me, or my management. The products have proven reliable. As far as performance, my hardware is not capable of pushing the VTL to Sepaton's stated limits, but this is due to my TSM server's limits not the VTL. I look forward to trying Sepaton's content aware compression, if you get just 1/3 the advertised compression it would prove very economical. If you need cartridge replication to a remote VTL over a network they also support that. When I went looking for a VTL, I wanted one vendor for both the VTL hardware and software. You don't state the hardware your TSM is on, but demand the vendor send you an evaluation VTL you can try on your server, Sepaton had no problems with that. Any other questions feel free to ask and good luck, H. Milton Johnson -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Larry Peifer Sent: Friday, August 11, 2006 3:02 PM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] VTL Sepaton vs SUN/STK(FalconStor) We've narrowed down our search for a VTL appliance to use with TSM to the 2 subject vendors. I'd like to hear the pros/ cons from the TSM users community on their experiences with these devices: Reliability, vendor service, performance etc. All comments welcomed. Larry Peifer TSM / AIX Administrator
Re: Tape Drive Choices: What, and why?
On-site tapes: Virtual Tape Library (Sepaton S2100-ES2) Off-site tapes: IBM 3494 with 2 3590E1A drives H. Milton Johnson -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Allen S. Rout Sent: Wednesday, August 02, 2006 9:37 PM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Tape Drive Choices: What, and why? Hi, all. I'm looking into what choices folks have made for their tape drives, and why they picked what they did. I'm really happy with what I've got, but I figure that state is perpetuated by questioning it, rather than settling in. I'm running 3590s (on the way out) and 3592s. The capacity is close to the top per-cartridge (500G raw per cart), and the speed is quite good, ~80GB/s. When we added the 1-gen 3592s a few years ago, seek speed was an important difference between that and the then current LTO2; I understand that LTO3 has made up some ground there but not all the way. My drives are getting a duty cycle approaching 100%; there are very few times of the day I don't have jobs waiting in line for them. My SE is kind of nervous about them; he says we're mean to them. :) I am given to understand that this kind of treatment tears LTO3s apart; they aren't designed for that kind of 24x7 usage. In a nutshell, I love my 3592s, I run them constantly and have essentially no maintenance issues with them. I've got some of them in a remote installation ~300 miles away, and run them with confidence, so far borne out. (8 months of production) So, any opinions? Love stories for LTO3 or that sun whatever-1000 ? Hate stories? - Allen S. Rout
Re: Reclamation processing behavior
This is normal behavior when reclaiming a storage pool that has a NEXT STGPOOL defined. I became aware to it when I upgraded to 5.3, I also have a VTL. However, being a VTL has nothing to do with it, it's having a NEXT STGPOOL defined that elicits this behavior. If you use the reclaim stg command then there is no delay. I found an IBM bulletin on the subject which is how I found that IBM considers normal behavior, that was 6 months ago so don't ask me to find it again. Hope that this helps, H. Milton Johnson -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Thorneycroft, Doug Sent: Tuesday, July 25, 2006 5:09 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Reclamation processing behavior They should both appear as ATL's to Tivoli. The real tape is a Qualstar, with AIT Drives and Media, and the VTL appears as a Quantum, With DLT Drives and media. And Both are defined as primary sequential storage pools. I would expect the behavior to be the same. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of Prather, Wanda Sent: Tuesday, July 25, 2006 2:59 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: Reclamation processing behavior This really isn't a problem, but I was just curious if anyone knows why Tivol treats the two types of storage pools differently. From TSM's point of view, why do you think they are 2 different types of storage pools? Aren't they both sequential tape devices, from the TSm server's point of view? Wanda Doug Thorneycroft Systems Analyst County Sanitation Districts of Los Angeles County 1955 Workman Mill Road Whittier, CA 90601 Tel: (562)699-7411, Ext. 1058 Fax:(562)695-6756 www.lacsd.org
Re: Sepaton users and experiences?
Chip, We have had a Sepaton S2100-ES2 for ~1 1/2 years and can report it has given very little trouble. Think of it as a library on steroids being very fast especially with tape mounts, dismounts and positioning. Our environment is: AIX 5300-04-00 Storage Management Server for AIX-RS/6000 - Version 5, Release 3, Level 3.0 S2100-ES2 (14 TB) IBM 3494 ATL with two 3590E1A drives The Sepaton configures and runs just like any other automated tape library, it doesn't require any special drivers, care or feeding. We use the Sepaton for our primary storage pools and use the 3494 to make copy pool storage volumes for the vault. Our needs grew to exceed the abilities of our 3494, so we looked to expand and a Virtual Tape Library (VTL) seemed to provide the most bang for the buck. While we are an IBM shop, IBM did not have a VTL at the time. We use a lot of HP wintel servers, but HP also did not have a VTL. Sepaton support has been excellent, when something does go amiss their support personnel not only know their product, all too rare these days, they also know TSM! Their engineers can read the bits flowing through a fibre channel, or off a drive, and know what they mean. Hope this helps, Milton -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Bell, Charles (Chip) Sent: Tuesday, June 20, 2006 10:27 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Sepaton users and experiences? We are looking hard at purchasing Sepaton. Are there any users out there can briefly describe their like/dislikes of the S2100 in a TSM environment? Also, it would be helpful to know if you already had relationships with HP and IBM, but did not purchase their OEM'd products (Sepaton and FalconStor respectively). Thanks all! God bless you!!! Chip Bell Network Engineer I IBM Tivoli Certified Deployment Professional (ITSM 5.2) Baptist Health System Birmingham, AL Office (205) 715-5106 Pager (205) 817-0357 Home (256) 739-0947 - Confidentiality Notice: The information contained in this email message is privileged and confidential information and intended only for the use of the individual or entity named in the address. If you are not the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this information is strictly prohibited. If you received this information in error, please notify the sender and delete this information from your computer and retain no copies of any of this information.
Re: OT? TSM in a hospital environment
This is an issue with turn-key systems. If you buy an application from a vendor and plan to hold them responsible for the application's uptime/availability and data restoration, it is reasonable that the vendor can dictate the hardware/os used, the ability to run other software on the system and the backup methodology implemented. You end up with some systems being outside the TSM back-up environment but that is part of the price paid when you must have a critical, third party vendor application. You still have to perform due diligence such as a demonstration of restoration at the time of implementation. Milton -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Tyree, David Sent: Monday, June 19, 2006 12:29 PM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] OT? TSM in a hospital environment Are there any folks on the list that are using TSM in a hospital? Sometimes we have to battle with some of our software venders to allow us to backup their system using TSM. Sometimes they will tell us that the system is FDA approved as is and must be backed up using a built-in tape drive and we can't touch the system. Some times that might be believable but not always. It seems that GE appears to be especially hard headed in this regard. We bought into TSM because you back up anything (well most anything) and not have to worry about having assorted different tape drives scattered everywhere. I would like to compare notes with other TSM people if possible. thanks David Tyree Enterprise Backup Administrator South Georgia Medical Center 229.333.1155 text pager [EMAIL PROTECTED] Confidential Notice: This e-mail message, including any attachments, is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message.
Re: VTL experiences?
I decided on a VTL because I wanted to have LAN-free backup ability and compression with no load on the TSM clients or TSM server. We have been using Sepaton's ES2100 VTL for over a year with no problems (HP rebrands Sepaton's product). There have been numerous threads in this list about VTL implementations: File dev. type vs. VTL, VTL experiences?, Sizing for a virtual tape library, VTS or san disk storage, Questions for people using Virtual tape libraries The big advantage VTLs, and DEVCLASS=FILE volume virtualizers, have over physical tape libraries are sub-second tape mounts, rewinds and dismounts. Combined with fast seek times those characteristics have eliminated my need for collocation. I have been very satisfied with the VTL choice. H. Milton Johnson -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Dearman, Richard Sent: Wednesday, January 04, 2006 2:42 PM To: ADSM-L@VM.MARIST.EDU Subject: VTL experiences? Anyone out there have any good or bad experiences with VTL solutions. I was thinking about budgeting for 1 or 2 in order to phase out the current san file system I am using for TSM disk storage. There are several vendors out there with VTL solutions most notably IBM and EMC. My first choice would be to choose IBM but it is a new product and EMC has been in the market longer. Any comment or recommendation appreciated. Thanks **EMAIL DISCLAIMER*** This email and any files transmitted with it may be confidential and are intended solely for the use of the individual or entity to whom they are addressed. If you are not the intended recipient or the individual responsible for delivering the e-mail to the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is strictly prohibited. If you have received this e-mail in error, please delete it and notify the sender or contact Health Information Management 312.413.4947.
Re: Define path for direct attached fiber
We use a Sepaton S2100-ES2 without problems. Vicki's advice is sound: make sure the vendor's product is TSM certified; make the vendor supply an evaluation system and test thoroughly. A VTL should faithfully emulate a particular physical ATL and particular physical drives. It should not require any drivers or patches unique to the VTL. Keep in mind the following points: 1) If you configure your VTL to be out of specs with the physical ATL you are emulating, your backup application, i.e. TSM, may have a problem. For example if the physical ATL has a max of 800 slots and you configure 1500 slots TSM may complain. 2) The VTL is a software/hardware product. All software has bugs and you may get bit, but then you may get bit by a software bug with a physical ATL also. The important thing is how responsive is the vendor when an issue does arise? This is where interviews with present customers is important. Insist on speaking to customers that have experienced problems. If the vendor can not or refuses to provide as a customer reference someone that had a problem that was successfully promptly resolved then look for a different vendor. Also remember that with a physical ATL you will always be subject to failures caused by wear to mechanical parts. The only mechanical parts in a VTL are fans and drives, and redundancy protects you against those failures. Overall you should expect a quality VTL to be more reliable then a physical ATL, at least this has been my experience. Good luck, I am glad I went to a VTL, Milton Johnson -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Larry Peifer Sent: Friday, December 09, 2005 11:56 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: Define path for direct attached fiber We're beginning to look into VTL and I'd be interested in what systems / vendors your considered and then which one you are going with. Running TSM 5.3 with AIX 5.2ML 5 on RS6000 P650. LTP San Clemente, California Victoria Ortepio [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU 12/09/2005 06:40 AM Please respond to ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU To ADSM-L@VM.MARIST.EDU cc Subject Re: [ADSM-L] Define path for direct attached fiber Be careful with this one. We just purchased a VTL ourselves. We are running TSM 5.2.3. We are currently waiting for a fix with the vendor in order to configure TSM. In TSM V5.3, the code seems to have loosened up. Verify that the TSM version, o/s version, device drivers (o/s or TSM), the type of drives, is a configuration that the vendor has certified. Our problem is with LTO2 drives. Try speaking with one of their customers that has the same configuration as you do. Regards, Vicki MCI Piscataway, NJ -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Thorneycroft, Doug Sent: Thursday, December 08, 2005 5:24 PM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Define path for direct attached fiber We are getting ready to purchase a Virtual Tape library. It will be direct fiber attached to our TSM 5.2.6 Win2K server via a host bus adapter. I was wondering how Tivoli will see the device for the path, is it similar the a scsi attached device ie. LB0.0.0.1 or something completely different?
Re: Disk Only backups
It's been my experience that the problem is not the large number of tapes a restore takes when not collocating, rather it's the large mount, unmount seek and rewind times associated with each tape mount that is the problem. If you have sub-second mount, unmount, seek and rewind times then there is not a large penalty to pay when not collocating. I use a Virtual Tape Library which is just an ATL emulation front end to a disk only stgpool. I do not collocate and have no problem restoring large servers housing thousands of small files, the kind of environment that usually demands collocation. The question to consider is what are the pros cons to a large native disk pool vs. an appliance such as a VTL. I decided on a VTL to preserve LAN-free backup ability and compression. Milton -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Spearman, Wayne Sent: Monday, December 05, 2005 3:34 PM To: ADSM-L@VM.MARIST.EDU Subject: Disk Only backups We are planning to move a large number of our nodes to disk only backups and eliminate tape for them. The diskpools will be devtype=file. I struggle with whether to collocate these disk volumes or not and how large to make them. I've had some discussions with IBM, but would like to ask others to share their experiences with me. Any input would be welcome. Thanks, Wayne - This message and any included attachments are from NOVANT HEALTH INC. and are intended only for the addressee(s). The information contained herein may include trade secrets or privileged or otherwise confidential information. Unauthorized review, forwarding, printing, copying, distributing, or using such information is strictly prohibited and may be unlawful. If you received this message in error, or have reason to believe you are not authorized to receive it, please promptly delete this message and notify the sender by e-mail. If you believe that any information contained in this message is disparaging or harassing on the basis of gender, race, age, disability, religion, or national origin, please contact Novant Health, Inc. at 1 -888-378-8250 or 1-800-350-0094 or forward the e-mail to [EMAIL PROTECTED] Thank you.
Re: VTS or san disk storage
I have 12TB of SATA storage in the form of a Virtual Tape Library (VTL) appliance, in my case a SEPATON S2100-ES2. To TSM it's just a tape library on steroids (rapid mounts, dismounts, etc). I have routinely pushed in excess of 80 MB/sec. with no problems. It's scalable to 1PB storage capacity and 4.3TB/hour. Mine is not that large, configured with only 64 virtual tape drives. The drives even do compression just like a real tape drive. I decided not to go with serial file devices because I did wanted to keep the ability to do LAN-free backups, easy scalability and did not want to force the overhead of compression on the TSM clients or server. Milton Johnson -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Paul Zarnowski Sent: Wednesday, November 30, 2005 10:10 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: VTS or san disk storage Any success stories out there for using large amounts of serial-access disk with TSM? At 06:19 PM 11/29/2005, you wrote: Richard, I share your pain. We have an EMC Clariion CX500 SAN. We have found that AIX in general, and TSM in particular, can just hose the sucker. I have about 6TB of san disk space used for nightly backups and the management of it is just a pain. I am curious what kind of problems you are running into. At the TSM Symposium at Oxford this year, IBM indicated that they were going to further develop the serial access disk support in TSM. And, TSM 5.3 just added the ability for a SAD devclass to span multiple filesystems. After hearing this, we have been leaning towards investing in inexpensive disk managed by TSM rather than buying a VTL appliance. I'm interested in other's comments about where, specifically, they are having problems managing SAD directly by TSM. -- Paul ZarnowskiPh: 607-255-4757 Manager, Storage Systems Fx: 607-255-8521 719 Rhodes Hall, Ithaca, NY 14853-3801Em: [EMAIL PROTECTED]
Re: BACKUP STG COMMAND
You could: 1) Create 2 offsite copypools (say OFF1 and OFF2) 2) Day 1 - for each volume in OFF1 do move data volume stg=oFF2 reconstruct=yes done backup stg primarypool OFF2 Bring back all OFF1 volume that are offsite 3) Day 2 - for each volume in OFF2 do move data volume stg=oFF1 reconstruct=yes done backup stg primarypool OFF1 Bring back all OFF1 volume that are offsite 4) Day 3 - go to step 2 -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Aaron Becar Sent: Monday, October 31, 2005 1:16 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: BACKUP STG COMMAND Hey! In an effort to minimize the number of tapes that go off site, is there an option that I can add to the backup stg command to copy everything in the primary pool to the copy pool, and resets the previous copy, and creates a new copy? Thanks!
Re: SOX :-)
My interpretation of electronic vaulting is that the tapes are transferred via wire to the storage vault. If you are doing a backup stg primary_pool copy_pool to a copypool 15 KM away, I would think that you are doing electronic vaulting. The key is you are not doing a physical transportation of tapes. H. Milton Johnson -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of goc Sent: Monday, October 24, 2005 5:46 AM To: ADSM-L@VM.MARIST.EDU Subject: SOX :-) hi all, interesting we also have SOX guys here so my question is how are your experiences with electornic vaulting ? i'm trying to explain to them that we do not export tapes and store them into vault coz we dont need to ... my copy pools are 15 km away :-) is this okay, and does anyone have something similar, i mean with SOX questions. thanks goran
Re: Which Tape Technology?
We were in a similar situation with a 3494 and two 3590E drives. We went with a VTL for the primary stgpools using the 3494 just for offsite copypools and have been very happy with it. Most everything goes straight to the VTL and during the night I do repeated backups of the primary stgpools in the VTL to the copypool stgpool in the 3494. In the morning one final backup from VTL to the 3494 followed by a DB backup and I'm ready to send tapes offsite. Since the primary disk stgpools were reduced to 1GB in size the migration time went to zip. We back up about 1TB per night. Milton -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Richard Rhodes Sent: Thursday, September 22, 2005 6:57 AM To: ADSM-L@VM.MARIST.EDU Subject: Which Tape Technology? Hi Everyone, Currently our tape environment consists of IBM 3494 libraries with 3590H (60gb) drives. It's possible that we may need to greatly expand our environment with some new libraries and drives. This has brought up a discussion about what tape technology we would use. Our environment consists of a mix of large file backups (Oracle databases), small file backups (Netware servers) and lots of stuff in between. If we have to do this, I really can't see purchasing more 3590H drives with cartridges that are only 60gb. I would think we would want to go to the newest 3592 drives or LTO2/LTO3. What are your thoughts/comments/experiences with . . . . . 1) Given our mix of large and small file backups, would LTO tape drives work as well as our current 3590's? 2) Does anyone have any experience using IBMs newest 3592 tape drives? 3) If LTO, is LTO3 the way to go, or stick with older LTO2? 4) Or, should we stick with 3590 drives? With any of the new tape drives, I'm concerned with throughput issues. The newest drives (3592 and LTO3) are so fast that I wonder if it becomes a problem keeping data streaming to them. The capacity is great, but if I can't keep them spinning I wonder if the new drives could cause more problems than they solve. Of course, another option would be a VTL or just local DISK on the TSM server. We've done some initial pricing of some configurations (tape libraries/drives/tapes, disk, and vtl) and so far tape is the least expensive. Just looking for others experiences with this kind of decision . . . . Thanks! Rick - 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: Splitting files across tapes
Are you talking about a 1TB VOLUME, or several smaller volumes (say 10GB) on a 1TB array? H. Milton Johnson -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Prather, Wanda Sent: Tuesday, June 07, 2005 9:07 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: Splitting files across tapes Hi Richard, Thanks for responding; maybe this will give you something to amuse your brain over morning coffee. The reason for the question, mgmt here is considering going to all-disk backup (for onsite). So our sequential volumes will be disk instead of tape. We occasionally have issues with mis-classified data ending up on a tape, and the tape has to be pulled and destroyed. No big deal with a tape. Big deal when the volume is a 1 TB raid array! So the question comes, what is the likelihood that we would contaminate TWO 1 TB raid arrays with a split file? I think for sequential volumes, TSM doesn't know that the volume is full, until it tries to write to it. If there isn't space for the next block, then it mounts a scratch and rewrites the block to a new tape, yes? So can I assume that the file would have to be larger than an aggregate (what is that, MOVESIZETHRESH?) in order to end up split across 2 tapes? Thanks for lending brain power! W -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Richard Sims Sent: Tuesday, June 07, 2005 9:55 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: Splitting files across tapes Hi, Wanda - I don't believe there is any rule, per se: it is just the case that the drive finally reaches end-of-volume (EOV - TSM msg ANR8341I). This results in the subsequent data being written in a spanned Segment on a new volume. Richard Sims On Jun 7, 2005, at 9:36 AM, Prather, Wanda wrote: Does anyone happen to know what rules TSM uses to decide when to split a backup file/aggregate across 2 tapes? Or can you point me to a document? (Management wants to know.)
Re: Encryption
My concerns with TSM based encryption are: 1) Since encrypted data does not compress well the TSM clients must do both the compression and encryption. 2) TSM compression and encryption can be a performance hit on the client increasing back-up time and further degrading performance during the backup period. 3) With TSM encryption the data is encrypted before it leaves the client so all copies of the data are encrypted. 4) With TSM encryption there are keys for each client that must be managed. This could mean hundreds-thousands of keys in some environments. I understand that TSM 5.3 does that management for you. 5) There is no simple way to encrypt data already backed up and on tape. For these reasons I am investigating using an encryption appliance that sits transparently between the TSM server and the tape drives used to write offsite tapes: 1) The appliance does the compression encryption in hardware so there is no performance hit to the clients. 2) Only the backup copies going off site are encrypted, it is not all or nothing. 3) There is only one set of encryption keys to manage. 4) Data already backed up and on tape can be encrypted using the move data command. 5) Stronger encryption than that provided by TSM is available. H. Milton Johnson -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Henrik Wahlstedt Sent: Wednesday, May 25, 2005 2:36 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: Encryption Hi Eric, Yes TSM can encrypt your data, both in 5.2 (des56) and 5.3 (aes 128). You add the lines in a client optionset or in dsm.opt. INCLUDE.ENCRYPT c:\...\* ENCRYPTKEY PROMPT or SAVE. Check the client manuals for more information. //Henrik Jones, Eric J [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU 2005-05-25 03:32 Please respond to ADSM: Dist Stor Manager To: ADSM-L@VM.MARIST.EDU cc: (bcc: Henrik Wahlstedt) Subject:Encryption Good Evening. Running TSM 5.2.2 on AIX 5.2 Clients are a mix ofSolaris 7,8,9 AIX 4.2, AIX 5.2, Windows NT, Windows 2000 and Windows 2003 most running TSM 5.2.2. I've been reading the forums and was thinking I would probably not have to worry about this until now. I was asked to check and see what it would take to encrypt our data. I have 2 questions. 1: Is it a problem to use an encryption device to encrypt the data before it is sent to the TSM server?I know I would have to have the encryption key to restore the data but I was wondering if there were any problems that I would face. 2: Can TSM encrypt the data? I've read 1 article that indicated it was in TSM 5.3 but I did not see much on 5.2.2 which we are running. Are there any potential problems with using TSM to encrypt if it is possible? I know if you loose the key your done but other than that. Thanks for all the help, Eric
Re: Virtual tape libraries
A 2 GB limit seems a bit restrictive, I wonder if that is a file system limit on the VTL. My VTL has no such restriction. When I installed my VTL I did not notice any change in TSM DB size due to an increase in the number of volumes. The amt of data per volume seems minimal. H. Milton Johnson -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Jon Evans Sent: Friday, May 20, 2005 5:02 AM To: ADSM-L@VM.MARIST.EDU Subject: Virtual tape libraries I have been experimenting with a virtual tape library connected to TSM (Windows 2k3 5.1.6.3 server) All seems to work perfectly and TSM is none the wiser. However, The maximum cartridge size in this virtual library is 2GB. I am currently using LTO1 and getting upto 100 times this amount of data on one tape. My database is 56GB and I currently have approx 600 volumes My question is.. if I were to move to a virtual library and had to increase the number of my volumes by up to 10 times What impact would this have on my database ? Thanks in advance Jon Evans Storage Consultant KBR
Re: Tape Encryption Appliances
1) You will need appliance(s) at the DR site, consider it an accessory to your library. 2) The appliances I've seen allow: A) Backing up the keys to DR media (CDROM, Smart Cards, files, etc.) for use at the DR site B) Hot appliance(s) can be kept off site but on the network, (i.e. your DR Site or another company site) and clustered with your production appliances. The appliances then keep their keys synced via an encrypted link. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Prather, Wanda Sent: Monday, May 16, 2005 12:13 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: Tape Encryption Appliances I have never heard of this applicance; but my first question would be, whatcha gonna do when you have to take your tapes to a DR site? -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Johnson, Milton Sent: Thursday, May 12, 2005 10:18 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: Tape Encryption Appliances This has not generated any response, and there is nothing in the archive, so I thought I might try once more. I'm looking for experiences/comments using TSM with a tape encryption appliance that sits between the TSM server and the tape drives. The appliance provides transparent compression and encryption. The two products I have found are NeoScale's CryptoStor Tape 700 and Decru's DataFort T-Series products. Any comments about these or another product would be appreciated. Thanks, H. Milton Johnson -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Johnson, Milton Sent: Thursday, May 05, 2005 8:19 AM To: ADSM-L@VM.MARIST.EDU Subject: Tape Encryption Appliances Has anyone had any experience with tape compression/encryption appliances such as the NeoScale CryptoStor Tape 700 (http://www.neoscale.com/English/Products/CryptoStor.html)? It is an appliance that sits between the TSM Server and the Tape Drives and transparently provide compression and encryption of tapes. We are using 3590E1A drives and comments from anyone using such a device with or without 3590E1A drives would be appreciated. Thanks, H. Milton Johnson
Re: Tape Encryption Appliances
This has not generated any response, and there is nothing in the archive, so I thought I might try once more. I'm looking for experiences/comments using TSM with a tape encryption appliance that sits between the TSM server and the tape drives. The appliance provides transparent compression and encryption. The two products I have found are NeoScale's CryptoStor Tape 700 and Decru's DataFort T-Series products. Any comments about these or another product would be appreciated. Thanks, H. Milton Johnson -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Johnson, Milton Sent: Thursday, May 05, 2005 8:19 AM To: ADSM-L@VM.MARIST.EDU Subject: Tape Encryption Appliances Has anyone had any experience with tape compression/encryption appliances such as the NeoScale CryptoStor Tape 700 (http://www.neoscale.com/English/Products/CryptoStor.html)? It is an appliance that sits between the TSM Server and the Tape Drives and transparently provide compression and encryption of tapes. We are using 3590E1A drives and comments from anyone using such a device with or without 3590E1A drives would be appreciated. Thanks, H. Milton Johnson
Re: Archives missing from archive list.
As usual Richard is correct Syntax -Query ARchive--+--+--+- filespec---+ '- options-' '- filespec-' Parameters filespec Specifies the path and file name that you want to query. Use wildcard characters to specify a group of files or all the files in a directory. If you use wildcard characters, enclose the file specification in double quotation marks. Specify an asterisk (*) to query all archived files in the current directory. ^^ H. Milton Johnson -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Richard Sims Sent: Monday, May 09, 2005 6:16 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: Archives missing from archive list. On May 8, 2005, at 11:45 PM, Stuart Lamble wrote: ...It would be nice to know why this is happening, ... The Archive facility is very much filespace-oriented: If you archive into one filespace, you can't expect to list its files by querying from another filespace. Backup, Archive, and HSM all have very different orientations. Richard Sims
Tape Encryption Appliances
Has anyone had any experience with tape compression/encryption appliances such as the NeoScale CryptoStor Tape 700 (http://www.neoscale.com/English/Products/CryptoStor.html)? It is an appliance that sits between the TSM Server and the Tape Drives and transparently provide compression and encryption of tapes. We are using 3590E1A drives and comments from anyone using such a device with or without 3590E1A drives would be appreciated. Thanks, H. Milton Johnson
Integrating ITSM with Iron Mountain's SecureSync
A few questions regarding using Iron Mountain (IM): 1) Is anyone using TSM and IM's SecureSync application? 1A) If so how do you integrate TSM with SecureSync? 2) Since TSM sends tapes to the vault and requests return of vaulted tapes in a random sequence, does anyone allow their Vault Vendor to sign that they picked-up a closed container of tapes but not document the individual tapes in the container until after the container has been received at their vault? In other words the vault company says I don't want my courier to take the time to verify each tape he's picking up, only that he picked up something. After that container arrives at the vault we'll note what that something was. This sounds undesirable to me but I was wondering if anyone followed this practice? Thanks, H. Milton Johnson
Re: Questions for people using Virtual tape libraries
1) Sepaton states that their VTL is TSM Certified 2) When we initially installed our S2100-ES we did have a Fiber adapter communication/compatibility problem. Sepaton's response was: A) To quickly acknowledge the problem. B) As an interim solution Sepaton sent us a S2100-DS that did not have the problem as it uses a different chip set (the ES used a QLogic chip set and the DS used a LSI chip set). C) Recreated the problem in their lab. D) Developed a firmware update to correct the problem. E) Delivered the firmware solution in a timely manner. F) During this period we had regularly scheduled conference calls with Sepaton so that both sides were aware of the status and expectations. We have not had any problems in the period since then, ~6 months ago. In implementing new technologies you have to expect problems, the key is how does the vendor respond? We found Sepaton's response to be professional, above board and competent. H. Milton Johnson -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Prather, Wanda Sent: Thursday, March 17, 2005 9:52 AM To: ADSM-L@VM.MARIST.EDU Subject: Questions for people using Virtual tape libraries For those of you who have made the leap to Virtual tape libraries: I don't see any of these devices on the TSM hardware support page; do you just base your TSM support on the device type that the VTL emulates? And has anyone run into problems with a VTL that have to be resolved by the VTL vendor? Any kind of SCSI errors, or problems other than replacing physical disks? Thanks!
Re: a simple question
I use a Combination of the Two as Janis would say. I tend to create TSM scripts to perform specific functions, then make calls to this library of functions from outside scripts. For instance I have a TSM script called bu_disk_stg_to_copypool that backs-up all primary stg pools of type disk to my copypools. When an outside script wants to perform that task it runs bu_disk_stg_to_copypool. If I add or delete a primary stg pool I just update bu_disk_stg_to_copypool instead of locating and modifying multiple outside scripts. H. Milton Johnson -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Warren, Matthew (Retail) Sent: Thursday, February 17, 2005 7:19 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: a simple question Interesting. You know, I didn't think the TSM scripting would be used much by people, to me it appears easier to control TSM with external scripts - to the extent I have never more than glanced at the TSM scripting abilities. Do people mix the two, or is it a case of 'We use TSM scripting' or 'We use Shell / python etc..' based on preference / environment restrictions. Are there any benefits to TSM scripting other than it doesn't require an external process and relevant software to achieve it? Matt. _-'-_ -|- -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Thursday, February 17, 2005 1:11 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: a simple question == On Thu, 17 Feb 2005 07:18:41 -0500, Richard Sims [EMAIL PROTECTED] said: Edit scripts outside of TSM, and put the edited version into effect with 'DEFine SCRIPT ... FILE='. Trying to edit Scripts within the TSM server is just too awkward. Amen. And to amplify and suggest: I've got several scripts whose meaning is 'reload this other script, from this well-known file location' For instance my 'retemp' script has del scr temp def scr temp file=/u/adsm/tmp/temp.scr so I can edit 'temp.scr' and pretend that it's close to the same thing as my temp script. This model has saved me a lot of time: I've got a large passel of scripts (40-60) I use in the management of my covey of servers, and just a few maintainance scripts let me reload all of them. - Allen S. Rout ___ Disclaimer Notice __ This message and any attachments are confidential and should only be read by those to whom they are addressed. If you are not the intended recipient, please contact us, delete the message from your computer and destroy any copies. Any distribution or copying without our prior permission is prohibited. Internet communications are not always secure and therefore Powergen Retail Limited does not accept legal responsibility for this message. The recipient is responsible for verifying its authenticity before acting on the contents. Any views or opinions presented are solely those of the author and do not necessarily represent those of Powergen Retail Limited. Registered addresses: Powergen Retail Limited, Westwood Way, Westwood Business Park, Coventry, CV4 8LG. Registered in England and Wales No: 3407430 Telephone +44 (0) 2476 42 4000 Fax +44 (0) 2476 42 5432
Re: Centricstor and TSM?
I am not familiar with their product, but I have been using Sepaton's Virtual Tape Library (VTL) for several months with no problems. The Centricstor appears to a similar product but I am at a loss as to why it would need third party software for syncronizing scratch tapes, what ever that is. A VTL should appear to TSM as just another automated tape library (ATL) and TSM would use it just like any other ATL. All TSM operations (backups/restorations/reclamations/etc.) happen just as with an ATL, just much faster. Sepaton's VTL has been TSM certified if that helps in making the VTL leap. I have been very satisfied in going with a VTL for on site storage pools and my 3494 for off site storage. H. Milton Johnson -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Jim Kirkman Sent: Tuesday, February 08, 2005 9:23 AM To: ADSM-L@VM.MARIST.EDU Subject: Centricstor and TSM? Anyone out there familiar with this product? It's marketed as a virtual tape solution and they make a case for using it to Improve Performance and Reduce Costs in a TSM Environment. In this document they also reference Gresham Software's 'Enterprise DistributTape' as a requirement for syncronizing scratch tapes but infer that 5.3 will incorporate this functionality. Not that we have any immmediate plans to go to 5.3 but I am curious whether that actually happened. Thanks! -- Jim Kirkman ITS Infrastructure UNC-Chapel Hill 919-698-8615
Re: size of active vs. inactive?
We have been using a VTL for 3-4 months and we consider it a success. Environment: * OS: AIX 4330-11 * TSM: Version 4, Release 2, Level 1.7 * Physical Library: Single frame 3494 w/2 3590E1A Drives * VTL: Sepaton ES2100 10.5TB (Raw) * VTL Drive Config: 50 Drives *VTL Tape Vol Size: 10 GB (picking a size is a religious belief) * VTL Tape Volume Quantity: 839 * Avg Nightly Backup Amt: ~750 GB * Client Types: AIX, Windoze(NT, 2000, 2003), Oracle (TDP), . Microsoft SQL (TDP), Novell * Collocation: None *Total Primary Stg Amt: ~10.3 TB Problems Leading Requiring Upgrade/VTL Purchase: * Poor restoration speed for file servers due to: - No use of collocation because of single frame 3494, amt of primary stg, desire . to make tape management simple (read desire tape library to house all primary . tape volumes, no overflow to a cabinet/vault) - Only 2 drives - Both drives spinning tapes 95%-99% of day doing migrations, backups and . reclamations, leaving little time for restorations. * Poor offsite reclamation performance: Offsite tape count growing to ~500 with . 400 being 50% reclaimable * Onsite tape count growth forcing expansion of existing library/purchase of new . library and associated disk stgpool Reasons Pushing to VTL over DASD and Physical Library: * Ability to do LAN Free back-ups w/o Sanergy * Storage compression w/o load on TSM server or client * Performance: Mounts/Unmounts, Reads, Writes (Comparison with physical tapes . need to keep in mind your clients/server may not be able to continuously . stream data to tape. * Desire to break out of the structure where growth requires growth of library . system AND disk stgpool * Ease of implementation Benefits Realized: * All of the problems requiring the upgrade have been eliminated * All primary stg pool data has been moved to the VTL * 3494 is only used for the offsite COPYPOOL stgpools and offsite DB back-ups * offsite COPYPOOL reduced to ~195 tapes with ~5 being 50% reclaimable * 3494 drives no longer have to spin 95% of the day * Back-up and restorations greatly improved w/o use of collocation * Implementation was easy: - VTL was TSM certified just like a physical library - VTL install and config: ~1 hours - TSM Config (Library, Drives, stgpool): ~20 minutes - TSM labeling of 839 volumes: ~2 hours - ~2 minutes to update the NEXT STGPOOL on the primary disk stgpools to point to . VTL stgpool We viewed the costs of the VTL vs. a physical library with drives (that performs like the VTL) and associated disk stgpool to be comparable. Needless to say, I disagree with the statement that TSM doesn't appear to be a good fit for a VTL. Remember a VTL is just a library that can mount/unmount a tape in less than one second and read/write to the tape at disk speeds. Why wouldn't TSM work well with a library on steroids? Thanks, H. Milton Johnson -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of David E Ehresman Sent: Monday, November 29, 2004 2:42 PM To: [EMAIL PROTECTED] Subject: Re: size of active vs. inactive? It has also been discussed several times that TSM doesn't appear to be a good fit for a VTL. May want to search the archives to find out more on the subject. Has anyone heard of good experiences with TSM on a virtual tape library? Can this ever be a good thing?
Re: size of active vs. inactive?
I agree with your comments and yes if your server/client can stream data fast enough to the tape drive you may be able to out-pace a disk drive. If you can not keep up with the tape drive then you can take a serious performance hit when the tape stops, repositions and restarts. This performance hit is not as great with a virtual tape. We also looked at the 3494 VTL or Tape Server and saw that it is indeed a poor fit for TSM. Most TSM configurations already have a disk based stgpool front-end to the tape library so you would not gain much by adding one inside the library. Than H. Milton Johnson -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Richard Sims Sent: Tuesday, November 30, 2004 9:36 AM To: [EMAIL PROTECTED] Subject: Re: size of active vs. inactive? On Nov 30, 2004, at 9:58 AM, Johnson, Milton wrote: ...Needless to say, I disagree with the statement that TSM doesn't appear to be a good fit for a VTL. Remember a VTL is just a library that can mount/unmount a tape in less than one second and read/write to the tape at disk speeds. Why wouldn't TSM work well with a library on steroids? ... Thanks for sharing your experience with VTL in a TSM environment: it's helpful to have the perspective of experience. As we've seen in past tape vs. disk discussions, though, don't regard disk speed as some kind of ultimate data processing I/O attainment: high performance tape technologies streaming to sequential media can in many cases out-pace disk throughput. It is in mounting and tape positioning that tape is a poor performer relative to disk, where one can wait a minute or more before I/O can proceed. That's were VTL shines. Richard Sims
Re: Eliminating copy storage pool
Are you stating that you would be duplicating the tapes in a manner completely unknown to TSM? If so a couple of potential issues are: 1) If one of your primary pool tapes becomes unreadable, you would be unable to have TSM do a RESTORE VOLUME. 2) When TSM reclaims one of your primary pool tapes how will you know which duplicate tape to return onsite? H. Milton Johnson -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of David Browne Sent: Monday, October 04, 2004 11:09 AM To: [EMAIL PROTECTED] Subject: Eliminating copy storage pool Our Storage Administrator asked if we could do away with our offsite copy storage pool.They would duplex our current onsite backups on a VTS, the backend 9840 tapes would be sent offsite, eliminating the need for TSM's copy--storage-pool processing. Has anyone done this before or have any thoughts on that? The information transmitted is intended only for the person or entity to which it is addressed and may contain CONFIDENTIAL material. If you receive this material/information in error, please contact the sender and delete or destroy the material/information.
Re: query stgp
From help q stg: Pct Util An estimate of the utilization of the storage pool, as a percentage. For sequential access devices, this is expressed as a percentage of the number of active bytes on each sequential access volume and the estimated capacity of all volumes in the storage pool. For disk devices, this is expressed as a percentage of the estimated capacity, including cached data and data that resides on any volumes that are varied offline. The value for Pct Util can be higher than the value for Pct Migr if you issue this command while a file creation transaction is in progress. The value for Pct Util is determined by the amount of space actually allocated (while the transaction is in progress). The value for Pct Migr represents only the space occupied by committed files. At the end of the transaction, these values become synchronized. The Pct Util value includes cached data on disk volumes. Therefore, when cache is enabled and migration occurs, the Pct Util value remains the same because the migrated data remains on the volume as cached data. The Pct Util value decreases only when the cached data expires or when the space that cached files occupy needs to be used for noncached files. So for DASD-NAS you used have ~62.496GB including cached data Pct Migr (primary storage pools only) An estimate of the percentage of data in the storage pool that can be migrated. The server uses this value and the high and low migration thresholds to determine when to start and stop migration. For disk devices, this value is specified as a percentage of the value for the estimated capacity, excluding cached data, but including data on any volumes varied offline. For sequential access devices, this value is the percentage of the total number of volumes in the pool that contain at least 1 byte of active data. The total number of volumes includes the maximum number of scratch volumes. The Pct Util value includes cached data on a volume; the Pct Migr value excludes cached data. Therefore, when cache is enabled and migration occurs, the Pct Migr value decreases but the Pct Util value remains the same because the migrated data remains on the volume as cached data. The Pct Util value decreases only when the cached data expires or when the space that cached files occupy needs to be used for noncached files. I'm guessing you have cache enabled, so looking at the q stg report below, I appears that all of the data in DASD-NAS has been migrated to 3494NAS, so all ~62.496GB of the data in DASD-NAS is in a cached state. Doe this help? H. Milton Johnson -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Hashim, Shukrie BSP-ISM/116 Sent: Monday, October 04, 2004 10:39 PM To: [EMAIL PROTECTED] Subject: query stgp Hi all, I have Version 5, Release 1, Level 9.4 can somebody explain to me Storage DeviceEstimated Pct Pct High Low Next Pool Name Class Name CapacityUtilMigrMig Mig Storage (MB)Pct Pct Pool --- -- -- - - --- --- DASD-NAS DISK 63 G99.2 0.0 0 0 3494NAS DASDFSDISK 18 G 0.0 0.0 60 0 3494FS DASDHSM DISK 19 G13.9 0.2 5030 3494HSM pct util : is this the cache or the actual disk pct migr : is this the actual disk or the percentage migrated to tapes for example DASD-NAS has a pct util of 99.2 so meaning .. it means that it's full but I dunno what is full either the disk is full or the cache is full ? somebody please explain to me the meaning of the table ... above Thanks Regards Shukrie
Re: direct attached disk (DAS) at a tape library?
A virtual tape library operates and connects just like a physical tape library in a SAN environment. The VTL, TSM server and your client are connected to the SAN so a LANFREE back-up works using TSM's LANFREE technology. Since the topology is conventional you should also be able to add a SAN Data Gateway and do a server free backup. The key is that a VTL is just a conventional fiber connected library with really fast robotics and drives. Yes, you do need to make sure that the VTL plays nice with TSM, so make sure your choice in VTL is TSM certified. H. Milton Johnson -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Mark D. Rodriguez Sent: Tuesday, September 28, 2004 10:43 PM To: [EMAIL PROTECTED] Subject: Re: direct attached disk (DAS) at a tape library? Johnson, Milton wrote: I am not quite sure what you meant by with TSM you can use disk only for backups instead of onsite tape. I do not see any reason why you can not use FILE device types for both primary and copypool stg pools. Of course if you actually want to move a copy of the data offsite, then you would need some type of removable media such as tape. For me two of the attractions of a virtual tape library are being able to do lanfree backups without using Sanergy, and having the VTL do compression. H. Milton Johnson Hi Milton, I am not sure how you get to do Lan-Free without using Sanergy. In order to do that wouldn't the VTL have to have some kind of similar code as Sanergy and then the question is does that play nicely with TSM. Or am I missing something really obvious here? Please explain how you will get Lan-Free to work in a TSM environment without the Sanergy code. Thank You. -- Regards, Mark D. Rodriguez President MDR Consulting, Inc. === MDR Consulting The very best in Technical Training and Consulting. IBM Advanced Business Partner SAIR Linux and GNU Authorized Center for Education IBM Certified Advanced Technical Expert, CATE AIX Support and Performance Tuning, RS6000 SP, TSM/ADSM and Linux Red Hat Certified Engineer, RHCE ===
Re: direct attached disk (DAS) at a tape library?
Bill, I am presently implementing the S2100-ES and S2100-DS VTLs by Sepaton which are also TSM certified. While at present I am using them as directly fiber attached devices to my TSM server, I chose a VTL solution over a DASD solution because: (1) I wanted to preserve the ability to do a LANFree back-up in the future; (2) the VTL offers compression without any performance hit to my TSM server or clients. As far as costs are concerned, sure you are paying something for the VTL layer, but compression decreases that cost, besides TANSTAAFL (There Ain't No Such Thing As A Free Lunch). We were faced with the need for a major expansion and sticking with the tradition tape with a disk stgpool front end would have been very expensive. Give me a month or two and I should be able to report on life with a TSM and VTL. H. Milton Johnson -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Bill Smoldt Sent: Wednesday, September 29, 2004 8:01 AM To: [EMAIL PROTECTED] Subject: Re: direct attached disk (DAS) at a tape library? Milton, After I wrote the last message, I noticed that FalconStor has certified TSM SAN clients with their product, which is used by EMC and other manufacturers. I was thinking that it would be more interesting to run the VTL software on the TSM server rather than add another piece of hardware, however. So VTL might be a nice alternative to trying to implement a shared SAN filesystem (SANergy) just to achieve shared file pools. I haven't looked at the price. Have you? Bill Smoldt STORServer, Inc. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Johnson, Milton Sent: Wednesday, September 29, 2004 6:48 AM To: [EMAIL PROTECTED] Subject: Re: direct attached disk (DAS) at a tape library? A virtual tape library operates and connects just like a physical tape library in a SAN environment. The VTL, TSM server and your client are connected to the SAN so a LANFREE back-up works using TSM's LANFREE technology. Since the topology is conventional you should also be able to add a SAN Data Gateway and do a server free backup. The key is that a VTL is just a conventional fiber connected library with really fast robotics and drives. Yes, you do need to make sure that the VTL plays nice with TSM, so make sure your choice in VTL is TSM certified. H. Milton Johnson -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Mark D. Rodriguez Sent: Tuesday, September 28, 2004 10:43 PM To: [EMAIL PROTECTED] Subject: Re: direct attached disk (DAS) at a tape library? Johnson, Milton wrote: I am not quite sure what you meant by with TSM you can use disk only for backups instead of onsite tape. I do not see any reason why you can not use FILE device types for both primary and copypool stg pools. Of course if you actually want to move a copy of the data offsite, then you would need some type of removable media such as tape. For me two of the attractions of a virtual tape library are being able to do lanfree backups without using Sanergy, and having the VTL do compression. H. Milton Johnson Hi Milton, I am not sure how you get to do Lan-Free without using Sanergy. In order to do that wouldn't the VTL have to have some kind of similar code as Sanergy and then the question is does that play nicely with TSM. Or am I missing something really obvious here? Please explain how you will get Lan-Free to work in a TSM environment without the Sanergy code. Thank You. -- Regards, Mark D. Rodriguez President MDR Consulting, Inc. === MDR Consulting The very best in Technical Training and Consulting. IBM Advanced Business Partner SAIR Linux and GNU Authorized Center for Education IBM Certified Advanced Technical Expert, CATE AIX Support and Performance Tuning, RS6000 SP, TSM/ADSM and Linux Red Hat Certified Engineer, RHCE ===
Re: direct attached disk (DAS) at a tape library?
Eliza, This is what I did in an AIX environment: 1) Configure, or confirm the config of, the VTL it self (it comes from Sepaton configed to your specs): Network config, email config, dns config, number of drives, number/size of cartridges, etc. 2) Connect the Ethernet port to your network (used for management of the VTL itself) 3) connect the Sepaton VTL to your fiber adapter on the AIX box 4) On AIX run cfgmgr (this allows AIX to make available the virtual tape drives at the OS level as rmt devices). 5) On AIX run lsdev -Cc tape to confirm that the drives are available. 6) Now to make the AIX tape devices available to TSM ___smitty-Devices-Tivoli Storage Manager Devices-Fibre Channel SAN Attached Devices-Discover Devices Supported by TSM ___This made 50 drives available to TSM as devices mt0 through mt49 and the library at lb0 7) Place the following TSM commands into a file ds_setup.txt, Comment lines begin with a # # Define a library DEFine LIBRary DS01 LIBType=SCSI DEVIce=/dev/lb0 SHAREd=no # Define each drive in the library (created these lines with some unix scripting) DEFine DRive DS01 DS01DRV00 DEVIce=/dev/mt0 ONLine=YES element=128 . . . DEFine DRive DS01 DS01DRV49 DEVIce=/dev/mt49 ONLine=YES element=177 # Define a device class for the VTL tapes DEFine DEVclass DS01TAPE LIBRary=DS01 DEVType=DLT FORMAT=DRIVE ESTCAPacity=10G MOUNTRetention=1 MOUNTWait=2 MOUNTLimit=DRIVES # Define a stgpool for DEFine STGpool DS01POOL DS01TAPE POoltype=PRimary ACCess=READWrite COLlocate=NO MAXSCRatch=999 REUsedelay=3 # Define a small disk stgpool as a front end for small files. This improves performance by # preventing the so called wiper effect (don't ask me, a 1GB stgpool is no big deal). DEFine STGpool DS01DISK DISK POoltype=PRimary ACCess=READWrite MAXSIze=100m NEXTstgpool=DS01POOL HIghmig=90 LOwmig=0 MIGPRocess=1 # Define a volume for DS01DISK DEFine Volume DS01DISK /tsm/stgpool/ds01disk/vol1.stg Formatsize=1000 # Now label and checkin the VTL cartridges, takes about 5-6 seconds per cartridge LABEl LIBVolume DS01 SEARCH=YES LABELSource=BARCODE CHECKIN=SCRATCH OVERWRITE=YES 8) Process ds_setup.txt egrep -v ^# ds_setup.txt | /usr/bin/dsmadmc -id=your_admin_id -pa=your_admin_password After doing this I pointed a test server to backup to DS01DISK and it wotked without a problem. Pretty simple. H. Milton Johnson -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Eliza Lau Sent: Wednesday, September 29, 2004 9:29 AM To: [EMAIL PROTECTED] Subject: Re: direct attached disk (DAS) at a tape library? Milton, Sepaton is going to ship us a S2100-DS for testing with no commitment to buy. Can you share with us your experience? Is it worth 3 times the cost of setting up our own DASD. Is it as easy to implement as they claim and how is their support? As far as I know, compression will be available in Q1 2005. Our goal is to put the VTL or DASD in a building 1.5 miles away and put the primary stgpool on it. The 3494 will stay in the machine room and will keep the 'offsite' tape pools. Then we will never have to mess around with tape vaulting ever again. Eliza Lau Virginia Tech Computing Center Bill, I am presently implementing the S2100-ES and S2100-DS VTLs by Sepaton which are also TSM certified. While at present I am using them as directly fiber attached devices to my TSM server, I chose a VTL solution over a DASD solution because: (1) I wanted to preserve the ability to do a LANFree back-up in the future; (2) the VTL offers compression without any performance hit to my TSM server or clients. As far as costs are concerned, sure you are paying something for the VTL layer, but compression decreases that cost, besides TANSTAAFL (There Ain't No Such Thing As A Free Lunch). We were faced with the need for a major expansion and sticking with the tradition tape with a disk stgpool front end would have been very expensive. Give me a month or two and I should be able to report on life with a TSM and VTL. H. Milton Johnson -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Bill Smoldt Sent: Wednesday, September 29, 2004 8:01 AM To: [EMAIL PROTECTED] Subject: Re: direct attached disk (DAS) at a tape library? Milton, After I wrote the last message, I noticed that FalconStor has certified TSM SAN clients with their product, which is used by EMC and other manufacturers. I was thinking that it would be more interesting to run the VTL software on the TSM server rather than add another piece of hardware, however. So VTL might be a nice alternative to trying to implement a shared SAN filesystem (SANergy) just to achieve shared file pools. I haven't looked at the price. Have you? Bill Smoldt STORServer, Inc. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Johnson, Milton Sent: Wednesday, September 29, 2004 6
Re: direct attached disk (DAS) at a tape library?
and other manufacturers. I was thinking that it would be more interesting to run the VTL software on the TSM server rather than add another piece of hardware, however. So VTL might be a nice alternative to trying to implement a shared SAN filesystem (SANergy) just to achieve shared file pools. I haven't looked at the price. Have you? Bill Smoldt STORServer, Inc. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Johnson, Milton Sent: Wednesday, September 29, 2004 6:48 AM To: [EMAIL PROTECTED] Subject: Re: direct attached disk (DAS) at a tape library? A virtual tape library operates and connects just like a physical tape library in a SAN environment. The VTL, TSM server and your client are connected to the SAN so a LANFREE back-up works using TSM's LANFREE technology. Since the topology is conventional you should also be able to add a SAN Data Gateway and do a server free backup. The key is that a VTL is just a conventional fiber connected library with really fast robotics and drives. Yes, you do need to make sure that the VTL plays nice with TSM, so make sure your choice in VTL is TSM certified. H. Milton Johnson -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Mark D. Rodriguez Sent: Tuesday, September 28, 2004 10:43 PM To: [EMAIL PROTECTED] Subject: Re: direct attached disk (DAS) at a tape library? Johnson, Milton wrote: I am not quite sure what you meant by with TSM you can use disk only for backups instead of onsite tape. I do not see any reason why you can not use FILE device types for both primary and copypool stg pools. Of course if you actually want to move a copy of the data offsite, then you would need some type of removable media such as tape. For me two of the attractions of a virtual tape library are being able to do lanfree backups without using Sanergy, and having the VTL do compression. H. Milton Johnson Hi Milton, I am not sure how you get to do Lan-Free without using Sanergy. In order to do that wouldn't the VTL have to have some kind of similar code as Sanergy and then the question is does that play nicely with TSM. Or am I missing something really obvious here? Please explain how you will get Lan-Free to work in a TSM environment without the Sanergy code. Thank You. -- Regards, Mark D. Rodriguez President MDR Consulting, Inc. == == === MDR Consulting The very best in Technical Training and Consulting. IBM Advanced Business Partner SAIR Linux and GNU Authorized Center for Education IBM Certified Advanced Technical Expert, CATE AIX Support and Performance Tuning, RS6000 SP, TSM/ADSM and Linux Red Hat Certified Engineer, RHCE == == ===
Re: direct attached disk (DAS) at a tape library?
Mark, No idea about TSM's LANFREE being a limited use copy of Sanergy. My understanding was that the big difference was in the client code so that the meta data goes over the LAN to the TSM server's DB and the actual backup data goes across the SAN directly to the SAN attached tape drive with the TSM server still controlling the tape drive access. I assumed this was just a case of the TSM server telling the client which tape drive to use and then the client sends the data to the SAN attached tape drive in the same manner the TSM server normally sends data to a SAN attached tape drive. When the client completes the back-up, it informs the TSM server and the server knows that the tape drive is now free for other usage. During IBM's presentation on tapeless back-ups they said that if you where going the route of DASD storage using a FILE device class stgpool, you would need the full blown Sanergy application to do a LANFREE back-up. I would assume that this meant at least two copies of Sanergy, one for the TSM server and one for the client. For back-ups I would prefer to use the simplest method which would seem to be TSM's LANFREE technology. I do not want to have to worry about compatible versions between two different products [TSM and Sanergy, not mention the OS(s)] even when both of the products are from IBM. H. Milton Johnson -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Mark D. Rodriguez Sent: Wednesday, September 29, 2004 1:05 PM To: [EMAIL PROTECTED] Subject: Re: direct attached disk (DAS) at a tape library? Milton, Do you realize that the TSM's LANFREE technology you are refering to is in fact Sanergy? TSM just gives you a limited use copy of Sanergy when yuo turn on the LANFREE stuff. That was why I questioned how you were going to do LANFREE without Sanergy. That clears that up. Thanks. Johnson, Milton wrote: A virtual tape library operates and connects just like a physical tape library in a SAN environment. The VTL, TSM server and your client are connected to the SAN so a LANFREE back-up works using TSM's LANFREE technology. Since the topology is conventional you should also be able to add a SAN Data Gateway and do a server free backup. The key is that a VTL is just a conventional fiber connected library with really fast robotics and drives. Yes, you do need to make sure that the VTL plays nice with TSM, so make sure your choice in VTL is TSM certified. H. Milton Johnson -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Mark D. Rodriguez Sent: Tuesday, September 28, 2004 10:43 PM To: [EMAIL PROTECTED] Subject: Re: direct attached disk (DAS) at a tape library? Johnson, Milton wrote: I am not quite sure what you meant by with TSM you can use disk only for backups instead of onsite tape. I do not see any reason why you can not use FILE device types for both primary and copypool stg pools. Of course if you actually want to move a copy of the data offsite, then you would need some type of removable media such as tape. For me two of the attractions of a virtual tape library are being able to do lanfree backups without using Sanergy, and having the VTL do compression. H. Milton Johnson Hi Milton, I am not sure how you get to do Lan-Free without using Sanergy. In order to do that wouldn't the VTL have to have some kind of similar code as Sanergy and then the question is does that play nicely with TSM. Or am I missing something really obvious here? Please explain how you will get Lan-Free to work in a TSM environment without the Sanergy code. Thank You. -- Regards, Mark D. Rodriguez President MDR Consulting, Inc. === = === MDR Consulting The very best in Technical Training and Consulting. IBM Advanced Business Partner SAIR Linux and GNU Authorized Center for Education IBM Certified Advanced Technical Expert, CATE AIX Support and Performance Tuning, RS6000 SP, TSM/ADSM and Linux Red Hat Certified Engineer, RHCE === = === -- Regards, Mark D. Rodriguez President MDR Consulting, Inc. === MDR Consulting The very best in Technical Training and Consulting. IBM Advanced Business Partner SAIR Linux and GNU Authorized Center for Education IBM Certified Advanced Technical Expert, CATE AIX Support and Performance Tuning, RS6000 SP, TSM/ADSM and Linux Red Hat Certified Engineer, RHCE ===
Re: direct attached disk (DAS) at a tape library?
This is my understanding SANergy and TSM's LANFREE. H. Milton Johnson -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Stapleton, Mark Sent: Wednesday, September 29, 2004 2:35 PM To: [EMAIL PROTECTED] Subject: Re: direct attached disk (DAS) at a tape library? From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Johnson, Milton No idea about TSM's LANFREE being a limited use copy of Sanergy. It is not. My understanding was that the big difference was in the client code so that the meta data goes over the LAN to the TSM server's DB and the actual backup data goes across the SAN directly to the SAN attached tape drive with the TSM server still controlling the tape drive access. I assumed this was just a case of the TSM server telling the client which tape drive to use and then the client sends the data to the SAN attached tape drive in the same manner the TSM server normally sends data to a SAN attached tape drive. When the client completes the back-up, it informs the TSM server and the server knows that the tape drive is now free for other usage. During IBM's presentation on tapeless back-ups they said that if you where going the route of DASD storage using a FILE device class stgpool, you would need the full blown Sanergy application to do a LANFREE back-up. I would assume that this meant at least two copies of Sanergy, one for the TSM server and one for the client. If you want a LAN-free backup of SAN-located client data to SAN-based disk used by the TSM server, you must use SANergy. SANergy creates an NFS-type mount from target-controlled disk to source-controlled disk, and initiates a copy of data from source to target. The how-tos are in the SANergy documentation. It is **fast**, since the bottleneck in such a transfer is the speed of the disk bus. Metadata about the client data still travels across the LAN, but that's a piffle compared to the size of the data itself. -- Mark Stapleton ([EMAIL PROTECTED]) Berbee Information Networks Office 262.521.5627
Re: direct attached disk (DAS) at a tape library?
I am not quite sure what you meant by with TSM you can use disk only for backups instead of onsite tape. I do not see any reason why you can not use FILE device types for both primary and copypool stg pools. Of course if you actually want to move a copy of the data offsite, then you would need some type of removable media such as tape. For me two of the attractions of a virtual tape library are being able to do lanfree backups without using Sanergy, and having the VTL do compression. H. Milton Johnson -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Prather, Wanda Sent: Tuesday, September 28, 2004 2:57 PM To: [EMAIL PROTECTED] Subject: Re: direct attached disk (DAS) at a tape library? If you read the thread D2D on AIX over the past week, it has lots of details on the pros and cons of using Disk only for backup. The answer overall, is that with TSM you can use disk only for backups instead of onsite tape, as long as you do a little advance planning. I think the virtual tape libraries may be more attractive to sites with non-TSM applications that are written specifically for tape. My concern is your statement that we don't remove tapes anyway. What do you do if 1) you lose your disk array, or 2) someone sets your building on fire? One of the advantages of tape, is that you can make as many extra tapes as you want, and send them somewhere in case of a building disaster. You can also keep adding storage space 200GB (one cartridge) at a time, without making an additional capital purchase. Still, a lot of people, and maybe you, will find that for at least the primary copy, disk-only is very cost effective as a backup pool. But, BE VERY CAREFUL about the quality of disk you buy, if that is going to be your only copy of the data. DO NOT THINK that you can't lose a RAID array; I have seen it happen, twice. It depends TOTALLY on the quality of the controller card in the RAID array. If it goes south, all you've got is a bunch of unrelated magnetized bits on your disk. And for sites that have ARCHIVE or HSM data (which may not exist any more on the client machines), there is NO magnetic media reliable enough that you can be safe with just 1 copy (except maybe those tapes they put in airline black-boxes, but I don't know where to buy those :). Wanda Prather I/O, I/O, It's all about I/O -(me) -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Alexander Lazarevich Sent: Friday, September 24, 2004 6:17 PM To: [EMAIL PROTECTED] Subject: direct attached disk (DAS) at a tape library? We have TSM 5.1.6.5 on win2k server. library is overland neo 4100 (60 tape capacity) with 2 X HP LTO-2 drives. We need another 12TB of backup capacity. We are considering getting something other that another tape library. Couldn't we buy a couple of 6.4TB SCSI-SATA RAID DAS devices, and attach that to our backup host via SCSI, and start using that DAS as one big disk(tape)? We would just tell TSM that the big disk is some massive spool, or even a tape. We could even buy several of the DAS units, and just keep adding them as spool (or tape) disks on the SCSI chain. This would give us FAST backup and restore. Why do we need tapes? I know there are disk systems like the Reo, which is just a DAS RAID that does tape virtualization, but those things cost 3 times as much as a regular DAS. Why is tape virtualization so expensive? Why do we need tape virtualization? Is there something about how TSM handles disks vs. tapes, that makes using DAS impossible, or not a good idea? We are not too worried about reliability. We think we can configure multiple RAID arrays on the devices so that we lessen the chance of disk failure causing backup data loss. There must be some things we don't realize that tape virtualization gives us that a bunch of DAS disks won't. Price isn't it though, because we can get 13TB of DAS for 24K. The equivalent in LTO-2 tape (with library) costs 35K. And Disk to Disk backup is even more, like 44K! The only disadvantage we can come up with are that we can't remove tapes. But we don't remove tapes anyway. Please tell me why we shouldn't just attach a big 13TB DAS to our TSM host, and start using that as the main backup disk. Thanks, Alex --- --- Alex Lazarevich | Systems Administrator | Imaging Technology Group Beckman Institute | University of Illinois | www.itg.uiuc.edu --- ---
Re: Diskspool volumes size
Read the recent thread D2D on AIX H. Milton Johnson -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Gilles Sent: Friday, September 24, 2004 8:04 AM To: [EMAIL PROTECTED] Subject: Diskspool volumes size Hi, I have 5 TB of disk stgspool available. I would like to create volumes on it - what's the recommended size/vol. ? does TSM have a limit regarding the number of volume it can handle ? Thanks.
Re: D2D on AIX
IBM gave a webinar on DISK ONLY backups including the advantages of DISK vs. FILE device classes. While your mileage may vary, in general it seems that a FILE devclass will give better performance for large pools (read TB not GB). Two quick examples: 1) With DISK TSM keeps track of each 4K block in the DISK volumes. This means that TSM must maintain a map of all those blocks and search/update that map every time a file is saved/expired. Also your files will be fragmented within those DISK volumes leading to further performance problems. 2) When it's time to backup what's on disk to offsite tapes, TSM has a speedy shortcut with SEQUENTIAL device classes. TSM keeps a flag for each sequential volume, when the sequential volume is backed the flag is set, and when the sequential volume is written to the flag is cleared. This means that when it's time to back-up those primary stgpool sequential volumes to a copypool TSM only needs to examine those files in the sequential volumes with the flag cleared. With the way TSM works, this greatly reduces the amount of time required by TSM to determine what data needs to be backed up. With a DISK device class, TSM has no choice but to examine each file in the STGPOOL being backed up to determine if it has been previously backed-up to the copypool. Incidentally, IBM hinted that a future enhancement would be to allow a list of mount points (directories) to be assigned as the destination to FILE device classes. This would allow utilization of dynamic allocation across multiple file systems. Of course one drawback with dynamic allocation is that fragmentation can occur overtime. Your particular OS will greatly influence the severity of this problem, however defining the stgpool volume explicitly will prevent that problem. H. Milton Johnson -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Ian Hobbs Sent: Monday, September 20, 2004 5:26 PM To: [EMAIL PROTECTED] Subject: Re: D2D on AIX Question, Why not use the DISK device class with RAW volumes? Personally, I find FILE classes a pain for user storage because you DO have to perform reclamation on them. Ian Hobbs On Mon, 20 Sep 2004 14:48:07 -0400, Eliza Lau wrote: Okay. I got it. It is a pain to manually define the volumes, but it can be done. I also received your pdf file. Thanks to everyone who answered, Eliza It depends upon how you configure things. For dynamic allocation of volumes, then yes you are limited to the size of the file system that you mount on that mount point. However if you define the stgpool volumes explicitly using the DEFINE VOLUME command, you can place the volumes across as many file systems as you want. I will email you a PDF presentation IBM has on Disk Only backups. H. Milton Johnson -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Eliza Lau Sent: Monday, September 20, 2004 12:11 PM To: [EMAIL PROTECTED] Subject: D2D on AIX Our 3494 with 3590K tapes in 3 frames is getting full. Instead of adding another frame or upgrading to 3590H or 3592 tapes we are looking into setting up a bunch of cheap ATA disks as primary storage. The FILE devclass defines a directory as its destination and JFS2 has a max file system size of 1TB. Does it mean the largest stgpool I can define is 1TB? My Exchange stgpool alone has 8TB of data. Do I have to split it up into 8 pieces? server: TSM 5.2.2.5 on AIX 5.2 database 90GB at 70% Total backup data - 22TB Eliza Lau Virginia Tech Computing Center [EMAIL PROTECTED] Ian Hobbs [EMAIL PROTECTED] === Never argue with an idiot. They drag you down to their level then beat you with experience. -Dilbert
Re: Duel tape write to LTO's
It depends upon where you define the copypool to reside. If it is contained in the 2nd library then yes. Has anyone out there in TSM land actually used this feature? What happens to the back-up when one of the tape volumes fills up? Does it go into a media wait state until the next volume is mounted? What happens if there isn't a volume available in the copypool? Any other gotcha's? H. Milton Johnson -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Timothy Hughes Sent: Tuesday, September 21, 2004 10:05 AM To: [EMAIL PROTECTED] Subject: Re: Duel tape write to LTO's Hi Milton, When TSM writes simultaneously to the copypool would this be on the 2nd Library for duel tape backup? Johnson, Milton wrote: You should be able to create a PRIMARY STGPOOL named TAPEPOOL and a COPY STGPOOL named COPYPOOL with both of them having a sequential access (tape) DEVICE CLASS such as DLT or LTO. Both stgpools can be in the same library. On the stgpool TAPEPOOL definition you set the COPYSTGPOOLS parameter to COPYPOOL. Then when your client backs up to TAPEPOOL, TSM will simultaneously write to COPYPOOL. Of course having an adequate number of tape drives is required. H. Milton Johnson -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Timothy Hughes Sent: Friday, September 17, 2004 8:01 AM To: [EMAIL PROTECTED] Subject: Re: Duel tape write to LTO's Hello, I was told that this could work If I have 2 backup disk pools. Like I have backup diskpool, then I can have like say a DB2 backup diskpool then I can have the next storage pool setting for the db backup pool so I can migrate to the one Library then for the other backup disk pool I can have it migrate to the other Library. I think I can have simultaneous write to two different libraries this way. Still not sure if this would work. TSM Library setup TSM SERVER LTO_LIB LIBRARY TSM SERVER RMT1 DRIVE LTO_LIB TSM SERVER RMT2 DRIVE LTO_LIB TSM SERVER RMT3 DRIVE LTO_LIB TSM SERVER RMT4 DRIVE LTO_LIB TSM SERVER RMT_LTO LIBRARY TSM SERVER RMT5 DRIVE RMT_LTO TSM SERVER RMT6 DRIVE RMT_LTO TSM SERVER RMT7 DRIVE RMT_LTO TSM SERVER RMT8 DRIVE RMT_LTO Any other ideas comments are welcome! Thanks Johnson, Milton wrote: It is the basic philosophy of TSM to have only one copy of a file in a PRIMARY STORAGE POOL. With TSM 5.x you can simultaneously write to a PRIMARY STORAGE POOL and COPY STORAGE POOL (see HELP DEFINE STGPOOL). H. Milton Johnson -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Timothy Hughes Sent: Thursday, September 16, 2004 10:28 AM To: [EMAIL PROTECTED] Subject: Duel tape write to LTO's Hello all, We are backing our server from disk to tape on a LTO 3584 Library drives 4 drives (1-4) We just added a 2nd library LTO (same 3584) Is it possible to backup to the 2nd library LTO simultaneously. In other words were backing up to tape 1 on Lib_LTO and would like to backup to Tape 2 on the new library at the same time. We want Duel tape backup and don't want to use copy groups if we don't have to. 3584 Lib_LTO A has 4 drives (1-4) 3584 Rmt_LTO B has 4 drives (5-8) TSM version 5.2.3.1 AIX 5.2 Thanks in advance for any help!
Re: D2D on AIX
Now we get into religion. IBM did offer a figure of ~5GB during the webinar, but there are a lot of factors that would affect this such as: REUSE DELAY: you want to be able to use those TSM DB backups RECLAMATION THRESHOLD: A lower threshold should lead to more efficient usage of volumes except that it causes more frequent tape reclamation leading to more pending volumes causing wasted space. Of course the exact opposite is true regarding higher reclamation thresholds. What yin yang is right for you? Experiment and find out. AVG SIZE OF STORED OBJECTS? EXPIRATION RATE OF STORED OBJECTS? I'm sure others will bring up other factors. How many volumes are too many? If TSM is keeping track of the volumes and you are not handling the physical volumes (i.e. loading/unloading tapes), is 4,000 too many? If so, why? H. Milton Johnson -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Eliza Lau Sent: Tuesday, September 21, 2004 11:20 AM To: [EMAIL PROTECTED] Subject: Re: D2D on AIX Eric, What is the recommended volume size. I have seen someone mentioned 5G, but then the number of volumes will explode from about 800 (current # of 3590 primary tapes) to thousands. How about keeping the staging space so clients backup to staging then migrate to FILE volumes. Then every volume will be filled up. Eliza Hi Eliza! You do want several smaller files, rather than a few very large files because each client session will allocate a volume. File volumes cannot be used concurrently by more than one session. Kindest regards, Eric van Loon KLM Royal Dutch Airlines -Original Message- From: Eliza Lau [mailto:[EMAIL PROTECTED] Sent: Monday, September 20, 2004 19:11 To: [EMAIL PROTECTED] Subject: D2D on AIX Our 3494 with 3590K tapes in 3 frames is getting full. Instead of adding another frame or upgrading to 3590H or 3592 tapes we are looking into setting up a bunch of cheap ATA disks as primary storage. The FILE devclass defines a directory as its destination and JFS2 has a max file system size of 1TB. Does it mean the largest stgpool I can define is 1TB? My Exchange stgpool alone has 8TB of data. Do I have to split it up into 8 pieces? server: TSM 5.2.2.5 on AIX 5.2 database 90GB at 70% Total backup data - 22TB Eliza Lau Virginia Tech Computing Center [EMAIL PROTECTED] ** 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: D2D on AIX
What do use for a reuse delay? How many pending volumes do you average? H. Milton Johnson -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Rushforth, Tim Sent: Tuesday, September 21, 2004 1:00 PM To: [EMAIL PROTECTED] Subject: Re: D2D on AIX Eliza: At the Disk only Backups Technical Exchange, IBM recommended 2-4 GB volume size. (This was stated by the presenter, it was not written on the PDF presentation.) We started with 25 GB volumes and have now switched to 4 GB volumes. Using smaller volume sizes allows a better utilization of space and increases restore performance with multi-session restore. (Also helps eliminate contention if multiple clients are restoring from the same volume) Tim Rushforth City of Winnipeg -Original Message- From: Eliza Lau [mailto:[EMAIL PROTECTED] Sent: Tuesday, September 21, 2004 11:20 AM To: [EMAIL PROTECTED] Subject: Re: D2D on AIX Eric, What is the recommended volume size. I have seen someone mentioned 5G, but then the number of volumes will explode from about 800 (current # of 3590 primary tapes) to thousands. How about keeping the staging space so clients backup to staging then migrate to FILE volumes. Then every volume will be filled up. Eliza Hi Eliza! You do want several smaller files, rather than a few very large files because each client session will allocate a volume. File volumes cannot be used concurrently by more than one session. Kindest regards, Eric van Loon KLM Royal Dutch Airlines -Original Message- From: Eliza Lau [mailto:[EMAIL PROTECTED] Sent: Monday, September 20, 2004 19:11 To: [EMAIL PROTECTED] Subject: D2D on AIX Our 3494 with 3590K tapes in 3 frames is getting full. Instead of adding another frame or upgrading to 3590H or 3592 tapes we are looking into setting up a bunch of cheap ATA disks as primary storage. The FILE devclass defines a directory as its destination and JFS2 has a max file system size of 1TB. Does it mean the largest stgpool I can define is 1TB? My Exchange stgpool alone has 8TB of data. Do I have to split it up into 8 pieces? server: TSM 5.2.2.5 on AIX 5.2 database 90GB at 70% Total backup data - 22TB Eliza Lau Virginia Tech Computing Center [EMAIL PROTECTED] ** 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: D2D on AIX
It depends upon how you configure things. For dynamic allocation of volumes, then yes you are limited to the size of the file system that you mount on that mount point. However if you define the stgpool volumes explicitly using the DEFINE VOLUME command, you can place the volumes across as many file systems as you want. I will email you a PDF presentation IBM has on Disk Only backups. H. Milton Johnson -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Eliza Lau Sent: Monday, September 20, 2004 12:11 PM To: [EMAIL PROTECTED] Subject: D2D on AIX Our 3494 with 3590K tapes in 3 frames is getting full. Instead of adding another frame or upgrading to 3590H or 3592 tapes we are looking into setting up a bunch of cheap ATA disks as primary storage. The FILE devclass defines a directory as its destination and JFS2 has a max file system size of 1TB. Does it mean the largest stgpool I can define is 1TB? My Exchange stgpool alone has 8TB of data. Do I have to split it up into 8 pieces? server: TSM 5.2.2.5 on AIX 5.2 database 90GB at 70% Total backup data - 22TB Eliza Lau Virginia Tech Computing Center [EMAIL PROTECTED]
Re: Duel tape write to LTO's
You should be able to create a PRIMARY STGPOOL named TAPEPOOL and a COPY STGPOOL named COPYPOOL with both of them having a sequential access (tape) DEVICE CLASS such as DLT or LTO. Both stgpools can be in the same library. On the stgpool TAPEPOOL definition you set the COPYSTGPOOLS parameter to COPYPOOL. Then when your client backs up to TAPEPOOL, TSM will simultaneously write to COPYPOOL. Of course having an adequate number of tape drives is required. H. Milton Johnson -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Timothy Hughes Sent: Friday, September 17, 2004 8:01 AM To: [EMAIL PROTECTED] Subject: Re: Duel tape write to LTO's Hello, I was told that this could work If I have 2 backup disk pools. Like I have backup diskpool, then I can have like say a DB2 backup diskpool then I can have the next storage pool setting for the db backup pool so I can migrate to the one Library then for the other backup disk pool I can have it migrate to the other Library. I think I can have simultaneous write to two different libraries this way. Still not sure if this would work. TSM Library setup TSM SERVER LTO_LIB LIBRARY TSM SERVER RMT1 DRIVE LTO_LIB TSM SERVER RMT2 DRIVE LTO_LIB TSM SERVER RMT3 DRIVE LTO_LIB TSM SERVER RMT4 DRIVE LTO_LIB TSM SERVER RMT_LTO LIBRARY TSM SERVER RMT5 DRIVE RMT_LTO TSM SERVER RMT6 DRIVE RMT_LTO TSM SERVER RMT7 DRIVE RMT_LTO TSM SERVER RMT8 DRIVE RMT_LTO Any other ideas comments are welcome! Thanks Johnson, Milton wrote: It is the basic philosophy of TSM to have only one copy of a file in a PRIMARY STORAGE POOL. With TSM 5.x you can simultaneously write to a PRIMARY STORAGE POOL and COPY STORAGE POOL (see HELP DEFINE STGPOOL). H. Milton Johnson -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Timothy Hughes Sent: Thursday, September 16, 2004 10:28 AM To: [EMAIL PROTECTED] Subject: Duel tape write to LTO's Hello all, We are backing our server from disk to tape on a LTO 3584 Library drives 4 drives (1-4) We just added a 2nd library LTO (same 3584) Is it possible to backup to the 2nd library LTO simultaneously. In other words were backing up to tape 1 on Lib_LTO and would like to backup to Tape 2 on the new library at the same time. We want Duel tape backup and don't want to use copy groups if we don't have to. 3584 Lib_LTO A has 4 drives (1-4) 3584 Rmt_LTO B has 4 drives (5-8) TSM version 5.2.3.1 AIX 5.2 Thanks in advance for any help!
Re: Duel tape write to LTO's
It is the basic philosophy of TSM to have only one copy of a file in a PRIMARY STORAGE POOL. With TSM 5.x you can simultaneously write to a PRIMARY STORAGE POOL and COPY STORAGE POOL (see HELP DEFINE STGPOOL). H. Milton Johnson -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Timothy Hughes Sent: Thursday, September 16, 2004 10:28 AM To: [EMAIL PROTECTED] Subject: Duel tape write to LTO's Hello all, We are backing our server from disk to tape on a LTO 3584 Library drives 4 drives (1-4) We just added a 2nd library LTO (same 3584) Is it possible to backup to the 2nd library LTO simultaneously. In other words were backing up to tape 1 on Lib_LTO and would like to backup to Tape 2 on the new library at the same time. We want Duel tape backup and don't want to use copy groups if we don't have to. 3584 Lib_LTO A has 4 drives (1-4) 3584 Rmt_LTO B has 4 drives (5-8) TSM version 5.2.3.1 AIX 5.2 Thanks in advance for any help!
Re: each dbbackup to new tape?
An interesting paper on an obviously VERY large TSM system, involving upwards to 40 TSM servers. Your problem was that you did not want to send 40 tapes offsite everyday with each tape containing a single backup of a TSM server DB. So your elegant solution was to create a TSM server instance, TSMDBB, and have the 40 TSM servers backup to TSMDBB. This means that you only had to dedicate a single tape to a single TSM server DB backup, specifically when you were backing up the TSM DB on TSMDBB. (Actually you said you would back up TSMDBB to a disk file and then copy that file to several locations, but the principle is the same.) This is an elegant way to reduce the number of daily TSM DB backup tapes from 40 to 1, however Lucian is already at the point of only having to send off a single TSM DB backup tape per day. H. Milton Johnson -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Thursday, September 16, 2004 11:17 AM To: [EMAIL PROTECTED] Subject: Re: each dbbackup to new tape? == In article [EMAIL PROTECTED], Lucian Greis [EMAIL PROTECTED] writes: I'm rather green with TSM, actually working through my first client-project with it and have come to a (small for sure) problem System: TSM 5.2 on SuSe SLES8, feeding an Adic Scalar24 with one IBM-LTO2. Basically, the system works. Whenever I command a dbBackup, wether full or incremetal, TSM wants to write to a scratch tape only. If i give the volser of a tape used for an earlier dbbackup explicitly, TSM says the tape is full (which it is not). Can someone point me to the right direction? My solution to this involved a second server on the same physical hardware. The DB backups are to remote server volumes, which I can then copy and send offsite. I discuss the evolution of my desin in some detail (including some blind alleys I went down) at: http://open-systems.ufl.edu/services/NSAM/whitepapers/design.html - Allen S. Rout
Re: Antwort: Re: each dbbackup to new tape?
OK, I just have to jump in. If I understand Hoa he: 1) Backs up the TSM database to a disk file 2) backs up that disk file to a TSM disk storage pool using DSM 3) moves that db backup to onsite/offsite tapes using backup stg and migration If this is so, then what do you do when you have lost your current TSM database? In Hoa's case, I guess he can get restore a copy of the db backup from his server located 11 miles away, if he has vaulted the files their and that server can restore an that individual file from those vaulted tapes. If however Lucian's case is more typical, having only one hot server, then I believe your restoration procedure consists of telling your boss you lost the entire TSM server along with all backups and then posting your resume on monster.com. Of course you may not want to mention your most recent employment. H. Milton Johnson -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Lucian Greis Sent: Wednesday, September 15, 2004 9:24 AM To: [EMAIL PROTECTED] Subject: Antwort: Re: each dbbackup to new tape? Hi Hoa, now this sounds interesting: I suppose I willhave to define a FileDrive device, since I belive that only device classes are allowed targets to the dbbackup command. And then set up a nice small storagepool so the file gets instantly transferred to tape... Thanks for all responses to my question Regards, Lucian Hoa V Nguyen [EMAIL PROTECTED] Gesendet von: ADSM: Dist Stor Manager [EMAIL PROTECTED] 15.09.2004 16:06 Bitte antworten an ADSM: Dist Stor Manager An: [EMAIL PROTECTED] Kopie: Thema: Re: each dbbackup to new tape? Lucian, This is what we're doing to save 3592 tapes: Incremental backup and full DB backup go to flat files, shift those files to offsite or onsite to Disk Storage Poll and let migrate functions put them on tapes. (We have servers onsite offsite 11 miles away for disaster). Hoa. Lucian Greis [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] 09/15/2004 08:13 AM Please respond to ADSM: Dist Stor Manager To [EMAIL PROTECTED] cc Subject each dbbackup to new tape? Hi list, I'm rather green with TSM, actually working through my first client-project with it and have come to a (small for sure) problem System: TSM 5.2 on SuSe SLES8, feeding an Adic Scalar24 with one IBM-LTO2. Basically, the system works. Whenever I command a dbBackup, wether full or incremetal, TSM wants to write to a scratch tape only. If i give the volser of a tape used for an earlier dbbackup explicitly, TSM says the tape is full (which it is not). Can someone point me to the right direction? Regards, Lucian Greis MKV GmbH
Re: How to run a unix shell script by an administrative schedule ?
I also do my scheduling via cron and have the cron job call admin scripts but of course you run into the problem of hard coding a password somewhere. You could also try something like: Last step in admin schedule: q stg /tmp/flags/BACKUP_SCHEDULE_DONE.FLAG Then have cron schedule your shell script to start at the same time as your admin schedule and have the shell script do the following: while true do if [ -a /tmp/flags/BACKUP_SCHEDULE_DONE.FLAG ] ; then rm /tmp/flags/BACKUP_SCHEDULE_DONE.FLAG copy important files exit fi sleep 60 done H. Milton Johnson -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Mark D. Rodriguez Sent: Wednesday, September 01, 2004 5:36 PM To: [EMAIL PROTECTED] Subject: Re: How to run a unix shell script by an administrative schedule ? Guenther Bergmann wrote: Hi *SMers, I have set up an administrative schedule, which does the following: - backup all primary pools to copy pool - backup db to tape - delete older db backups. Next step should be to copy some important files (volhist.out, devconf.out etc) to a remote server. I've written a shell script to accomplish this. Question: How can this shell script be called by the above mentioned admin. schedule? Any help is appreciated regards Guenther -- Guenther Bergmann, Am Kreuzacker 10, 63150 Heusenstamm, Germany Guenther_Bergmann at gbergmann dot de http://www.gbergmann.de Guenther, You can not do this directly as a Admin Schedule, however you could do a little trick and get it done. I am assuming that the TSM server system also has a TSM node assigned to it. If so you could run a client schedule that calls the OS level script. But you might just consider running this script from an OS scheduler like cron if it is a Unix machine. I hope that helps. -- Regards, Mark D. Rodriguez President MDR Consulting, Inc. === MDR Consulting The very best in Technical Training and Consulting. IBM Advanced Business Partner SAIR Linux and GNU Authorized Center for Education IBM Certified Advanced Technical Expert, CATE AIX Support and Performance Tuning, RS6000 SP, TSM/ADSM and Linux Red Hat Certified Engineer, RHCE ===
Re: Sizing for a virtual tape library
Just to add another fly in the ointment, if you have an aggressive reclamation threshold, say 25%, and a reuse delay of say 5 days, you may end up with a lot more tapes in a pending state then you anticipated. A pending tape is not a scratch tape. H. Milton Johnson -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Coats, Jack Sent: Wednesday, September 01, 2004 12:42 PM To: [EMAIL PROTECTED] Subject: Re: Sizing for a virtual tape library I agree, think of it as so many tapes. Since they are 'really fast tapes', being on disk, you might consider doing reclaimation at some unusually low number to get expired data out of the way ASAP. If you don't need the space that badly, relax the reclaimation percentage a bit. Instead of starting withe 80 or 60 percent like you would on tapes, you might start with 40 percent and go to 20 percent if you need the space. This still leaves you with about 20% of the library with 'old data', plus your need for at least one or two 'scratch tapes' in the library at a minimum! If emulating LTO1 drives, at 100G each, 62T gives you about 600 (being conservative) volumes. Take away even 2 scratch volumes as a minimum for scratch tapes and subtract 20% of the rest as 'expired data' you still get (598 - 120) 478 volumes at 100G each of real data, or 47.8T on your 62T library. If you know your data, and know you get a real world 30% compression, then it should find close to your 62T of data ( 47.8*1.3=62.14T but that is close with this level of engineering estimate). If you get better compression you really win. Depending on your needs, you could use client compression, or tape drive compression. There are religous camps on both sides, but I suggest you give it a try both ways to see what you really get. ... green with envy ... JC
Re: determining which files will be copied to copy stgpool
If clients are backing-up during the migration period, those files will be migrated to the primary tape pool. Do you disable sessions during the migration? H. Milton Johnson -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Richard Rhodes Sent: Wednesday, September 01, 2004 2:34 PM To: [EMAIL PROTECTED] Subject: determining which files will be copied to copy stgpool We've got a strange problem. We run the normal tsm processes . . . . - run backup stgpool for primary disk pool to copy tape pool - run migration - run backup stgpool of the primary tape pool to the copy tape pool For some reason after we do this, we start to get lots of files that are in the primary tape pool but not in the copy pool. It's as if someone is doing backups straight into the primary tape pool. We've check, this is not the problem. So . . .I'm trying to figure out what these files are and where they come from. The backup stgpool primarytapepool copytapepool preview=yes cmd tells me how much data needs to be copies and the tape vols, but I also want the nodes and the files for the nodes that need copied. Q) How can you tell the nodes and files that need to be copied from a primary tape pool to a copy tape pool? Thanks Rick - 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: SQL Select statement help
You can create a script with the following select statements: select stgpool_name,'1' as Days Pending,count(*) as Total from volumes where status='PENDING' - and cast((current_timestamp-PENDING_DATE)days as decimal)=1 group by stgpool_name select stgpool_name,'2' as Days Pending,count(*) as Total from volumes where status='PENDING' - and cast((current_timestamp-PENDING_DATE)days as decimal)=2 group by stgpool_name select stgpool_name,'3' as Days Pending,count(*) as Total from volumes where status='PENDING' - and cast((current_timestamp-PENDING_DATE)days as decimal)=3 group by stgpool_name select stgpool_name,'4' as Days Pending,count(*) as Total from volumes where status='PENDING' - and cast((current_timestamp-PENDING_DATE)days as decimal)=4 group by stgpool_name select stgpool_name,'=5' as Days Pending,count(*) as Total from volumes where status='PENDING' - and cast((current_timestamp-PENDING_DATE)days as decimal)=5 group by stgpool_name When you run it you get something like: STGPOOL_NAME Days Pending TOTAL -- --- COPYPOOL 1 10 TAPEPOOL 1 9 STGPOOL_NAME Days Pending TOTAL -- --- COPYPOOL 2 10 TAPEPOOL 2 13 STGPOOL_NAME Days Pending TOTAL -- --- COPYPOOL 3 10 TAPEPOOL 3 12 STGPOOL_NAME Days Pending TOTAL -- --- COPYPOOL 4 10 TAPEPOOL 4 11 STGPOOL_NAME Days Pending TOTAL -- --- COPYPOOL =50 TAPEPOOL =50 H. Milton Johnson Voice: (210) 677-6728 -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Prather, Wanda Sent: Tuesday, August 31, 2004 1:52 PM To: [EMAIL PROTECTED] Subject: Re: SQL Select statement help I hope I'm wrong, but I don't think it's possible to do that. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Warren, Matthew (Retail) Sent: Tuesday, August 31, 2004 10:51 AM To: [EMAIL PROTECTED] Subject: SQL Select statement help Hallo ([I]T/AD)SM'ers Can any wise and clever SQL types help with the following?; I am trying to get TSM to show the number of tapes that went pending by date. I can get this; ANS8000I Server command: 'select cast(pending_date as char(10)),count(*) from volumes where status='PENDING' group by pending_date' Unnamed[1] Unnamed[2] -- --- 2004-08-27 1 2004-08-27 1 2004-08-27 1 2004-08-28 1 2004-08-28 1 2004-08-28 1 2004-08-28 1 2004-08-28 1 2004-08-29 1 2004-08-29 1 etc.. but what I would like is for the count(*) to be totaling per day. I hoped perhaps the cast() would force this to happen, but it appears the underlying timestamp is still being taken into account. I have tried various other permutations, along the lines of; ANS8000I Server command: 'select cast(pending_date as char(10)) as pending,count(*) from volumes where status='PENDING' group by pending' ANR2940E The reference 'PENDING' is an unknown SQL column name. | V.. g,count(*) from volumes where status='PENDING' group by pending but, alas, no joy. I'm wondering if it is actually possible? - I know a little Ksh script that can do it, but I was hoping to achieve it just within TSM - either with a select as I am trying or via some other method. Thanks, Matt. ___ Disclaimer Notice __ This message and any attachments are confidential and should only be read by those to whom they are addressed. If you are not the intended recipient, please contact us, delete the message from your computer and destroy any copies. Any distribution or copying without our prior permission is prohibited. Internet communications are not always secure and therefore Powergen Retail Limited does not accept legal responsibility for this message. The recipient is responsible for verifying its authenticity before acting on the contents. Any views or opinions presented are solely those of the author and do not necessarily represent those of Powergen Retail Limited. Registered addresses: Powergen Retail Limited, Westwood Way, Westwood Business
Re: Select for Tape Use
Will this work for you? tsm: TSMSRV1select volume_name,cast(last_write_date as date) as Date,cast(LAST_WRITE_DATE as time)as TIME from volumes where devclass_name='3590TAPE' and cast((current_timestamp-LAST_WRITE_DATE)days as decimal)=1 and status='FULL' VOLUME_NAME DATE TIME -- -- 34 2004-08-30 11:46:38 79 2004-08-30 13:00:20 93 2004-08-29 22:55:01 98 2004-08-30 05:57:27 000147 2004-08-30 16:16:14 000165 2004-08-30 00:58:03 001182 2004-08-30 02:53:58 001392 2004-08-29 20:42:10 001409 2004-08-30 09:14:30 A00317 2004-08-30 09:22:33 A00843 2004-08-30 14:55:18 tsm: TSMSRV1select count(*) as Total_Tapes_Used from volumes where devclass_name='3590TAPE' and cast((current_timestamp-LAST_WRITE_DATE)days as decimal)=1 and status='FULL' TOTAL_TAPES_USED 11 This is selecting the full tapes that were last written to between 24 and 48 hours ago. H. Milton Johnson Voice: (210) 677-6728 -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Hart, Charles Sent: Tuesday, August 31, 2004 3:38 PM To: [EMAIL PROTECTED] Subject: Re: Select for Tape Use I've run in to a similar req to justify tapes. (Kinda like justifying we need electricity) Anyway what I did is in excel using the odbc ran the sql below on each server which tells me the amount of backup data the backup server is maintaining. Then the following day I run a audit license on each TSM server which updates the occupancy of each node, copy that data to a new line in excel, then re-run the query below which populates the data of the previous days backup then I figure the difference. I've been doing this on a weekly basis for two years and now show one heck of a trending line. Or you could just use the TSM Operational reporter product witch tells you daily how much was backed up. SQL Statement to get All Backup Client Occupancy SELECT AUDITOCC.NODE_NAME, AUDITOCC.BACKUP_MB, AUDITOCC.BACKUP_COPY_MB, AUDITOCC.ARCHIVE_MB, AUDITOCC.ARCHIVE_COPY_MB, AUDITOCC.SPACEMG_MB, AUDITOCC.SPACEMG_COPY_MB, AUDITOCC.TOTAL_MB FROM AUDITOCC AUDITOCC -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of Owings, Don Sent: Tuesday, August 31, 2004 3:25 PM To: [EMAIL PROTECTED] Subject: Re: Select for Tape Use Why you ask? Because I'm having to justify ordering tapes and in order to do that I have to organize the data in order create some type of forecasting. What I'm looking for is a down and dirty select statement that just shows the previous nights usage. Maybe it's in TSM but I haven't found it, plus I'm dealing with TB's of data so I need it consolidated. Hope that clarifies what I'm trying to do. Don -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of David E Ehresman Sent: Tuesday, August 31, 2004 2:22 PM To: [EMAIL PROTECTED] Subject: Re: Select for Tape Use I'm looking for a select statement that shows exactly what tapes were used the previous night and what was written to the tapes. Why? TSM keeps track of all that so you don't have to.
Re: Tier'ed library
Tab, We've asked the same thing and came to the following points: 1) The $/TB is about as cheap as you can get. 2) With a VTL you can do LAN free backups. 3) To create an equiv Primary StgPool using sequential-access FILE volumes you would have to create a 200TB file system. Even using JFS2, I'm not sure you would get the same throughput as with a VTL. 4) Sepaton claims that by second quarter 2005, they will also have compression which would increase the VTL's usable capacity. AIX does not offer a compressed JFS2 filesystem, and if it did it would have to have a serious impact on performance. 5) A tape library can be shared between systems which may/may not be relevant to you. 6) We could not think of a technical advantage that favored using sequential-access FILE volumes. The biggest hurtle is changing your mind set to allow the use of disks versus tape. We have come to the following conclusions: 1) If RAID-5 is that unreliable then why are we using it for our on-line databases? 2) We will not be a tape free environment, we would just be replacing our on-site tapes with disks. The amount of time when a backup is on disks only is very short. 3) The VTL costs are low enough so that we can have a mirrored on-site tape pool. The mirror would be in another building and TSM would simultaneously write the backup to both stgpools. This would give a level of protection that would be very costly reproduce using physical tapes. The fact that IBM provides the service for the Sepaton VTL is an added plus in our shop. Please note that I originally posted this to Tab instead of the list because I did not want it to seem that I was using the list to promote Sepaton. H. Milton Johnson -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Tab Trepagnier Sent: Wednesday, June 16, 2004 8:48 AM To: [EMAIL PROTECTED] Subject: Re: Tier'ed library Milton, Thanks for the info. I briefly looked at Sepaton, but I had no idea they were that inexpensive. I will probably give them a second look. But one thing that I'm struggling with is why a VTL? Between random-access DISK volumes and sequential-access FILE volumes what does a VTL buy me that I couldn't implement using those two volume types in TSM? Thanks. Tab Trepagnier TSM Administrator Laitram, L.L.C. Johnson, Milton [EMAIL PROTECTED] 06/15/2004 03:13 PM To: Tab Trepagnier [EMAIL PROTECTED] cc: Subject:Tier'ed library Tab, We are faced with the same options and are seriously looking at Virtual Tape Libraries (VTL), an appliance that is physically a large SATA Raid Array but presents itself to TSM as a tape library. The product we are looking at is the Sepaton S2100-ES (www.sepaton.com). The things we like include: 1) It's TSM certified, meaning that it has passed the same certification the real tape libraries passed. 2) Cheap. We have been quoted $30K (USD) for the first 3TB and $18K (USD) for each additional 3TB. 3) Modular: Purchase the first 3Tb then expand in 3TB increments up to 200TB. After that you purchase another VTL. 4) Performance: Since it's disk based it's very fast, up to 1.6 TB/hour. Since the tape drives are virtual tape drives you can configure a tape library to have 200 tape drives, eliminating the tape drive bottleneck. Tape mounts happen instantly. 5) Because of the high performance and large number of available virtual tape drives, you should be able to reclaim the virtual tapes when they are only 25% reclaimable, instead of waiting until they are 50% reclaimable. This should allow much more efficient usage of the tape space. We will just use our present 3494 ATL to cut off-site tapes. We haven't implemented it yet, but we are actively pursuing it. Our contact is: David Littman The More Group 47 East Grove Street Middleboro, MA 02346 [EMAIL PROTECTED] 508-946-2255 x19 H. Milton Johnson
Re: 3590 cleaning scheduling
Clean Me requests are also generated when the drive encounters a problem. A faulty/failing drive can cause an abnormal spike in cleaning requests. I monitor these requests daily as an indicator of drive health. I have found that an increase in Clean Me messages correlates with an Attn Drive message on the LCD of the 3590E1A. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Zoltan Forray/AC/VCU Sent: Friday, June 04, 2004 1:10 PM To: [EMAIL PROTECTED] Subject: OT?: 3590 cleaning scheduling Lately, I have been noticing lots of Clean Me messages in ERRPT of the TSM AIX system, for the 3590E1A drives it uses. So, I started looking into the setting on the 3494, which controls cleaning. Currently, it is set to clean by usage (65). Upon digging through the IBM TotalStorage Enterprise Tape - A Practical Guide Redbook, I found the paragraph: We recommend that drive cleaning be based on a drive request. Use time-based cleaning only if drive usage is very low. For 3590 tape drives, use a value of 999 mounts to perform cleaning based on a drive request rather than an initiated library. So, what do you use to control the cleaning cycle for your 3494/3590 drives ? Do you follow the above recommendation ?Is this a global recommendation that can be applied to *ALL* 359x drives ? Inquiring minds want to know ?
Highly Available TSM
Management is desiring to implement a highly available TSM system with the following requirements: Campus consists of 3 buildings, presently with the lone TSM server in Bldg. 3. If Bldg. 3 goes down then all TSM activities are unavailable and management wants to eliminate that single point of failure. The goal is that the loss of a single TSM server or building would have zero impact on TSM activities, i.e. back-ups, restores, producing off-site tapes, with no/minimal intervention. They do not want to have to modify the clients to utilize an alternative TSM server. Our present server is running on AIX. OK, so this sounds like running TSM on a HACMP cascading cluster could be an answer. I can see the following shared/non-shared resources: Physical Location - Bldg 3 Bldg 1 Description HDISK2 HDISK3 TSM DB Volumes mirrored via TSM - Separate VGs HDISK4 HDISK5 TSM LOG Volumes mirrored via TSM - Separate VGs HDISK6 HDISK7 Singled mirrored VG housing TSM Storage Pool used for on- . site tape pool, Stgpool name=TAPEPOOL. An alternative . could be a mirrored virtual tape library. 3494ATL Used to create/read offsite tape volumes when Bldg 3 is . the active node using 3494E drives. Stgpool name=COPYPOOL . This is a non-shared TSM resource. . 3494ATLUsed to create/read offsite tape volumes when Bldg 1 is . the active node using 3494E drives. Stgpool name=COPYPOOL . this is a non-shared TSM resource. So when failover to Bldg 1 happens, HDISKs 3, 5 7 are used and that takes care of the DB, Logs onsite tapes, and clients can continue to backup/restore to/from TAPEPOOL. The issues with the tape library for COPYPOOL present me with some questions. The issues I see include: 1) After failover TSM will have an incorrect view of what is in the library. I . assume that running an Audit Library LibName Checklabel=barcode followed . a LABEL LIBVolume LibName SEARCH=Yes CHECKIN=SCRatch DEVType=3590 . OVERWRITE=Yes will give TSM an accurate view of the library contents and a . supply of scratch tapes. 2) After failover, COPYPOOL volumes in the failed library may actually be . physically lost/destroyed. I believe that if I identify those volumes and . update their access to destroyed and backup TAPEPOOL to COPYPOOL I will have . solved that problem. When Bldg 3 comes back on-line and HDISKs 2,4 6 are available I would: 1) Resync HDISK6 via AIX. (this could take a while) 2) varyon the VGs for HDISKs 2 4 and mount the file systems 3) resync the DB LOG volumes on HDISKs 2 4 via TSM So my questions are: What have I missed? Anyone out there administering a HA-TSM system with cluster nodes in different buildings? If so what is your architecture like? is their a way to achieve these goals without HACMP? If so, how? Thanks, Milton Johnson
Re: DRM Procedures
Dave, If you make a slight change in order you should solve your problem: 1) backup clients to disk where possible, tape where not 2) backup diskpools to copypool 3) backup tapepools to copypool 4) backup DB to tape *NOTE: At this point ALL of your data has been copied to your copypool and you have a DB backup that reflects that. You can now eject your DRM volumes (copypool and DB backup) and send them to your vault. 5) migrate disk to tape 6) expire inventory We actually migrate and expire at the same time, having the I/O and CPU bandwidth to support doing that. H. Milton Johnson -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of David Benigni Sent: Thursday, April 29, 2004 8:29 AM To: [EMAIL PROTECTED] Subject: Re: DRM Procedures Steve, Our Tivoli setup was actually done by an outside group. Here is how it is currently run: bbackup clients to disk where possible tape where not backup diskpools to copypool backup tapepools to copypool migrate disk to tape.ackup DB expire inventory The problem with this is that what there is a massive amount of data the migration is not done before the db backup. SO, I can't be sure that everything is offsite on the copy pool. Flipping the schedules around would fix this. I was attacking it by lets get the migration as fast as possible. Shouldn't be any draw backs this way. Thanks! Dave [EMAIL PROTECTED] 4/28/2004 7:34:33 PM Dave You can set maxproc on your diskpool and run as many processes as you have drives. That works fine. But, why is the disk to tape dump speed important to you? Most shops run a cycle of backup clients to disk where possible tape where not backup diskpools to copypool backup tapepools to copypool backup DB expire inventory migrate disk to tape. In my shop we leave the data on disk until about 5PM so that most restores are done from disk rather than tape. But, we could start migrating as early as about 11AM with our current volumes. TSM is very efficient with its tape drives as compared with other competing products. As long as the migrate is complete before the next backup cycle that's enough. Or do you have some sort of special requirement that I don't understand? Regards Steve. [EMAIL PROTECTED] 29/04/2004 6:15:27 Steve, I could run the backup stg more times, that a different idea that I have not thought about. After looking at the timing the making the copy pool is very fast. The time hog is migrating the disk pool to the primary tape pool. Now, besides throwing more drives at this, is there any way to make this process quicker? Thanks for the insight. Dave [EMAIL PROTECTED] 4/27/2004 7:18:12 PM Dave, The maxprocess idea is a good one and will help, but yes, you will send more tapes offsite. As an alternative, could you run the backup stg process more often, say two or three times over the night? Then the last part of the copy will only take a small amount of time and your window is reduced. HTH Steve Steve Harris AIX and TSM Admin Queensland HEalth, Brisbane, Australia [EMAIL PROTECTED] 27/04/2004 23:35:36 For our DRM procedures we have a script that runs nightly that does a backup of all the primary storage pool to our copy pool. Currently on a daily basis we are taking 1 tape of data and 1 database tape off site. I would like to reduce the windows which it takes the copy pool to be created. I believe by doing the backup with the maxprocess directive that would allow me to mount more tapes during this process, but this would increase the number of tapes going off site. Does this sound correct to everyone? TIA for the input. Dave *** This email, including any attachments sent with it, is confidential and for the sole use of the intended recipient(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 recipient(s), or if you have received this email in error, you are asked to immediately notify the sender by telephone or by return email. You should also delete this email and destroy any hard copies produced. *** *** This email, including any attachments sent with it, is confidential and for the sole use of the intended recipient(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.
Any experience with Sepaton VTL
I got a call from a rep asking if I was interested in a Sepaton S2100 VTL (Virtual Tape Library) (www.sepaton.com). It's billed as: * a fiber connected SATA RAID Virtual Tape Library Appliance * 3-200 TB Capacity / 1.6 TB/hour throughput * configure up to 200 virtual tape drives * Emulates various tape libraries * serviced by IBM * works with TSM You would: * define the VTL as a primary storage pool, called say SEPPOOL, and point all your backups to SEPPOOL * define SEPPOOL's next stg pool to be your traditional TAPEPOOL Your present tape library would be used to cut, read and reclaim off-site tapes and as a backup in case you unexpectedly fill up SEPPOOL. There would be no need for collocation because of the speed of the VTL. There would be no need for a DISKPOOL or migrations. You could effectively reclaim off-site tapes with as few as 1 drive in your real tape library. It will also wash your car, mow your lawn and cure the common cold (OK, I exaggerating a little). I'm not sure on the pricing, somewhere around $30K/3.6TB US dollars. My questions include where's the down side? What's the catch? If your choice is between expanding by purchasing a second 3494 frame or a S2100 VTL, why choose a 3494 frame? Thanks, H. Milton Johnson UNIX Systems Administrator - USCC San Antonio, TX Email: [EMAIL PROTECTED]
Re: Server IP controls
Zoltan, According to RFC 1918, the following are private, non-routed subnets: 10.0.0.0 - 10.255.255.255 172.16.0.0 - 172.31.255.255 192.168.0.0 - 192.168.255.255 Being non-routed you cannot connect from 128.172.6.177 to 192.168.20.44 unless you have a connection to the same physical subnet as 192.168.20.44. We use a private, non-routed subnet for our clients, but the clients are required a second NIC connected to the private, non-routed subnet. H. Milton Johnson Voice: (210) 677-6728 -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Zoltan Forray/AC/VCU Sent: Tuesday, April 13, 2004 8:22 AM To: [EMAIL PROTECTED] Subject: Server IP controls Recently, we have been reconfiguring/locking down a lot of the TCPIP ports in use by the TSM servers and clients, attempting to control/route TSM traffic across a private subnet versus the more heavily used public network. However, we have been having some TSM scheduler communications, due to port blocking issues. I am trying to figure out if/how the TSM server can be configured to control which of its 2-IP connections it uses to communicate with the clients. Here is my configuration: TSM AIX 5.2.1.3 server. 2-IP connections, 128.172.6.201 (primary/public) and 192.168.20.44 (private). The TSM client in question only has 1-IP connection, 128.172.6.177. The DSM.SYS (AIX) points to the server via DNS name that resolves to 192.168.20.44. My networking person says the traffic is flowing across the 6.201 connection, not the 20.44 private connection. How, if possible, can I get the TSM server to use the private 20.44 connection to perform the backups ? Is there some server setting that can control this ? We are trying to get another connection to the client, using the private subnet. Unfortunately, there aren't any available ports in the switch, at this time. Yes, I know that when I get the other port in the client, I can use the TCPNODEADDRESS options to control this.
Re: Server IP controls
Zoltan, Try this, from a command line on the client: ping 192.168.20.44 Does the ping work? If the ping fails then you do not have a connection to 192.168.20.44 and no amount of port opening, aliasing, etc. can get your traffic to flow to and from 192.168.20.44. H. Milton Johnson -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Zoltan Forray/AC/VCU Sent: Tuesday, April 13, 2004 12:01 PM To: [EMAIL PROTECTED] Subject: Re: Server IP controls The connection isn't the problem. The client talks to the server (and vice-versa) just fine, if the ports are not blocked. I want the server to use its private subnet to talk to the client, not its public connection. After all, this can be forced on the client via TCPNODEADDRESS, can the server do the same. Yes, I believe the private network is routed since lots of systems, both physically on the same and not in the same building, connect to the TSM server, just fine. ADSM: Dist Stor Manager [EMAIL PROTECTED] wrote on 04/13/2004 11:42:40 AM: Zoltan, According to RFC 1918, the following are private, non-routed subnets: 10.0.0.0 - 10.255.255.255 172.16.0.0 - 172.31.255.255 192.168.0.0 - 192.168.255.255 Being non-routed you cannot connect from 128.172.6.177 to 192.168.20.44 unless you have a connection to the same physical subnet as 192.168.20.44. We use a private, non-routed subnet for our clients, but the clients are required a second NIC connected to the private, non-routed subnet. H. Milton Johnson Voice: (210) 677-6728 -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Zoltan Forray/AC/VCU Sent: Tuesday, April 13, 2004 8:22 AM To: [EMAIL PROTECTED] Subject: Server IP controls Recently, we have been reconfiguring/locking down a lot of the TCPIP ports in use by the TSM servers and clients, attempting to control/route TSM traffic across a private subnet versus the more heavily used public network. However, we have been having some TSM scheduler communications, due to port blocking issues. I am trying to figure out if/how the TSM server can be configured to control which of its 2-IP connections it uses to communicate with the clients. Here is my configuration: TSM AIX 5.2.1.3 server. 2-IP connections, 128.172.6.201 (primary/public) and 192.168.20.44 (private). The TSM client in question only has 1-IP connection, 128.172.6.177. The DSM.SYS (AIX) points to the server via DNS name that resolves to 192.168.20.44. My networking person says the traffic is flowing across the 6.201 connection, not the 20.44 private connection. How, if possible, can I get the TSM server to use the private 20.44 connection to perform the backups ? Is there some server setting that can control this ? We are trying to get another connection to the client, using the private subnet. Unfortunately, there aren't any available ports in the switch, at this time. Yes, I know that when I get the other port in the client, I can use the TCPNODEADDRESS options to control this.
Re: Question on Restoration from DBSNAPSHOT
Mark / Mike, Nice to here from you Mark. I am aware that DBSNAPSHOT can only be used for PIT restoration, at least after refreshing myself, and that only the BACKUP DB FULL/INCR resets the recovery log. What I'm now asking is can I make two DBB (full), one immediately after the other, and then use either one to do a restore to the point of failure using the recovery log? Thanks, H. Milton Johnson Voice: (210) 677-6728 -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Mark D. Rodriguez Sent: Tuesday, February 17, 2004 10:23 AM To: [EMAIL PROTECTED] Subject: Re: Question on Restoration from DBSNAPSHOT Hi Milton, It's been a long time since we talked. You know you could have just called me and I would have helped you out. But anyway here is what I recommend: DBSNAPSHOT - should be used for your DR backups of the DB. They should be to a tape and taken offsite with your DR tapes. DBSNAPSHOT is effectively a full backup of the DB, but it does not involve the LOG in any way. Therefore, it can only be used for a PIT (point in time) restore. Also, please note that a DBSNAPSHOT does not reset the LOG like a DBB (full or incremental) does if the LOG is set to ROLLFORWARD. This makes it perfect for a DR type restore since in a disaster you would expect that the LOG would be lost. Please note if you are using DRM then you should update your scheduled Prepare command to include Prepare Source=DBSnapshot so that it manages the correct tapes for you. I sure do wish that the ITSM developers would make this the default! DBB(full and incremental) - should be kept onsite for rapid DB recovery including restore to the most recent time using a ROLLFORWARD log. I prefer to do these DBB to a device of type FILE. This allows for much faster backups and restores. Furthermore, I can schedule a full once a week and incrementals the rest of the week with no penalty on the restore time for multiple volumes since they are all coming from disk. This methodology offers a few more not so obvious advantages, you could easily schedule multiple DBB incrementals a day thus reducing the size requirement of you LOG. Also, if you use DEFine DBBackuptrigger you can set your triggered backups to go to the same device of type FILE which means in a triggered event your DBB will take place much faster and a rapidly growing DB would be less likely to trigger the DB spacetrigger. Remember when defining your DBBackuptrigger to make sure you specify NUMINCremental to 32 allowing for as many incrementals as possible between fulls, again there is no penalty here for multiple volumes since it is going to a device of type FILE. BTW, based on your note you were doing DBSNAPSHOT's daily which takes as much space as a DBB full does. If you switch to the method described above, you will use far less space on disk since you will be doing mostly incremental backups of the DB. If you are anyone else has any questions about this please feel free to contact me either by this list or send me email directly. -- Regards, Mark D. Rodriguez President MDR Consulting, Inc. === MDR Consulting The very best in Technical Training and Consulting. IBM Advanced Business Partner SAIR Linux and GNU Authorized Center for Education IBM Certified Advanced Technical Expert, CATE AIX Support and Performance Tuning, RS6000 SP, TSM/ADSM and Linux Red Hat Certified Engineer, RHCE === Johnson, Milton [IT] wrote: All, TSM: Storage Management Server for AIX-RS/6000 - Version 4, Release 2, Level 1.7 OS: AIX 4.3.3 ML 9 Log Mode: RollForward (Upgrade project planned in near future, but that's another story) Everyday I do a full backup of the database to 3590E tape, immediately followed by a DBSNAPSHOT to a file on disk. The 3590E tape promptly goes offsite. My question is if I experience a loss of the database can I then restore from the DBSNAPSHOT and recover to the point of failure using the RECOVERY LOG? I would like to avoid the time delay of returning the 3590E tape, containing the database backup, from the vault. Anyone done this? Thanks, H. Milton Johnson UNIX Systems Administrator - USCC San Antonio, TX Email: [EMAIL PROTECTED]
Re: Question on Restoration from DBSNAPSHOT
Mark, Actually it's not confusing. Logically since there have been no transactions between the two full DBB, resetting the recovery log should not logically cause any problems. Of course if TSM is marking each DBB and recovery log set with some sort of serial number, and will only play with matching serial numbers I can understand the mechanical reason why it won't work. Of course I can have my cake and eat it too by: 1) Doing a full DBB to disk 2) Sending that DBB to tape during my daily Sysback system backup Thanks, H. Milton Johnson Voice: (210) 677-6728 -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Mark D. Rodriguez Sent: Tuesday, February 17, 2004 1:05 PM To: [EMAIL PROTECTED] Subject: Re: Question on Restoration from DBSNAPSHOT Milton, The short answer is no. You can only use the most recent full/incremental series to restore to the most current state, i.e. using the ROLLFORWARD log. The reason is that once you do a DBB (either full or incremental) the log is reset. Therefore any older version, in your case the first DBB full, can only be used for a PIT restore. Hang in there, I know it gets confusing at times but it really does make sense in a crazy sort of way! -- Regards, Mark D. Rodriguez President MDR Consulting, Inc. === MDR Consulting The very best in Technical Training and Consulting. IBM Advanced Business Partner SAIR Linux and GNU Authorized Center for Education IBM Certified Advanced Technical Expert, CATE AIX Support and Performance Tuning, RS6000 SP, TSM/ADSM and Linux Red Hat Certified Engineer, RHCE === Johnson, Milton [IT] wrote: Mark / Mike, Nice to here from you Mark. I am aware that DBSNAPSHOT can only be used for PIT restoration, at least after refreshing myself, and that only the BACKUP DB FULL/INCR resets the recovery log. What I'm now asking is can I make two DBB (full), one immediately after the other, and then use either one to do a restore to the point of failure using the recovery log? Thanks, H. Milton Johnson Voice: (210) 677-6728
Re: Question on Restoration from DBSNAPSHOT
Mike, I'm somewhat surprised that so far yours has been the only reply. I have reviewed the 4.2 Administrators Reference and it clearly states on page 873 that a snapshot can not be used to restore a db to it's most current state, so I guess that answer's my original question but begs another. If I make a full backup to tape/disk and immediately follow it with another full backup to disk/tape, can I do a db restore to it's most current state using either one of the full db backups as a starting point and the recovery log? Richard, Do you have any thoughts/knowledge on this? Thanks, H. Milton Johnson Email: [EMAIL PROTECTED] -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Mike Wiggan Sent: Friday, February 13, 2004 10:38 PM To: [EMAIL PROTECTED] Subject: Re: Question on Restoration from DBSNAPSHOT Milton, We recently introduced disaster recovery, and I pondered this for a while. The outcome is that we store the DBSNAPSHOT off site, as one can recover to a point in time. In our case VIA a SAN to another robot. We keep the full backup + any incremental within the local robot to avoid time delay. Prior to introducing DR, I remember one evening when we had to recover the database and it took two hours before we got the tape into the robot. One soon learns. Kind Regards Mike Wiggan, TCS/14 IT Infrastructure Integration Specialist Petroleum Devlopment Oman LLC ([EMAIL PROTECTED]) -Original Message- From: Johnson, Milton [IT] [mailto:[EMAIL PROTECTED] Sent: Thursday, February 12, 2004 20:06 To: [EMAIL PROTECTED] Subject: Question on Restoration from DBSNAPSHOT All, TSM: Storage Management Server for AIX-RS/6000 - Version 4, Release 2, Level 1.7 OS: AIX 4.3.3 ML 9 Log Mode: RollForward (Upgrade project planned in near future, but that's another story) Everyday I do a full backup of the database to 3590E tape, immediately followed by a DBSNAPSHOT to a file on disk. The 3590E tape promptly goes offsite. My question is if I experience a loss of the database can I then restore from the DBSNAPSHOT and recover to the point of failure using the RECOVERY LOG? I would like to avoid the time delay of returning the 3590E tape, containing the database backup, from the vault. Anyone done this? Thanks, H. Milton Johnson UNIX Systems Administrator - USCC San Antonio, TX Email: [EMAIL PROTECTED]
Question on Restoration from DBSNAPSHOT
All, TSM: Storage Management Server for AIX-RS/6000 - Version 4, Release 2, Level 1.7 OS: AIX 4.3.3 ML 9 Log Mode: RollForward (Upgrade project planned in near future, but that's another story) Everyday I do a full backup of the database to 3590E tape, immediately followed by a DBSNAPSHOT to a file on disk. The 3590E tape promptly goes offsite. My question is if I experience a loss of the database can I then restore from the DBSNAPSHOT and recover to the point of failure using the RECOVERY LOG? I would like to avoid the time delay of returning the 3590E tape, containing the database backup, from the vault. Anyone done this? Thanks, H. Milton Johnson UNIX Systems Administrator - USCC San Antonio, TX Email: [EMAIL PROTECTED]
Re: Restoring files from a savevg
You have stacked files onto one tape. To restore the XXXvg use: # mt -f /dev/rmt0.1 fsf 1; restorevgfiles -f /dev/rmt0.1 To restore the YYYvg use: # mt -f /dev/rmt0.1 fsf 2; restorevgfiles -f /dev/rmt0.1 Milton Johnson Voice: 210-677-6728 Email: [EMAIL PROTECTED] -Original Message- From: Calvin Chang [mailto:[EMAIL PROTECTED] Sent: Monday, December 08, 2003 1:53 PM To: [EMAIL PROTECTED] Subject: Restoring files from a savevg Hello everyone, I'm having trouble trying to restore a file from my VG. Here is the scenario: Basically every night I backup my mksysb, XXX Volume group, and YYY Volume group all to one tape using this command #mksysb -ie /dev/rmt0.1 #savevg -i -f /dev/rmt0.1 XXXvg #savevg -i -f /dev/rmt0.1 YYYvg How do I access data that I need to restore from the XXXvg?? I tried using the #restorevgfiles -f /dev/rmt0 command and it returns saying that the file is not in an archive format. Any help would be deeply appreciated. Thanks
Re: TSM on AIX now, platform change coming?
Personally I would never consider a WinDoze solution. WinDoze does not have a rich scripting environment like UNIX does. Using scripting I have been able to: * Increase the performance of my TSM server * Improve reclamation efficiency * Created a menu driven program to aid the day-to-day maintenance * Monitor TSM for problems with notification via web pages, email and pager * Store useful information in the TSM DB such as: - Number of cleaning cartridges in library - Number of cleaning cycles remaining on those cartridges - Number of times each tape drive was cleaned in the last 24 hours (excessive cleaning could point to a problem) * etc, etc A WinDoze environment is just too limiting an environment. You have TSM on AIX experience, so I would not change without a very compelling reason. Also TSM on AIX means that one vendor supports the hardware, OS and application. Any problem arising from that combination is IBM's problem. I try to avoid situations where multiple vendors can point fingers at each other. Milton Johnson -Original Message- From: Nancy Reeves [mailto:[EMAIL PROTECTED] Sent: Friday, December 05, 2003 8:52 AM To: [EMAIL PROTECTED] Subject: Re: TSM on AIX now, platform change coming? I was reminded that another of our options is using Windows (Win2K3). How does that compare with using AIX Sun for TSM servers? Nancy Reeves Technical Support, Wichita State University [EMAIL PROTECTED] 316-978-3860 -Original Message- We are now running TSM 4.2 on an AIX box. Not only is the TSM level unsupported, so is the AIX level. And the box is running on empty, plus we are really tight on storage, both disk and tape. Any thoughts on comparing AIX vs. Sun for a TSM server?
Re: Tivoli Field Guides
Thanks, unfortunately the Reclamation Tips guide link is broken. Milton Johnson -Original Message- From: Richard Sims [mailto:[EMAIL PROTECTED] Sent: Tuesday, November 18, 2003 7:51 AM To: [EMAIL PROTECTED] Subject: Tivoli Field Guides A lesser-known information source for registered IBM customers is found in the Tivoli Field Guides - yet another area in the amazing information store created and maintained by IBM. Here you can find explorations of various topics such as HSM, Windows cluster service database backup and restoral, a treatise on the full-incremental backup philosophy, patches, and other topics. There are some rough edges, such as the broken link for the Reclamation Tips guide, but nevertheless a helpful information source. Go to: http://www.ibm.com/software/sysmgmt/products/support/Field_Guides.html and wend your way through its subdivisions. Richard Sims, BU
Re: Move nodedata - what is moved first
Marc, Part of our routine to send tapes offsite includes BACKUP STGPOOL DISKDIRPOOL COPYPOOL which send the DIRMC storage pool offsite. Part of the restoration procedure includes RESTORE STGPOOL DISKDIRPOOL Milton Johnson Voice: 210-677-6728 Email: [EMAIL PROTECTED] -Original Message- From: Marc Levitan [mailto:[EMAIL PROTECTED] Sent: Friday, October 24, 2003 8:13 AM To: [EMAIL PROTECTED] Subject: Re: Move nodedata - what is moved first What would happen if there was a site disaster and the data was only on the disk which is no longer available to perform restores? I guess what I am asking is, without sending DIRMC off-site, can you recover from a site disaster? |-+--- | | Deon George | | | [EMAIL PROTECTED]| | | .COM | | | Sent by: ADSM: | | | Dist Stor | | | Manager| | | [EMAIL PROTECTED]| | | T.EDU | | | | | | | | | 10/23/2003 08:07| | | PM | | | Please respond | | | to ADSM: Dist | | | Stor Manager | | | | |-+--- --- | | | |To: [EMAIL PROTECTED] | |cc: | |Subject: Re: Move nodedata - what is moved first | --- | Peter, servers . Currently, our main file server has data on over 200 3590 tapes therefore a directory restore can potentially have hours added to the process directly related to tape mounts. Is the directory information you referring about related to Windows systems? You should use the DIRMC client option to store all your directory information in a DISK based storage pool (DISK or FILE), so that it remains on faster quicker access media for restore purposes. (Dont let that stuff go to tape for the reasons you have outlined below.) The DIRMC client option is not really required for Unix based systems, as the database has enough space to store that information. ...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: SQL to determine what offsite volumes are needed for move dat a
Bill, I also have only 2 tape drives and was running in to the problem of tapes going off sight and never coming back. I solved it by creating a reclamation script that does the following (pseudo code): for stgpool in TAPEPOOL COPYPOOL do while [count(stgpool tapes 51% reclaimable) -gt 0] do find percent_reclaimable of most reclaimable tape in stgpool update stg stgpool recl=percent_reclaimable while reclaimation in process do sleep 5 minutes done update stg stgpool recl=100 done done With this approach I have brought the count of COPYPOOL tape 51% reclaimable down from ~130 to ~6. I was pleasantly surprised by the impact this approach had. Thanks, Milton Johnson Voice: 210-677-6728 Email: [EMAIL PROTECTED] -Original Message- From: Bill Kelly [mailto:[EMAIL PROTECTED] Sent: Thursday, October 16, 2003 9:54 AM To: [EMAIL PROTECTED] Subject: SQL to determine what offsite volumes are needed for move data Hi, We're running TSM server 5.1.6.2 on z/OS. One of the (many) resources we're short on is tape drives. Consequently, I'm always looking to streamline processes that use these drives. Here's the problem I'm currently looking at: Our tape copy pools are kept offsite. Reclamation for these pools is handled by leaving the TSM reclamation threshhold at 100% so that he never does reclaims on his own. On a regular basis, we run a job that queries the server for copy pool tapes with a reclamation threshhold greater than 'n' percent. This list of tapes is used by the operators to go and fetch the tapes to be brought onsite. They then run a job that updates those tapes to access=readwrite, and issues a 'move data' command for each tape. Now the problem. Some of these 'move data' processes treat the volume that is being emptied as 'offsite', even though the volume has been loaded into the library and its access updated to readwrite. I'm pretty sure the reason for this is that the volumes in question have files at the beginning and/or end that span to other copy pool volumes which are themselves still offsite. If the volume being emptied is treated as 'onsite', then the move data runs pretty quickly - the copy pool volume is mounted for input, the data is copied, and the volume goes pending. However, if the volume being emptied is treated as 'offsite', TSM will perform the move data by mounting for input *all* of the primary pool tapes that have data on this copy pool tape. Since our primary tape pools are collocated, while our copy pools are not, this results in dozens of tape mounts for primary pool volumes to use as input. The move data process can take hours in this case, tying up tape drives much longer than necessary. For the moment, I'll ignore the question of whether TSM should be smart enough to mount only the one or two primary pool volumes that contain the spanned files, and use the single copy pool volume that's being emptied for all the other data. The way I've been handling this is rather cumbersome. These are the steps I take: - after the move data's have started, issue a 'q proc' command - cancel all of the move data's that are treating their input volume as 'offsite' - issue an 'audit v' command for each of the copy pool volumes being treated as 'offsite' - each audit volume process fails with the following message: ANR2456E AUDIT VOLUME: Unable to access associated volume NN - access mode is set to offsite. - this tells me which additional copy pool volume needs to be brought onsite in order to make a move data process treat the original volume to be emptied as an onsite volume - go get the additional offsite volumes needed, load them into the library, update their access to readwrite, and issue move data commands for the original volumes being treated as offsite by TSM Then, of course, the entire process has to be repeated because the 'audit volume' command will only tell me *one* offsite volume that might be needed; if a volume has files that span from both the beginning and end of the tape, I won't know that until the 2nd round of 'move data' commands is issued. As you can see, this is a laborious, difficult-to-automate process. Things would be greatly simplified if we could tell right up front which copy pool volumes were going to be treated as offsite, and which additional copy pool volumes would be needed to be brought onsite in order to make the move data's all run as 'onsite'. Having this information up front would allow me to build a list of *all* tapes needing to be brought onsite, requiring only one trip to the offsite location, saving all the hassle of canceling/auditing/etc. I *know* that the information about which offsite volumes are needed must be easy/quick to retrieve, because the 'audit volume' commands fail instantly with the message telling me what offsite volume is needed. So, here's my question (finally!): can anyone provide SQL that could be used to tell me, given a copy pool
