Re: Archiving
HEllo, we do archive our diatheque (more than 3'000 dias with a size of 30 MB, total 90 GB) on Magstar in an IBM 3494 library. The backup copy group for the specific managment class is defined as " 1 1 0 NOLIMIT". Regards, Ren Lambelet Nestec S.A. / Informatique du Centre 55, av. Nestl CH-1800 Vevey (Switzerland) *+41'21'924'35'43 7+41'21'924'28'88 * K4-117 email [EMAIL PROTECTED] Visit our site: http://www.nestle.com This message is intended only for the use of the addressee and may contain information that is privileged and confidential. -Original Message- From: Christoph Pilgram [SMTP:[EMAIL PROTECTED]] Sent: Tuesday, January 16, 2001 9:00 AM To: [EMAIL PROTECTED] Subject: Archiving Hy everyone, we are discussing the possibilities of archiving data with TSM or other products (from NT,UNIX). Our requirements are to archive data for about 30 years. TSM is in discussion because we use it already for backup ( and in some cases we use the archive-command ). The policy domains for the clients for archiving will be (from my point of view) totally different to those for backup. Can anybody share his good (or bad) experience in long term archiving with whatever kind of library in the background (DVD or tape). Thanks a lot Christoph
Re: tcpwindowsize
Hi Ruud, in ADSM V3 tcpwindowsize must be indicated in KB boundary. I don't know if this is still valid ... Best regards Valeriano Bassi [EMAIL PROTECTED] "Van Ruler, Ruud R SSI-ISES-32" [EMAIL PROTECTED] on 15/01/2001 17.09.12 Please respond to "ADSM: Dist Stor Manager" [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc:(bcc: Valeriano Bassi/SSB) Subject: tcpwindowsize Lg In TSM reference the following is stated: "To improve backup performance, increase the TCPWINDOWSIZE on the server." We have installed TSM4.1 Level0.0 on a S/390 Server. But during startup we get the following messages: ANR0902W Unsupported keyword found in file dsmserv.opt. ANR0906I Line No. : 143 ANR0907I Statement : tcpwindowsize 2048 ANR0908W Error : .|.. Is this a valid parameter for S/390 ??? same applies to TCPNODELAY !! Ruud van Ruler, Shell Services International BV - ISES/32 Our Data Storage Management home page: http://sww2.shell.com/os390/ Room 0C/G06 Dokter van Zeelandstraat 1, 2285 BD Leidschendam NL Tel : +31 (0)70 - 3034644, Fax 4011, Mobile +31 (0)6-55127646 Email Internet: [EMAIL PROTECTED] [EMAIL PROTECTED] R.vanRuler
TSM 3.7.4 Netscape AIX 4.3.3
Hi I had a problem with TSM 3.7.4 and the Netscape Browser. I did a upgrade from TSM3.7.2 to 3.7.4 because I had to attach a IBM ULTRIUM Tape library to this TSM System. After the update from TSM I do dsmserv upgrade db Then I defined the library the drives and the deviceclass with the define command at the commandline. Because it was not possible to define the deviceclass with the Netscape. Now the problem: Some entries like Automated Drives or Automated Libraries are doubled at the Netscape. I do dsmserv runfile dsmserv.idl but no change. Has anyone an idea how I can fix this problem. At the TIVOLI website I didn`nt find anything to solve the problem. Thanks for Help Felix
Sybase backup procedure options?
Can anyone provide me the options for backing up Sybase. Any comments will be greatly appreciated.
Re: Sybase backup procedure options?
Jacques, You can use SQL Backtrack for Sybase. Give me a call and we can discuss it. Regards Gerrit Jacques Butcher wrote: Can anyone provide me the options for backing up Sybase. Any comments will be greatly appreciated.
Re: Archiving
Our requirements are to archive data for about 30 years. TSM is in discussion because we use it already for backup... That kind of situation is very problematic, in all respects. You will basically have to commit to freezing the hardware and software technology upon which the backup is based, and the environment in which it runs, in order to expect to retrieve the data that far in the future. Consider, for example, how many of us still have 7-track, open-reel tape drives and the operating system and driver cards ready to retrieve data from such tapes. I have never seen a software vendor commit to maintaining software such that it will be able to viably handle data written decades earlier. Keep in mind also that products such as TSM write the data in proprietary, unpublished form, which prevents retrieval by other means. Richard Sims, BU
Re: Archiving
Archival, from a user's point of view, is quite easy with TSM. Archival, from a technical point of view, is complicated when you start talking long term retention. REALLY long term retention like 30 years. Two things come to mind... First: Media life. How long will any tape cartridge remain in good condition? Second: Media hardware reader: Will you still have the hardware mechanism, 'DRIVE", to access the media thirty years from now? For the first issue, be sure to copy the archival. In TSM this is simply done by copying the storage pool. For the second issue, TSM provides capabilities to move/migrate data from one storage pool to the other as new storage technology becomes prevalent. If, however, you find that your storage technology does not change, it will be prudent to recycle or reclaim any archived data to ensure it can still be read and regenerated. Or, am I paranoid about losing bits and bytes on my magnetic media over a long period of time? John G. Talafous IS Technical Principal The Timken CompanyGlobal Software Support P.O. Box 6927 Data Management 1835 Dueber Ave. S.W. Phone: (330)-471-3390 Canton, Ohio USA 44706-0927 Fax : (330)-471-4034 [EMAIL PROTECTED] http://www.timken.com
Re: TSM 4.1 and Informix Data Protection on HPUX (Work Around)
Check the archives on this discussion list at http://search.adsm.org/ . I too have stumbled into this with my pack of angry DBA's. The feedback I received was very confused. From a number of sources. Putting it all together we get that TSM is working on TDP for INTEL, scheduled 1Q2001. This will be GA by July, 2001. However TDP for Intel is NOT TDP for Informix on HP-UX. TDP for Informix on HP-UX requires HP's PA-RISC processor, not Intel. Again, Please note that the response is "for Intel". We run Informix on HP's PA-RISC processors running HP-UX 11.0. I periodically rattle TSM's support people about this. But, alas, no solution in sight. John G. Talafous IS Technical Principal The Timken CompanyGlobal Software Support P.O. Box 6927 Data Management 1835 Dueber Ave. S.W. Phone: (330)-471-3390 Canton, Ohio USA 44706-0927 Fax : (330)-471-4034 [EMAIL PROTECTED] http://www.timken.com
ANS5127W NT 4.1.2
Has anyone ever seen the error code ANS5127W File Excluded? I am trying to use the new 4.1.2 client for NT and explicitly include a statement to backup the adsm.sys directory [ include "*:\adsm.sys\...\*" ] This is apparently unsuccessful, as I do notice the files are marked with a red x in the GUI. I thought this was the desired procedure to do full backup/restores with this new client. Thanks for any help! Derron Judd WSRC Corp
SMS Scripting for NT installation
Hi everyone! Has anyone been able to get around the html pop up window when scripting the installation for Windows NT? Also, the number of re-boots required? I have someone in our NT group doing the scripting for me and he is having trouble with these areas. If you have ideas or even a sample script that you would be willing to share, I would really appreciate it. Do you know what the switches mean that are for installation? /v and /qn Thanks, Brenda Collins, Storage Management Phone: 651-848-5808 Email: [EMAIL PROTECTED] Disclaimer: "The views, opinions and judgements expressed in this message are solely those of the author. The message contents have not been reviewed or approved by West Group."
Re: Backup Exec
The answer is yes. You need to define a storage pool for the BE on the TSM server. See the module for this on the Veritas site. Mike -Original Message- From: Jacques Butcher [SMTP:[EMAIL PROTECTED]] Sent: 16 2001 8:34 To: [EMAIL PROTECTED] Subject: Backup Exec Can Backup Exec be setup in such a way that it sends data off to TSM without having a storage device locally attached to the server it's running on? I.e. TSM handles the backup device (library) as well as manage all the volumes. Any comments will be greatly appreciated Jacques Butcher.
DB2 Backups
Hi everyone, When you are backing up DB2, do the logs get picked up with the database backup or are you catching them with filesystem backups? I have the retention set for the logs to be the same as the backup, thinking that retention was being taken care of through db2adutl by the DBA's. I am told now that they only take care of the actual database with their scripts and not the logs. How is anyone else handling these? Also, due to their running all the backups through scripts, I do not see the failed or missed events. Is there a way to capture this information so I know exactly what has been run? Thank you, Brenda Collins, Storage Solutions Group Phone: 651-848-5808 Email: [EMAIL PROTECTED] Disclaimer: "The views, opinions and judgements expressed in this message are solely those of the author. The message contents have not been reviewed or approved by West Group."
Windows 2000 Restore
Hi everyone! I am sorry to be such a pain today. As you can probably tell, I am going in many directions at once and trying to keep up with it all. I do really appreciate any help I get from you because this listserv is a very good tool. For Windows 2000, we were testing the process of doing a re-directed restore to recover a system to test whether we could re-name the server and then disconnect the original from the network and replace it with the recovered system. Obviously, we have determined that we can not do a re-directed restore with the system state objects without re-naming the server first. What we ended up doing was: 1. Re-naming the server we were restoring to. 2. Restored System State/Registry. 3. Restored all the drives 4. Restored System State/Registry a second time. Was step 2 really necessary? We didn't want to take chances so we did. The only problem with the whole process is that you would have to have the original server disconnected from the network throughout the process. If we could have done a re-directed restore of the System State/Registry, we could have completed the whole process and only disconnected the original from the network at the point we were ready to re-boot. Brenda Collins, Storage Solutions Group Phone: 651-848-5808 Email: [EMAIL PROTECTED] Disclaimer: "The views, opinions and judgements expressed in this message are solely those of the author. The message contents have not been reviewed or approved by West Group."
APAR IC28571 : NT EVENT VIEW REPORTS PERFLIB ERRORS AGAINST DSM CPERF.DLL - TSM 4.1.1
Hello TSMers, I have scoured the TSM Knowledge Base at http://www.tivoli.com/asktivoli on the subject error and found the APAR. However the work around does not work for us. First, the local fix using the unlodctr doesn't work because it is not called "TSM Client Performance", but "ADSM Client Performance". Then, the "lodctr perfctr.ini" command doesn't work because TSM Client Performance is hard-coded into the perfctr.ini file when it needs to say ADSM Client Performance. However, even when you make these modifications, it still does not get rid of the error messages. As for the changes to the registry, the registry key they mention doesn't exist. Any other options? John G. Talafous IS Technical Principal The Timken CompanyGlobal Software Support P.O. Box 6927 Data Management 1835 Dueber Ave. S.W. Phone: (330)-471-3390 Canton, Ohio USA 44706-0927 Fax : (330)-471-4034 [EMAIL PROTECTED] http://www.timken.com
Re: SMS Scripting for NT installation
The new windows installer service that goes in with the new client is responsible for at least one of the reboots. Someone one the list said awhile back that if IE5.5 exists on the client already then a reeboot will not be necessary. I tried this one one client and it worked without a reeboot. We also tried putting the new MDAC(MS Data Access Components) this added the windows installer service but in some cases it still required a reeboot. All in all its not very consistent behavior. All NT boxen are at sp5 at least (very few at 6a) and all were upgrades from ADSM client 3.1.7. I blame the new MS code that is introduced in the new clients probably put there for w2k support. As far as scripting an install there is a lengthy one line command that interfaces with the new MS installer service that can be used to install the client in the background with no intervention (silent install) On every machine I've used the command on it caused a Dr Watson. The install finishes anyway and the client seems to operate just fine but I am not about to release that out to the NT admins. I am sure they will have a cow over that. So I just wrote up some docs to walk them thru the install. So far there have been no problems. You may be able to get around the pop up by directly running the setup.exe instead of the .msi file. Jack -Original Message- From: Collins, Brenda [mailto:[EMAIL PROTECTED]] Sent: Tuesday, January 16, 2001 8:25 AM To: [EMAIL PROTECTED] Subject: SMS Scripting for NT installation Hi everyone! Has anyone been able to get around the html pop up window when scripting the installation for Windows NT? Also, the number of re-boots required? I have someone in our NT group doing the scripting for me and he is having trouble with these areas. If you have ideas or even a sample script that you would be willing to share, I would really appreciate it. Do you know what the switches mean that are for installation? /v and /qn Thanks, Brenda Collins, Storage Management Phone: 651-848-5808 Email: [EMAIL PROTECTED] Disclaimer: "The views, opinions and judgements expressed in this message are solely those of the author. The message contents have not been reviewed or approved by West Group."
Re: DB2 Backups
The logs are not picked up by the backup. The method of handling the logs, is to compile C language the user exit program provided by DB2 to archive (not backup) the log files. "Collins, Brenda" wrote: Hi everyone, When you are backing up DB2, do the logs get picked up with the database backup or are you catching them with filesystem backups? I have the retention set for the logs to be the same as the backup, thinking that retention was being taken care of through db2adutl by the DBA's. I am told now that they only take care of the actual database with their scripts and not the logs. How is anyone else handling these? Also, due to their running all the backups through scripts, I do not see the failed or missed events. Is there a way to capture this information so I know exactly what has been run? Thank you, Brenda Collins, Storage Solutions Group Phone: 651-848-5808 Email: [EMAIL PROTECTED] Disclaimer: "The views, opinions and judgements expressed in this message are solely those of the author. The message contents have not been reviewed or approved by West Group."
Re: Sybase backup procedure options?
There is a great product called SQL-Backtrack for Sybase from BMC Software http://www.bmc.com. You'll also need the TSM OBSI module. -- Shawn Raymond Sr. Technical Consultant Synergy, INC. 518-782-3457 Jacques Butcher To: [EMAIL PROTECTED] jacques@MAXTcc: EC.CO.ZASubject: Sybase backup procedure options? Sent by: "ADSM: Dist Stor Manager" [EMAIL PROTECTED] RIST.EDU 01/16/01 05:34 AM Please respond to "ADSM: Dist Stor Manager" Can anyone provide me the options for backing up Sybase. Any comments will be greatly appreciated.
Re: tcpwindowsize
Hi, From memory, I do not think that TCPWINDOWSIZE can be specified for an OS390 server, This sort of parameter is handled elsewher in the OS390 system. TCPNODELAY is a client option "Van Ruler, Ruud R SSI-ISES-32" [EMAIL PROTECTED] on 01/15/2001 04:09:12 PM Please respond to "ADSM: Dist Stor Manager" [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc:(bcc: John Naylor/HAV/SSE) Subject: tcpwindowsize Lg In TSM reference the following is stated: "To improve backup performance, increase the TCPWINDOWSIZE on the server." We have installed TSM4.1 Level0.0 on a S/390 Server. But during startup we get the following messages: ANR0902W Unsupported keyword found in file dsmserv.opt. ANR0906I Line No. : 143 ANR0907I Statement : tcpwindowsize 2048 ANR0908W Error : .|.. Is this a valid parameter for S/390 ??? same applies to TCPNODELAY !! Ruud van Ruler, Shell Services International BV - ISES/32 Our Data Storage Management home page: http://sww2.shell.com/os390/ Room 0C/G06 Dokter van Zeelandstraat 1, 2285 BD Leidschendam NL Tel : +31 (0)70 - 3034644, Fax 4011, Mobile +31 (0)6-55127646 Email Internet: [EMAIL PROTECTED] [EMAIL PROTECTED] R.vanRuler ** The information in this E-Mail is confidential and may be legally privileged. It may not represent the views of Scottish and Southern Energy plc. It is intended solely for the addressees. Access to this E-Mail by anyone else is unauthorised. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful. Any unauthorised recipient should advise the sender immediately of the error in transmission. Scottish Hydro-Electric and Southern Electric are trading names of Scottish and Southern Energy Group. **
Re: SMS Scripting for NT installation
The Autorun you can be stopped by changing a value in the registry namely: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Cdromvariable Autorun which must be set to 0 This is for all future CD's not only for TSM Hope this is usefull, Michel "Collins, Brenda" [EMAIL PROTECTED] on 01/16/2001 02:25:29 PM Please respond to "ADSM: Dist Stor Manager" [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc:(bcc: Michel Engels/BE/Devoteam) Subject: SMS Scripting for NT installation Hi everyone! Has anyone been able to get around the html pop up window when scripting the installation for Windows NT? Also, the number of re-boots required? I have someone in our NT group doing the scripting for me and he is having trouble with these areas. If you have ideas or even a sample script that you would be willing to share, I would really appreciate it. Do you know what the switches mean that are for installation? /v and /qn Thanks, Brenda Collins, Storage Management Phone: 651-848-5808 Email: [EMAIL PROTECTED] Disclaimer: "The views, opinions and judgements expressed in this message are solely those of the author. The message contents have not been reviewed or approved by West Group."
Re: APAR IC28571 : NT EVENT VIEW REPORTS PERFLIB ERRORS AGAINST DSM CPERF.DLL - TSM 4.1.1
Hello, I believe that the following procedure should do the trick. Step 2 especially is the key (no pun intended). WARNING: This procedure involves editing the NT registry. THE REGISTRY EDITOR IS NOT FORGIVING OF MISTAKES! Errors in editing the registry have the potential to render the system unstable or even unbootable. If you are unfamiliar or uncomfortable with editing the registry, then either ask someone who is more experienced do this for you or install this fixtest (which automatically performs these operations for you). 1) From an MS-DOS command line prompt, enter the following commands: unlodctr "ADSM Client Performance" unlodctr "TSM Client Performance" If the performance counters were previously installed, you should see messages similar to this: Removing counter names and explain text for ADSM Client Performance Updating text for language 009 If the performance counters were not previously installed, you will see a message similar to this: Counters for ADSM Client Performance have not been installed yet 2) Using the registry editor, remove the following keys (including their values): HKEY_LOCAL_MACHINE\ SYSTEM\ CurrentControlSet\ Services\ ADSM Client Performance HKEY_LOCAL_MACHINE\ SYSTEM\ CurrentControlSet\ Services\ EventLog\ Application\ ADSM Client Performance Note: Also check for keys with "TSM" in the name instead of "ADSM". The performance counters and registry entries are now removed. Regards, Andy Andy Raibeck IBM/Tivoli Tivoli Storage Manager Client Development e-mail: [EMAIL PROTECTED] "The only dumb question is the one that goes unasked." Hello TSMers, I have scoured the TSM Knowledge Base at http://www.tivoli.com/asktivoli on the subject error and found the APAR. However the work around does not work for us. First, the local fix using the unlodctr doesn't work because it is not called "TSM Client Performance", but "ADSM Client Performance". Then, the "lodctr perfctr.ini" command doesn't work because TSM Client Performance is hard-coded into the perfctr.ini file when it needs to say ADSM Client Performance. However, even when you make these modifications, it still does not get rid of the error messages. As for the changes to the registry, the registry key they mention doesn't exist. Any other options?
Re: Windows 2000 ?
My fave is fudge Sunday ;-P -Original Message- From: Serein, Gilbert Claudio [mailto:[EMAIL PROTECTED]] Sent: Tuesday, January 16, 2001 10:57 AM To: [EMAIL PROTECTED] Subject: Windows 2000 ? I have to install TSM 4.1 on a windows machine and the manual does not specify which flavor of Windows 2000. Which version should I install ? Thanks for your help in advance, Gilbert
Windows 2000 ?
I have to install TSM 4.1 on a windows machine and the manual does not specify which flavor of Windows 2000. Which version should I install ? Thanks for your help in advance, Gilbert
Re: TSM and LTO
Hi Hunny, Glad to see you are here too. You almost saying you are an IBMer (or TSMer). Randy warned me just do "read only" activities for whatever his reasons because it got me to do extra work once. Be careful what you say in public, someone may hold you responsible. --- Hunny Kershaw [EMAIL PROTECTED] wrote: TSM 4.1 also has support for IBM LTO libraries (3581,3583 and 3584). The next PTF should include the support for a few LTO libraries, i.e. Plasmon FTA, Exabyte 110L, ... --- Shawn Raymond [EMAIL PROTECTED] wrote: TSM 4.1 has support for IBM LTO drives at least on AIX and NT with the latest Atape driver. -- Shawn Raymond Sr. Technical Consultant Synergy, INC. 518-782-3457 Andreas Rensch RenschA@ALTE-LEITo: [EMAIL PROTECTED] PZIGER.DE cc: Sent by: "ADSM: Subject: TSM and LTO Dist Stor Manager" [EMAIL PROTECTED] .EDU 01/15/01 10:56 AM Please respond to "ADSM: Dist Stor Manager" Hi, does anybody know when TSM (on Unix) or LegatoNetworker comes with LTO-Support? (Ultrium)drives and (Exabyte or StorageTek) autoloader and libraries. mfg / regards andreas rensch / rz-qs tel : +49(0)6171 66 3692 / fax : +49(0)6171 66 7500 3692 / mobil : +49(0)172 6649 016 / mailto:[EMAIL PROTECTED] Alte Leipziger Lebensversicherung aG - Alte Leipziger Platz 1 - D 61440 Oberursel - http://www.alte-leipziger.de Two rules for success in life. 1. Don't tell people everything you know. 2. __ Do You Yahoo!? Get email at your own domain with Yahoo! Mail. http://personal.mail.yahoo.com/ __ Do You Yahoo!? Get email at your own domain with Yahoo! Mail. http://personal.mail.yahoo.com/
Re: Archiving
THIRTY YEARS is a LNG time. One nice thing about archiving with TSM is that the TSM server makes it very easy to rotate your media, make extra copies for vault storage (copy pools), or just move the data to new media at any point. So you can easily avoid the probems associated with aging/obsolete media. However, as much as I like the product, I might think twice about archiving with it for THIRTY YEARS. One disadvantage I see is that the ONLY thing that can retrieve the archived data is the TSM client, and you have to retrieve UNIX data to UNIX machines, and NT data to Wintel-type machines. Assuming Tivoli/TSM are viable for the next 30 years, do you want to count on your company having the same platforms and running the client code for the next 30 years? Another problem with TSM archiving is that the data is indexed/tied to the host that archived it. It's a real pain to deal with that when you go through a server consolidation where multiple machines get merged into one. Your archives are still split up and tied to the old host names (been there done that one already.) If I had your requirement, I think I would at least take a look around to see if there is something that would leave the data in a form that would provide an easier means to see what is archived, without the data being tied so tightly to the machine that archived it originally and that machine's directory structure. And if possible, to leave the data machine readable directly by multiple pieces of software, without depending on the specific TSM client code. Such a thing may not exist, but I would at least THINK about it. Or at the very least, make sure all your long-term archives are done by ONE host. -Original Message- From: Christoph Pilgram To: [EMAIL PROTECTED] Sent: 1/16/01 3:00 AM Subject: Archiving Hy everyone, we are discussing the possibilities of archiving data with TSM or other products (from NT,UNIX). Our requirements are to archive data for about 30 years. TSM is in discussion because we use it already for backup ( and in some cases we use the archive-command ). The policy domains for the clients for archiving will be (from my point of view) totally different to those for backup. Can anybody share his good (or bad) experience in long term archiving with whatever kind of library in the background (DVD or tape). Thanks a lot Christoph
Re: deleting rman data
How do I verify the state of the objects? "Michel Engels" [EMAIL PROTECTED]@VM.MARIST.EDU on 01/15/2001 08:51:28 AM Please respond to "ADSM: Dist Stor Manager" [EMAIL PROTECTED] Sent by: "ADSM: Dist Stor Manager" [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: Subject: Re: deleting rman data You should verify the state of the objects. After the deletion of the files via RMAN the state should change from active to inactive. Be sure your RetO value is set to 0 otherwise the files will be kept for some time depending your settings in the managementclass. When the files become inactive, the retention is set to 0 and the expiration on the server has run the files should disappear. Hope this helps, Michel "James healy" [EMAIL PROTECTED] on 01/12/2001 10:49:32 PM Please respond to "ADSM: Dist Stor Manager" [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc:(bcc: Michel Engels/BE/Devoteam) Subject: deleting rman data i have a question about verifying the deletion of rman data. i'd like to know how anyone verifies that old versions of rman files are getting deleted. My DBAs say they are running the commands to expire old versions but I don't see it happening Are there any commands that I could erify this with. I've checked q occ and the number of files does not decrease for that rman client.
TDP for ORACLE restores
hi Bruce, Your setup for TDPO seems to be fine. Just want to add something to do for RMAN. On location B: % rman RMAN connect target RMAN connect rcvcat catalog info RMAN restore controlfile RMAN sql 'alter database mount' RMAN restore database RMAN recover database Of course you will have to allocate the channels and set the correct env vars. reagards, Thiha I'm wondering if anyone has successfully restored using RMAN from a di= fferent TSM server. One of our DBA's is attempting to do this. Environment :- Oracle 8.1.6. TDP for Oracle V.2.1.9 (no we wont use V2.1.10 because it core dumps o= n any TSM client with cloptsets). TSM server version 4.1.2.0 Solaris 2.07 The scenario is as follows : - Location A contains TSM server xx . Oracle DB yy and DMSO_NODE zz So yy backs up to server xx , via TSM client zz=A0 ( using dsm.optora = to point to server xx in the dsm.sys file) Location B contain TSM server aa.=A0 Oracle DB bb and DSMO_NODE cc aa backs up to server bb , via TSM client cc ( using dsm.optora to poi= nt to server cc in the dsm.sys file) To restore yy to Node in Location B, my intention for him (DBA)=A0 is = to :- export DSMO_NODE=3Dzz (as known in location A) export DSMI_CONFIG=3D/home/oracle/dsm.optorarest This opt file points to server xx (location A) in dsm.sys stanza. We've set up TDPO.zz password file. Will this work or, is there anything else required? We want to get a handle on this to perform cross server/cross client r= estores, as we have a local TSM server per tech suite (of which there = are several), and DBA's want to restore Oracle DB's between locations f= or BCP purposes.
Re: Backup Exec
Yes. Backup Exec has a TSM interface that will do just what you describe. I tested it a couple of years ago, worked fine. (We ended up not using it because there was just too much data to send across our network at the time, but that was a network issue, not a problem with the Backup Exec interface.) At the time I looked at it, the TSM(ADSM) interface was an extra cost option, but that may have changed since. It's pretty easy to set up, they provide explicit instructions. -Original Message- From: Jacques Butcher To: [EMAIL PROTECTED] Sent: 1/16/01 1:34 AM Subject: Backup Exec Can Backup Exec be setup in such a way that it sends data off to TSM without having a storage device locally attached to the server it's running on? I.e. TSM handles the backup device (library) as well as manage all the volumes. Any comments will be greatly appreciated Jacques Butcher.
Re: deleting rman data
*sm show versions nodename * Brgds, Othonas "James healy" [EMAIL PROTECTED]@VM.MARIST.EDU on 01/16/2001 11:31:26 AM Please respond to "ADSM: Dist Stor Manager" [EMAIL PROTECTED] Sent by: "ADSM: Dist Stor Manager" [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: Subject: Re: deleting rman data How do I verify the state of the objects? "Michel Engels" [EMAIL PROTECTED]@VM.MARIST.EDU on 01/15/2001 08:51:28 AM Please respond to "ADSM: Dist Stor Manager" [EMAIL PROTECTED] Sent by: "ADSM: Dist Stor Manager" [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: Subject: Re: deleting rman data You should verify the state of the objects. After the deletion of the files via RMAN the state should change from active to inactive. Be sure your RetO value is set to 0 otherwise the files will be kept for some time depending your settings in the managementclass. When the files become inactive, the retention is set to 0 and the expiration on the server has run the files should disappear. Hope this helps, Michel "James healy" [EMAIL PROTECTED] on 01/12/2001 10:49:32 PM Please respond to "ADSM: Dist Stor Manager" [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc:(bcc: Michel Engels/BE/Devoteam) Subject: deleting rman data i have a question about verifying the deletion of rman data. i'd like to know how anyone verifies that old versions of rman files are getting deleted. My DBAs say they are running the commands to expire old versions but I don't see it happening Are there any commands that I could erify this with. I've checked q occ and the number of files does not decrease for that rman client.
Re: IBM 35xx Libraries, Windows 2000 and TSM - Observations
Kelly, Would you kindly post an overview of the steps invovled in configuring the LTO changers with TSM Windows 2000? No sense in ALL of us going through the same learning curve... LOL Thanks! Glen Smith Sent by: "ADSM: Dist Stor Manager" [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: Subject: IBM 3583 and Ultrium Drives, Windows 2000 - Second Edition We were able to get the library defined. The README distinctly lacks the define drive command for Win2K. Does this mean it is isn't necessary? That somehow RSM provides drives to the RSM defined library? __ FREE Personalized Email at Mail.com Sign up at http://www.mail.com/?sr=signup
Re: deleting rman data
Othonas thanks for your reply thats exactly what I was looking for but I guess I still have a problem. My DBAs run this command change backuppiece tag 'TRIB20001215' delete. and it says the files are deleted from ORacle . I run expiration, expiration completes and yet the files are still in TSM Can anyone see if I'm still missing something or have I encountered a bug? "Othonas Xixis" [EMAIL PROTECTED]@VM.MARIST.EDU on 01/16/2001 11:59:15 AM Please respond to "ADSM: Dist Stor Manager" [EMAIL PROTECTED] Sent by: "ADSM: Dist Stor Manager" [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: Subject: Re: deleting rman data *sm show versions nodename * Brgds, Othonas "James healy" [EMAIL PROTECTED]@VM.MARIST.EDU on 01/16/2001 11:31:26 AM Please respond to "ADSM: Dist Stor Manager" [EMAIL PROTECTED] Sent by: "ADSM: Dist Stor Manager" [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: Subject: Re: deleting rman data How do I verify the state of the objects? "Michel Engels" [EMAIL PROTECTED]@VM.MARIST.EDU on 01/15/2001 08:51:28 AM Please respond to "ADSM: Dist Stor Manager" [EMAIL PROTECTED] Sent by: "ADSM: Dist Stor Manager" [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: Subject: Re: deleting rman data You should verify the state of the objects. After the deletion of the files via RMAN the state should change from active to inactive. Be sure your RetO value is set to 0 otherwise the files will be kept for some time depending your settings in the managementclass. When the files become inactive, the retention is set to 0 and the expiration on the server has run the files should disappear. Hope this helps, Michel "James healy" [EMAIL PROTECTED] on 01/12/2001 10:49:32 PM Please respond to "ADSM: Dist Stor Manager" [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc:(bcc: Michel Engels/BE/Devoteam) Subject: deleting rman data i have a question about verifying the deletion of rman data. i'd like to know how anyone verifies that old versions of rman files are getting deleted. My DBAs say they are running the commands to expire old versions but I don't see it happening Are there any commands that I could erify this with. I've checked q occ and the number of files does not decrease for that rman client.
Re: deleting rman data
It sounds like a problem at the API level between TSM and Oracle, either upgrade yr RMAN module, or the TSM Client API, or both... it seems to me that they don't hook up appropriately. Do you receive any errors on the dsierror.log file ? if yes... you might want to troubleshoot them and you will probably find the end. Finally, I trust that all your management classes/copygroup stuff are set properly... Good luck... Othonas "James healy" [EMAIL PROTECTED]@VM.MARIST.EDU on 01/16/2001 01:18:05 PM Please respond to "ADSM: Dist Stor Manager" [EMAIL PROTECTED] Sent by: "ADSM: Dist Stor Manager" [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: Subject: Re: deleting rman data Othonas thanks for your reply thats exactly what I was looking for but I guess I still have a problem. My DBAs run this command change backuppiece tag 'TRIB20001215' delete. and it says the files are deleted from ORacle . I run expiration, expiration completes and yet the files are still in TSM Can anyone see if I'm still missing something or have I encountered a bug? "Othonas Xixis" [EMAIL PROTECTED]@VM.MARIST.EDU on 01/16/2001 11:59:15 AM Please respond to "ADSM: Dist Stor Manager" [EMAIL PROTECTED] Sent by: "ADSM: Dist Stor Manager" [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: Subject: Re: deleting rman data *sm show versions nodename * Brgds, Othonas "James healy" [EMAIL PROTECTED]@VM.MARIST.EDU on 01/16/2001 11:31:26 AM Please respond to "ADSM: Dist Stor Manager" [EMAIL PROTECTED] Sent by: "ADSM: Dist Stor Manager" [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: Subject: Re: deleting rman data How do I verify the state of the objects? "Michel Engels" [EMAIL PROTECTED]@VM.MARIST.EDU on 01/15/2001 08:51:28 AM Please respond to "ADSM: Dist Stor Manager" [EMAIL PROTECTED] Sent by: "ADSM: Dist Stor Manager" [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: Subject: Re: deleting rman data You should verify the state of the objects. After the deletion of the files via RMAN the state should change from active to inactive. Be sure your RetO value is set to 0 otherwise the files will be kept for some time depending your settings in the managementclass. When the files become inactive, the retention is set to 0 and the expiration on the server has run the files should disappear. Hope this helps, Michel "James healy" [EMAIL PROTECTED] on 01/12/2001 10:49:32 PM Please respond to "ADSM: Dist Stor Manager" [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc:(bcc: Michel Engels/BE/Devoteam) Subject: deleting rman data i have a question about verifying the deletion of rman data. i'd like to know how anyone verifies that old versions of rman files are getting deleted. My DBAs say they are running the commands to expire old versions but I don't see it happening Are there any commands that I could erify this with. I've checked q occ and the number of files does not decrease for that rman client.
Novell Archive Errors
After upgrading our ADSM 3.1 server to TSM 3.7.4, we had problems with archiving volumes from a Novell client running extremely slow. We ran a CLEAN ARCHDIR DELETEDIRS command and a couple of archives were run successfully with the elapsed time being close to that of the ADSM 3.1 server. However, any subsequent archives have started running normally and eventually encounter errors such as: from dsmsched.log 01/15/2001 22:06:19 Normal File-- 2,348 LPD:/Maildata/MMF/ARWARCHI/E000731/ADJ.RPZ ** Unsuccessful ** 01/15/2001 22:06:19 ANS1228E Sending of object 'LPD:/Maildata/MMF/ARWARCHI/E000731/ADJ.RPZ' failed 01/15/2001 22:06:19 ANS4005E Error processing 'LPD:/Maildata/MMF/ARWARCHI/E000731/ADJ.RPZ': file not found matching dsmerror.log 01/15/2001 22:06:08 (TSA500.NLM 5.3 269) No data sets can be found. 01/15/2001 22:06:08 (TSA500.NLM 5.3 269) No data sets can be found. 01/15/2001 22:06:08 ANS1228E Sending of object 'LPD:/Maildata/MMF/ARARCHIV/E000731/ADJ.RPZ' failed File does exist on server. Novell server at 5.0 SP6. We are using the following NLM levels: TSA500.NLM 5.03 TSANDS.NLM 5.25 SMDR.NLM 5.04 Novell client level: 3.7.2.11 We are going to attempt to re-cycle the NLM's in off hours to see if that is the problem. Just wondering if anyone has encountered similar errors during archive processing. TIA Tom Bebee
Expiration not expiring Archives
Hello *Sers, I have a problem that I hope someone will be able to tell me how to fix. I am running TSM 3.7 on AIX 4.3.3, and I have my archives set to expire after 7 days. The problem I have is that TSM is not expiring the archives. I still see archives from a 14 days. When I run expire inventory nothing expires. All my policy sets are set to 7 days. Is there something that I missed, or is this a known problem. Any info would be great. Thanks in advance, Bill Wheeler AIX Administrator La-Z-Boy Incorporated [EMAIL PROTECTED] mailto:[EMAIL PROTECTED]
Re: Archiving
And let me chime in with another point or three :-) I agree with Wanda and Scott, TSM will at least let you keep the media fresh and recoverable. My experience is that you won't have an application that can use the data! You either need a contract, signed in blood, that the vendor of the product that generated/uses the data will support a 30-year old format on as-yet undeveloped platforms -- or you need to make sure the data is in as generic a format as possible. Flat, comma-delimited ASCII comes to mind. Do not even *think* of archiving a database in database format! (I've been on the wrong end of trying to get a Burroughs Forte/II database off tape so it could be converted to IMS . . .) Tom Kauffman NIBCO, Inc -Original Message- From: Scott McCambly [mailto:[EMAIL PROTECTED]] Sent: Tuesday, January 16, 2001 1:56 PM To: [EMAIL PROTECTED] Subject: Re: Archiving Here's my $0.02 on this topic Wanda makes some good points pro and con, however I don't think they were given appropriate weighting. Whatever product or method is used to store data for 30 years, the problem of maintaining support and cross-platform data types will plague them all! I would assume that they are not going to do the archive and then walk away for 30 years, only to come back and brush the dust off and try and restore. The restore requirement could be anytime from now until 30 years from now. Anyway, the comment... One nice thing about archiving with TSM is that the TSM server makes it very easy to rotate your media, make extra copies for vault storage (copy pools), or just move the data to new media at any point. So you can easily avoid the probems associated with aging/obsolete media. I think outweighs all the other more trivial problems. I still today occasionally restore files from an archive of my old Windows 3.1 system onto my Win2K with no problems. TSM is one of the top storage managment products in use today, so why not stick with it. If 15 years from now Tivoli decides to stop supporting TSM, then the storage administrator at that time will have to come up with a migration strategy. Hopefully by then he/she/it will just transfer it to his neo-cortical implant and go back to playing on the hollodeck :-). Perhaps use a generic node name, and think about using a separate TSM server as the Archive server, but definitely do use TSM. Scott. At 11:46 AM 1/16/01 -0500, you wrote: THIRTY YEARS is a LNG time. One nice thing about archiving with TSM is that the TSM server makes it very easy to rotate your media, make extra copies for vault storage (copy pools), or just move the data to new media at any point. So you can easily avoid the probems associated with aging/obsolete media. However, as much as I like the product, I might think twice about archiving with it for THIRTY YEARS. One disadvantage I see is that the ONLY thing that can retrieve the archived data is the TSM client, and you have to retrieve UNIX data to UNIX machines, and NT data to Wintel-type machines. Assuming Tivoli/TSM are viable for the next 30 years, do you want to count on your company having the same platforms and running the client code for the next 30 years? Another problem with TSM archiving is that the data is indexed/tied to the host that archived it. It's a real pain to deal with that when you go through a server consolidation where multiple machines get merged into one. Your archives are still split up and tied to the old host names (been there done that one already.) If I had your requirement, I think I would at least take a look around to see if there is something that would leave the data in a form that would provide an easier means to see what is archived, without the data being tied so tightly to the machine that archived it originally and that machine's directory structure. And if possible, to leave the data machine readable directly by multiple pieces of software, without depending on the specific TSM client code. Such a thing may not exist, but I would at least THINK about it. Or at the very least, make sure all your long-term archives are done by ONE host. -Original Message- From: Christoph Pilgram To: [EMAIL PROTECTED] Sent: 1/16/01 3:00 AM Subject: Archiving Hy everyone, we are discussing the possibilities of archiving data with TSM or other products (from NT,UNIX). Our requirements are to archive data for about 30 years. TSM is in discussion because we use it already for backup ( and in some cases we use the archive-command ). The policy domains for the clients for archiving will be (from my point of view) totally different to those for backup. Can anybody share his good (or bad) experience in long term archiving with whatever kind of library in the background (DVD or tape). Thanks a lot Christoph Scott McCambly AIX/NetView/ADSM Specialist - Unopsys Inc. Ottawa, Ontario, Canada (613)799-9269
Re: 4.12 ANS1074I User Abort
Tivoli has opened APAR IC29368 for this. Basically the client ends with "ANS1074I *** User Abort ***" (scheduler or cmdline) or "MSG "ANS5011I Backup Stopped by User" (GUI) instead of displaying the real error message. In our case we experienced 3 different errors that produced user aborts: - "ANS1311E Server out of data storage space" - "ANS1448E An error occurred accessing NTFS security information" (Exchange 2000 Web Store) - "ANS4036E An error occurred saving the registry key" Instead of displaying the above message, the 4.12 client just ends with the User Abort. The 4.11 client displays the proper message. We experienced this on WIN32 and Solaris 4.12 clients. Tim Rushforth City of Winnipeg -Original Message- From: Rushforth, Tim Sent: Thursday, December 28, 2000 10:10 AM To: 'ADSM: Dist Stor Manager' Subject: RE: Backing Up Windows 2000 SysFiles We have experienced the "User Abort" on two of our servers running the new 4.12 Client. Both Servers are Windows 2000 SP1. One server is an Exchange 2000 server and the user abort happens when the Web Store (Drive "M") is attempted to be backed up. The other server, has happened 3 out of 5 incrementals is a 2000 DC. I have opened a problem with Tivoli on this. Tim Rushforth City of Winnipeg [EMAIL PROTECTED] -Original Message- From: Markus Stegmeier [mailto:[EMAIL PROTECTED]] Sent: Thursday, December 28, 2000 9:36 AM To: [EMAIL PROTECTED] Subject: Backing Up Windows 2000 SysFiles Hello there, does anybody know, who to backup Windows 2000 Sysfiles. On our new Testserver the backup systemobjects fails with a user abort "ANS1074I". It seems the backup sysfiles found no sysfiles why? Best regards. Markus Stegmeier
Support for TSM 3.7.3.8
Hello All, Can someone please tell me does TSM still support 3.7.3 after 01/31/2001? If not do I have to go to 4.1? Thanks in advance Ray Baughman Engineering Systems Administrator TSM Administrator National Machinery Co. Phone: 419-443-2257 Fax: 419-443-2376 Email: [EMAIL PROTECTED]
Re: Support for TSM 3.7.3.8
As pointed out to me, try: http://www.tivoli.com/support/storage_mgr/tivolieoc.html [EMAIL PROTECTED] 01/16/01 03:06PM Hello All, Can someone please tell me does TSM still support 3.7.3 after 01/31/2001? If not do I have to go to 4.1? Thanks in advance Ray Baughman Engineering Systems Administrator TSM Administrator National Machinery Co. Phone: 419-443-2257 Fax: 419-443-2376 Email: [EMAIL PROTECTED]
Copypools for disks
I'm nearly ready to activate DRM on a new server, but I have a worry about copypools for disk storage. One of the diskpools is for smaller servers which migrate to a limited number of collocated tapes. This pool is not yet very active, so there are many nodes which have not yet migrated off to tape. I have the time and resources to copy my diskpools to tape daily, but I wonder what sort of confusion I may be generating. For instance, what happens to cached files that are on tape as well as disk? Do I get two copies? or only the one that already exists from the backup of the tape? What happens to a file that migrates to tape some time after a copy is made from disk? does it supercede the previous copy? or are there again two copies in the copypool? What happens in case of disaster requiring a restore storage operation? At this point, I really don't know what to expect. All assistance will be gratefully accepted.
Re: Novell Archive Errors
As has been noted there are some new nlm's available from Novell for 5.0 and 5.1 servers. They are packaged as tsa5up3. Check Novell's support site. Tom Bebee wrote: After upgrading our ADSM 3.1 server to TSM 3.7.4, we had problems with archiving volumes from a Novell client running extremely slow. We ran a CLEAN ARCHDIR DELETEDIRS command and a couple of archives were run successfully with the elapsed time being close to that of the ADSM 3.1 server. However, any subsequent archives have started running normally and eventually encounter errors such as: from dsmsched.log 01/15/2001 22:06:19 Normal File-- 2,348 LPD:/Maildata/MMF/ARWARCHI/E000731/ADJ.RPZ ** Unsuccessful ** 01/15/2001 22:06:19 ANS1228E Sending of object 'LPD:/Maildata/MMF/ARWARCHI/E000731/ADJ.RPZ' failed 01/15/2001 22:06:19 ANS4005E Error processing 'LPD:/Maildata/MMF/ARWARCHI/E000731/ADJ.RPZ': file not found matching dsmerror.log 01/15/2001 22:06:08 (TSA500.NLM 5.3 269) No data sets can be found. 01/15/2001 22:06:08 (TSA500.NLM 5.3 269) No data sets can be found. 01/15/2001 22:06:08 ANS1228E Sending of object 'LPD:/Maildata/MMF/ARARCHIV/E000731/ADJ.RPZ' failed File does exist on server. Novell server at 5.0 SP6. We are using the following NLM levels: TSA500.NLM 5.03 TSANDS.NLM 5.25 SMDR.NLM 5.04 Novell client level: 3.7.2.11 We are going to attempt to re-cycle the NLM's in off hours to see if that is the problem. Just wondering if anyone has encountered similar errors during archive processing. TIA Tom Bebee -- Jim Kirkman AIS - Systems UNC-Chapel Hill 966-5884
Archive running a lonnngg time...
Hi, We were on TSM 4.1.2 and AIX 4.3.2. About a week or so ago we upgraded to TSM 4.1.2 and one of our Archive was running 4 times a long, We notices other backups were taking longer than usual. Because of this problem we backed out and went back to TSM 4.1.0. We have an open PMR on this. Taking one night for example (Saturday), one of our Archive job that usually run for 2 to 3 hours, ran for 18 hours. Of course this is unacceptable for our clients. We looked at our tuning performances and everything looks good as it was before 4.1.2. Did anyone else run into this problem? If yes, did you have a solution? Thanks for any help you can give Dave Pearson IS Production Support Analyst Snohomish County PUD Everett Washington 425.347.4420 [EMAIL PROTECTED]
No Subject
I am trying to backup a Netware 5.1 server using ADSM 4.01a. I am receiving the following error messaged while using the sched option and the incremental option error message in the dsmsched.log ANS1301E Server detected system error error message in the dsmerror.log cuSignOnResp: Server rejected session; result code: 53 01/16/2001 08:03:21 (TSA500.NLM 5.3 259) This program cannot allocate a directory handle. 01/16/2001 08:03:21 ANS1076E *** Directory path not found *** I have not been able to find out much information from the Tivoli web site. Does anyone have any idea what I should be looking for? I have tried increasing the maximum number of directory handles but this has not helped. Thanks, Lorrie Lorrie J. Marnell Network Operations Manager College of Human Ecology G85 MVR Hall [EMAIL PROTECTED] 607-255-8877 http://www.human.cornell.edu/Admin/CSG/home.html "That which does not kill me makes me stronger"
Re: Mountable to Notmountable
Issue the following command: update vol xx access=offsite This will change the status of the volume from "mountable" to "vault" -Original Message- From: Selva, Perpetua [SMTP:[EMAIL PROTECTED]] Sent: Monday, January 08, 2001 11:01 AM To: [EMAIL PROTECTED] Subject:Mountable to Notmountable Hi, Can please someone tell me how to fix this problem Apparently i have some tapes in 'mountable' state ..,but out of the adsm library and i'm unable to change their status.. Please Advise
Re: IBM 35xx Libraries, Windows 2000 and TSM - Observations
Excellent! Let the tape boys so the drive drivers, but let you TSM guys do the library. Leaving it to Microsoft is a real bad idea! While we're on this topic: I'm having trouble getting tapes to label properly in a 3584. The barcodes on the tapes (provided with the IBM tapes) have eight characters. label libvol appears to label them correctly, but when attempts are made to use the tapes we're getting an I/O error reading the labels. Are we limited to six characters? If so, why do the LTO specified labels have eight characters (six useful ones with the last two being L1)? Any ideas how to work around this short of using a magic marker to wipe out the L1? Thanks, Kelly -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of Mike Collins Sent: Tuesday, January 16, 2001 10:52 AM To: [EMAIL PROTECTED] Subject: Re: IBM 35xx Libraries, Windows 2000 and TSM - Observations Hi Kelly, Here's some information regarding your recent post. TSM recognizes that there are some short comings with RSM and will be providing the ability to define 3581, 3583 and 3584 libraries as type SCSI in the near future. This will be accomplished with updates to ADSMSCSI to control the medium-changer in the 3581, 3583 and 3584 libraries. This work is currently in test and will be released as a PTF when it completes the test process. The README will document how to migrate from an RSM environment to a SCSI environment. TSM will continue to support the definition of the library as type RSM for those customers who wish to utilize RSM. With the introduction of the SSD LTO technology, TSM has changed how it supports SSD tape devices and uses the SSD device driver to control the LTO drives on the NT platforms. Now SSD LTO customers can easily download microcode updates and perform other serviceability functions. Whether RSM or ADSMSCSI controls the medium-changer in the library, the SSD device driver will control the LTO drives. Kelly J. Lipp writes: Gang, Well, with any luck this will rile up the works! This is whacked. The use of TSM Libraries through RSM will cause you to seriously rethink the way you manipulate media. As there is no longer checkin/checkout/label libvol, those operational procedures must be changed. You must use RSM to perform these steps. Checking in tapes appears to require the opening of the library and the insertion of a tape into the library rather than using the Bulk Port. Opening a library that has a bulk port would seem silly. Overall this strategy appears flawed in its initial release. I would not recommend to anyone that they try to run this configuration. From our days worth of fooling with it the learning curve is too steep. Tape manipulation is already complicated enough within TSM and this makes it more so. Our recommendation essentially suggests that the purchase of IBM 35xx libraries for use with TSM on Windows 2000 is a mistake. I can't imagine that anyone within IBM or Tivoli wants this. From all appearances these libraries seem to be very nice units indeed. Not with TSM and Windows 2000 though. That's a conundrum. What we need to know from Tivoli is the following: 1. Is the use of RSM on Windows 2000 an interim step leading to the use of ADSMSCSI, or is this the way it's going to be? 2. Will other libraries receive the same treatment? I.e., is this the wave of the future? 3. Has anyone within Tivoli tested this stuff and is there some documentation which might simplify this? I've seen list entries as far back as October. I haven't seen anyone from Tivoli weigh in on this. I'm sure some guys in Tucson or San Jose have fooled with this. How about giving us some guidance? In the meantime if any of you are considering going down this path, STOP. I don't think you're going to like where it takes you. Kelly J. Lipp Storage Solutions Specialists, Inc. PO Box 51313 Colorado Springs CO 80949-1313 (719) 531-5926 Fax: (240) 539-7175 Email: [EMAIL PROTECTED] or [EMAIL PROTECTED] www.storsol.com www.storserver.com Best Regards, Mike Collins Tivoli Storage Manager Development E Mike Collins/Tivoli Systems or [EMAIL PROTECTED]
Backup Exec backing up to TSM?
A few questions related to the above-mentioned: 1. How does TSM handle data that was backed up from a Backup Exec client? 2. Do you register that node on TSM? 3. Can you generate a backup set for that node? 4. Does versioning of files apply to that node? Any comments will be greatly appreciated. Jacques Butcher.
