Tivoli-Client: Debian (Ubuntu 5.10) Kernal 2.6
Hallo, we have an TSM-Client with OS Ubuntu 5.10. We need the installation packages (*.deb) for TSM-Clients Where can I found them or who can send me informations where can I get this packages Best regards for help. Christiane Kühn -- Institut für Informatik Christiane Kühn Tel.: 0228/73-4200 Römerstraße 164 Fax.: 0228/7360304 53117 Bonn Email: [EMAIL PROTECTED]
Re: Tivoli-Client: Debian (Ubuntu 5.10) Kernal 2.6
Hi, I think you can use alien to convert the rpms to dep packages. regards, Volker Am Freitag, den 17.03.2006, 10:04 +0100 schrieb Christiane Kühn: Hallo, we have an TSM-Client with OS Ubuntu 5.10. We need the installation packages (*.deb) for TSM-Clients Where can I found them or who can send me informations where can I get this packages Best regards for help. Christiane Kühn
SV: Exception_access_violation
Hi Richard, We found the problem. We upgrade the BA client to 5.2.4.7 then did the restore work fine accept the customer hasn't backup all data so we found some other issues. :( Thanks Christian -Ursprungligt meddelande- Från: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] För Richard Sims Skickat: den 16 mars 2006 13:50 Till: ADSM-L@VM.MARIST.EDU Ämne: Re: Exception_access_violation On Mar 16, 2006, at 7:31 AM, Christian Svensson wrote: Hi Everyone, I got funny problem. I using ITSM BA Client version 5.2.3.12 ... But if I try to restore C:\Lotus then does my DSM.EXE just quit without any comments. But if I try to restore any files under C:\WinNT\ then does my DSM.EXE crash and send out a dump. The only thing I can get out is Exception_access_violation but I can't find anything in the email archive about this issue that is relevant for me. So please does anyone got any ideas why this is happend? The fourth numerical position in your version number (12, in this case) suggests that you are using a provisional patch level of the software rather than a fully tested maintenance level. Unless you are using a patch level per TSM Support instructions, I would suggest going to a proper maintenance level instead. Beyond that, all the usual things: Check permissions for actually being able to perform the operation, look for error log indications of issues, check your Windows Event Log, etc. Richard Sims
Schedule Repeatation
Hi, I had a requirement to backup client data every 15mins. Is it possible? can anyone help how to to do so in ITSM 5.3 enviornment. Regards Pranav
Re: Tivoli-Client: Debian (Ubuntu 5.10) Kernal 2.6
On Friday 17 March 2006 10:07, Volker Maibaum wrote: Hi, I think you can use alien to convert the rpms to dep packages. You can also install rpm (apt-get install rpm) and install the rpm's with rpm -ihv --nodeps rpm file. Stef
Re: Schedule Repeatation
On Mar 17, 2006, at 5:38 AM, Pranav Parikh wrote: Hi, I had a requirement to backup client data every 15mins. Is it possible? can anyone help how to to do so in ITSM 5.3 enviornment. Given that client backups usually take substantially more than 15 minutes, that doesn't sound realistic with a classic backup product. Your site needs to better define exactly what it is trying to achieve. Your site may want a data protection product like Tivoli Continuous Data Protection for Files (see http://www.ibm.com/software/ tivoli/products/continuous-data-protection/). Richard Sims
Re: Schedule Repeatation
Thanks Richard, Requirement is to backup incremental data contineously every 15 to 20 mins. Regards Pranav Richard Sims [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU 03/17/2006 05:35 PM Please respond to ADSM: Dist Stor Manager To: ADSM-L@VM.MARIST.EDU cc: Subject:Re: [ADSM-L] Schedule Repeatation On Mar 17, 2006, at 5:38 AM, Pranav Parikh wrote: Hi, I had a requirement to backup client data every 15mins. Is it possible? can anyone help how to to do so in ITSM 5.3 enviornment. Given that client backups usually take substantially more than 15 minutes, that doesn't sound realistic with a classic backup product. Your site needs to better define exactly what it is trying to achieve. Your site may want a data protection product like Tivoli Continuous Data Protection for Files (see http://www.ibm.com/software/ tivoli/products/continuous-data-protection/). Richard Sims
3584 - to partition or not . . .
We are about ready to setup a 3584 library for the first time. The 3584 will be shared between 3 tsm instances (2 production instances and a library mgr instance) using tsm library sharing. At this time we do not need any logical libraries, but there are several projects coming that may make logical libraries desirable (hsm for Windows, getting rid Omniback by moving clients to TSM, some archiving applications). Given the possibility of using logical libraries in the future, does it make sense to partition the 3584 into a single logical library now, or, is it better to wait until the need arises? 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: 3584 - to partition or not . . .
On Fri, 17 Mar 2006, Richard Rhodes wrote: Given the possibility of using logical libraries in the future, does it make sense to partition the 3584 into a single logical library now, or, is it better to wait until the need arises? Repartitioning it is pretty quick, but the big problem is clients may not see the changes until they do whatever kind of reconfiguration is necessary. On Linux, we would typically reboot the attached servers after reconfiguring the library. --Jim
Re: restoring backup sets from one node to another
Hello, We are testing Backup Set restores for GW post offices. In 2 of 6 the restores user files were missing in a directory which are the users mailboxes. We did a point-in-time restore and got the files back. So, somehow the backupset, when created is missing files that exist in the incremental backups. Has anyone encountered this before? Thanks for any help! TSM 5.3.2.1 Novell TSM client 5.3.0.12 NW 6.5 SP2 Richard Sims wrote: Tim - Using -Virtualnodename is the standard way to restore data across clients. Try that. Have a look at the Unix client manual, which has better documentation on this point than the Novell one. Richard On Mar 14, 2006, at 9:19 AM, Timothy Hughes wrote: William, Thanks again, Tried it the command is, restore backupset monthlydocgrppoa.410125866 poa:swsp/ DOQCW2\poa:restore/ -subdir=yes That helps, but does not resolve the problem of restoring a backupset where the server from which the set was created no longer exists. Would this mean the client would have to rename and existing server? (not easy in Novell) according to the novell person or build a new server with the former server's name to do a backupset restore? William wrote: Yes you can. As Andy said, you must use the original node name. On 3/13/06, Timothy Hughes [EMAIL PROTECTED] wrote: Andrew, Thanks, Does this mean that we cannot restore a backupset to a different server? Andrew Raibeck wrote: The SET ACCESS and -FROMNODE options do not pertain to backup sets. You cannot use -FROMNODE to restore data from another node's backup sets. You must connect with the node name for which the backup set was created. Also, backup sets contain backup data only; they do not contain archive data. Regards, Andy Andy Raibeck IBM Software Group Tivoli Storage Manager Client Development Internal Notes e-mail: Andrew Raibeck/Tucson/[EMAIL PROTECTED] Internet e-mail: [EMAIL PROTECTED] IBM Tivoli Storage Manager support web page: http://www-306.ibm.com/software/sysmgmt/products/support/ IBMTivoliStorageManager.html The only dumb question is the one that goes unasked. The command line is your friend. Good enough is the enemy of excellence. ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU wrote on 2006-03-13 09:08:34: I am having problems restoring a backup set from one node to another. I set access archive * * on node DOQCRPS and tried to restore the same backupset to DOQCW2, but I get the error ANS1934E Backup set 'monthlydocqrppoi.410125866' not found. I checked the backupset name and it is still active and the name is correct. If I try a set access on DOQCRPS that specifies a path (e.g., set access archive poi:/* *) I always get ANS1083E No files have previously been archived for 'poi:/*' The command used that got ANS1934E on CW2 was: restore backupset monthlydoqcrppoi.410125866 poi:swsp/ poi:restore/ -subdir=yes This backupset was created on DOQCRPS and I issued set access archive * * on DOQCRPS before attempting the restore on CW2. But I'm not sure the command is working right because when I try to set access to a specified path, e.g. set access archive poi:/* * I get the other error ANS1083E. We should be able to restore a backupset created on one server to a different server correct? Is there something I am missing? P.S. - Is it just me or is information regarding backups extremely limited? Thanks for any help in advance! TSM 5.3.2.1 Novell client 5.3.0.12 Thanks
NetWare and Unicode/Macintosh files?
Hello all, I found FAQ 1225499 and APAR IC44954, both dealing with NetWare and Unicode/Macintosh file names not being backed up. We're running NW 6.0 SP5*, and we're going to move to NW 6.5 SP4 at least. Does anyone know if this problem has been worked around? I see the /useoldunicodeapi switch to TSA; is that the right solution? What are other people doing? --Jim * I am not the NetWare admin, and I have only the vaguest idea on how to check such things like a service pack level on NetWare.
Virtual Volume Copy Pool Reclamation....
Greetings, all. I'm trying to work out exactly how IBM thinks virtual volume reclamation is supposed to proceed, and also how we think it does in fact proceed. ;) Noodling around in the docs and QuickFacts, I find that volumes of a devclass of type SERVER may not be set to access=offsite, and experimentation confirms this. Such would lead me to the conclusion that SERVER devclass volumes would be reclaimed in a manner logically equivalent to local volumes, to wit a source virtual volume and a target virtual volume would both be mounted, the source read from and the target written to. This is also what Dave said in Oxford, and what I see happening on some of the servers. However, on one of them servers I observe reclamation proceeding in the 'offsite' manner, with a new virtual volume being built from (many!) mounts of primary volumes. I'm not sure how I can control this, but the difference is giving me the aggravations something fierce. I can see circumstances in which I might want to do things in either way, but optimizations in favor of one are a pain for the other. Any ideas? - Allen S. Rout
Re: New TSM Server, DB and STG POOL question
Prior to TSM 5 you could get away with just an inventory, but now it has become necessary to delete and redefine the paths, which will wipe out all your libvols. (TSM 4 didn't even have paths.) It is critical to do the two checkin libvol commands in the order in your list - scratch first, and then private - otherwise you will lose all your scratch tapes. TEST the checkin libvol step FIRST! I have been bitten badly, twice, by failures in the driver or the library itself preventing checkin libv from working. This has caused us long milti-day downtimes twice during the past year. This happened to us with a simple tape library upgrade, adding more slots to the same Quantum P7000 library. The danger you run is that with new versions of both Solaris and TSM, you are running different drivers, which could make library operations fail. Make sure this is going to work before you get into a situation where you can't back out. If things go wrong in this area you face a LONG downtime with a LOT of finger-pointing between IBM/Tivoli, Sun, and your tape library maker. They will each blame somebody else. It will get very ugly. Other than that, you are changing too many things at once for comfort. Last time I made a server change, I took great pains to insure that the TSM and AIX versions on the old and new servers were identical. At least this way, you can limit the scope of what went wrong. Roger Deschner University of Illinois at Chicago [EMAIL PROTECTED] Anything you try to fix will take longer and cost more than you thought. On Thu, 16 Mar 2006, Farren Minns wrote: TSM 5.1.6.2 on Solaris 2.7 - moving to 5.2.7.0 on Solaris 2.9 Hi all Regarding Anton's check list below, I have a couple of questions. 1) Do I really need to delete and redefine the drives,libray,paths etc? I understand that I will need to update the /dev/rmt/??? entry for the drives to make sure they reflect how the drives are viewed on the new system. But apart from that things should in my mind be exactly the same as before. As far as the library is concerned, it's just an alias in the ibmatl.conf file anyway and I know that works as I can use the mtlib command to interrogate it. Am I missing something? and... 2) Do I really need to run the 'checkin libv' commands. Looking at the newly restored system I can see that TSM knows all the vols in the TAPEPOOL and also the qlibv command shows me the volumes I also see on the still live server. Again, am I missing something? Many thanks again for this list Anton, much appreciated. All the best Farren Minns |-+---| | anton walde | | | [EMAIL PROTECTED] | | | Sent by: ADSM: Dist Stor | To| | Manager | ADSM-L@VM.MARIST.EDU | | ADSM-L@VM.MARIST.EDU| cc| | | | | 15/03/2006 15:44 |Subject| | | Re: [ADSM-L] New TSM | | Please respond to | Server, DB and STG| | ADSM: Dist Stor| POOL question | | Manager| | | ADSM-L@VM.MARIST.EDU | | | | | | | | | | | | | | |-+---| Hallo. We changed our Hardware a year ago. We asked support to help us and got a good hand-out with all the steps to make. Here is the 'cook book': 1. you must have the samt TSM-Version on the old and new server. 2. migrate all diskpools to tape 3. backup the TSM-DB on the old server maybe to a file-devclass ( better for restore ) 4. stop the old server 5. save all the config-files from the old server ( dsmserv.opt,dsmserv.dsk,devconfig.out,volhist.out,nodelock ) 6. connect the libraryies to the new server 7. install the tsm device driver on the new server all the following steps are on the new server 8. copy the config-files from step 5. to the new server, over the existing! 9. create log-files and db-files with dsmserv format 10. check the config-files! for example the devconfig.out for devclass,devices,pathes,etc. 11. restore the db from step 3. 12. change dsm.opt: nomigrrecl expinterval = disablescheds yes 13. start the tsm-server in foreground ( dsmserv ) 14. disable sessions 15. delete all paths, drives
scratch tape question
As a result of expiration, reclamation and removal of a large storage pool. We are getting back approximately 100 scratch tapes/week We run an SL8500 library with 1600 cells of which 600 are free. Is there any difference whether I check these scratch tapes in as they arrive or place them in an inventory outside the silo. Right now we have 250 scratch tapes in the silo and use approximately 15/night. 60 more are coming in today. I can see that placing them in an inventory will require an extra step to keep the tapes in some sort of order. But, is there any disadvantages to have so many scratch tapes available in the silo? AdThanksvance! Dave Zarnoch Nationwide Provident [EMAIL PROTECTED]
Library sharing
Hi Everybody, I'll be upgrading from TSM 5.1.6 to 5.2.6.4 this weekend. I will also up updating the tivoli.tsm.devices.aix5.rte fileset ( it was at aix43 because I upgraded from AIX 4.3.3 to 5.2 ML6 a few weeks ago and didn't update it ). From what I've read, updating this fileset will mess up all my tape definitions. If this is the case, do I have to pay any special attention to the library sharing between two instances I have on this server ? Rich
Re: New TSM Server, DB and STG POOL question
Hi there Thanks for that but I'm still confused. I have already installed 5.1.6.2 on the new server and restored the dB etc to make sure that the old and new servers are exactly the same. I then upgraded to 5.2.2 and then to 5.2.2.7 without any problems (this is all just a test as the original server is still in use). Now, when I look at the tapepool I see the exact volumes I am expecting to see. Also, when I use the mtlib commands from the command line (or qlibv from within TSM), to interrogate the library I see exactly what I did when connected to the old server. So from that I would assume that both TSM and the server can still see exactly what tape volumes are where just as they did on the old server. Also, the new definitions for the drives,path,lib etc are going to be exactly the same on the new server (as they are going to be connected to the same drives and lib as before), so what does deleting and redefining actually change? The only think that will be different is that the old drives were /dev/rmt/0stc and 1stc but will now be 2stc and 3stc which I will change. Sorry, I'm not doubting you here, I'm just trying to get my head around things as this is something new I hadn't considered. Many thanks Farren Minns |-+---| | Roger Deschner| | | [EMAIL PROTECTED] | | | Sent by: ADSM: Dist Stor | To| | Manager | ADSM-L@VM.MARIST.EDU | | ADSM-L@VM.MARIST.EDU| cc| | | | | 17/03/2006 16:01 |Subject| | | Re: [ADSM-L] New TSM | | Please respond to | Server, DB and STG| | ADSM: Dist Stor| POOL question | | Manager| | | ADSM-L@VM.MARIST.EDU | | | | | | | | | | | | | | |-+---| Prior to TSM 5 you could get away with just an inventory, but now it has become necessary to delete and redefine the paths, which will wipe out all your libvols. (TSM 4 didn't even have paths.) It is critical to do the two checkin libvol commands in the order in your list - scratch first, and then private - otherwise you will lose all your scratch tapes. TEST the checkin libvol step FIRST! I have been bitten badly, twice, by failures in the driver or the library itself preventing checkin libv from working. This has caused us long milti-day downtimes twice during the past year. This happened to us with a simple tape library upgrade, adding more slots to the same Quantum P7000 library. The danger you run is that with new versions of both Solaris and TSM, you are running different drivers, which could make library operations fail. Make sure this is going to work before you get into a situation where you can't back out. If things go wrong in this area you face a LONG downtime with a LOT of finger-pointing between IBM/Tivoli, Sun, and your tape library maker. They will each blame somebody else. It will get very ugly. Other than that, you are changing too many things at once for comfort. Last time I made a server change, I took great pains to insure that the TSM and AIX versions on the old and new servers were identical. At least this way, you can limit the scope of what went wrong. Roger Deschner University of Illinois at Chicago [EMAIL PROTECTED] Anything you try to fix will take longer and cost more than you thought. On Thu, 16 Mar 2006, Farren Minns wrote: TSM 5.1.6.2 on Solaris 2.7 - moving to 5.2.7.0 on Solaris 2.9 Hi all Regarding Anton's check list below, I have a couple of questions. 1) Do I really need to delete and redefine the drives,libray,paths etc? I understand that I will need to update the /dev/rmt/??? entry for the drives to make sure they reflect how the drives are viewed on the new system. But apart from that things should in my mind be exactly the same as before. As far as the library is concerned, it's just an alias in the ibmatl.conf file anyway and I know that works as I can use the mtlib command to interrogate it. Am I missing something? and... 2) Do I really need to run the 'checkin libv' commands. Looking at the newly restored system I can see that TSM knows all the vols in the TAPEPOOL and also the
Re: scratch tape question
On Fri, 17 Mar 2006 11:03:35 -0500, Dave Zarnoch [EMAIL PROTECTED] said: But, is there any disadvantages to have so many scratch tapes available in the silo? If you've got the slots to spare, fill 'em up. Keep enough free for unforseen events (maybe 10-20 slots?) but no reason to do more than that. - Allen S. Rout
Re: New TSM Server, DB and STG POOL question
Hi me again From the points on the list (below) is says to delete and redefine the lib,drives etc because of possible changed scsi-id's, but the library is referred to by it's alias in the ibmatl.conf file, and this alias will be the same on the new server. I know this works as I can use the mtlib command to speak to it. So I really can't see a reason to redefine, and thus I wont have to checkin the vols again. I may be missing something here of course. 15. delete all paths, drives and libraries 16. define all paths, libraries and drives again you must do step 15. and 16. because of possible changed scsi-id's 17. checkin libv library search=yes status=scratch checklabel=barcode 18. checkin libv library search=yes status=private checklabel=barcode Many thanks Farren |-+---| | Roger Deschner| | | [EMAIL PROTECTED] | | | Sent by: ADSM: Dist Stor | To| | Manager | ADSM-L@VM.MARIST.EDU | | ADSM-L@VM.MARIST.EDU| cc| | | | | 17/03/2006 16:01 |Subject| | | Re: [ADSM-L] New TSM | | Please respond to | Server, DB and STG| | ADSM: Dist Stor| POOL question | | Manager| | | ADSM-L@VM.MARIST.EDU | | | | | | | | | | | | | | |-+---| Prior to TSM 5 you could get away with just an inventory, but now it has become necessary to delete and redefine the paths, which will wipe out all your libvols. (TSM 4 didn't even have paths.) It is critical to do the two checkin libvol commands in the order in your list - scratch first, and then private - otherwise you will lose all your scratch tapes. TEST the checkin libvol step FIRST! I have been bitten badly, twice, by failures in the driver or the library itself preventing checkin libv from working. This has caused us long milti-day downtimes twice during the past year. This happened to us with a simple tape library upgrade, adding more slots to the same Quantum P7000 library. The danger you run is that with new versions of both Solaris and TSM, you are running different drivers, which could make library operations fail. Make sure this is going to work before you get into a situation where you can't back out. If things go wrong in this area you face a LONG downtime with a LOT of finger-pointing between IBM/Tivoli, Sun, and your tape library maker. They will each blame somebody else. It will get very ugly. Other than that, you are changing too many things at once for comfort. Last time I made a server change, I took great pains to insure that the TSM and AIX versions on the old and new servers were identical. At least this way, you can limit the scope of what went wrong. Roger Deschner University of Illinois at Chicago [EMAIL PROTECTED] Anything you try to fix will take longer and cost more than you thought. On Thu, 16 Mar 2006, Farren Minns wrote: TSM 5.1.6.2 on Solaris 2.7 - moving to 5.2.7.0 on Solaris 2.9 Hi all Regarding Anton's check list below, I have a couple of questions. 1) Do I really need to delete and redefine the drives,libray,paths etc? I understand that I will need to update the /dev/rmt/??? entry for the drives to make sure they reflect how the drives are viewed on the new system. But apart from that things should in my mind be exactly the same as before. As far as the library is concerned, it's just an alias in the ibmatl.conf file anyway and I know that works as I can use the mtlib command to interrogate it. Am I missing something? and... 2) Do I really need to run the 'checkin libv' commands. Looking at the newly restored system I can see that TSM knows all the vols in the TAPEPOOL and also the qlibv command shows me the volumes I also see on the still live server. Again, am I missing something? Many thanks again for this list Anton, much appreciated. All the best Farren Minns |-+---| | anton walde | | | [EMAIL PROTECTED] | | | Sent by: ADSM: Dist Stor | To| | Manager | ADSM-L@VM.MARIST.EDU | | ADSM-L@VM.MARIST.EDU | cc| |
Re: TSM 5.3 Inst. on MSCS
Hi Pranav! There are two excellent resources available to help you with this. IBM has two redbooks that cover the process pretty well. Go to the IBM website and in the redbooks section do a search for the following: SG24-6844-01 SG24-6761-00 The first SG number is for Disaster Recovery Strategies with Tivoli Storage Management. The second SG number is for Deployment Guide for IBM Tivoli Storage Manager V5.3. I hope this information helps! Jim Neal -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Pranav Parikh Sent: Thursday, March 16, 2006 8:08 PM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] TSM 5.3 Inst. on MSCS Hi, Can any one help me to install TSM5.3 in MSCS cluster enviornment. We have two IBM xseries servers with each having 3584 Library and shared storage. Where can I found resources for this? Regards Pranav
Re: Schedule Repeatation
Hi Pranav! If you really need to back up a client(s) that often with Tivoli, the way to do it is to create three separate schedules that run every hour and run 20 minutes apart. Then assign the client to all three schedules. For example: Start time Runs Schedule 1 09:00Hourly Schedule 2 09:20Hourly Schedule 3 09:40Hourly Please let me know if you need any additional info. Jim Neal -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Pranav Parikh Sent: Friday, March 17, 2006 4:10 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Schedule Repeatation Thanks Richard, Requirement is to backup incremental data contineously every 15 to 20 mins. Regards Pranav Richard Sims [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU 03/17/2006 05:35 PM Please respond to ADSM: Dist Stor Manager To: ADSM-L@VM.MARIST.EDU cc: Subject:Re: [ADSM-L] Schedule Repeatation On Mar 17, 2006, at 5:38 AM, Pranav Parikh wrote: Hi, I had a requirement to backup client data every 15mins. Is it possible? can anyone help how to to do so in ITSM 5.3 enviornment. Given that client backups usually take substantially more than 15 minutes, that doesn't sound realistic with a classic backup product. Your site needs to better define exactly what it is trying to achieve. Your site may want a data protection product like Tivoli Continuous Data Protection for Files (see http://www.ibm.com/software/ tivoli/products/continuous-data-protection/). Richard Sims
Re: scratch tape question
Hi Dave, Actually, I can only see advantages to checking the tapes in as they arrive: 1) The tapes are less likely to be lost or suffer environmental damage 2) At the rate you are using tapes, you won't have to check in any new tapes for quite a while. 3) You won't have to worry about the tapes taking up too much space outside of the silo or getting in the way. Others people may be able to think of something I haven't, but that's my 2 cents. I hope it helps. Jim Neal -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Dave Zarnoch Sent: Friday, March 17, 2006 8:04 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] scratch tape question As a result of expiration, reclamation and removal of a large storage pool. We are getting back approximately 100 scratch tapes/week We run an SL8500 library with 1600 cells of which 600 are free. Is there any difference whether I check these scratch tapes in as they arrive or place them in an inventory outside the silo. Right now we have 250 scratch tapes in the silo and use approximately 15/night. 60 more are coming in today. I can see that placing them in an inventory will require an extra step to keep the tapes in some sort of order. But, is there any disadvantages to have so many scratch tapes available in the silo? AdThanksvance! Dave Zarnoch Nationwide Provident [EMAIL PROTECTED]
Re: Library sharing
Hi Richard! Other than having to redefine the tape paths on each instance, as long as the databases are up to date for each instance, there shouldn't be any problems. I'm sure that you already know to make backups of all the recovery files just prior to doing the upgrade just in case. : ) Jim Neal -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Richard Mochnaczewski Sent: Friday, March 17, 2006 8:09 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Library sharing Hi Everybody, I'll be upgrading from TSM 5.1.6 to 5.2.6.4 this weekend. I will also up updating the tivoli.tsm.devices.aix5.rte fileset ( it was at aix43 because I upgraded from AIX 4.3.3 to 5.2 ML6 a few weeks ago and didn't update it ). From what I've read, updating this fileset will mess up all my tape definitions. If this is the case, do I have to pay any special attention to the library sharing between two instances I have on this server ? Rich
Re: backup performance
Looks to me based on the calculations if it goes over a little more than 2 hours acceptable. What's acceptable to me might not be acceptable to others. 225 GB per hour, or 62.5 MB/s LTO2 drives can writes 70 ~75 MB/s It's difficult to PD without seeing the whole environment where the bottle neck is, but one area I would check woud be how LTO drives are assigned to HBA card(s) on TSM server. If you have fibre LTO drives, I would check how HBAs are assigned to LTO drives. For example, If you have 1 HBA assigned to LTO drive 1 and 2 another HBA assigned to LTO drive 3,4 When backup occurs, if tapes are mounted from each HBA: drive1 and drive 3, would have a greater performance than say you were to use drive1 and drive 2. Sung Y. Lee ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU wrote on 03/16/2006 06:46:40 AM: Hi, we use oracle TDP with LTO 2 dirvers for Rman database backup. Normally, the backup for database (450G) take 2h with 2 channels. but some time (intermittent) the backup take more than 2h30. the problem is that in this case only on channel work fine but the other is very slow, so when we do recovery test , the multiplexing not work. any idea please ? Thanks
Re: 3584 - to partition or not . . .
This sounds like a design question. Based on what you described, if you currently have free cycles and eventually you will do it later on, if you do the work now, you have less work later on. So that makes sense to me. When you do partition the library, you also have to assign tape drive(s) and allocate # of slots. These resources won't be in use(idle) . Since projection of data usage and need can change over night, I would wait until the need arises. Sung Y. Lee ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU wrote on 03/17/2006 07:18:08 AM: We are about ready to setup a 3584 library for the first time. The 3584 will be shared between 3 tsm instances (2 production instances and a library mgr instance) using tsm library sharing. At this time we do not need any logical libraries, but there are several projects coming that may make logical libraries desirable (hsm for Windows, getting rid Omniback by moving clients to TSM, some archiving applications). Given the possibility of using logical libraries in the future, does it make sense to partition the 3584 into a single logical library now, or, is it better to wait until the need arises? 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: scratch tape question
If you have a space floor and an ideal location to safely store scratch tapes coming back my preference would be to put them there, then check in scratch tapes as needed. Disadvantages: This does not happen frequently but sometimes when a tape drive goes bad, it would mount the tape and mark it unavailable every scratch tapes until runs out. Let's say there is a fire before you could offsite drm for that day. Ejecting or getting out 600 less tapes sound good to me. Sung Y. Lee ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU wrote on 03/17/2006 11:03:35 AM: As a result of expiration, reclamation and removal of a large storage pool. We are getting back approximately 100 scratch tapes/week We run an SL8500 library with 1600 cells of which 600 are free. Is there any difference whether I check these scratch tapes in as they arrive or place them in an inventory outside the silo. Right now we have 250 scratch tapes in the silo and use approximately 15/night. 60 more are coming in today. I can see that placing them in an inventory will require an extra step to keep the tapes in some sort of order. But, is there any disadvantages to have so many scratch tapes available in the silo? AdThanksvance! Dave Zarnoch Nationwide Provident [EMAIL PROTECTED]
Re: Reclimation Error
When reclaiming our offsite tapes I receive the folloing error for only one of our copypools. The other two copypools have no problems reclaiming. I am thinking there are some files that have vanished that it is looking for. Maybe some files that did not get migrated to tape. 03/17/2006 11:40:49 ANRD ssalloc.c(775): ThreadId19 Space already preallocated. Callchain of previous message: 0x087c8cc3 outDiagf+0x203 - 0x0873e6ea ssAlloc+0xaa - 0x0825db82 AfAllocSpace+0xb2 - 0x0825c81f AfCopy+0xef - 0x0827f2e9 BfCopy+0x1c9 - 0x08233e76 DfTransferBitFile+0xec6 - 0x08216f57 BfTransferBitFile+0x2b7 - 0x082713ab HandleOffsiteFile+0x11b - 0x08269357 AfMoveOffsiteQueueThread+0x467 - 0x0809dccf StartThread+0x8f - 0x003b7341 *UNKNOWN* - 0x002496fe *UNKNOWN* - Thanks! Aaron
Re: Backups of Intel-based Macs
I am waiting to get my hands on some of those beauties! I am excited to see how TSM works and how it handles everything. The new Intel Macs seem pretty impressive, and I know that we will not be dissapointed. [EMAIL PROTECTED] 03/15 4:05 am Our initial attempts at trying 5.3.2.1 on the Intel Macs were good, but we then ran into some problems. As there is no support from IBM, I am nervous about relying on it. At 08:38 PM 3/14/2006, you wrote: On Mar 14, 2006, at 4:44 PM, Paul Zarnowski wrote: Intel Macs are starting to show up on our campus and we are being asked how to back them up. What are other TSM sites doing to backup these new beasties? TSM doesn't support Intel-based Macs yet. Hi, Paul - Good question... I recently got one of the new iMac's as a media storage and feeder for my family room (connecting it to my A/V receiver via optical audio and S-video). Wonderful machine. Reading your posting, and Aaron's response about depending upon Rosetta, I decided to try installing a TSM client (5.2.4). An awkwardness is that the download file is in .hqx format: PowerPC Macs are shipped with Stuffit Expander to handle that stuff, but the new Macs are Intel, so it appears that Apple feels it inappropriate to ship a non-PowerPC binary. I got SE off the net and installed it, and it worked fine to generate the TSM installer, which I then ran to install the TSM client. And the client itself ran fine, as I tried some basic Archive and Backup operations. Apple's Rosetta is excellent, as was promised. I would suggest having one of your eager adopters go ahead and give an existing TSM client level a full workout, with a new nodename. Have them report back on general functionality and speed. Richard Sims long time Mac guy (why settle for mediocrity?) -- Paul ZarnowskiPh: 607-255-4757 Manager, Storage Systems Fx: 607-255-8521 719 Rhodes Hall, Ithaca, NY 14853-3801Em: [EMAIL PROTECTED]
Re: restoring backup sets from one node to another
Hi, Yes we TSM 5.3.2.1 on W2K3Sp1 Novell client 5.3.2.0 NW 6.5 SP2 Had exactly the same problem and hoped downgrade to 5.3.0.12 would help Suppose we will have to log a call We are using on tsafs /enablegw=true which usually gives us 100% quality on GW backup. Kind Regards Marco Malgarini Malga Consulting Mob.: 0409 918 027 Mail: [EMAIL PROTECTED] www: www.malgarini.org -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Timothy Hughes Sent: Saturday, 18 March 2006 00:56 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] restoring backup sets from one node to another Hello, We are testing Backup Set restores for GW post offices. In 2 of 6 the restores user files were missing in a directory which are the users mailboxes. We did a point-in-time restore and got the files back. So, somehow the backupset, when created is missing files that exist in the incremental backups. Has anyone encountered this before? Thanks for any help! TSM 5.3.2.1 Novell TSM client 5.3.0.12 NW 6.5 SP2 Richard Sims wrote: Tim - Using -Virtualnodename is the standard way to restore data across clients. Try that. Have a look at the Unix client manual, which has better documentation on this point than the Novell one. Richard On Mar 14, 2006, at 9:19 AM, Timothy Hughes wrote: William, Thanks again, Tried it the command is, restore backupset monthlydocgrppoa.410125866 poa:swsp/ DOQCW2\poa:restore/ -subdir=yes That helps, but does not resolve the problem of restoring a backupset where the server from which the set was created no longer exists. Would this mean the client would have to rename and existing server? (not easy in Novell) according to the novell person or build a new server with the former server's name to do a backupset restore? William wrote: Yes you can. As Andy said, you must use the original node name. On 3/13/06, Timothy Hughes [EMAIL PROTECTED] wrote: Andrew, Thanks, Does this mean that we cannot restore a backupset to a different server? Andrew Raibeck wrote: The SET ACCESS and -FROMNODE options do not pertain to backup sets. You cannot use -FROMNODE to restore data from another node's backup sets. You must connect with the node name for which the backup set was created. Also, backup sets contain backup data only; they do not contain archive data. Regards, Andy Andy Raibeck IBM Software Group Tivoli Storage Manager Client Development Internal Notes e-mail: Andrew Raibeck/Tucson/[EMAIL PROTECTED] Internet e-mail: [EMAIL PROTECTED] IBM Tivoli Storage Manager support web page: http://www-306.ibm.com/software/sysmgmt/products/support/ IBMTivoliStorageManager.html The only dumb question is the one that goes unasked. The command line is your friend. Good enough is the enemy of excellence. ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU wrote on 2006-03-13 09:08:34: I am having problems restoring a backup set from one node to another. I set access archive * * on node DOQCRPS and tried to restore the same backupset to DOQCW2, but I get the error ANS1934E Backup set 'monthlydocqrppoi.410125866' not found. I checked the backupset name and it is still active and the name is correct. If I try a set access on DOQCRPS that specifies a path (e.g., set access archive poi:/* *) I always get ANS1083E No files have previously been archived for 'poi:/*' The command used that got ANS1934E on CW2 was: restore backupset monthlydoqcrppoi.410125866 poi:swsp/ poi:restore/ -subdir=yes This backupset was created on DOQCRPS and I issued set access archive * * on DOQCRPS before attempting the restore on CW2. But I'm not sure the command is working right because when I try to set access to a specified path, e.g. set access archive poi:/* * I get the other error ANS1083E. We should be able to restore a backupset created on one server to a different server correct? Is there something I am missing? P.S. - Is it just me or is information regarding backups extremely limited? Thanks for any help in advance! TSM 5.3.2.1 Novell client 5.3.0.12 Thanks
