managed system for SAN
Are the 'Managed systen for SAN storage Agent's' part of the 5.1 base product for the extended edition, or are the separately licensed?
Re: Restore: Gui vs. CLI - Differences?
Andy, Andrew Raibeck wrote: See one of my prior posts on this topic in the ADSM-L archives at http://msgs.adsm.org/cgi-bin/get/adsm0103/207.html for explanation and suggestions. Thanks for that very quick answer and the link (I had searched, but too many results...). That pretty much explains why the GUI client does what it does (actually, we had thought of the missing "entry point" [no dir for that date] as a possibility, but then excluded that, thinking this could never be...), unfortunately not, why such a design decision has been taken... :) We will now take a closer look at this and choose from one of the possibilities outlined in your post. Is there anywhere I could "vote" for new features in TSM? :) Thanks again, regards, tobias hofmann -- -- Dipl.-Ing. Tobias Hofmann Bauhaus-Universitaet Weimar D99423 Weimar Professur fuer Graphische Datenverarbeitung Projekt medienquadrat SnailMail: Bauhaus-Universitaet Weimar, Fak. Medien, D99421 Weimar Location: D99423 Weimar Karl-Haussknechtstr. 7 Zimmer 111 Fon: ++49-(0)3643-58-3780 Fax : -3701 e-mail: mailto:[EMAIL PROTECTED] --
5.2 manual CD
We received our set of TSM 5.2 CD's yesterday. I noticed there wasn't a CD of manuals delivered as with 5.1. Did anyone receive 5.2 specific manual CDs with their delivery?
Flash for SuSE Linux packages update
TSM Community, I just learned of a Flash regarding SuSE Linux...please read below: == BEGINNING OF FLASH === Problem: ITSM Server and Storage Agent packages, versions 5.1.5 and 5.2.0 for Linux/x86 cannot be installed on SuSE Linux Enterprise Server 7 (SLES7) due to incompatibility of C runtime libraries. The following error results from executing the command rpm -ivh TIVsm-server-5.1.5-0.i386.rpm on SLES7 with glibc version 2.2.2 installed: error: failed dependencies: libc.so.6(GLIBC_2.2.3) is needed by TIVsm-server-5.1.5-0 Who is Affected: Users trying to install versions 5.1.5 and 5.2.0 of ITSM Server or Storage Agent packages on the SuSE Linux Enterprise Server 7 for x86 operating system, with glibc version 2.2.2 installed. NOTE: Red Hat users are NOT affected. Recommendation: In order to install Linux packages on SLES7, the following procedure should be followed: 1) Download the latest maintenance or patch from service.boulder.ibm.com for your corresponding release. For example, for ITSM release 5.1.5, download maintenance level 5.1.7.0, or patch level 5.1.7.1(These are the latest maintenance and patch levels available for ITSM 5.1.5 as of the time of this writing). For ITSM release 5.2.0, download maintenance level 5.2.0.1(This is the latest patch level available for ITSM 5.2.0 as of this writing). 2) Install the downloaded maintenance or patch packages on your SLES7 system. For installation instructions, see the README file accompanying the maintenance or patch package. 3) Insert the CD that contains the corresponding ITSM release packages and install the license files from the CD. For installation instructions, refer to the ITSM for Linux Quick Start book. Conclusion: In order to comply with C runtime library compatibility on all Linux/x86 distributions supported by ITSM, the latest maintenance and patch level packages have been refreshed on the IBM maintenance web site. Users should follow the procedure described above in order to install ITSM on SuSE Linux Enterprise Server 7 successfully. = END OF FLASH Finally, the ftp for the latest maintenance and patch levels are at : ftp://ftp.software.ibm.com/storage/tivoli-storage-management/maintenance/ and, ftp://ftp.software.ibm.com/storage/tivoli-storage-management/patches/ Cordially, Sam J. Giallanza Knowledge Engineer Tivoli Certified Consultant [EMAIL PROTECTED] 520.799.5512 - T/L 321.5512 Our new web Support site and KB is at : http://www-3.ibm.com/software/sysmgmt/products/support/IBMTivoliStorageManager.html
Re: moving TSM to another server
From: Leonard Lauria [mailto:[EMAIL PROTECTED] > Even if I let the backups slowly expire on the old > system, and do new ones to the new server...which > will be extremely difficult due to the number of > tape drives I have...I still have 15 TBs of HSM data > on a single node that must be moved. Is the only way > to do this export/inport? Yes. > Why can't the database be dumped and loaded on a new > server? Isn't that what happens for DR? Why can't > I just pretend I am doing a DR to my new server and > leave the data there? This must be a stupid idea > since it is not in the FAQ, but I don't see why at > the moment. > > I am changing the type of platformmoving from > a Solaris system to a AIX system. That's the crux of the problem. Because moving a TSM database from one OS to another, while it may work when you're staying within the UNIX world, is not supported. If it's not supported, there are probably good reasons for it. If you were moving from one Solaris box to another, it wouldn't be an issue. -- Mark Stapleton ([EMAIL PROTECTED]) Berbee Information Networks Office 262.521.5627
Large file backup strategies
We resently purchased a couple of sql server boxes for use in storing ESRI GIS layers. This includes the storing of orthophotography images covering our entire state. The orthos are stored in SQL Server with the initial load creating a backup file 55 GBs in size. As we load more TIFs this backup file will only grow. According to the administrator of our backups the policy governing this machine is set to maintain 60 versions of a file. I thought this was over kill before but with SQL Server backups that will approach 100GBs our backup server will probably drown in orthophoto backups. My administrator states that the system can not be configured to retain x number of versions of one file type and y number of versions for all others . Are there any work arounds so that I don't have 60 versions of .bak files while retaining that number for all other files? Thank you, Randy Kreuziger ArcSDE Administrator
Re: bACKING UP A SERVER WITH 500gb
Look out for the network speed on this! 100 Mb is 15 GB/hr. 1 GB is 50 GB/hr. So, if you get 4 sessions going (4 nics on TSM) you could crank 200 GB/hr on the 1 Gb network. Your milage will vary! Fritz Hayes > Subject: Re: bACKING UP A SERVER WITH 500gb > > We are looking at the same issue. In our case, we need to perform IMAGE > backups of 2-4 Terabytes of data, weekly. > > We are looking at LTO2 (200GB native per cartridge). > > Saw this blurb: > > "The Ultrium LTO2 is the ideal choice for modern data centers where the > backup window is shrinking, backing up 400 GB in less than two hours. This > device has 60MB/s data transfer rate (compressed) with Data Rate Matching > to > accommodate host speeds between 10 MB/s and 30MB/s. LTO2 allows backup of > 216.0 GB/hour (compressed). " > > Of course this is a sales pitch (not mine, the vendors). > > Subject:bACKING UP A SERVER WITH 500gb > > > i am using using tsm with primary disk storage pools (zos 3390's) and > secondary storage pools > 3590's > > new server i installed has a file that is over 300gb's, changes daily > i have had to exclude the folder that contains the file till i can find > a storage medium that will have enough capacity > > what are other folks doing to backup this amount of data > > > Tim Brown > Systems Specialist > Central Hudson Gas & Electric > 284 South Ave > Poughkeepsie, NY 12601 > Phone: 845-486-5643 > Fax: 845-486-5921
AW: virtual write error on Raid-1
There is always some space left, lately about 16 GB, which is more than MAXCAP (5GB) but less then MAXCAP times MOUNTLIMIT (5*6). Neverthless, this was probably not the reason, since scratch files created immediately afterwards by the very same reclaim process were written without problem. thanks Juraj -Ursprüngliche Nachricht- Von: Bill Boyer [mailto:[EMAIL PROTECTED] Gesendet: Mittwoch, 06. August 2003 13:20 An: [EMAIL PROTECTED] Betreff: Re: virtual write error on Raid-1 Is there space in the filesystem? The MAXCAPACITY of the device class...is there that much space available? Bill Boyer DSS, Inc. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of Salak Juraj Sent: Wednesday, August 06, 2003 5:30 AM To: [EMAIL PROTECTED] Subject: virtual write error on Raid-1 Hello all, anyone has seen before? TSM Server reports sometiems write error on a disk raid-1 volume, while neither an evidence about an error is elsewhere (Raid-Controller, event log) nor I am able to provoke an write error wit a test program. This problem occures sometimes, but not always, when an reclamation process reclaimss an LTO tape to a disk volume defined in 2003.08.05 11:41:50 ANR1340I Scratch volume V:\TSM\RECLAIMPOOL1\0DAA.BFS is now defined in storage pool RECLAIMTPDB. 2003.08.05 11:47:11 ANRD pvrfil64.c(1056): ThreadId<30> Error writing FILE volume V:\TSM\RECLAIMPOOL1\0DAA.BFS. 2003.08.05 11:47:11 ANR1411W Access mode for volume V:\TSM\RECLAIMPOOL1\0DAA.BFS now set to "read-only" due to write error. TSM 5.1.7.0 on W2K SP3 IBM 345 with two Raid 4m controller, RAID-1 Disks
Re: Problem between TSM and Autoloader
Hi Nguyen, Thank very much about your help. Nice to meet you. Are you vietnamese ? Regards, - Original Message - From: Vo An Nguyen To: [EMAIL PROTECTED] Sent: Thursday, August 07, 2003 1:15 AM Subject: Re: Problem between TSM and Autoloader Hello Hieu, This is APAR IC36636 "THE 5.1.5.X TSM SERVER IS UNABLE TO RECONIGNIZE THE IBM 360716X LIBRARY" It is fixed in the patch level 5.1.7.1 available at: ftp://service.boulder.ibm.com/storage/tivoli-storage-management/patches/server/NT/5.1.7.1/ Regards, Vo An Nguyen Email: [EMAIL PROTECTED] Le Minh Hieu <[EMAIL PROTECTED]>@VM.MARIST.EDU> on 08/03/2003 11:49:32 PM Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> Sent by:"ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> To:[EMAIL PROTECTED] cc: Subject:Problem between TSM and Autoloader I have problem in using TSM with Tape Autoloader TSM Device drivers only recognise tape drive. Can I use TSM&Tape Autoloader run with medium changer controlled by Windows native drivers and drive controlled by TSM Device drivers? My configuration: TSM5.1.5 for Windows, Windows2K SP3, IBM Tape Autoloader 360716X. Thanks
Re: Fw: NEW Magstar Drive ????
It is not yet officially announced. It ought to be based on the 1 TB prototype and compete with STK 9940B. Zlatko Krastev IT Consultant Fabrice HERISSE <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> 08.08.2003 12:04 Please respond to "ADSM: Dist Stor Manager" To: [EMAIL PROTECTED] cc: Subject:Fw: NEW Magstar Drive Hi All, Do you have informations about the new Magstar Drive called 3592 ?? thanks for your help
