We are running three TSM 6.2 server instances on one AIX machine, without LPAR, HACMP, or VM. One of them is Library Manager for the other two.
It works great if you are very careful with directory and file names, and Unix permissions, so as to keep everything separate. Run each instance as non-root, which mostly keeps them from walking on each other. Map out your directory and file naming conventions in advance of installing ANY of them, using the worksheets in the manuals as a starting point. The large amount of time I spent in this basic planning stage has been very worthwhile. Just follow the instructions in "Installation Guide" and it works. The manuals and installation procedures were mostly written with multple instances in mind, so this works much better than it did on TSM 5. The only change I made there, is that the manual suggests making the Instance Directory to be /home/tsminst1/tsminst1. However I have found it is much easier to keep track of it all by naming them /home/tsminst1/instancedir or /home/tsminst2/instancedir ... Everything else (database, logs, etc...) is stored under /var/tsminst1/ or /var/tsminst2/... However, DISK and FILE storage pools are generic, because sometimes I move them from one server to another as load dictates. (Changing Unix ownership when I do move them.) Our Client Nodes all expect to connect via Port 1500, and with hundreds of nodes, we cannot get them to change without me spending a year going office to office, which cannot work because I'd need to change them all in one day. Therefore we use xinetd to forward port 1500 to other port numbers. This requires one NIC per instance, which is better for performance reasons anyway. Your biggest pitfall will be Unix permissions. It works if you are careful and get it right. Make each instance ID the owner of everything it actually owns. Set the Unix Group to be "tsmsrvrs" everywhere, but be careful not to give one instance write access to another instance's things by setting group-write. Let the Library Manager keep each instance's tapes separate. DO NOT let permissions issues tempt you to run any instance as root! That is an invitation to disaster. What this does is that in the future we can combine multiple TSM servers onto fewer machines, or split them apart to separate machines, with minimum disruption. All this without the overhead of virtual machines. P.S. After trying for months to migrate nodes from an old V5 server to a new V6 server, we gave up, and simply upgraded the V5 server using the upgrade procedure. (We used the New System, Network method.) Moving nodes individually turned out to be worse than herding cats. (I'm dealing with college faculty!) A V5 to V6 upgrade is a couple of days of downtime and very hard work, but then you're done. This decision to upgrade instead of moving nodes, is why we now have multiple instances. Roger Deschner University of Illinois at Chicago [email protected] ======I have not lost my mind -- it is backed up on tape somewhere.===== On Mon, 13 Jan 2014, Meunier, Yann wrote: >Hi, > >I'm in this configuration ! :) >I've 4 TSM 6.4 instances on 2 AIX servers in HACMP. >We went in production last month, so I did'nt have any feedback. >We begin the migration of our nodes this week and we have more than 2000 nodes >to do! > >For the moment we haven't : >- VTL >- Active pool >- dedup >- Replication > >We hope to term implement replication. > >Best regards, > >Yann > >-----Message d'origine----- >De : ADSM: Dist Stor Manager [mailto:[email protected]] De la part de >Dwight Cook >Envoyé : vendredi 10 janvier 2014 21:00 >à : [email protected] >Objet : [ADSM-L] Who might be running multiple V6 TSM instances on the same >LPAR/system??? > >Would greatly appreciate any input/feedback on what to look out for, tips, >hints, etc. in an AIX environment. >Ce message et toutes les pièces jointes (ci-après le « message ») sont >confidentiels et établis à lâintention exclusive de ses destinataires. >Toute utilisation de ce message non conforme à sa destination, toute >diffusion ou toute publication, totale ou partielle, est interdite, sauf >autorisation expresse. Si vous recevez ce message par erreur, merci de le >détruire sans en conserver de copie et dâen avertir immédiatement >lâexpéditeur. Internet ne permettant pas de garantir lâintégrité de ce >message, la Caisse des Dépôts et Consignations décline toute >responsabilité au titre de ce message sâil a été modifié, altéré, >déformé ou falsifié. Par ailleurs et malgré toutes les précautions prises >pour éviter la présence de virus dans nos envois, nous vous recommandons de >prendre, de votre côté, les mesures permettant d'assurer la non-introduction >de virus dans votre système informatique. > >This email message and any attachments (âthe emailâ) are confidential and >intended only for the recipient(s) indicated. If you are not an intented >recipient, please be advised that any use, dissemination, forwarding or >copying of this email whatsoever is prohibited without Caisse des Depots et >Consignations's prior written consent. If you have received this email in >error, please delete it without saving a copy and notify the sender >immediately. Internet emails are not necessarily secured, and declines >responsibility for any changes that may have been made to this email after it >was sent. While we take all reasonable precautions to ensure that viruses are >not transmitted via emails, we recommend that you take your own measures to >prevent viruses from entering your computer system. > >
