Re: Restoring inactive file to Novell
Tomas, You have two options. The one which is easiest is to start using the web access part of the ADSM which will then allow you a graphical interface of sorts, and which is a million times easier to work then the command line. The second option is of course the command line, and then you have to give it the -INA and -PI parameters. the -INA is inactive, and the -PI is Pick to chose the files to restore. In my opinion, go with the web access and throw the command line away forever. The manuals explain how to get it running. Mike > -Original Message- > From: Tomas Hallin [SMTP:[EMAIL PROTECTED]] > Sent: ã àåâåñè 02 2000 21:40 > To: [EMAIL PROTECTED] > Subject: Restoring inactive file to Novell > > Hello, > > I'm wondering how to restore an inactive file to a Novell client. In > Windows, I'd use the GUI to select "show inactive files", but since > there's no GUI with the Novell client, how is it done? > > Thanks, > > /Tomas > > Tomas Hallin > Affinity Technology Group > Columbia, SC
Re: NDS backups
These are NDS objects. We get exactly the same issue showing when ours gets backed up, even tho we know for a fact that the size of the files is much smaller. We put it down to a quirk in ADSM. By the way, we do NOT trust the ADSM NDS backups as a restore-able backup. All our NDS backups are done to a seperate tape for safety reasons (as in, ADSM failing to restore NDS on more then one occassion claiming it didn't have rights when it did). Mike > -Original Message- > From: David Browne. [SMTP:[EMAIL PROTECTED]] > Sent: ã àåâåñè 02 2000 22:26 > To: [EMAIL PROTECTED] > Subject: NDS backups > > My network guy was monitoring a backup and asked me if the number that > appears after the" Normal File-->" is the size of the file being backed > up. It appears all of these files are the same size and he is telling me > they shouldn't be very large. Could TSM be using up space unnecessarily? > This is a Netware 4.11 server with TSM 3.7.1 on it. Can someone give me > some information? > > Normal File--> 2,097,152 .[Root].O=HUM.OU=Area42.OU=PIN.CN=Lms6224 > [Sent] > Normal File--> 2,097,152 .[Root].O=HUM.OU=Area42.OU=PIN.CN=Mjr3663 > [Sent] > Normal File--> 2,097,152 .[Root].O=HUM.OU=Area42.OU=PIN.CN=Mmf2355 > [Sent] > Normal File--> 2,097,152 .[Root].O=HUM.OU=Area42.OU=PIN.CN=Mmk7095 > [Sent] > Normal File--> 2,097,152 .[Root].O=HUM.OU=Area42.OU=PIN.CN=MWH4505 > [Sent] > Normal File--> 2,097,152 .[Root].O=HUM.OU=Area42.OU=PIN.CN=Netman > [Sent] > Normal File--> 2,097,152 > .[Root].O=HUM.OU=Area42.OU=PIN.CN=NetShield_PI > MKT1 [Sent] > Normal File--> 2,097,152 .[Root].O=HUM.OU=Area42.OU=PIN.CN=PINMKT1
HSM with TSM 4.1
I appears that HSM is still not suppoted for NT clients. Does IBM/Tivoli still believe that the open systems environment is a passing fad?? From looking at the website, I was not able to find anything stating that HSM was supported for NT. Looks like we have to consider another source for HSM functionality. Guess it will be ready by TSM 9.1. If anyone knows differently, then please let me know. T Anthony Garrison, MCSE, MCP+I, A+ Cell (210) 913-9836 Pager 753-9836 [EMAIL PROTECTED] The Key to Success is "Be worth more then you earn!"
Re: HSM on NT/Netware?
You can try OTG's DiskXtender. I have been considering looking at it myself. But was hoping that TSM 4.1 would support it. No such luck though. go to www.otg.com Anthony Garrison, MCSE, MCP+I, A+ Cell (210) 913-9836 Pager 753-9836 [EMAIL PROTECTED] The Key to Success is "Be worth more then you earn!" -Original Message- From: Phillip Guan [SMTP:[EMAIL PROTECTED]] Sent: Thursday, July 27, 2000 2:47 PM To: [EMAIL PROTECTED] Subject:HSM on NT/Netware? I have a client who'd like to run HSM on NT and especially Netware. Looking at Tivoli's site it looks like it's only supported on AIX/Solaris as those are the only platforms it mentions. Is this true? I'm just looking for a confirmation.. Anyone know of any other products that provide similar functionality particularly on netware? Thanks, Gerald Wichmann Sansia System Solutions
AW: Tsm 4.1 client.
> > Will someone please show the idiots at Tivoli > > As anyone else on this list (including me) the people from > Tivoli are far from being perfect - but do you think they deserve > being called "idiots"? > My English is not perfect - so if this word has another more pleasant > meaning please disregard this message. > > Kind regards > Thomas Rupp > Vorarlberger Illwerke AG > MAIL: [EMAIL PROTECTED] > TEL: ++43/5574/4991-251 > FAX: ++43/5574/4991-820-8251 >
Attention: TDP for Exchange V2 - Beta Program Nomination Form
Customers interested in participating in the beta test of Tivoli Data Protection for Exchange V2 should fill == out the following form and send it to: [EMAIL PROTECTED] Nominations will be accepted until 8/18/2000. The beta test is expected to start in October. Highlights of V2 of TDP for Exchange are as follows: * Automatic Expiration and version control by TSM server policy => The current product stores each backup object with a unique name thereby circumventing the automatic expiration and version control provided by the TSM server. The new version provides significant changes in the backup object naming and handling to allow exploitation of these automatic data management features in TSM. * Support and Exploitation of Exchange 2000 - support for multiple storage groups - backup/restore of individual databases within a storage group - parallel backup/restore of separate storage groups - restore log and patch files to a temporary location *Exploitation of Win2000 Installer Here is the nomination form: Tivoli Data Protection for Exchange V2 Beta Test Nomination Form Company Info Company Name: Address1: Address2: Country: Customer Contact Info - name: title: email address: phone number: fax number: 1.) How many Exchange servers and what release levels are currently in use at your company? 2.) What levels of Exchange server would you be able to use in the beta test? 3.) What levels of Windows NT/2000 server would you be able to use in the beta test? 4.) What features of Exchange 2000 backup architecture do you wish to exploit? 5.) Do you have plans to migrate your production servers to Exchange 2000 in the 1st half of 2001 (or sooner)? If not, when? 6.) What is the range of database sizes you would be able to use in the beta test? 7.) Are you currently using the TDP for Exchange V1 product? If so, what release level? 8.) Are you currently using any other TDP clients? If so, which? 9.) What release level of TSM server do you have..and on what platform? 10.) Would you be willing to upgrade the TSM server for this beta test if necessary? 11.) What level(s) of TSM clients are you using on your NT systems? 12.) Do you have available resource (both people and test environment) to be able to exercise the TDP for Exchange V2 Beta code in a timely fashion? Thank you for your interest in participating in the beta test of TDP for Exchange V2. Customer selection for participation will be completed by the end of August and all those submitting nomination forms will be notified soon thereafter whether or not they are selected for participation. Tivoli Data Protection Development [EMAIL PROTECTED] ==
Re: alternate plan for DASD primary pools...
I've tried something similar (AIX server 3.1.1.5) on SSA disks.
It did not work. In fact, I would say that it was disastrous.
I'd considered doing something like this for a couple of years,
and finally "just did it" and paid in pain. For one thing, the
combination of MAXSCRATCH and MAXCAP with multiple storage pools
is very tricky. If you have a total of 50GB of disk, with 5
storage pools, you might think to set MAXCAP at 1GB and
MAXSCRATCH at 50. But which storage pool will get the MAXSCRATCH
of 50? If you set all five of your storage pools to
MAXSCRATCH=50, and your devclass MAXCAP=1GB, you will end up in
the situation where *each* of the five storage pools will attempt
to create 50 1GB volumes. At some point, when your filesystem is
full, ADSM will complain that your server is out of storage
space, because it has gone and created 250 partially full volumes
in each of your five storage pools.
I never quite understood or investigated why, but
backups/archives would fail at that stage, rather than simply
move on the the pool defined by NEXTSTGPOOL. I was too frustrated
by the experience to bother.
I had wanted to implement something exactly as you described. I
had a bunch of disk space for my disk pools, and I needed to have
multiple disk pools so that they could migrate to different pools
(if you search the depths of the archives, there is a thread from
'98 or so regarding one disk pool migrating to multiple tape
pools). All we really want is one big landing pad for all
incoming data. We don't want to have to micromanage that set of
disks. It's all there, and it's all available, but the way ADSM
is currently structure, you must preallocate that storage space
to one pool or another.
With my experience, I would recommend against what you are trying
to do. Go with regular disk pools.
CAVEAT: We are on 3.1.1.5 of the AIX server--yes it's down rev,
it also works; we're not in the QA business :-). I can't speak to
whether these issues are addressed/fixed in any newer releases of
{AD,T}SM.
-- Tom
Thomas A. La Porte
DreamWorks SKG
[EMAIL PROTECTED]
On Wed, 2 Aug 2000 [EMAIL PROTECTED] wrote:
>Greetings, all.
>
>I'm kicking around a near-total reconstruction of my disk pools, as we're
>getting some new DASD in before too long, and I'll therefore have an "empty
>tile" to play with. I wanted to trot out the plan I was considering, and let
>some other clue poke holes in it. :)
>
>
>Currently, we've got ~54G of primary DISK pools. These are partitioned in a
>fairly copplex way, with the aim of maximizing the number of spindles I can
>hand to my stgpools, regardless of their size.
>
>So, a ~4G stgpool gets two 1.7G volumes, each on a different spindle. My
>biggest stgpool (18G) has four 4G and a 1.7G, each on different spindles.
>
>And so on.
>
>This is useful so long as I am correct in my incremetal-size estimations, but
>I have to plan each stgpool for the "reasonable maxiimum" of an incremental,
>which means that for some I have, say, 4G allocated but almost never use more
>than 2.
>
>So much for the sad story. Now to what I plan to do about it:
>
>
>When I get my new disk in, I plan to make a single RAID5 volume, and make a
>directory on it for a FILE devclass. I'll permit something large like 50
>mounts on that class, and I'll make the volume size somewhere around 250M.
>
>I'll define stgpools against this devclass, and I'll control their peak size
>with MAXSCRATCH directives. My 2G stgpool will have maxscratch=8, and so on.
>
>This will give me most of the speed of my current solution (minus the RAID
>overhead) and permit the stgpools to grow and shrink as demand varies.
>
>I could even generate a second stgpool on the same AIX volume, for my dinky,
>numerous workstation backups, with a volume size of ca. 100M, and colocate it.
>
>
>
>Thoughts? Is the raid5 on the stgpools a _drastic_ performance hit? (my
>bottleneck is currently the database, and then the network. Disk speed is a
>distant third)
>
>
>- Allen S. Rout
>
Re: Issue with door extension on 9710
It's been quite a while, and my memory is rusty -- but let me guess. You just added the door extension, right? We haven't done that, but I seem to remember a similar problem when we added additional tape drives and had to re-configure the 9710 microcode. As I recall, we ended up deleting the drives AND the library, and then re-adding them. ADSM seems to check maximum drives/slots at library definition time, and doesn't (or didn't back then) have any method of changing on the fly. The good news is that you should be able to do this with no real repercussions -- 1) delete all tape drives (required to delete the library -- but get a listing first :-) 2) delete the library 3) define the library 4) define the drives 5) audit the library should do it . . . we were under ADSM 3.1.2.20 when we ran into this, IIRC. Tom Kauffman NIBCO, Inc > -Original Message- > From: Long, Matt [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, August 02, 2000 3:19 PM > To: [EMAIL PROTECTED] > Subject: Issue with door extension on 9710 > > > All, > > Has anyone seen this type of error? For some reason ADSM does > recognize the door extension. We are running 3.7.3 server. > > 08/02/00 15:55:51 ANRD mmsscsi.c(4404): Element > address mismatch; > > slotInfo.elem = 392, slotInv.addr = 0 > > 08/02/00 15:55:51 ANR8460E AUDIT LIBRARY process for > library STK9710D > > failed. > > Matt Long > Systems Administration > Marriott International > 301-696-2690 >
Re: Tsm 4.1 client.
InstallShield for the Web was discussed and discarded since, as far as we are able to determine, it does not provide for a silent install. There are a lot of users for whom silent install is very important. As far as other methods go, we provide a companion .BAT file to help with the extraction (complete with HELP info if you just run the BAT file without a parameter), and a README.FTP file that tells you how to download and extract the install image. 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." > When you extract the file, you need to use the -d flag. ... Will someone please show the idiots at Tivoli "InstallShield for the Web" or any number of other methods. Forcing "joe user" to run a command with a fixed parameter is cruel and unusual punishment ... and what must be fine software look like ... never mind (again). Wayne T. Smith [EMAIL PROTECTED] ADSM Technical Coordinator - UNET University of Maine System
Re: Tsm 4.1 client.
In article <[EMAIL PROTECTED]>, "Robinson, Cris" <[EMAIL PROTECTED]> says: > >Well said Wayne! > For the ba_dsm.opt file you can just use dsm.opt in the config directory. I did not check on the sa_dsm.opt file. len >And another thing... what happened to the BA_DSM.OPT and SA_DSM.OPT template >files that you could customize?
Re: ibm3494 question
On Wed, 2 Aug 2000, Joe Faracchio wrote: > we don't have a window but from what I read and understand it should work. With the convience I/O door, just issue checkout's with remove=yes. The I/O station can be either 10, or 30, depending on what you purchased. Once the I/O door slots are full, remove them, and do the rest, if necessary. For checkin's, put them in the convience I/O slots, and close the door to it. The library will put the tapes away. Once that is done, issue the checkin command. Mind is: checkin libvol 3494 search=yes checklabel=no stat=scr volr=a0,a9 devt=3590 > > Without a window but with a bulk output area my experience is this: > > for output we use remove=yes and the 10 slots we have reserved get filled. > and then an INT REQ occurs > > for input we open the door check that no tapes are mounted and then just > put the tapes in any free slot available. with checkin or label you have > to use the search=yes for a range it appears adsm just asks for the tape > and the robot obliges. > > ... joe.f. > > Joseph A Faracchio, Systems Programmer, UC Berkeley > > > On Wed, 2 Aug 2000, Gerald Wichmann wrote: > > > On an ibm3494 hooked up to an ibm h70 running aix 4.3.3 and tsm 3.7.3, what > > the procedure to checking out 30 tapes? I am familiar with smaller magstar > > libraries where a simple checkout libvol command will spit the tape out of > > the entry/exit port. Does this also work with the ibm3494 or do I need to > > use the console at the rear of the library? Reason Im asking is Im trying > > to determine how much operating intervention will be required to do this (I > > am remote of the 3494). > > > > Secondly, I also need to check in 30 tapes. Again with magstars that Im > > familiar with I could have the tapes placed in the entry/exit port and > > remotely issue checkin libvol commands within TSM and the library sucks the > > tape in and does all the work. Can I have an operator stick 30 blank > > pre-labelled tapes into the 3494 and then do a checkin command without > > instructing him to go to the console? > > > > Appreciate any help on the details of doing these two steps! > > > > > > Gerald Wichmann > > RS Engineer > > Sansia System Solutions > > 408-844-8893 work > > 408-844-9801 fax > > > > Steve Roder, University at Buffalo VM Systems Programmer UNIX Systems Administrator (Solaris and AIX) ADSM Administrator ([EMAIL PROTECTED] | (716)645-3564 | http://ubvm.cc.buffalo.edu/~tkssteve)
Re: ibm3494 question
we don't have a window but from what I read and understand it should work. Without a window but with a bulk output area my experience is this: for output we use remove=yes and the 10 slots we have reserved get filled. and then an INT REQ occurs for input we open the door check that no tapes are mounted and then just put the tapes in any free slot available. with checkin or label you have to use the search=yes for a range it appears adsm just asks for the tape and the robot obliges. ... joe.f. Joseph A Faracchio, Systems Programmer, UC Berkeley On Wed, 2 Aug 2000, Gerald Wichmann wrote: > On an ibm3494 hooked up to an ibm h70 running aix 4.3.3 and tsm 3.7.3, what > the procedure to checking out 30 tapes? I am familiar with smaller magstar > libraries where a simple checkout libvol command will spit the tape out of > the entry/exit port. Does this also work with the ibm3494 or do I need to > use the console at the rear of the library? Reason Im asking is Im trying > to determine how much operating intervention will be required to do this (I > am remote of the 3494). > > Secondly, I also need to check in 30 tapes. Again with magstars that Im > familiar with I could have the tapes placed in the entry/exit port and > remotely issue checkin libvol commands within TSM and the library sucks the > tape in and does all the work. Can I have an operator stick 30 blank > pre-labelled tapes into the 3494 and then do a checkin command without > instructing him to go to the console? > > Appreciate any help on the details of doing these two steps! > > > Gerald Wichmann > RS Engineer > Sansia System Solutions > 408-844-8893 work > 408-844-9801 fax >
NDS backups
My network guy was monitoring a backup and asked me if the number that appears after the" Normal File-->" is the size of the file being backed up. It appears all of these files are the same size and he is telling me they shouldn't be very large. Could TSM be using up space unnecessarily? This is a Netware 4.11 server with TSM 3.7.1 on it. Can someone give me some information? Normal File--> 2,097,152 .[Root].O=HUM.OU=Area42.OU=PIN.CN=Lms6224 [Sent] Normal File--> 2,097,152 .[Root].O=HUM.OU=Area42.OU=PIN.CN=Mjr3663 [Sent] Normal File--> 2,097,152 .[Root].O=HUM.OU=Area42.OU=PIN.CN=Mmf2355 [Sent] Normal File--> 2,097,152 .[Root].O=HUM.OU=Area42.OU=PIN.CN=Mmk7095 [Sent] Normal File--> 2,097,152 .[Root].O=HUM.OU=Area42.OU=PIN.CN=MWH4505 [Sent] Normal File--> 2,097,152 .[Root].O=HUM.OU=Area42.OU=PIN.CN=Netman [Sent] Normal File--> 2,097,152 .[Root].O=HUM.OU=Area42.OU=PIN.CN=NetShield_PI MKT1 [Sent] Normal File--> 2,097,152 .[Root].O=HUM.OU=Area42.OU=PIN.CN=PINMKT1
ibm3494 question
On an ibm3494 hooked up to an ibm h70 running aix 4.3.3 and tsm 3.7.3, what the procedure to checking out 30 tapes? I am familiar with smaller magstar libraries where a simple checkout libvol command will spit the tape out of the entry/exit port. Does this also work with the ibm3494 or do I need to use the console at the rear of the library? Reason Im asking is Im trying to determine how much operating intervention will be required to do this (I am remote of the 3494). Secondly, I also need to check in 30 tapes. Again with magstars that Im familiar with I could have the tapes placed in the entry/exit port and remotely issue checkin libvol commands within TSM and the library sucks the tape in and does all the work. Can I have an operator stick 30 blank pre-labelled tapes into the 3494 and then do a checkin command without instructing him to go to the console? Appreciate any help on the details of doing these two steps! Gerald Wichmann RS Engineer Sansia System Solutions 408-844-8893 work 408-844-9801 fax
ADSM 3.1.2.20 under NT Service Pack 6?
Greetings *SM'ers! I have a customer with ADSM 3.1.2.20 running under NT 4 Service Pack 5, but they would like to install Service Pack 6. Do any of you know of any problems related to this? They would like to anticipate it up from as much as possible. Thanks, John Schneider *** * John D. Schneider Email: [EMAIL PROTECTED] * Phone: 636-651-4641 * Lowery Systems, Inc. * 1329 Horan Disclaimer: Opinions expressed here are * Fenton, MO 63026 mine and mine alone. ***
Issue with door extension on 9710
All, Has anyone seen this type of error? For some reason ADSM does recognize the door extension. We are running 3.7.3 server. 08/02/00 15:55:51 ANRD mmsscsi.c(4404): Element address mismatch; slotInfo.elem = 392, slotInv.addr = 0 08/02/00 15:55:51 ANR8460E AUDIT LIBRARY process for library STK9710D failed. Matt Long Systems Administration Marriott International 301-696-2690
Attention: TDP for SQL V2 - Beta Program Nomination Form
Customers interested in participating in the beta test of Tivoli Data Protection for SQL V2 should fill out = the following form and send it to: [EMAIL PROTECTED] Nominations will be accepted until 8/18/2000. The beta test is expected to start in late September or early October. Highlights of V2 of TDP for SQL are as follows: * Automatic Expiration and version control by TSM server policy => The current product stores each backup object with a unique name thereby circumventing the automatic expiration and version control provided by the TSM server. The new version provides significant changes in the backup object naming and handling to allow exploitation of these automatic data management features in TSM. * Support for Differential backup/restore of SQL databases * Support for backup/restore of individual file groups * Support for backup/restore of individual db files * Support for backup/restore of a set of file groups and files * Support for SQL Data Striping => multiple parallel sessions to backup/restore individual objects. This capability, together with the additional granularity described in the prior bullets greatly improves manageability of Very Large DataBases (VLDBs) * Support and Exploitation of SQL 2000 - Restore to a named mark - Partial restores - Support multiple SQL server instances on the same machine - Restore using fewer data stripes than were used on backup * Restore to a Standby SQL server * Restore to different physical file names * Exploitation of Win2000 Installer Here is the nomination form: === Tivoli Data Protection for SQL V2 Beta Test Nomination Form Company Info Company Name: Address1: Address2: Country: Customer Contact Info - name: title: email address: phone number: fax number: 1.) How many SQL servers and what release levels are currently in use at your company? 2.) What levels of SQL server would you be able to use in the beta test? 3.) What levels of Windows NT/2000 server would you be able to use in the beta test? 4.) What features of SQL 7 or SQL 2000 backup architecture do you wish to exploit? 5.) What is the range of database sizes you would be able to use in the beta test? 6.) Are you currently using the TDP for SQL V1 product? If so, what release level? 7.) Are you currently using any other TDP clients? If so, which? 8.) What release level of TSM server do you have..and on what platform? 9.) Would you be willing to upgrade the TSM server for this beta test if necessary? 10.) What level(s) of TSM clients are you using on your NT systems? 11.) Do you have available resource (both people and test environment) to be able to exercise the TDP for SQL V2 Beta code in a timely fashion? Thank you for your interest in participating in the beta test of TDP for SQL V2. Customer selection for participation will be completed by the end of August and all those submitting nomination forms will be notified soon thereafter whether or not they are selected for participation. Tivoli Data Protection Development [EMAIL PROTECTED]
Re: Three questions
>"file thought to be compressed but was not Fred - This is one that keeps coming up...which the developers could certainly handle better to make the reason apparent, given the cause. The files were backed up by a higher level client, then attempted restoral with a lower level client. Richard Sims, BU
Three questions
First, let me thank those who helped resolve our recent uncertainty about a shared 3494. Three unrelated questions. 1. A user is having difficulty restoring files. His explanation: >Hello Fred, > >Just a bit more information. > >I haven't been able to restore any files. I tried restore 3 excel files >from my directory to 3 different places(on my local drive, to a new place on >ais-1, and to the original location). > >All failed with the same message > >"file thought to be compressed but was not >"report how you got this" > >all this was through the gui Version 3, release 7 level 1.0 > >louis I've changed to boldface the error message that I can find no explanation for. Has anyone seen this message? (He claims there's nothing in the error log.) 2. Does the "AUTHQUERY" option also govern the execution of scripts? I'd like to prevent people from doing an adhoc select query, sut if I do that can they still run scripts? 3. Is there an easy way to copy scripts from one server to another? I'm not looking forward to hand typing from one AIX machine to another. TIA Fred Johanson System Administrator, ADSM S.E.A. University of Chicago 773-702-8464
Restoring inactive file to Novell
Hello, I'm wondering how to restore an inactive file to a Novell client. In Windows, I'd use the GUI to select "show inactive files", but since there's no GUI with the Novell client, how is it done? Thanks, /Tomas Tomas Hallin Affinity Technology Group Columbia, SC
alternate plan for DASD primary pools...
Greetings, all. I'm kicking around a near-total reconstruction of my disk pools, as we're getting some new DASD in before too long, and I'll therefore have an "empty tile" to play with. I wanted to trot out the plan I was considering, and let some other clue poke holes in it. :) Currently, we've got ~54G of primary DISK pools. These are partitioned in a fairly copplex way, with the aim of maximizing the number of spindles I can hand to my stgpools, regardless of their size. So, a ~4G stgpool gets two 1.7G volumes, each on a different spindle. My biggest stgpool (18G) has four 4G and a 1.7G, each on different spindles. And so on. This is useful so long as I am correct in my incremetal-size estimations, but I have to plan each stgpool for the "reasonable maxiimum" of an incremental, which means that for some I have, say, 4G allocated but almost never use more than 2. So much for the sad story. Now to what I plan to do about it: When I get my new disk in, I plan to make a single RAID5 volume, and make a directory on it for a FILE devclass. I'll permit something large like 50 mounts on that class, and I'll make the volume size somewhere around 250M. I'll define stgpools against this devclass, and I'll control their peak size with MAXSCRATCH directives. My 2G stgpool will have maxscratch=8, and so on. This will give me most of the speed of my current solution (minus the RAID overhead) and permit the stgpools to grow and shrink as demand varies. I could even generate a second stgpool on the same AIX volume, for my dinky, numerous workstation backups, with a volume size of ca. 100M, and colocate it. Thoughts? Is the raid5 on the stgpools a _drastic_ performance hit? (my bottleneck is currently the database, and then the network. Disk speed is a distant third) - Allen S. Rout
Restore Speeds : Collocated vs Not
Does anyone have some performance numbers from a non collocated restore and then from a collocated restore of the same data/server? Thanks! Mooney
Re: Tsm 4.1 client.
yes i did it with -d flag. install tesed working ok , thnaks a lot.
Re: Tsm 4.1 client.
Well said Wayne! And another thing... what happened to the BA_DSM.OPT and SA_DSM.OPT template files that you could customize? Oh well. C __ Cris Robinson Sr. Technical Analyst Enterprise Storage Management / TSM Liberty Mutual Insurance Portsmouth, New Hampshire 603.431.8400.54837 mailto:[EMAIL PROTECTED] > -Original Message- > From: Wayne T. Smith [SMTP:[EMAIL PROTECTED]] > Sent: Wednesday, August 02, 2000 1:04 PM > To: [EMAIL PROTECTED] > Subject: Re: Tsm 4.1 client. > > > When you extract the file, you need to use the -d flag. ... > > Will someone please show the idiots at Tivoli "InstallShield for the > Web" or any number of other methods. Forcing "joe user" to run a > command with a fixed parameter is cruel and unusual punishment ... > and what must be fine software look like ... never mind (again). > > Wayne T. Smith [EMAIL PROTECTED] > ADSM Technical Coordinator - UNET University of Maine System
Re: 3590 K
Steve,Hi! Can't a 3494 have two distinct scratch pools defined for a system. Right now I have x'0190' and x'0192' where x'0190' is 'owned-inuse' and x'0192' is 'owned-scratch' and '' is insert, etc. So why not an x'0193' for 'owned-scratch-alternate'? I already have my onsite pool pointing to devc=3590 ... BUT ... my offsite pool pointing to devc=3590C a little trick I decided to use after having two 15-slot DLT boxes for a year. :-) So I can just have onsite scratches pointing to "K" only tapes? joe.f. Joseph A Faracchio, Systems Programmer, UC Berkeley
Re: 3590 K
> I think what Eliza was asking and I too would like an experienced answer > on is "cohabitation." > > Could I keep an offsite copypool that is "J" tapes and an onsite > "K" library? If all I have are "E" drives that can read/write "J" and > "K"s??? To do this, I think you would have to assign your J tapes to the copypool, and the K tapes to the primary, and manage the scratch pools yourself, more or less manually, via define volume. Unless you could partition the library into multiple logical libraries, and checkin J's to one, and K's to the other. I have never done this with a 3494, but I would guess that means "dedicating" drives to each logical library, which is probably not something most shops can afford. > Re-cycling the "J"s for offsite only is ideal as I only send tapes that > have reached "FULL" status off to Arcus every Wed. I'm not really sure why this makes a difference. Come Wed., no matter if your copypool is on J's or K's, you will have as many "filling" tapes as you run "backup stgpool" processes. So, if you run one process to backup your primary pool, you will have one filling tape, and some number of Full tapes. Now, if the filling tape is a K, then you may have more data not going offsite that day than if the filling tape were a J, but then, you could then decide to mark it R/O and send it offsite anyway... ...but, perhaps I am missing something about your setup and schedule... Steve Roder, University at Buffalo VM Systems Programmer UNIX Systems Administrator (Solaris and AIX) ADSM Administrator ([EMAIL PROTECTED] | (716)645-3564 | http://ubvm.cc.buffalo.edu/~tkssteve)
Warning to Network Associates Netshield users: Upgrade to ver.4.5 kills ADSM performance
We are running ADSM Client Version 3.1.0.8 For WindowsNT We upgrade our Networks Associates Netshield to Version 4.5 on four of our servers over the weekend, and on all four servers, the average backup time increased by about 20 times. (A former 5 minute backup now takes almost 2 hours) Using the pre schedule commands to stop the McShield service during the backup returns the backup times to normal.
Re: Tsm 4.1 client.
> When you extract the file, you need to use the -d flag. ... Will someone please show the idiots at Tivoli "InstallShield for the Web" or any number of other methods. Forcing "joe user" to run a command with a fixed parameter is cruel and unusual punishment ... and what must be fine software look like ... never mind (again). Wayne T. Smith [EMAIL PROTECTED] ADSM Technical Coordinator - UNET University of Maine System
Re: 4.1 client for Windows
Andy Raibeck wrote, in part.. > The TSM 4.1 clients are supported only on TSM 3.7 and 4.1 > servers. Theoretically the 4.1 client might run on an ADSM > 3.1 server, but such a configuration is UNSUPPORTED. This > means that if you try to run the 4.1 client with a 3.1 server, > it might work, but you do so at your own risk!!! > > Translation: Don't do it! (not to Andy Raibeck...) Translation: Tivoli will begrudgingly take your money for Tivoli ADSM/VM v3.1, but won't test the v4.1 clients with it. Maybe to attract and keep enough good workers to support what the customers want, I should offer: Bring your testing lab to Maine. People will love the summers here. And in the winter ... How far can you go on a snowmobile with a full tank of gas? (Not far enough to get a high-paying job like Tivoli execs no doubt enjoy). Land cheap. Can arrange TIFs and other incentives. Must be able to spell "VM" though. Never mind. Wayne T. Smith [EMAIL PROTECTED] ADSM Technical Coordinator - UNET University of Maine System
Re: ADSM for DB2 HACMP
Eric, Is there something else that's overriding the DSMI_CONFIG and DSMI_DIR settings, in a script that runs the backups? I'd recomend using a different name for the DB2 databases, rather than the node names. This way the data for DB2 is controlled seperately from the node data, making things easier on you (except when you failover HACMP - you'll have to come up with a trick to keep the passwords in synch between the two HACMP nodes). Nick Cassimatis [EMAIL PROTECTED] "I'm one cookie away from happy." - Snoopy (Charles Schulz)
Re: 3590 K
I think what Eliza was asking and I too would like an experienced answer on is "cohabitation." Could I keep an offsite copypool that is "J" tapes and an onsite "K" library? If all I have are "E" drives that can read/write "J" and "K"s??? Re-cycling the "J"s for offsite only is ideal as I only send tapes that have reached "FULL" status off to Arcus every Wed. thanks ... joe.f. Joseph A Faracchio, Systems Programmer, UC Berkeley On Wed, 2 Aug 2000, Steven P Roder wrote: > > > We have been using them since 6/25. We have 300 3M K tapes. No prolems > > > at all. We paid around $60/each, including labeling and initialization, > > > although the vendor did properly label then internally for AIX/ADSM, as I > > > had to label them all. > > > > Hi Steve, > > > > We are also looking into the K tapes. Can the 3590-E1A drives with Extended > > Media Support r/w both the old J tapes and the Extended Length K tapes? Can > > I use both kind of tapes or do I have to replace all 1000 J tapes with K > > tapes? > Hi Eliza, > > Yes, the E drives can write to both the J and K tapes. With the J's, > you will have to mark all of your "filling" tapes R/O at conversion time. > Once those tapes cycle back to scratch, and are reused by TSM, they will > be reused at the new density, doubling their capacity. The K's can also > read the 128track J tapes. If you do not upgrade all of your drives at > the same time, and have to mix B and E drives, you will have to create a > new storage pool, and a second logical library. I would recommend against > this, if at all possible. The readme file for the TSM server has a good > section on conversion of B to E drives. > > Hope this helps, > > > Steve Roder, University at Buffalo > VM Systems Programmer > UNIX Systems Administrator (Solaris and AIX) > ADSM Administrator > ([EMAIL PROTECTED] | (716)645-3564 | http://ubvm.cc.buffalo.edu/~tkssteve) >
Re: Why not use many cheap disks as a PRIMARY stg?
and if you are going for max capacity (large number of physical devices) in order to NOT run out of slots in your processor for device controller cards, you probably want to be looking at SSA disks ;-) Dwight > -- > From: Roger C Cook[SMTP:[EMAIL PROTECTED]] > Reply To: ADSM: Dist Stor Manager > Sent: Wednesday, August 02, 2000 9:59 AM > To: [EMAIL PROTECTED] > Subject: Re: Why not use many cheap disks as a PRIMARY stg? > > ADSM considerations aside, from a hardware view in this environment SCSI > is > definitely the way to go. Not only is SCSI superior handling multiple > simultaneous accesses, it is much less CPU intensive. When a SCSI drive is > accessing, it normally uses 10-20% of the CPU, where IDE can use between > 70-90%. That's why on a desktop system using IDE, when you transfer large > amounts of data (such as copy one drive to another) the system becomes > extremely sluggish during the transfer. SCSI will not normally have this > impact. IDE may have evolved to surpass SCSI in some aspects, but SCSI is > still the only choice in a server/multi-access environment. > > Roger C Cook > RCG Information Services > > > Hi, > > Recently, we're trying to decide about the various ways in which TSM can > be > set up. We need about 2Tb of primary pool space. For primary pool only , > we > may either: > > 1) Get a big library, and a lot of tapes, amounts to >$50.000. (With the > lib > we can also maintain the copy pool) > > 2) Get a bunch of IDE-disk cabinets, and a lot of 70 Gb IDE disks, amounts > to $25.000 or so (of course we will also need a small library for the copy > pool). These cabinets have a scsi interface. > > It seems IDE disks are not only the cheaper, but also the much faster > solution for daily retrieve operations. In this case we would opt for a > RAID-5 IDE set for primary stg (but also a fast(er) SCSI system for the DB > and LOG). With this amount of disks some are bound to crash every now and > then, RAID-5 helps. All in all, the TSM server only 'sees' scsi. > > One cabinet would show up like one disk, in reality 70Gb disk times 7 > disks > = 0.5 Tb/cabinet, which is a rather big 'disk' size. > > Question 1) However, on the forum no-one seems to use a PRimary IDE > (PRIDE) > disk pool? Why? I'm i missing something or what? > > Question 2) If PRIDE seems like a good solution, would the better way to > use > DISK devices (any TSM limits?, caused by size or sheer number of DISK > volumes on the PRIDE disk) or FILE devices (but fragmenting files all over > the disks, and need of reclaim) > > Question 3) Any (other) TSM limits endangering this plan (we are talking > about 2Tb or more on disk...) > > Of course OS limits have been accounted for. It seems AIX and NT are OK. > > Thank you, > > > Allshare Personnel BV > Jochem van Hal > TSM admin > [EMAIL PROTECTED] >
Re: DRM
Well, if you have a nice fresh RS/6000 with nothing but the rootvg and a bunch of disks & tape drives you do a fresh install of TSM server code You then use the "database restore tapes" to perform a dsmserv restore db now you have your TSM environment up and running but all your primary storage pools are gone, they burned up with the server over in that location that the 747 crashed into... You then use the "storage pool restore tapes" to get back the actual data that all the clients will need to restore to get THEIR disaster recovery machines up and running. hope this helps later, Dwight > -- > From: Shekhar Dhotre[SMTP:[EMAIL PROTECTED]] > Reply To: ADSM: Dist Stor Manager > Sent: Wednesday, August 02, 2000 9:30 AM > To: [EMAIL PROTECTED] > Subject: DRM > > <> > hello everyone, > > i want to know > 1.difference between database restore tapes , storage pool restore tapes ? > pls. help me? as i am confused , i am reading > Tivoli storage manager for AIX :Administrators Guide , but not finding > refernce. > > Everymorning , i get amail from TSM as a following > > Subject: Disaster Recovery Infomtion for ADSM > > > > Recovery Plan for Server TSM > Created by DRM PREPARE on 08/02/00 10:00:01 > DRM PLANPREFIX /tsm/drm/drm > Storage Management Server for AIX-RS/6000 - Version 3, Release 7, Level > 2.0 > > > Volumes required for data base restore > > Location = VAULT > Device Class = STK9710 > Volume Name = >MED540 > > Volumes required for storage pool restore > > Location = > Copy Storage Pool = COPYPOOL > Device Class = STK9710 > Volume Name = >MED517 >MED541 > > Location = VAULT > Copy Storage Pool = COPYPOOL > Device Class = STK9710 > Volume Name = >MED500 >MED501 >MED502 >MED503 >MED505 >MED506 >MED507 >MED508 >MED509 >MED510 >MED511 >MED512 >MED513 >MED514 >MED520 >MED521 >MED522 >MED523 >MED524 >MED525 >MED526 >MED527 >MED528 >MED529 >MED530 >MED531 >MED532 >MED533 >MED534 >MED535 >MED536 >MED537 >MED538 >MED539 > >
Re: Why not use many cheap disks as a PRIMARY stg?
On 2 Aug 00, at 11:53, Jochem van Hal wrote: > 2) Get a bunch of IDE-disk cabinets, and a lot of 70 Gb IDE disks, > amounts to $25.000 or so (of course we will also need a small library > for the copy pool). These cabinets have a scsi interface. On 2 Aug 00, at 10:59, Roger C Cook wrote: > ADSM considerations aside, from a hardware view in this environment > SCSI is definitely the way to go. Not only is SCSI superior handling > multiple simultaneous accesses, it is much less CPU intensive. When a > SCSI drive is accessing, it normally uses 10-20% of the CPU, where IDE > can use between 70-90%. That's why on a desktop system using IDE, when > you transfer large amounts of data (such as copy one drive to another) > the system becomes extremely sluggish during the transfer. SCSI will not > normally have this impact. IDE may have evolved to surpass SCSI in some > aspects, but SCSI is still the only choice in a server/multi-access > environment. > This is not the point, because the RAID controller in these cabinets, usually an i960 chip, handels the IDE load and presents the RAID set as one SCSI (SE or LVD) disk to the server. We are using about 10 of these boxes since two years for several purposes in multiuser environments with good success. We never had any problem with them, except the laughter from collegues ;-) The throughput is not overwhelming, about 15 MByte/s, interestingly regardless of RAID Level 0 or 5. There are new ones out with Intel i960RN 64bit Processor which are said to be twice as fast for reading and 50% faster for writing. The point why we are not using these boxes but an expensive SCSI RAID box as the primary pool with the ADSM Server is that in some cases (archive, hsm) the version of some date on your primary pool might be the only existing version. Given that - the memory cache of the IDE boxes consists of simple PC memory modules without ECC - cache mirroring is not available - there is no meta communication between RAID and server. - there is no sniffing for bad blocks in the RAID software, - you cannot build several RAID sets with a global hot spare disk thus having one 400 GByte disk which takes several hours to copy to tape I would argue that this solution is - let's say one order of magnitude less secure than a decent SCSI RAID. In other words, you have to decide how much money the difference between 99,99 and 99,999 is worth. However, if your choice is in fact, to have a primary pool on *tape* without any disk pool (which makes sense only when you have very few clients AFAIK) or to have one on IDE RAID's, I would recommend the latter. At least, from my experience the ratio of unreadable tapes to damaged disks to (usually due to operator mistakes) damaged RAID sets is about 100:10:1. Regards, Michael Bruewer Dr. Michael Br"uwer RZ der Univ. Hohenheim 70593 Stuttgart [EMAIL PROTECTED] www.uni-hohenheim.de/~bruewer Fon: +49-711-459-3838 Fax: -3449 PGP Public Key: RSA: http://www.uni-hohenheim.de/~bruewer/pgpkey_V2
Re: Why not use many cheap disks as a PRIMARY stg?
ADSM considerations aside, from a hardware view in this environment SCSI is definitely the way to go. Not only is SCSI superior handling multiple simultaneous accesses, it is much less CPU intensive. When a SCSI drive is accessing, it normally uses 10-20% of the CPU, where IDE can use between 70-90%. That's why on a desktop system using IDE, when you transfer large amounts of data (such as copy one drive to another) the system becomes extremely sluggish during the transfer. SCSI will not normally have this impact. IDE may have evolved to surpass SCSI in some aspects, but SCSI is still the only choice in a server/multi-access environment. Roger C Cook RCG Information Services Hi, Recently, we're trying to decide about the various ways in which TSM can be set up. We need about 2Tb of primary pool space. For primary pool only , we may either: 1) Get a big library, and a lot of tapes, amounts to >$50.000. (With the lib we can also maintain the copy pool) 2) Get a bunch of IDE-disk cabinets, and a lot of 70 Gb IDE disks, amounts to $25.000 or so (of course we will also need a small library for the copy pool). These cabinets have a scsi interface. It seems IDE disks are not only the cheaper, but also the much faster solution for daily retrieve operations. In this case we would opt for a RAID-5 IDE set for primary stg (but also a fast(er) SCSI system for the DB and LOG). With this amount of disks some are bound to crash every now and then, RAID-5 helps. All in all, the TSM server only 'sees' scsi. One cabinet would show up like one disk, in reality 70Gb disk times 7 disks = 0.5 Tb/cabinet, which is a rather big 'disk' size. Question 1) However, on the forum no-one seems to use a PRimary IDE (PRIDE) disk pool? Why? I'm i missing something or what? Question 2) If PRIDE seems like a good solution, would the better way to use DISK devices (any TSM limits?, caused by size or sheer number of DISK volumes on the PRIDE disk) or FILE devices (but fragmenting files all over the disks, and need of reclaim) Question 3) Any (other) TSM limits endangering this plan (we are talking about 2Tb or more on disk...) Of course OS limits have been accounted for. It seems AIX and NT are OK. Thank you, Allshare Personnel BV Jochem van Hal TSM admin [EMAIL PROTECTED]
DRM
hello everyone, i want to know 1.difference between database restore tapes , storage pool restore tapes ? pls. help me? as i am confused , i am reading Tivoli storage manager for AIX :Administrators Guide , but not finding refernce. Everymorning , i get amail from TSM as a following Subject: Disaster Recovery Infomtion for ADSM Recovery Plan for Server TSM Created by DRM PREPARE on 08/02/00 10:00:01 DRM PLANPREFIX /tsm/drm/drm Storage Management Server for AIX-RS/6000 - Version 3, Release 7, Level 2.0 Volumes required for data base restore Location = VAULT Device Class = STK9710 Volume Name = MED540 Volumes required for storage pool restore Location = Copy Storage Pool = COPYPOOL Device Class = STK9710 Volume Name = MED517 MED541 Location = VAULT Copy Storage Pool = COPYPOOL Device Class = STK9710 Volume Name = MED500 MED501 MED502 MED503 MED505 MED506 MED507 MED508 MED509 MED510 MED511 MED512 MED513 MED514 MED520 MED521 MED522 MED523 MED524 MED525 MED526 MED527 MED528 MED529 MED530 MED531 MED532 MED533 MED534 MED535 MED536 MED537 MED538 MED539 Received: from medrs2.medf.bayer.com ([10.74.96.12]) by mop0sy.intsmtp.bayer.com (Lotus Domino Build 166.1) with ESMTP id 280210183844:23036 ; Wed, 2 Aug 2000 10:18:38 -0400 Received: (from root@localhost) by medrs2.medf.bayer.com (AIX4.3/8.9.3/8.9.3) id KAA42608 for [EMAIL PROTECTED]; Wed, 2 Aug 2000 10:15:01 -0400 Date: Wed, 2 Aug 2000 10:15:01 -0400 From: [EMAIL PROTECTED] To: [EMAIL PROTECTED], [EMAIL PROTECTED] Subject: Disaster Recovery Infomtion for ADSM X-MIMETrack: Itemize by SMTP Server on MOP0SY/US/BAYER(Release 5.0 (Intl)|30 March 1999) at 08/02/2000 10:18:38 AM, Serialize by Router on MOP014/US/BAYER(Release 5.0.2b (Intl)|16 December 1999) at 08/02/2000 10:16:59 AM, Serialize complete at 08/02/2000 10:16:59 AM X-Notes-Item: Memo; name=Form X-Notes-Item: CN=MOP0SY/OU=US/O=BAYER; type=501; flags=44; name=$UpdatedBy X-Notes-Item: CN=MOP0SY/OU=US/O=BAYER, CN=MOP0SY/OU=US/O=BAYER; type=501; flags=0; name=RouteServers X-Notes-Item: 02-Aug-2000 10:18:38 EDT/02-Aug-2000 10:18:39 EDT =?us-ascii?q?=2C_?= =?us-ascii?q?02-Aug-2000?= 10:18:39 EDT/02-Aug-2000 10:18:39 EDT; type=401; flags=0; name=RouteTimes X-Notes-Item: 7174CBAD:A2904EBA-8525692F:004E9C77; type=4; name=$Orig X-Notes-Item: 2; name=$MsgTrackFlags Message-ID: <[EMAIL PROTECTED]> X-Notes-Item: 22; type=300; name=$Hops X-Notes-Item: BAYER-INTERNAL-SMTP; name=FromDomain MIME-Version: 1.0 Recovery Plan for Server TSM Created by DRM PREPARE on 08/02/00 10:00:01 DRM PLANPREFIX /tsm/drm/drm Storage Management Server for AIX-RS/6000 - Version 3, Release 7, Level 2.0 Volumes required for data base restore Location = VAULT Device Class = STK9710 Volume Name = MED540 Volumes required for storage pool restore Location = Copy Storage Pool = COPYPOOL Device Class = STK9710 Volume Name = MED517 MED541 Location = VAULT Copy Storage Pool = COPYPOOL Device Class = STK9710 Volume Name = MED500 MED501 MED502 MED503 MED505 MED506 MED507 MED508 MED509 MED510 MED511 MED512 MED513 MED514 MED520 MED521 MED522 MED523 MED524 MED525 MED526 MED527 MED528 MED529 MED530 MED531 MED532 MED533 MED534 MED535 MED536 MED537 MED538 MED539
Re: Why not use many cheap DISK...
Jochem van Hal wrote: Hi, Recently, we're trying to decide about the various ways in which TSM can be set up. We need about 2Tb of primary pool space. For primary pool only , we may either: 1) Get a big library, and a lot of tapes, amounts to >$50.000. (With the lib we can also maintain the copy pool) 2) Get a bunch of IDE-disk cabinets, and a lot of 70 Gb IDE disks, amounts to $25.000 or so (of course we will also need a small library for the copy pool). These cabinets have a scsi interface. It seems IDE disks are not only the cheaper, but also the much faster solution for daily retrieve operations. In this case we would opt for a RAID-5 IDE set for primary stg (but also a fast(er) SCSI system for the DB and LOG). With this amount of disks some are bound to crash every now and then, RAID-5 helps. All in all, the TSM server only 'sees' scsi. One cabinet would show up like one disk, in reality 70Gb disk times 7 disks = 0.5 Tb/cabinet, which is a rather big 'disk' size. Question 1) However, on the forum no-one seems to use a PRimary IDE (PRIDE) disk pool? Why? I'm i missing something or what? Question 2) If PRIDE seems like a good solution, would the better way to use DISK devices (any TSM limits?, caused by size or sheer number of DISK volumes on the PRIDE disk) or FILE devices (but fragmenting files all over the disks, and need of reclaim) Question 3) Any (other) TSM limits endangering this plan (we are talking about 2Tb or more on disk...) Of course OS limits have been accounted for. It seems AIX and NT are OK. Thank you, Allshare Personnel BV Jochem van Hal TSM admin [EMAIL PROTECTED] -- - Here is my personal opinion of how to think about backup data. 1) If only backing up data in the event of a disaster, IE: lots of DB files, and that data is hardly ever required to be restored. Keeping this data in a tape library is the best and most cost effective solution, full tapes are taken out of the library marked unavailable and the storage pool in the library can be X times the size of the amount of tapes in. Of course no space reclaim is realistic in this case, and tapes would have to be manually place a tape back in the library if needed. (We use this method with SAP/Oracle backups and a 7337) consisting of about 40 DLT(14 in library) tapes holding approx 180G each and all changes based on expiration, no reclaim. one 180G offsite copy daily runs in the same library. (Although it sounds that this library is a little small for you solution, this library runs about 22 hours a day with 180G to the storage pool and the offsite copy of said data) 2) If the storage pool which will require some restoration on a limited basis. It may still be cost effective to use a tape library. Some considerations are, if many of small files changing constantly tape transfers are not as good on performance for this, if large amounts of data that will require a lot of recliam/move of data.. time may become a issue. The initial cost of a library verse a five year cost on disk failure is not going to make disk look cheaper and if the library can hold and server the data in a manner required it will be the most cost effective solution after the five year window. 3) If the storage pool will require a lot of clients with small files and is very large and quick online access for restore, then disk is the answer. Cost is high and failure is high. I am sure others have methods of making these decisions, and may be better focused for your need. Good day, Bart
Server Instalation disturb the OleDateTime ?
Hi EveryBody ! Does someone has heard about problem in using COleDateTime from Compiled DLL (in another computer) running on a computer where TSM Server is installed ? The Code (without any call to the server) falls there inside COleDataTime, but after recompile inside the SAME computer (with the TESM Server installed) , the code doesn't fall. Strange problem. Thank You for any help ! __ Do You Yahoo!? Kick off your party with Yahoo! Invites. http://invites.yahoo.com/
Re: Export Node - Usage to fake Archiving
Well, remember that "DRM" is for Disaster Recovery of your "environment". If an SST crashes into your site, DRM is designed to allow you to build up a TSM environment with pretty recent copies of your client's data and then allow the clients to be rebuilt from your rebuilt TSM server. I classify that as being pretty different than someone just asking to keep specific data for a really long time. One example of where an "export" of the node has been used in our environment is... a bunch of seismic studies of land had been performed in preparation for drilling oil wells, it was then decided not to develop a large portion of these areas, this land is in a holding state with the possibility of being sold later, all the seismic studies (already done) could make the land more profitable... so rather than just throw the data away, it was isolated on a client, that client was backed up, that client was exported (to two different sets of tapes) and the physical client box was turned off and thrown away... (I hope those tapes hang in there...) So for the purpose of long term storage of data... if you're totally out in the blue, you're not alone... I'm out there too. Dwight > -- > From: Henrik Hansson[SMTP:[EMAIL PROTECTED]] > Reply To: ADSM: Dist Stor Manager > Sent: Wednesday, August 02, 2000 8:28 AM > To: [EMAIL PROTECTED] > Subject: Export Node - Usage to fake Archiving > > Would this "Export Node" be something that could replace the Archiving > command?. > I understand that I have to keep track of the backups, and tapes myself. > Maybe its still easier then letting DRM keep track of them and it will > reduce the space used on the server right?? (Find the archiving somewhat > tricky to set up, but I'm a newbie :-)) ) > > Or am totaly out in the blue here?? > > Henrik Hansson > Nomafa AB > Web; www.nomafa.com > Mail; [EMAIL PROTECTED] > > > > "Cook, Dwight > E" To: [EMAIL PROTECTED] > <[EMAIL PROTECTED]cc: > M> Subject: Re: Export DB - > Usage > Sent by: > "ADSM: Dist > Stor Manager" > <[EMAIL PROTECTED] > RIST.EDU> > > > 2000-08-01 > 21:14 > Please > respond to > "ADSM: Dist > Stor Manager" > > > > > > > I'm doing that... > Lots of different situations... > If they say the data is REALLY REALLY REALLY important I leave it in the > tsm > server, have it in an isolated storage pool with a copypool copy of it AND > I > export the node, twice, and give the end user one of the copies. > If it is REALLY important (like IRS data) I keep it in the server and have > an isolated primary and copy pool with it (and run periodic audits on the > volumes) > If they stand there picking their nose and say "Duh, we better keep this > around forever 'cause duh..." I just export the node, print the summary > info > from the tsm server's activity log showing ALL THE VOLUMES AND THEIR > SEQUENCE, check the tapes out of the atl and stick the tapes in a rack > with > the paper work in a folder at the end... > and when I export the client, I only export ACTIVE data... > > GOD I LOVE TSM :-) > > Dwight > > > > > -- > > From: Siciliano, Gerald > > (Moody's)[SMTP:[EMAIL PROTECTED]] > > Reply To: ADSM: Dist Stor Manager > > Sent: Tuesday, August 01, 2000 1:42 PM > > To: [EMAIL PROTECTED] > > Subject: Export DB - Usage > > > > Has anyone ever used 'export node' as long term storage for node data? > > > > I have about 24 nodes that are being retained for 10yrs, the data has > not > > been accessed since the backups were initially done. These nodes > > represent > > about 30% of my TSM server database. To reclaim the space in the DB can > > the > > 'export node' command be used for this purpose? > > > > This is just a thought I had, any suggestions? > > > > > > Thanks, > > Jerry Siciliano > > >
Re: 3590 K
> > We have been using them since 6/25. We have 300 3M K tapes. No prolems > > at all. We paid around $60/each, including labeling and initialization, > > although the vendor did properly label then internally for AIX/ADSM, as I > > had to label them all. > > Hi Steve, > > We are also looking into the K tapes. Can the 3590-E1A drives with Extended > Media Support r/w both the old J tapes and the Extended Length K tapes? Can > I use both kind of tapes or do I have to replace all 1000 J tapes with K > tapes? Hi Eliza, Yes, the E drives can write to both the J and K tapes. With the J's, you will have to mark all of your "filling" tapes R/O at conversion time. Once those tapes cycle back to scratch, and are reused by TSM, they will be reused at the new density, doubling their capacity. The K's can also read the 128track J tapes. If you do not upgrade all of your drives at the same time, and have to mix B and E drives, you will have to create a new storage pool, and a second logical library. I would recommend against this, if at all possible. The readme file for the TSM server has a good section on conversion of B to E drives. Hope this helps, Steve Roder, University at Buffalo VM Systems Programmer UNIX Systems Administrator (Solaris and AIX) ADSM Administrator ([EMAIL PROTECTED] | (716)645-3564 | http://ubvm.cc.buffalo.edu/~tkssteve)
Re: DRM eject problems
Wes, We had a similar situation at Marriott and we had a path applied with version 3.7.3.5. This patch enable us to perform a "move drmedia * wherestate=mountable tostate=vault untilee=full". This made it so that ADSM would not issue a request until the eeport was completely full. I created a script which executes this pattern in a loop until all the tapes are ejected. How are your fiber attached drives running? What are you using as a medium? Thanks Matt Long Systems Administration Marriott International 301-696-2690 -Original Message- From: DUNHAM, WES (SBCSI) [mailto:[EMAIL PROTECTED]] Sent: Wednesday, August 02, 2000 8:59 AM To: [EMAIL PROTECTED] Subject: DRM eject problems Hello Everyone, Just wondering if anybody has a fix for a problem I am having. Have an STK 9310 with 8 9840 drives, fiber attached. Have 2 40 slot caps on the library, being controlled, of course, by ACSLS. When I run move drm * wherest=mountable tost=vault, and there are several eligible tapes, only the first 4 are ejected, then once a request is generated and a reply is issued manually, the rest of the tapes are ejected. (i.eif there are 20 tapes eligible for vaulting, when the command is issued, the first 4 are checked out, then TSM generates a request, I reply to it, and then the next 16 are ejected, with a second request). I can't figure out what the limitation is. Must be something configurable in ACSLS (5.3.2). TSM Server is 3.7.3.0 (AIX). Any help would be greatly appreciated. Thanks! Wes Dunham
Export Node - Usage to fake Archiving
Would this "Export Node" be something that could replace the Archiving command?. I understand that I have to keep track of the backups, and tapes myself. Maybe its still easier then letting DRM keep track of them and it will reduce the space used on the server right?? (Find the archiving somewhat tricky to set up, but I'm a newbie :-)) ) Or am totaly out in the blue here?? Henrik Hansson Nomafa AB Web; www.nomafa.com Mail; [EMAIL PROTECTED] "Cook, Dwight E" To: [EMAIL PROTECTED] <[EMAIL PROTECTED]cc: M> Subject: Re: Export DB - Usage Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED] RIST.EDU> 2000-08-01 21:14 Please respond to "ADSM: Dist Stor Manager" I'm doing that... Lots of different situations... If they say the data is REALLY REALLY REALLY important I leave it in the tsm server, have it in an isolated storage pool with a copypool copy of it AND I export the node, twice, and give the end user one of the copies. If it is REALLY important (like IRS data) I keep it in the server and have an isolated primary and copy pool with it (and run periodic audits on the volumes) If they stand there picking their nose and say "Duh, we better keep this around forever 'cause duh..." I just export the node, print the summary info from the tsm server's activity log showing ALL THE VOLUMES AND THEIR SEQUENCE, check the tapes out of the atl and stick the tapes in a rack with the paper work in a folder at the end... and when I export the client, I only export ACTIVE data... GOD I LOVE TSM :-) Dwight > -- > From: Siciliano, Gerald > (Moody's)[SMTP:[EMAIL PROTECTED]] > Reply To: ADSM: Dist Stor Manager > Sent: Tuesday, August 01, 2000 1:42 PM > To: [EMAIL PROTECTED] > Subject: Export DB - Usage > > Has anyone ever used 'export node' as long term storage for node data? > > I have about 24 nodes that are being retained for 10yrs, the data has not > been accessed since the backups were initially done. These nodes > represent > about 30% of my TSM server database. To reclaim the space in the DB can > the > 'export node' command be used for this purpose? > > This is just a thought I had, any suggestions? > > > Thanks, > Jerry Siciliano >
No Subject
You cannot backup those DBs since they are locked by SYSTEM on NT. Instead you must backup the backup copy of them (usually in the system32/wins/backup folder as for WINS). You'll have to setup WINS to make an automatic backup of its DB in WINS manager. Remember you MUST backup WINS DB manually once for the automated process to take place. See http://support.microsoft.com/support/kb/articles/Q235/6/09.ASP for more info on backing up & restoring WINS DB. DHCP, if I remember, is saved periodically and all you have to do is backup the backup copy of the DB in system32/dhcp/backup. You also can make a copy of the DHCP registry setup information in a REG file for backup. The key is located in HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\DHCPServer\Configur ation. See http://support.microsoft.com/support/kb/articles/Q130/6/42.asp for other details on moving DHCP DB. Contains usefull information on how to back it up completely. See http://support.microsoft.com/support/kb/articles/Q145/8/81.ASP for more info & hints on DHCP & WINS. Hope this helps. Vince -Message d'origine- De : Leos Stehlik [mailto:[EMAIL PROTECTED]] Envoyé : mercredi 2 août 2000 14:30 À : [EMAIL PROTECTED] Objet : If you set serilization to shared static, TSM will try X number of retries to check if the file is closed, if it remains in open state (this propably will be your case), TSM skips these files. You should set serilization to shared dynamic to be able to backup open files, but use it with care... Leos Stehlik > Hello there > > Does anyone know if TSM 3.7+ can backup the open WINs and DHCP databases. Using > Legato currently and Legato skips these files. > Planning to set the parameter to shared static under TSM for the backup of open > files > > > > > > TIA > > > Toni
Re: DRM eject problems
Hi, Same configuration i am having ,only stk9710,(1 cap (15 vols) last week ACSLS was not ejecting mountable tapes at all , i just restarted the library and ACSLS. it worked, good luck .
Re: 4.1 client for Windows
<< Theoretically the 4.1 client might run on an ADSM 3.1 server, but such a configuration is UNSUPPORTED. This means that if you try to run the 4.1 client with a 3.1 server, it might work, but you do so at your own risk!!! Translation: Don't do it!>> Sure, now you tell me! I have not seen a problem , yet. C __ Cris Robinson Sr. Technical Analyst Enterprise Storage Management / TSM Liberty Mutual Insurance Portsmouth, New Hampshire 603.431.8400.54837 mailto:[EMAIL PROTECTED] -Original Message- From: Andy Raibeck [SMTP:[EMAIL PROTECTED]] Sent: Tuesday, August 01, 2000 7:12 PM To: [EMAIL PROTECTED] Subject:Re: 4.1 client for Windows I'm not sure if this question was answered yet, so apologies in advance I'm retreading covered ground. The TSM 4.1 clients are supported only on TSM 3.7 and 4.1 servers. Theoretically the 4.1 client might run on an ADSM 3.1 server, but such a configuration is UNSUPPORTED. This means that if you try to run the 4.1 client with a 3.1 server, it might work, but you do so at your own risk!!! Translation: Don't do it! 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." Can I run this client if my ADSM server is still at ADSM and hasn't been moved to TSM yet ? Or is this only for environments running TSM on the server as well ? Mike
DRM eject problems
Hello Everyone, Just wondering if anybody has a fix for a problem I am having. Have an STK 9310 with 8 9840 drives, fiber attached. Have 2 40 slot caps on the library, being controlled, of course, by ACSLS. When I run move drm * wherest=mountable tost=vault, and there are several eligible tapes, only the first 4 are ejected, then once a request is generated and a reply is issued manually, the rest of the tapes are ejected. (i.eif there are 20 tapes eligible for vaulting, when the command is issued, the first 4 are checked out, then TSM generates a request, I reply to it, and then the next 16 are ejected, with a second request). I can't figure out what the limitation is. Must be something configurable in ACSLS (5.3.2). TSM Server is 3.7.3.0 (AIX). Any help would be greatly appreciated. Thanks! Wes Dunham
Re: Backing up open WINs and DHCP databases
>Does anyone know if TSM 3.7+ can backup the open WINs and DHCP databases. Backing up active databases using simple incremental backup, from outside the database, is problematic because part of the database is on disk and part is in memory, and perhaps elsewhere. As a general rule, it's advisable to back up databases using an API-based utility which participates in the database environment to back it up from the inside, and thus get a consistent and restorable image. TSM provides Data Protection agents for some databases, but for others you'll have to seek another source. Richard Sims, BU
No Subject
If you set serilization to shared static, TSM will try X number of retries to check if the file is closed, if it remains in open state (this propably will be your case), TSM skips these files. You should set serilization to shared dynamic to be able to backup open files, but use it with care... Leos Stehlik > Hello there > > Does anyone know if TSM 3.7+ can backup the open WINs and DHCP databases. Using > Legato currently and Legato skips these files. > Planning to set the parameter to shared static under TSM for the backup of open > files > > > > > > TIA > > > Toni
AW:
We let Windows create a flat file of the WINS database and back it up with TSM. Kind regards Thomas Rupp > -Ursprüngliche Nachricht- > Von: Toni Banire [SMTP:[EMAIL PROTECTED]] > Gesendet am: Mittwoch, 2. August 2000 14:07 > An: [EMAIL PROTECTED] > Betreff: > > Hello there > > Does anyone know if TSM 3.7+ can backup the open WINs and DHCP databases. > Using > Legato currently and Legato skips these files. > Planning to set the parameter to shared static under TSM for the backup of > open > files > > TIA > > Toni
Re: XL format, red 3570 tapes
I would try to update the format to drive instead of 3570C >I have a problem with an 3575 L32 tape library with 2 C drives (XL format, red > 3570 tapes) connected to an Netfinity 5000 running NT 4.0 and TSM 3.7. > Client and server compression are turnd off, let the hardware do the > compression, but the drives not compress. >that this happening? > >Q DEVCLASS * F=D > >Device Class Name: 3575 >Device Access Strategy: Sequential >Storage Pool Count: 6 >Device Type: 3570 >Format: 3570C
Error with Novell Netware 5 backup
Hello everyone, When backing up my Netware 5 client I get the following error message: TSA500.NLM 5.3 259 This program cannot allocate a directory handle. ANS1087E Access to the specified file or directory is denied. I didn't get this error message the first time I backed up this client. Anyone know of any problems? My client is at 3.1.0.8 My server is at 3.1.2.54 Thanx a lot in advance, Jerry Caupain
No Subject
Hello there Does anyone know if TSM 3.7+ can backup the open WINs and DHCP databases. Using Legato currently and Legato skips these files. Planning to set the parameter to shared static under TSM for the backup of open files TIA Toni
Why not use many cheaps disk as a PRIMARY stg?
(send again, msg was misplaced as a reply under another msg) Hi, Recently, we're trying to decide about the various ways in which TSM can be set up. We need about 2Tb of primary pool space. For primary pool only , we may either: 1) Get a big library, and a lot of tapes, amounts to >$50.000. (With the lib we can also maintain the copy pool) 2) Get a bunch of IDE-disk cabinets, and a lot of 70 Gb IDE disks, amounts to $25.000 or so (of course we will also need a small library for the copy pool). These cabinets have a scsi interface. It seems IDE disks are not only the cheaper, but also the much faster solution for daily retrieve operations. In this case we would opt for a RAID-5 IDE set for primary stg (but also a fast(er) SCSI system for the DB and LOG). With this amount of disks some are bound to crash every now and then, RAID-5 helps. All in all, the TSM server only 'sees' scsi. One cabinet would show up like one disk, in reality 70Gb disk times 7 disks = 0.5 Tb/cabinet, which is a rather big 'disk' size. Question 1) However, on the forum no-one seems to use a PRimary IDE (PRIDE) disk pool? Why? I'm i missing something or what? Question 2) If PRIDE seems like a good solution, would the better way to use DISK devices (any TSM limits?, caused by size or sheer number of DISK volumes on the PRIDE disk) or FILE devices (but fragmenting files all over the disks, and need of reclaim) Question 3) Any (other) TSM limits endangering this plan (we are talking about 2Tb or more on disk...) Of course OS limits have been accounted for. It seems AIX and NT are OK. Thank you, Allshare Personnel BV Jochem van Hal TSM admin [EMAIL PROTECTED]
