Restore NT-Registry
Hy all, last weekend we had to restore a NT-Terminal-Server completely. Restoring the Registry from any tested client ended with a message similar to "Unable to restore one or more registry keys". You could click on a button and the message has gone. My question : Is this a normal message or does it say that the registry is now faulty ? And where can I see which keys the restore was unable to update. TSM-Server : aix3.3 , tsm 3.7.4 Client : WIN NT Server V4.0 Terminal-Server-Edition, tsm 3.7.2 and 4.1.1.16 (both tested) Thanks for any help Christoph
Re: Fileserver data expiration
In unix you can also use the hsm-feature of tsm. This would give your
users better comfort, since the files seems to persist at disk, and are
filled with data, when used again.
S W Branch schrieb:
>
> On unix you can use the find command to identify the files that haven't
> been modified in x number of days and copy them to another directory that
> you can then archive from.
>
> find searchpath -mtime +numberof days -exec mv {} targetpath \; -exec
> echo {} \;
>
> dsmc archive -DELETEFILEs "targetpath" >> /tmp/archive_to_adsm.log
>
> Alex Paschal <[EMAIL PROTECTED]>
> Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
>
> 03/02/2001 05:56 PM
> Any replies will be addressed to: "ADSM: Dist Stor Manager"
>
> To: [EMAIL PROTECTED]
> cc:
> Subject: Fileserver data expiration
>
> Howdy.
>
> Does anybody know of products that can check the last modification/access
> times of files, delete, and archive them?
>
> I know the BA Client (GUI) can Archive > Search (Modify and Access Date) >
> Filter, then archive/delete, but that's a manual process. I could write a
> C
> or perl program to do it, possibly using the API or piping filenames into
> DSMC, but I don't want to get into the business of writing/supporting
> custom
> software. This feels like it goes a bit beyond the level of 'admin
> scripting.' I'd like to use this product, if it exists, on both NT and AIX
> platforms.
>
> Thanks,
> Alex Paschal
> Storage Administrator
> Freightliner, LLC
> (503) 745-6850 phone/vmail
--
Mit freundlichen Grüßen
Bernhard Unold
begin:vcard
n:Unold;Bernhard
tel;work:+49 7071/29-80130
x-mozilla-html:FALSE
adr:;;
version:2.1
email;internet:[EMAIL PROTECTED]
fn:Bernhard Unold
end:vcard
Re: Auditdb
The problem is that i had just reset my TSM database two week ago, this is suggest by Tivoli support I think that there are are problem!!! is not poossible that I have a database corrupted after two week, starting with a fresh DB Davide Fanizzo System Administrator Banca Akros S.p.A. tel +390243444040 cell +393488705668 - Original Message - From: "Richard Sims" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Sunday, March 04, 2001 5:12 AM Subject: Re: Auditdb > Davide - The messages indicate that you have an ugly problem in the > TSM database. Your only recourse seems to be to restore the > database to an earlier point in time. But I strongly recommend that > you first consult Tivoli Support, to try to avoid losing data. > Richard Sims, BU > >
Lotus Domino on Solaris problem
Hello , I am trying to solve following problem - I saw similar thing some month with Del Hoobler response - but I dont like such solution too much . Problem : during backup of Lotus Domino ( 5.0.5 on Solaris 2.7 with TDPfLD 1.1.1 ) - techies did some changes in network between Domino client and server and backup proces domdsmc - goes into ... - I understand it as waiting for TSM server ( server 4.1.2.1 on W2K ) . We kill proces and try to run it once more - we received for some Domino databases following error : Backup of ebmail/database.nsf failed. Attempt to backup a database that is currently being backed up. Del responce from list was : First, make sure all backup and restore processes that are running on the Domino Server machine are stopped/killed. Then...you may have already done this...but... ...try recycling your Domino Server to see if this releases the "lock" on the database. FYI...TDP for Domino uses a backup/restore Domino R5 API to do the backup. TDP for Domino doesn't decide whether a backup is running already or not... it is the Domino R5 API that passes back the return code and message (which is why it doesn't have ACD prepended.) Thanks, Del Well - recycle of this Domino server is the very very last solution - so my question is what I am missing in dsm.sys of api client ? I guess client had to time out and clean up in Domino before end . It is really painfull that Domino client can left databases in "backup pending" status without any chance to reset them without shutdown/restart or Domino server . Any help will be highly appreciated. Petr Pøerost H.T.D., spol. s r.o. Praha , Pod prùsekem 12 Èeská republika/Czech republic e-mail [EMAIL PROTECTED]
ANS1312E Server media mount not possible
Hi Can somebody help me. A W2K Server TSM Client vers. 4.1.1 TSM server OS/390 4.1.1.0 StorageTek VSM tape library. When I run a backup, I receive the follow error message: ANS1312E Server media mount not possible Can any tell me what the problem is. Regards, Bo Nielsen FDB dataPhone: +45 4386 4671 Roskildevej 65 Fax: +45 4386 4990 DK-2620 AlbertslundE-mail: [EMAIL PROTECTED] Denmark
Re: Longlasting tape-reclamation run
I was interested in the recent items on slow reclamations - see mail from Richard Sims below. I started having problems with long-running reclamations about 18 months ago when we converted from 800MB to 20GB cartridges. We had a three-hour window in which the reclaim threshold was set to 70. With the small tapes, this worked o.k., but with the large ones, reclamations began running for many hours (not days, but certainly as much as 16 hours). Since we only have a small number of drives for the high-capacity cartridges, a reclamation holding two drives for this long caused chaos for later bits of the schedule. I posted an item here in February last year, and also raised the issue with Tivoli support. Neither provided any solution, but various things I saw along the way may still be of interest. 1. "Collocation clusters" I noticed that the tapes which ran for a long time had a large number of collocation clusters, as shown by message ANR1142I issued during reclamation. Tapes with a small number of clusters reclaimed within an hour or two and caused me no grief. I also found I could predict in advance how many clusters were on a tape by running the classic "select volume_name,node_name from volumeusage where " and counting the number of repetitions of each volume/node combination. Like Richard, I had no luck finding any useful documentation on this. 2. Influence of client type. I have clients of the following types: Novell Netware, Unix, NT, and also NT with the Lotus Notes agent. Since I have collocation on my onsite tape pool, I was able to determine that the tapes causing trouble all belonged to Notes clients. Looking at a list of my tape pool today (about 200 volumes), I can say that for the non-Notes clients, the number of clusters is always less than 10. The Notes client volumes have HUNDREDS (highest today is 967). I don't know if this is something to do with the Notes agent itself, or just a result of the fact that Notes seems to generate vast numbers of very small documents. The only hope on the horizon, for me, is that this issue will go away when the Notes servers get converted to Domino V5 and the individual email backups get replaced by a transaction log file. But maybe other kinds of client with many small files will still have a problem, especially with the way tape capacities keep increasing. 3. Why do the reclamations run so slow? I was able to determine that the process spends most of its time waiting for data from the input tape. In S/390 terms, every small burst of data transfer (few milliseconds) is followed by a Locate Block (tape search) function which takes more like 10 SECONDS. With offsite reclamations, there is an additional issue with large tapes because of the requirement to sort a potentially huge number of database entries (see below). 4. Did Tivoli help? I got excellent help from the local (Australian) IBM support, but the eventual response from the change team was that all was working as designed and that if I wanted sensible housekeeping performance I should ask for it through my marketing rep. I forwarded my correspondence to such a person but got no reply. Regret to say I didn't follow up at the time because by this stage I knew enough to be able to live with the situation. By now I assume that the response would be to say it's time to get the Notes servers upgraded to Domino 5. I know that, but the Notes people seem to have plenty else to do (and besides, they like the present ability of ADSM to recover individual emails!) 5. How do I live with it? (a) My main salvation was to use an external sheduling package to cancel reclamation processes at a specific time (can't do this from within ADSM). This allows the rest of the schedule to carry on o.k.. (b) I learned the difference between onsite reclamations (one tape at a time) and offsite reclamations (pick a bunch of volumes, sort database entries to get order for mounting input tapes, then start data transfer). (c) With onsite reclamations, I use various manual tricks, such as using Move Data into a disk pool, or selectively making volumes unavailable so a Netware tape gets reclaimed ahead of a Notes tape). I just keep my head above water, but it is a bit of a struggle. (d) With offsite reclamations, the sorting process can be quite indigestible because of the large number of files on large tapes. I find I have to keep tinkering with the reclaim threshold so it doesn't try to reclaim more than three or four volumes at a time. Geoff Fitzhardinge Australian Gas Light Company > -Original Message- > From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of > Richard Sims > Sent: Wednesday, February 28, 2001 1:59 PM > To: [EMAIL PROTECTED] > Subject: Re: Longlasting tape-reclamation run > > > > my TSM-server 3.7.2 on AIX 4.3.3 runs a tape-reclamation now for > >nearly 4 days. Why does it last so long ? > ... > >02/28/01 09:26:04
Antwort: ANS1312E Server media mount not possible
The client tries to write directly into a sequentiel storage pool and on the server the point MAX MOUNT POINTS for the client ist set to zero. __ Da E-Mails leicht unter fremdem Namen erstellt oder manipuliert werden koennen, muessen wir zu Ihrem und unserem Schutz die rechtliche Verbindlichkeit der vorstehenden Erklaerungen ausschliessen. Die fuer die Stadtsparkasse Koeln geltenden Regeln ueber die Verbindlichkeit von rechtsgeschaeftlichen Erklaerungen mit verpflichtendem Inhalt bleiben unberuehrt.
Re: How to find out what tape's a client data are on ?
q occu or select * from occupancy Steve Hicks schrieb: > > What would the command be to show utilization of the tape vs. the client's > data. With collocation turned off, this command doesn't help too much by > itself. How would I query how much space is taken in my pool overall by one > client? > > > "Sharp, Neil > (London)" To: [EMAIL PROTECTED] > UK.ML.COM> Subject: Re: How to find out what >tape's a client data are on ? > Sent by: "ADSM: > Dist Stor Manager" > <[EMAIL PROTECTED] > DU> > > > 03/02/01 07:31 AM > Please respond to > "ADSM: Dist Stor > Manager" > > > > Thanks for the suggestion > > > -Original Message- > > From: Bernhard Unold [SMTP:[EMAIL PROTECTED]] > > Sent: Friday, March 02, 2001 1:21 PM > > To: [EMAIL PROTECTED] > > Subject: Re: How to find out what tape's a client data are on ? > > > > I can't help with Sql, but i wonder, why do you need tapes from offsite > > for a client restore? Perhaps this will not help you now, but my > > suggestion is, to backup your storage pool(s) and put the backups > > offsite. So for the next restore you will not have to recall a tape at > > all from offsite. Ask me, if you want to know more. > > > > Allen Barth schrieb: > > > > > > While your statement is technically true Andy, *SM does take the > > liberty > > > of folding various fields to UPPER CASE which IMHO is just plain dumb. > > > OOPS, forgot that mainframe heritage. > > > > > > Al Barth > > > Zurich Scudder Investments > > > > > > Andy Raibeck > > > > [EMAIL PROTECTED] > > > IVOLI.COM> cc: > > > Sent by: "ADSM: Subject: Re: How to > > find out what tape's a client data are on ? > > > Dist Stor > > > Manager" > > > <[EMAIL PROTECTED] > > > .EDU> > > > > > > 03/01/01 11:47 AM > > > Please respond to > > > "ADSM: Dist Stor > > > Manager" > > > > > > This is not a case (no pun intended) of TSM being case-sensitive. > > Rather, > > > it is the standard SQL "is equal to" operator, '=', that is case > > sensitive > > > when comparing strings. This is per the SQL standard, and is not > > specific > > > to TSM's SQL implementation. > > > > > > 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." > > > > > > Shekhar Dhotre <[EMAIL PROTECTED]>@VM.MARIST.EDU> on > 03/01/2001 > > > 10:41:16 AM > > > > > > Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> > > > > > > Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> > > > > > > To: [EMAIL PROTECTED] > > > cc: > > > Subject: Re: How to find out what tape's a client data are on ? > > > > > > Thanks .Worked .. .. i was thinking that TSM is not case sensitive > > > application > > > .. hmm.. > > > > > > Glen Churchfield <[EMAIL PROTECTED]>@VM.MARIST.EDU> on > 03/01/2001 > > > 11:57:38 AM > > > > > > Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> > > > > > > Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> > > > > > > To: [EMAIL PROTECTED] > > > cc: > > > > > > Subject: Re: How to find out what tape's a client data are on ? > > > > > > Shekhar, > > > Remember that the node name is case sensitive and is all caps. > > > > > > -Original Message- > > > From: Shekhar Dhotre [mailto:[EMAIL PROTECTED]] > > > Sent: Thursday, March 01, 2001 11:40 AM > > > To: [EMAIL PROTECTED] > > > Subject: Re: How to find out what tape's a client data are on ? > > > > > > I am trying same command for the One of my AIX Box , that is getting > > backed > > > up > > > regularly . > > > I am not getting any output .. IS anything wrong here .. > > > > > > tsm: TSM>select volume_name,node_name from volumeusage where > > > node_name='medrs2' > > > group by volume_name,node_name > > > ANR2034E SELECT: No match found using this criteria. > > > ANS8001I Return code 11. > > > > > > "Sharp, Neil (London)" <[EMAIL PROTECTED]>@VM.MARIST.EDU> on > > > 03/01/2001 11:02:07 AM > > > > > > Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> > > > > > > Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> > > > > > > To: [EMAIL PROTECTED] > > > cc: > > > > > > Subject: Re: How to find out what tape's a client data are on ? > > > > > > Thanks for your help. It has answered my question. > > > > > > Neil > > > > > > > -Original Message- > > > > From: Ruddy STOUDER [SMTP:[EMAIL PROTECTED]] > > > >
Re: ANS1312E Server media mount not possible
Answer from dsmc: dsmc h 39 Explanation: Server media mount not possible. The server timed out waiting for a mount of an offline volume. System Action: File skipped. User Response: Retry later when server volumes can be mounted. The server couldn't mount a tape and reached a timeout waiting for it. Look at the server log for the reason. Perhaps all drives are in use or you have no scratch volume in the library or not enough scratch volumes in your storage pool. Bo Nielsen schrieb: > > Hi > > Can somebody help me. > > A W2K Server TSM Client vers. 4.1.1 > TSM server OS/390 4.1.1.0 > StorageTek VSM tape library. > > When I run a backup, I receive the follow error message: > > ANS1312E Server media mount not possible > > Can any tell me what the problem is. > > Regards, > Bo Nielsen > > FDB dataPhone: +45 4386 4671 > Roskildevej 65 Fax: +45 4386 4990 > DK-2620 AlbertslundE-mail: [EMAIL PROTECTED] > Denmark -- Mit freundlichen Grüßen Bernhard Unold begin:vcard n:Unold;Bernhard tel;work:+49 7071/29-80130 x-mozilla-html:FALSE adr:;; version:2.1 email;internet:[EMAIL PROTECTED] fn:Bernhard Unold end:vcard
serveral domino servers on the sama machine
I have installed TDP for Notes 2.1.9 to backup Lotus Domino 4.6.7 I have two different notes servers runnng on one NT machine and my problem is how to tell the ADSM Connect agent which is the notes server to backup each time. Is there any environment variable to set? Is it possible to do backup of several notes servers running on the same machine? Perhaps it is only possible to backup one notes server per machine. Any help will be appreciated. Thanks. Eduardo Gonzalez _ Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com.
Re: Auditdb
>is not poossible that I have a database corrupted after two week, starting >with a fresh DB Davide - The problem you are having is extremely unusual, and from what I've seen in the past, can result from operating system crashes, mistakes by operators, or unreliable disk hardware used by the server. If you have not been doing so, mirror your TSM database and recovery log, with MIRRORWrite Sequential. Many of us have been doing that, and have successfully avoided server problems in the face of other irregularities in the server's environment. Richard Sims, BU
Re: Antwort: ANS1312E Server media mount not possible
That sounds like that is exactly your problem. I was caught by this when we moved our first server to TSM. I believe 3.7 sets these to 0. You will have to make it something other than 0 for it to work. Jack -Original Message- From: Gisbert Schneider [mailto:[EMAIL PROTECTED]] Sent: Monday, March 05, 2001 6:51 AM To: [EMAIL PROTECTED] Subject: Antwort: ANS1312E Server media mount not possible The client tries to write directly into a sequentiel storage pool and on the server the point MAX MOUNT POINTS for the client ist set to zero. __ Da E-Mails leicht unter fremdem Namen erstellt oder manipuliert werden koennen, muessen wir zu Ihrem und unserem Schutz die rechtliche Verbindlichkeit der vorstehenden Erklaerungen ausschliessen. Die fuer die Stadtsparkasse Koeln geltenden Regeln ueber die Verbindlichkeit von rechtsgeschaeftlichen Erklaerungen mit verpflichtendem Inhalt bleiben unberuehrt.
Re: copy process direct from disk pool?
Yes we do this all the time. First run backup from disk to copy pool backup stg diskpool copytapepool maxpr=4 Then we do a backup of primary tape pool to same copy tape pool incase overflow of disk pool happened: backup stg tapepool copytapepool maxpr=4 Then finally we migrate the diskpool to tapepool. Note that the copytapepools must be the same pools or you will get multiple copies. Hope that helps -- Phillip Ford Senior Software Specialist Corporate Computer Center Schering-Plough Corp. (901) 320-4462 (901) 320-4856 FAX [EMAIL PROTECTED] -Original Message- From: Hagen Finley [mailto:[EMAIL PROTECTED]] Sent: Sunday, March 04, 2001 8:22 PM To: [EMAIL PROTECTED] Subject: copy process direct from disk pool? > Othonas wrote: >2) Activate your migration processes and empty yr disk pools. From 2:00-3:00 am > to 4:00-5:00 am. > 3) Make copies (backup) of your tape storage pools (onsite/offsite). From > 4:00-06:00 am to 07:00-10:00 am. On the scheduling topic - is there a way to run the copy process from the diskpool first, and then migrate to tape - that would appear to be more efficient, but it adds some complexity to the copy process. Hagen Finley
Re: Longlasting tape-reclamation run
Geoff - Greetings from Up Over. ;-) >2. Influence of client type. > > I have clients of the following types: Novell Netware, Unix, NT, and >also NT with the Lotus Notes agent. Since I have collocation on my >onsite tape pool, I was able to determine that the tapes causing trouble >all belonged to Notes clients. Looking at a list of my tape pool today >(about 200 volumes), I can say that for the non-Notes clients, the >number of clusters is always less than 10. The Notes client volumes have >HUNDREDS (highest today is 967). > I don't know if this is something to do with the Notes agent itself, >or just a result of the fact that Notes seems to generate vast numbers of >very small documents. Though we may have collocation activated in the server, I believe it to be the general case that API-based clients either cannot or do not collocate. (This is the case with HSM, at least.) API-based clients which back up numerous small client files thus pose a special burden on the server. > I was able to determine that the process spends most of its time >waiting for data from the input tape. In S/390 terms, every small burst >of data transfer (few milliseconds) is followed by a Locate Block (tape >search) function which takes more like 10 SECONDS. What tape technology was involved? Just curious, as some types are bow-wow's in the Start-Stop department. >5. How do I live with it? I guess the ultimate solution is to not do Reclamations. We should all have libraries with so many tapes that the files just age out so that the tapes go empty and return to scratch by themselves. And we should all be getting six-figure salaries - to the left of the decimal point. Richard Sims, BU
Re: Longlasting tape-reclamation run
Hello Geoff, Richard Sims wrote: > > Geoff - Greetings from Up Over. ;-) > > >2. Influence of client type. > > > > I have clients of the following types: Novell Netware, Unix, NT, and > >also NT with the Lotus Notes agent. Since I have collocation on my > >onsite tape pool, I was able to determine that the tapes causing trouble > >all belonged to Notes clients. Looking at a list of my tape pool today > >(about 200 volumes), I can say that for the non-Notes clients, the > >number of clusters is always less than 10. The Notes client volumes have > >HUNDREDS (highest today is 967). > > I don't know if this is something to do with the Notes agent itself, > >or just a result of the fact that Notes seems to generate vast numbers of > >very small documents. > > Though we may have collocation activated in the server, I believe it to be > the general case that API-based clients either cannot or do not collocate. > (This is the case with HSM, at least.) API-based clients which back up > numerous small client files thus pose a special burden on the server. > setting up several STGs on our Server ( adsm3.1.2.40) I only have one STG with (Client) Collocation - this is the only one which shows up 'clusters' between 2 and just 4 ... This Pool just consists of 2 Clients ( Solaris - multipurpose FileServer, client-compression turned on ) and at the moment has 19 3590e Volumes / 3 Mio Files - the reclamation threshold is at 50 % and it runs without problem - I just believe it has to do with the number of Clients, kind of Collocation in the STG and at last with the total-number of tapes in that pool ... -- Mit freundlichen Grüßen / best regards Rainer Wolf __ Rainer Wolf [EMAIL PROTECTED] Tel: 0731-50-22482 Fax: 0731-50-22471 University of Ulmhttp://www.uni-ulm.de/urz University Computing Center Albert-Einstein-Allee 11 AG Basissysteme 89069 Ulm
SV: Antwort: ANS1312E Server media mount not possible
Thanks for the advise. MaxMountPoint was set to 0. I set it to > 0, and then the backups run. Regards, Bo Nielsen > -- > Fra: Palmadesso Jack[SMTP:[EMAIL PROTECTED]] > Svar til: ADSM: Dist Stor Manager > Sendt:5. marts 2001 14:18 > Til: [EMAIL PROTECTED] > Emne: Re: Antwort: ANS1312E Server media mount not possible > > That sounds like that is exactly your problem. I was caught by this when > we > moved our first server to TSM. I believe 3.7 sets these to 0. You will > have to make it something other than 0 for it to work. > > Jack > > -Original Message- > From: Gisbert Schneider [mailto:[EMAIL PROTECTED]] > Sent: Monday, March 05, 2001 6:51 AM > To: [EMAIL PROTECTED] > Subject: Antwort: ANS1312E Server media mount not possible > > > The client tries to write directly into a sequentiel storage pool and on > the > server > the point MAX MOUNT POINTS for the client ist set to zero. > > > > __ > > >Da E-Mails leicht unter fremdem Namen erstellt oder manipuliert werden >koennen, muessen wir zu Ihrem und unserem Schutz die rechtliche >Verbindlichkeit der vorstehenden Erklaerungen ausschliessen. Die fuer > die >Stadtsparkasse Koeln geltenden Regeln ueber die Verbindlichkeit von >rechtsgeschaeftlichen Erklaerungen mit verpflichtendem Inhalt bleiben >unberuehrt. >
Client 4.1.1 for Netware not accepting login parameters
Anyone, I have just installed the 4.1.1 Netware client on one of my servers, after we shifted from ADSM to TSM server. After I enter the line to start a scheduled backup, I get the following prompt : Please enter NetWare user for "nwserver": In the previous clients, If this happened, I entered the user who has rights for backup, using the full contextual name, ie, .backup.organization When I do that now, it throws me out, and the log file (error) shows the following : 03/05/2001 17:08:10 sessOpen: Error 137 from signon authentication. 03/05/2001 17:08:19 cuSignOnResp: Server rejected session; result code: 53 03/05/2001 17:08:19 sessOpen: Error 53 receiving SignOnResp verb from server 03/05/2001 17:08:19 ANS1353E Session rejected: Unknown or incorrect ID entered The log file shows : 03/05/2001 17:08:10 Querying server for next scheduled event. 03/05/2001 17:08:10 Node Name: MASKORET 03/05/2001 17:08:10 Please enter your user id : ANS1353E Session rejected: Unknown or incorrect ID entered 03/05/2001 17:08:19 Scheduler has been stopped. Does anyone have any idea what format the user name should take to be accepted ? I have only one user who has backup rights, and I do not want to create a user for backups on each server. Anyone ? Mike Glassman System & Security Admin Israeli Airports Authority Ben-Gurion Airport http://www.ben-gurion-airport.co.il Tel : 972-3-9710785 Fax : 972-3-9710939 Email : [EMAIL PROTECTED] Usage of this email address or any email address at iaa.gov.il for the purpose of sales pitches, SPAM or any other such unwanted garbage, is illegal, and any person, whether corporate or alone doing so, will be prosecuted to the fullest possible extent.
Re: Client 4.1.1 for Netware not accepting login parameters
It is not asking for a NetWare ID, it is asking for a TSM nodename and node password. Look at what is in <>, this is the default... Mark -Original Message- From: Mike Glassman - Admin [mailto:[EMAIL PROTECTED]] Sent: Monday, March 05, 2001 10:18 AM To: [EMAIL PROTECTED] Subject: Client 4.1.1 for Netware not accepting login parameters Anyone, I have just installed the 4.1.1 Netware client on one of my servers, after we shifted from ADSM to TSM server. After I enter the line to start a scheduled backup, I get the following prompt : Please enter NetWare user for "nwserver": In the previous clients, If this happened, I entered the user who has rights for backup, using the full contextual name, ie, .backup.organization When I do that now, it throws me out, and the log file (error) shows the following : 03/05/2001 17:08:10 sessOpen: Error 137 from signon authentication. 03/05/2001 17:08:19 cuSignOnResp: Server rejected session; result code: 53 03/05/2001 17:08:19 sessOpen: Error 53 receiving SignOnResp verb from server 03/05/2001 17:08:19 ANS1353E Session rejected: Unknown or incorrect ID entered The log file shows : 03/05/2001 17:08:10 Querying server for next scheduled event. 03/05/2001 17:08:10 Node Name: MASKORET 03/05/2001 17:08:10 Please enter your user id : ANS1353E Session rejected: Unknown or incorrect ID entered 03/05/2001 17:08:19 Scheduler has been stopped. Does anyone have any idea what format the user name should take to be accepted ? I have only one user who has backup rights, and I do not want to create a user for backups on each server. Anyone ? Mike Glassman System & Security Admin Israeli Airports Authority Ben-Gurion Airport http://www.ben-gurion-airport.co.il Tel : 972-3-9710785 Fax : 972-3-9710939 Email : [EMAIL PROTECTED] Usage of this email address or any email address at iaa.gov.il for the purpose of sales pitches, SPAM or any other such unwanted garbage, is illegal, and any person, whether corporate or alone doing so, will be prosecuted to the fullest possible extent.
Re: Longlasting tape-reclamation run
>Though we may have collocation activated in the server, I believe it to be > the general case that API-based clients either cannot or do not collocate. >(This is the case with HSM, at least.) API-based clients which back up >numerous small client files thus pose a special burden on the server. To correct my own posting, this is what should have appeared: Though Aggregation occurs with the standard clients, I believe it to be the general case that API-based clients either cannot or do not Aggregate. (This is the case with HSM, at least.) API-based clients which back up numerous small client files thus pose a special burden on the server. Sorry if I confused anyone. My brain preoccupied with the blizzard that is going on outside. And me without a sled! Richard Sims, BU
Re: Restore NT-Registry
FWIW, I've seen the same behavior on Win2K Pro, with TSM 3.7.2 client. Restoring the registry gives "unable to restore one or more registry keys", with no further error message or explanation. However, in every case, I was able to reboot, then run the registry restore a second time. It always worked OK the second time, so I was sure the registry was (eventually) OK. Should have reported it, but never got around to it, since it never caused me a serious problem. -Original Message- From: Christoph Pilgram [mailto:[EMAIL PROTECTED]] Sent: Monday, March 05, 2001 3:32 AM To: [EMAIL PROTECTED] Subject: Restore NT-Registry Hy all, last weekend we had to restore a NT-Terminal-Server completely. Restoring the Registry from any tested client ended with a message similar to "Unable to restore one or more registry keys". You could click on a button and the message has gone. My question : Is this a normal message or does it say that the registry is now faulty ? And where can I see which keys the restore was unable to update. TSM-Server : aix3.3 , tsm 3.7.4 Client : WIN NT Server V4.0 Terminal-Server-Edition, tsm 3.7.2 and 4.1.1.16 (both tested) Thanks for any help Christoph
FW: MediaW, Tape drive availability, Disk STGpool space and under stan ding what TSM is doing....
It happens when you don't have sufficient free space in your disk pool for a client to send its backup data. The client doesn't just wait - TSM automatically tries to switch the client to direct-to-tape operation rather than failing the backup. THEN the client will wait until a mount point (drive) becomes free. (Unless you specify MAXNUMMP=0 in the definition of the node when it is registered.) That appears to be what is happening, since you have a migration for disk pool SERVER in progress, and it's still 80% full. The pool doesn't have to be totally full to trigger this condition, either - just too full for the largest thing the client wants to send. So if there is still some free space in the pool, you may have some clients still backing up successfully to disk, while others grab a tape. However, once a client is queued to wait for a tape (mount point), even if migration does clear some space in the disk pool, the client will not get switched BACK to the disk pool, it will still finish its backup direct to tape. There is nothing really wrong with this; the data is getting where it is supposed to go, and your backups are working and not failing due to the disk pool filling up (that's what TSM is supposed to do for you, yes?) So you can just ignore it! Or, here are some things you can do if you need to PREVENT clients using the tape drives: - Add more space to the disk pool, as you are planning to do - Force a migration of the disk pool down to 0 before most of these backups start, to make sure you have the max available amount of free space. - Turn on compression on the client, so less data comes into the disk pool (Now this has it's own potential drawbacks - check the list archives at www.adsm.org for all the pros & cons of using client compression. But not having enough disk pool space is one of the reasons TO use client compression.) - Reschedule your clients a bit so that your data arrival is spread out more. - Set MIGPROCESS=2 on your disk pool, so that when a migration IS triggered, you get two output tapes mounted and clear the pool out twice as fast. Those are just some of the things you can do. But again, you don't have to, your backups are getting done as is! -Original Message- From: Talafous, John G. To: [EMAIL PROTECTED] Sent: 3/4/01 2:56 PM Subject: MediaW, Tape drive availability, Disk STGpool space and understan ding what TSM is doing This is more a TSM internal logic question than anything else. I am seeing times that a TSM server has more tapes mounted than would be necessary for Administrative tasks like migration and backup of storage pools. When and how does this happen? The details Looking at system queries for this particular instance, I can see that there is one migration task with an output tape volume in use and a backup stgpool task waiting for a mount point in devclass 3590-E1A. (Devclass 3590-E1A has a mount limit of DRIVES, which we have four (4).) So, I am thinking that three (3) client tasks are, in fact, utilizing physical tape drives. Notice also that there are twenty-three (23) client tasks with MediaW as the session state. We have not begun sending client data direct to tape because of the limited number of tape drives available. To date, this performance enhancement has not been an issue. What is TSM doing? How can I better understand and provide the best services with the resources I have? Are there TSM classes that deal with this type of concept? Environment is TSM 3.7.2 server on a 3466-C00 (AIX 4.3.2) with a 3494 library containing four (4) 3590-E1A drives. (Soon to be increased by 2 more 3590-E1A drives and 144GB of SSA disk.) Here I include the results of four commands. Query STG, Q PRocesses, Q Mounts, Q SEsssions F=D. Thanks in advance for reviewing this long post... Tivoli Storage Manager Command Line Administrative Interface - Version 4, Release 1, Level 2.0 (C) Copyright IBM Corporation, 1990, 1999, All Rights Reserved. Session established with server FSPHNSM1: AIX-RS/6000 Server Version 3, Release 7, Level 2.0 Server date/time: 03/04/2001 01:00:24 Last access: 03/04/2001 00:30:01 Storage Device Estimated Pct Pct High Low Next Stora- Pool Name Class Name Capacity Util Migr Mig Mig ge Pool (MB) Pct Pct --- -- -- - - --- --- ARCHIVE DISK 81,370.0 48.8 48.3 74 50 ARCHIVE_TA- PE ARCHIVE_CO- 3590-E1A 18,071,904 39.7 PY.7 ARCHIVE_TA- 3590-E1A 17,506,379 40.9 47.0 90 70 PE.0 DIR DISK 9,908.0 21.3 21.3 90 70 DIR_TAPE DIR_COPY3590-E1A200,000.0 0.7 DIR_TAPE3590-E1A 0.0
TDP for SQL server login problem
We have an NT4.0 SP5 system with SQL 6.5. Recently upgraded from TSM client 3.1.0.6 and TDP MSSQL 1.1.1 to TSM 4.1.0.0 and TDP 1.1.1.01. After we did, the SQL databases weren't being backed up. We use the sqlfull.cmd for backups. When I checked logs I found this in sqlfull.log. —-- 03/01/2001 21:01:45,COMMAND LINE : C:\Progra~1\Tivoli\TSM\Mssql\sqldsmc /sqluser:sa /sqlpwd:pwd /backupfull:* /adsmoptfile:C:\Progra~1\Tivoli\TSM\Mssql\dsm.opt /logfile:C:\Progra~1\Tivoli\TSM\Mssql\sqlfull.log 03/01/2001 21:01:45,Logging on to the TSM server... 03/01/2001 21:01:51,Logging on to the SQL server... 03/01/2001 21:01:51,ACO4210E -- Failed to connect to SQL server. —- I can use the GUI and it connects to SQL server and backs up databases o.k. I can run the sqlfull.cmd on an NT window and it runs o.k. there. When this sqlfull.cmd is run from TSM Server, it does run because the ADSM autodelete, which is the last line in cmd does run successfully. (We did have problems deleting the "old" *SM stuff from the NT machine before installing new versions. The uninstall didn't work at all and our NT Admin, who is really good, had a difficult time deleting files and Registry entries for old stuff. There had apparently been some ODBC installed sometime in the past and that may have been part of problem.) I checked Tivoli Web site and can't find any relevant info. Why can't it connect to SQL when run as CMD from TSM Server? Thanks for ideas, David B. Longo System Administrator Health First, Inc. 3300 Fiske Blvd. Rockledge, FL 32955-4305 PH 321.434.5536 Pager 321.634.8230 Fax:321.434.5525 [EMAIL PROTECTED] "MMS " made the following annotations on 03/05/01 10:34:15 -- This message is for the named person's use only. It may contain confidential, proprietary, or legally privileged information. No confidentiality or privilege is waived or lost by any mistransmission. If you receive this message in error, please immediately delete it and all copies of it from your system, destroy any hard copies of it, and notify the sender. You must not, directly or indirectly, use, disclose, distribute, print, or copy any part of this message if you are not the intended recipient. Health First reserves the right to monitor all e-mail communications through its networks. Any views or opinions expressed in this message are solely those of the individual sender, except (1) where the message states such views or opinions are on behalf of a particular entity; and (2) the sender is authorized by the entity to give such views or opinions. &eacgr;&eacgr;&eacgr;&eacgr;&eacgr;&eacgr;&eacgr;&eacgr;&eacgr;&eacgr;&eacgr;&eacgr;&eacgr;&eacgr;&eacgr;&eacgr;&eacgr;&eacgr;&eacgr;&eacgr;&eacgr;&eacgr;&eacgr;&eacgr;&eacgr;==
Re: ARCHIVE command - length restrictions
Hi Bernhard. > Any idea? Perhaps tsm doesn't want to search several files systems. You > can get the names of the filesystems with a simple df. > So perhaps you can archive '/TST11/data/*.dbf /TST11/data/*.dbf .' > and so on if /TST11/data and /TST11/data/ are filesystems. It's not the case. TST1 is a filesystem itself. Here you have the output of df - k | grep -w TST1: /dev/TST1 983040420800 58% 778 1% /TST1 The problem seems to be related to the single quotes. I tried several combinations (including '/TST11/data/*.dbf /TST11/data/*.dbf .') and nothing works.The only way that TSM accepts wildcards is by using double quotes, and in this case I also have problems in many cases. The best approach that I found is to backup /TST1/ with subdir=yes, but I'm archiving a lot of garbage in a few cases where there are lots of "undesiderable" files in the file system. It really would be useful to me to find out how to backup /TST1/*/*.dbf, but I couldn't do it so far. > From another > answer i know that you can do up to 20 specifications in one > tsm-command. > > Sergio Cherchyk schrieb: > > > > Bernhard. > > Thanks for your reply. It seems to fit our requirements, if I manage myself to > > do it work properly. > > Unfortunately, I was busy these days so I didn't see your message until > > yesterday. > > I tested the command with the sintax that you gave me (cut & paste) but I > > cannot have it running as I expect. > > Instead, I have an error message: > > > > ANS1081E Invalid search file specification '/TST11/*/*.dbf' entered > > > > I'm running a 3.7.2 client and a 3.7.2 server, both in AIX machines. > > What can I be doing wrong? > > > > Bernhard Unold wrote: > > > > > I don't know the real restriction. But i have a suggestion to avoid it. > > > Check if you can use this > > > dsmc archive -archmc=ORACLE_DIARIO -desc="TST11 OFFLINE ORACLE_DIARIO > > > 20010216.153447" /oracle/rdbms/8.0.5/dbs/initTST11.ora '/TST11/*/*.dbf' > > > The single quotes inhibits the shell to interpret the wildcards. So you > > > can archive a lot of files in a single dsmc-command. You must check if > > > my specification meets your requirements: are all files includet you > > > want to back up, but not any other file? > > > > > > Sergio Cherchyk schrieb: > > > > > > > > Hi everybody! > > > > > > > > I'm trying to backup ORACLE databases using a script that uses an > > > > ARCHIVE command to which a list of files to back up is given, so that > > > > the final command is something like this: > > > > > > > > dsmc archive -archmc=ORACLE_DIARIO -desc="TST11 OFFLINE ORACLE_DIARIO > > > > 20010216.153447" /oracle/rdbms/8.0.5/dbs/initTST11.ora > > > > /TST11/dbs/system01.dbf /TST11/data/ajes_data.dbf > > > > /TST11/data/amul_data.dbf /TST11/index/amul_ind.dbf > > > > /TST11/rollback/rbs.dbf /TST11/temporary/temporary.dbf > > > > /TST11/dbs/user.dbf /TST11/index/ajes_ind.dbf /TST11/data/eul_data.dbf > > > > /TST11/data/eft_data.dbf /TST11/index/eft_ind.dbf > > > > /TST11/data/cheques_data.dbf /TST11/index/cheques_ind.dbf > > > > /TST11/redologs1/log3a.dbf /TST11/redologs2/log2b.dbf > > > > /TST11/redologs1/log1a.dbf /TST11/redologs1/ctrl1.dbf > > > > /TST11/redologs2/ctrl2.dbf /TST11/redologs1/ctrl3.dbf > > > > /TST11/dbs/cfstby.dbf > > > > > > > > The error message that I get after this command is issued is: > > > > > > > > ANS1102E Excessive number of command line arguments passed to the > > > > program! > > > > ANS1133W An expression might contain a wildcard not enclosed in quotes > > > > > > > > Not seeing any wildcards and not finding a limit in the number of > > > > parameters to be passed to an ARCHIVE command, I thought that it should > > > > have failed because an exesive number of characters in the command line. > > > > TSM specifies 256 character as a maximun limit, so it appeared natural > > > > to me that this command doesn't work. > > > > > > > > However this, the following comman DOES work, even if it is largely > > > > superior to 256 characters in length: > > > > > > > > dsmc archive -archmc=ORACLE_DIARIO -desc="TST1 OFFLINE ORACLE_DIARIO > > > > 20010216.152135" /oracle/rdbms/7.3.4/dbs/initTST1.ora > > > > /TST1/dbs/system01.dbf /TST1/dbs/user.dbf /TST1/data/data.dbf > > > > /TST1/rollback/rbs.dbf /TST1/temporary/temporary.dbf /TST1/index/ind.dbf > > > > /TST1/redologs1/log1a.dbf /TST1/redologs2/log1b.dbf > > > > /TST1/redologs2/log2b.dbf /TST1/redologs2/log2a.dbf > > > > /TST1/redologs1/log3a.dbf /TST1/redologs2/log3b.dbf > > > > /TST1/redologs2/log4b.dbf /TST1/redologs2/log4a.dbf /TST1/dbs/ctrl1.dbf > > > > /TST1/redologs1/ctrl2.dbf /TST1/redologs2/ctrl3.dbf /TST1/dbs/cfstby.dbf > > > > /TST1/archivelog > > > > > > > > Does anyone know which is the real restriction that I'm not respecting > > > > in the first example? > > > > > > > > The client is TSM 3.7.2 in an AIX 4.3.2 > > > > > > > > Thanks in advance > > > > -- > > > > > > > > Sergio R.
Remove policy set
Hi *SM-ers! I would like to remove an old policy set. Does anybody know an SQL query to check whether there are no files bound to it? Thanks in advance! Kindest regards, Eric van Loon KLM Royal Dutch Airlines ** This e-mail and any attachment may contain confidential and privileged material intended for the addressee only. If you are not the addressee, you are notified that no part of the e-mail or any attachment may be disclosed, copied or distributed, and that any other action related to this e-mail or attachment is strictly prohibited, and may be unlawful. If you have received this e-mail by error, please notify the sender immediately by return e-mail, and delete this message. Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its employees shall not be liable for the incorrect or incomplete transmission of this e-mail or any attachments, nor responsible for any delay in receipt. **
Re: Client 4.1.1 for Netware not accepting login parameters
Have you tried going into the server and just resetting that users rights and password in TSM? -Original Message- From: Mike Glassman - Admin [mailto:[EMAIL PROTECTED]] Sent: Monday, March 05, 2001 10:18 AM To: [EMAIL PROTECTED] Subject: Client 4.1.1 for Netware not accepting login parameters Anyone, I have just installed the 4.1.1 Netware client on one of my servers, after we shifted from ADSM to TSM server. After I enter the line to start a scheduled backup, I get the following prompt : Please enter NetWare user for "nwserver": In the previous clients, If this happened, I entered the user who has rights for backup, using the full contextual name, ie, .backup.organization When I do that now, it throws me out, and the log file (error) shows the following : 03/05/2001 17:08:10 sessOpen: Error 137 from signon authentication. 03/05/2001 17:08:19 cuSignOnResp: Server rejected session; result code: 53 03/05/2001 17:08:19 sessOpen: Error 53 receiving SignOnResp verb from server 03/05/2001 17:08:19 ANS1353E Session rejected: Unknown or incorrect ID entered The log file shows : 03/05/2001 17:08:10 Querying server for next scheduled event. 03/05/2001 17:08:10 Node Name: MASKORET 03/05/2001 17:08:10 Please enter your user id : ANS1353E Session rejected: Unknown or incorrect ID entered 03/05/2001 17:08:19 Scheduler has been stopped. Does anyone have any idea what format the user name should take to be accepted ? I have only one user who has backup rights, and I do not want to create a user for backups on each server. Anyone ? Mike Glassman System & Security Admin Israeli Airports Authority Ben-Gurion Airport http://www.ben-gurion-airport.co.il Tel : 972-3-9710785 Fax : 972-3-9710939 Email : [EMAIL PROTECTED] Usage of this email address or any email address at iaa.gov.il for the purpose of sales pitches, SPAM or any other such unwanted garbage, is illegal, and any person, whether corporate or alone doing so, will be prosecuted to the fullest possible extent.
Re: ARCHIVE command - length restrictions
Perhaps you get a better result by using a backslash to mask the asterisk. We are using in our Oracle-save-script: dsmc archive -servername=$ADSMSERV -archmc=$ADSMCLASS -DELETEFILES -verbose /bigspace/\*$ORACLE_SID* >> $ORACLEPROT and it works. The script is not written by me, but as far i know all important datasets are asked from oracle and copied to the "bigspace" directory before. adsmserv is the name of our adsmserver adsmclass ist the name of our mgmtclass oracle_sid is the name of the database (for example orc1) oracleprot is a dataset to keep the output from dsmc I remember that after beeing testet successfully there was the same problem if it went to production. With the \ masking the * this problem didn't occour again and all worked fine even with 100 files in one command. Sergio Cherchyk schrieb: > > Hi Bernhard. > > > Any idea? Perhaps tsm doesn't want to search several files systems. You > > can get the names of the filesystems with a simple df. > > So perhaps you can archive '/TST11/data/*.dbf /TST11/data/*.dbf .' > > and so on if /TST11/data and /TST11/data/ are filesystems. > > It's not the case. TST1 is a filesystem itself. Here you have the output of df - k | > grep -w TST1: > > /dev/TST1 983040420800 58% 778 1% /TST1 > > The problem seems to be related to the single quotes. I tried several combinations > (including '/TST11/data/*.dbf /TST11/data/*.dbf .') and nothing works.The only > way that TSM accepts wildcards is by using double quotes, and in this case I also > have problems in many cases. The best approach that I found is to backup /TST1/ with > subdir=yes, but I'm archiving a lot of garbage in a few cases where there are lots > of "undesiderable" files in the file system. It really would be useful to me to find > out how to backup /TST1/*/*.dbf, but I couldn't do it so far. > > > From another > > answer i know that you can do up to 20 specifications in one > > tsm-command. > > > > Sergio Cherchyk schrieb: > > > > > > Bernhard. > > > Thanks for your reply. It seems to fit our requirements, if I manage myself to > > > do it work properly. > > > Unfortunately, I was busy these days so I didn't see your message until > > > yesterday. > > > I tested the command with the sintax that you gave me (cut & paste) but I > > > cannot have it running as I expect. > > > Instead, I have an error message: > > > > > > ANS1081E Invalid search file specification '/TST11/*/*.dbf' entered > > > > > > I'm running a 3.7.2 client and a 3.7.2 server, both in AIX machines. > > > What can I be doing wrong? > > > > > > Bernhard Unold wrote: > > > > > > > I don't know the real restriction. But i have a suggestion to avoid it. > > > > Check if you can use this > > > > dsmc archive -archmc=ORACLE_DIARIO -desc="TST11 OFFLINE ORACLE_DIARIO > > > > 20010216.153447" /oracle/rdbms/8.0.5/dbs/initTST11.ora '/TST11/*/*.dbf' > > > > The single quotes inhibits the shell to interpret the wildcards. So you > > > > can archive a lot of files in a single dsmc-command. You must check if > > > > my specification meets your requirements: are all files includet you > > > > want to back up, but not any other file? > > > > > > > > Sergio Cherchyk schrieb: > > > > > > > > > > Hi everybody! > > > > > > > > > > I'm trying to backup ORACLE databases using a script that uses an > > > > > ARCHIVE command to which a list of files to back up is given, so that > > > > > the final command is something like this: > > > > > > > > > > dsmc archive -archmc=ORACLE_DIARIO -desc="TST11 OFFLINE ORACLE_DIARIO > > > > > 20010216.153447" /oracle/rdbms/8.0.5/dbs/initTST11.ora > > > > > /TST11/dbs/system01.dbf /TST11/data/ajes_data.dbf > > > > > /TST11/data/amul_data.dbf /TST11/index/amul_ind.dbf > > > > > /TST11/rollback/rbs.dbf /TST11/temporary/temporary.dbf > > > > > /TST11/dbs/user.dbf /TST11/index/ajes_ind.dbf /TST11/data/eul_data.dbf > > > > > /TST11/data/eft_data.dbf /TST11/index/eft_ind.dbf > > > > > /TST11/data/cheques_data.dbf /TST11/index/cheques_ind.dbf > > > > > /TST11/redologs1/log3a.dbf /TST11/redologs2/log2b.dbf > > > > > /TST11/redologs1/log1a.dbf /TST11/redologs1/ctrl1.dbf > > > > > /TST11/redologs2/ctrl2.dbf /TST11/redologs1/ctrl3.dbf > > > > > /TST11/dbs/cfstby.dbf > > > > > > > > > > The error message that I get after this command is issued is: > > > > > > > > > > ANS1102E Excessive number of command line arguments passed to the > > > > > program! > > > > > ANS1133W An expression might contain a wildcard not enclosed in quotes > > > > > > > > > > Not seeing any wildcards and not finding a limit in the number of > > > > > parameters to be passed to an ARCHIVE command, I thought that it should > > > > > have failed because an exesive number of characters in the command line. > > > > > TSM specifies 256 character as a maximun limit, so it appeared natural > > > > > to me that this command doesn't work. > > > > > > > > > > However this, the following comman DOES work, even if it is largely > > > >
Re: ADSM-L Digest - 3 Mar 2001 to 4 Mar 2001 (#2001-62)
Hello, I am hoping that the following error for a Restore operation is known to someone on the ADSM listserver: Running the TSM Mac client 4.1.2 on MacOS9.1 with an AIX-RS/6000 Server : 05-03-2001 16:51:33 DTcpipInterface::ciReadAvailable: UnKnown Error Code : rc = 268435556 05-03-2001 16:51:33 sessRecvVerb: Error -50 from call to 'readRtn'. 05-03-2001 16:51:33 sessRecvVerb: Error -50 from call to 'readRtn'. 05-03-2001 16:51:33 mpDestroy: Memory Pool #14 doesn't exist 05-03-2001 16:51:33 ANS1809E Session is lost; initializing session reopen procedure. 05-03-2001 16:51:40 ANS1811S TSM session could not be reestablished. Administrator is sure that the Server is not at fault!? Thanks -- Louis Giannone Max Planck Institut fuer Plasmaphysik Boltzmannstrasse 2, D-85748 Garching bei Muenchen, BRD. e-mail: [EMAIL PROTECTED] Tel.0049 - 89 - 3299 1499 FAX 0049 - 89 - 3299 2584 Office 0049 - 89 - 3299 1963 http://www.rzg.mpg.de/~giannone/
Re: Antwort: ANS1312E Server media mount not possible
>> Fra: Palmadesso Jack[SMTP:[EMAIL PROTECTED]] >> That sounds like that is exactly your problem. I was caught >by this when >> we >> moved our first server to TSM. I believe 3.7 sets these to >0. You will >> have to make it something other than 0 for it to work. Having just upgraded to the most recent version of TSM, from ADSM 3.1.2.55 on AIX, I decided to look at all the nodes I have. I found that all the nodes I had previously defined before the upgrade were all set to 0. The new ones I created are set to 2. Better make a note in the document everyone got from me to update your nodes. Now that that's fixed I wonder what other things I'll find out about in the future. This is really annoying, I've been involved with delivering software to the government in the past and we had proceedures to follow. In those proceedures were proceedures from past deliveries to make sure the same functions, that worked in the past, still work, not just enhancements. I thought this would be SOP for all companies delivering software to its customers but I guess not. Geoff (I have enough to do without having to go back and fix things from software updates) Gill NT Systems Support Engineer SAIC Computer Systems Group E-Mail: [EMAIL PROTECTED] Phone: (858) 826-4062 Pager: (888) 997-9614
Re: ARCHIVE command - length restrictions
>...The only way that TSM accepts wildcards is by using double quotes... You're confusing TSM and Unix shell actions. As long as TSM gets the wildcard characters, it can expand them. Whether the wildcard characters that you type actually get to TSM is a function of what command shell you are running in a given context and what options may govern its handling of operands. Shells usually pass wildcard characters without interpretation when they are enclosed in single or double quotes; if no quotes, they try to expand the wildcard characters themselves. Richard Sims, BU
Re: Error Msg: ANR0102E asalloc.c(3936)
>From what my messages manual stated, there should be other messages issued with the >ANR0102E. Jim - can you provide some more info? * What server level and platform are you on? * What other messages (ANRD, for example) were issued along with the ANR0102E? I think this has something to do with duplicate entries, but it's difficult to tell without the other / associated messages. Glen Smith To: [EMAIL PROTECTED] cc: Subject:Re: Error Msg: ANR0102E asalloc.c(3936): We've seen this when doing reclamation. Does anyone know if there is a PMR open on this? 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 -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of Jim Coen Sent: Friday, March 02, 2001 2:38 PM To: [EMAIL PROTECTED] Subject: Error Msg: ANR0102E asalloc.c(3936): Today I encountered something new: While attempting to move data from a volume in a copypool I received the following error and a failure: ANR0102E asalloc.c(3936): Error 1 inserting row in table "AS.Segments". Any of you gurus have a clue what this means. Thanks ahead of time. Jim __ FREE Personalized Email at Mail.com Sign up at http://www.mail.com/?sr=signup
Re: Longlasting tape-reclamation run
Hi Geoff & Richard, I thought I would add some insight. On point 2 - yes, the client type does greatly affect the nature of the aggregate as well as the eventual reclamation of the aggregate. Notes is notorious for tons of small files. At backup time, aggregation is a blessing because the DB doesn't increase at exponential rates. But, if the small files have a mix of expiration / deletion rates, reclamation will become a significant pain. Regarding times (point 3) - 4 days is pretty excessive, but I'm not certain if you mean for one volume or the entire process. For the entire process, and with lots of itty-bitty files, that's actually not too unusual. For one tape that shouldn't take 4 days. point 4 - It's always good to hear that the support team was responsive and answered your questions. I'm sure they appreciate the positive comments. From my conversations with development, I understand they're aware of the performance issues within reclamation. Hopefully, they'll have time to work on it sometime soon. on your last point (workarounds) - you might try smaller reclamation percentages. Instead of high being 70, try 90 and see if the reclamation process exits quicker. It will work on fewer tapes this way, but that cuts down on the workload that the server has to manage. Also - if you can isolate the problematic clients in some manner, you might just use move data to reclaim those volumes instead. The physical occupancy will be greater than the logical occupancy (ie. there is 'wasted' space in the aggregate), but the reclaim happens a lot faster that way. If I recall correctly, scripts have been generated by list members that identify candidates for this process - take a look through the archives. Glen Smith To: [EMAIL PROTECTED] cc: Subject:Re: Longlasting tape-reclamation run I was interested in the recent items on slow reclamations - see mail from Richard Sims below. I started having problems with long-running reclamations about 18 months ago when we converted from 800MB to 20GB cartridges. We had a three-hour window in which the reclaim threshold was set to 70. With the small tapes, this worked o.k., but with the large ones, reclamations began running for many hours (not days, but certainly as much as 16 hours). Since we only have a small number of drives for the high-capacity cartridges, a reclamation holding two drives for this long caused chaos for later bits of the schedule. I posted an item here in February last year, and also raised the issue with Tivoli support. Neither provided any solution, but various things I saw along the way may still be of interest. 1. "Collocation clusters" I noticed that the tapes which ran for a long time had a large number of collocation clusters, as shown by message ANR1142I issued during reclamation. Tapes with a small number of clusters reclaimed within an hour or two and caused me no grief. I also found I could predict in advance how many clusters were on a tape by running the classic "select volume_name,node_name from volumeusage where " and counting the number of repetitions of each volume/node combination. Like Richard, I had no luck finding any useful documentation on this. 2. Influence of client type. I have clients of the following types: Novell Netware, Unix, NT, and also NT with the Lotus Notes agent. Since I have collocation on my onsite tape pool, I was able to determine that the tapes causing trouble all belonged to Notes clients. Looking at a list of my tape pool today (about 200 volumes), I can say that for the non-Notes clients, the number of clusters is always less than 10. The Notes client volumes have HUNDREDS (highest today is 967). I don't know if this is something to do with the Notes agent itself, or just a result of the fact that Notes seems to generate vast numbers of very small documents. The only hope on the horizon, for me, is that this issue will go away when the Notes servers get converted to Domino V5 and the individual email backups get replaced by a transaction log file. But maybe other kinds of client with many small files will still have a problem, especially with the way tape capacities keep increasing. 3. Why do the reclamations run so slow? I was able to determine that the process spends most of its time waiting for data from the input tape. In S/390 terms, every small burst of data transfer (few milliseconds) is followed by a Locate Block (tape search) function which takes more like 10 SECONDS. With offsite reclamations, there is an additional issue with large tapes because of the requirement to sort a potentially huge number of database entries (see below). 4. Did Tivoli help? I got excellent help from the local (Australian) IBM support, but the eventual response from the change team was that all was working as designed and that if I wanted sensible housekeeping performance I should ask for it through my marketing re
Re: TDP for SQL server login problem
David, You might check the "Log on As:" parameter for the TSM scheduler service that is running the command type schedule. Is it the same user as when it worked with the command line in the NT command window? Do you know if TDP for SQL 1.1.1 also fails now or just 1.1.1.01? If checking the users doesn't help, you should call IBM service. Bob KingIBM Global Services [EMAIL PROTECTED]
Backup sets on MVS
Is anyone running TSM on MVS and successfully generating and then using backup sets for your clients? It's my understanding that backup sets need to be generated on sequential media that is compatible/readable by the client. The sequential device classes I have defined are 3590 tape - which is not compatible with my NT and AIX clients. Any suggestions on how I can generate a backup set from MVS that would be readable by an NT or AIX client? What are other people doing? Thanks - your comments and suggestions are appreciated, Cheri Howard Lead Software Systems Analyst 920-730-4700, ext. 4166 [EMAIL PROTECTED] Aid Association for Lutherans (AAL) 4321 N. Ballard Road, Appleton, WI 54919-0001 http://www.aal.org
Rman Bkups with copypool
Has anyone successfully restored RMAN/TDP data with copypool tapes? We gave it a try this weekend for the first time at a DR drill and had no success. It almost appears like rman holds the storage pool name and possibly the vol ser in its catalog and when it attempts to retrieve the data it can't because TSM has the primary copies marked as destroyed as designed. Jim
Re: Exchange Problem
Upgrade to TDP for exchange v1.1.1.01. You can ftp it from the IBM site: service.boulder.ibm:/storage/tivoli-storage-management/maintenance/tivoli-data-protection/ntexch/1.1.1 We are running TSM server 4.1.2, and exchange backup/restore works just fine. Eliza Lau Virginia Tech Computing Center [EMAIL PROTECTED] > > I have an Exchange problem. We just upgraded from adsm ver 3.1.2.20 > on aix to TSM 4.1.0 Now when I try to restore > the information database for a individual mail box restore( restore > database to test box and then import) the test server > hangs up. To make sure it was not a bad backup I tried the last three > full backups, the same result every time. The > Exchange client is TDP ver 1.1.1.0 Is there any problems with 4.1 and > the exchange client? Any help or advice is > appreciated > > Mike Anderson > [EMAIL PROTECTED] >
Exchange Problem
I have an Exchange problem. We just upgraded from adsm ver 3.1.2.20 on aix to TSM 4.1.0 Now when I try to restore the information database for a individual mail box restore( restore database to test box and then import) the test server hangs up. To make sure it was not a bad backup I tried the last three full backups, the same result every time. The Exchange client is TDP ver 1.1.1.0 Is there any problems with 4.1 and the exchange client? Any help or advice is appreciated Mike Anderson [EMAIL PROTECTED]
Backing up NT-shares trough an Win2k-Server
Hi there, I am new to this list, so I hope this is the rigth place for my request. I got some trouble configuring my ADSM-Client properly and hope you can give me some assistance. I got a Windows 2000 Server on which I mounted some shares from my old NT-fileserver. This files can be accesed by the Windows-explorer, so the networkpermissions seem to be set correctly. But my ADSM-Client cannot backup them. First it complained about an error occuring while trying to access NTFS security information. Using the "skipntsecuritycrc"-option did not help, so I tried the "skipntpermissions"-option. This resulted in the ADSM-Client being able to access the volume, but now it complains about the access to the objects being denied, but not by all of them, although there is now visible difference in the file properties. This confuses me, because the ADSM-Client runs as an Administratorprocess and all files in the volume are readable and accessable by the Administrator. I am sure it's just a silly thing, but I don't get. Could you please give me some advice? Sincerely, Christian Huber
Re: Rman Bkups with copypool
James, We have done it 3 times with copypool tapes. Regards, Sean M. English Distributed Storage Management/TSM IBM Global Services Service Delivery Center-South, Charlotte, NC External: (704)594-2232 T/L: 8-794-2232 Pager: (800)946--4646 PIN: 1428698 Good news is just life's way of keeping you off balance. " " Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] cc: Subject: Rman Bkups with copypool Has anyone successfully restored RMAN/TDP data with copypool tapes? We gave it a try this weekend for the first time at a DR drill and had no success. It almost appears like rman holds the storage pool name and possibly the vol ser in its catalog and when it attempts to retrieve the data it can't because TSM has the primary copies marked as destroyed as designed. Jim
capture output from prescheduled command
I am trying to figure out how to capture the output of an ncompact.exe -B command (a Domino server command that reassigns new DBIIDs to the compacted databases) that is run as a prescheduled command in a special dsm_sel.opt. The scheduler picks up the schedule, and the selective TDP backup occurs, (and says it is using the c:\progra~1\tivoli\tsm\domino\dsm_sel.opt) but I can not tell whether the compact was successful. I have tried putting the statement in the dsm_sel.opt file preschedcommand d:\domino\ncompact.exe -B 10 >> c:\progra~1\tivoli\tsm\domino\compact.log with all sorts of variations of where the quotes are-- no out put. I have also tried putting these commands into another command file that is called by the prescheduled command, and no go on it, either. Has anyone done this? thanks!! lisa
Re: Longlasting tape-reclamation run
Sorry to be replying so late on this thread, I am just back from a weeks absence. Collocation clusters are filespaces for ordinary clients. For api clients like notes they may be filespaces also or something that equates to a filespace in the database. Reclaim not only squeezes out the empty space in aggregates, but it also brings together all the pieces of each filespace, which means it has to skip down the tape to get to each piece; the server will know where to skip to, it isn't reading all blocks and hunting. For the initial post with 4000+ clusters, that's a lot of skipping! It will depend on how many times this tape was the object of a migration task and thus how many pieces of each filespace are on the tape. In addition, if the target storage pool is collocated, each cluster may ask for a new output tape, and tsm isn't smart enough to find all the clusters that are bound for a particular output tape and reclaim them together. Instead it is driven by the order of filespaces on the input tape, so the same output tape may be mounted many times. Move data does the same thing but without the aggregate squeeze. -- -- Bill Colwell C. S. Draper Lab Cambridge, Ma. [EMAIL PROTECTED] -- In <[EMAIL PROTECTED]>, on 03/05/01 at 03:24 PM, Richard Sims <[EMAIL PROTECTED]> said: >>Though we may have collocation activated in the server, I believe it to be >> the general case that API-based clients either cannot or do not collocate. >>(This is the case with HSM, at least.) API-based clients which back up >>numerous small client files thus pose a special burden on the server. >To correct my own posting, this is what should have appeared: > Though Aggregation occurs with the standard clients, I believe it to be > the general case that API-based clients either cannot or do not Aggregate. > (This is the case with HSM, at least.) API-based clients which back up > numerous small client files thus pose a special burden on the server. >Sorry if I confused anyone. My brain preoccupied with the blizzard that >is going on outside. And me without a sled! > Richard Sims, BU
Re: Backing up NT-shares trough an Win2k-Server
If you are trying to back up these shares through a schedule, then you must change the ADSM Scheduler service to use an account with administrative rights to those shares. The system account is used by default, and it does not have rights to any remote computers or shares. === John Monahan Network Team Coordinator Liberty Diversified Industries (763) 536-6677 === Christian Huber <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> 03/05/01 01:59 PM Please respond to "ADSM: Dist Stor Manager" To: [EMAIL PROTECTED] cc: Subject:Backing up NT-shares trough an Win2k-Server Hi there, I am new to this list, so I hope this is the rigth place for my request. I got some trouble configuring my ADSM-Client properly and hope you can give me some assistance. I got a Windows 2000 Server on which I mounted some shares from my old NT-fileserver. This files can be accesed by the Windows-explorer, so the networkpermissions seem to be set correctly. But my ADSM-Client cannot backup them. First it complained about an error occuring while trying to access NTFS security information. Using the "skipntsecuritycrc"-option did not help, so I tried the "skipntpermissions"-option. This resulted in the ADSM-Client being able to access the volume, but now it complains about the access to the objects being denied, but not by all of them, although there is now visible difference in the file properties. This confuses me, because the ADSM-Client runs as an Administratorprocess and all files in the volume are readable and accessable by the Administrator. I am sure it's just a silly thing, but I don't get. Could you please give me some advice? Sincerely, Christian Huber
Netware/NAV-CE
We are trying to find out the deadly cocktail between NLMs on Novell. So far we have noted there seems to be something adverse when the TSM 4.1.x client and NAV CE is running concurrently. (Note: we have not seen the same problems running the ADSM 3.1.x clients) The server is running Netware 4.11, Service Pack 8a. Anyone experience similar problems? Cheers, Suad --
Re: Backing up NT-shares trough an Win2k-Server
The local system account has null credentials and therefore has no implicit access to network resources. Remote resources deny access to null sessions unless explicitly granted access. Network resources may be accessed by services running under the local system account by adding the following registry entry to permit null session access to a particular share: HKLM\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters\NullSessionShares\ShareName where ShareName is REG_SZ value which specifing the name of the share. Blanket null session access to ANY remote resource (shares, pipes, etc.) may be granted by assigning the following REG_DWORD registry value 0: HKLM\SYSTEM\CurrentControlSet\Service\LanmanServer\Parameters\RestrictNullSessionAccess Note that the above is a huge security hole and is not recommended. Hope this helps Pete Tanenhaus Tivoli Storage Solutions Software Development email: [EMAIL PROTECTED] tieline: 855.7620, external: 607.755.7620 "Those who refuse to challenge authority are condemned to conform to it" -- Forwarded by Pete Tanenhaus/San Jose/IBM on 03/05/2001 05:40 PM --- John Monahan <[EMAIL PROTECTED]>@VM.MARIST.EDU> on 03/05/2001 03:55:20 PM Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] cc: Subject: Re: Backing up NT-shares trough an Win2k-Server If you are trying to back up these shares through a schedule, then you must change the ADSM Scheduler service to use an account with administrative rights to those shares. The system account is used by default, and it does not have rights to any remote computers or shares. === John Monahan Network Team Coordinator Liberty Diversified Industries (763) 536-6677 === Christian Huber <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> 03/05/01 01:59 PM Please respond to "ADSM: Dist Stor Manager" To: [EMAIL PROTECTED] cc: Subject:Backing up NT-shares trough an Win2k-Server Hi there, I am new to this list, so I hope this is the rigth place for my request. I got some trouble configuring my ADSM-Client properly and hope you can give me some assistance. I got a Windows 2000 Server on which I mounted some shares from my old NT-fileserver. This files can be accesed by the Windows-explorer, so the networkpermissions seem to be set correctly. But my ADSM-Client cannot backup them. First it complained about an error occuring while trying to access NTFS security information. Using the "skipntsecuritycrc"-option did not help, so I tried the "skipntpermissions"-option. This resulted in the ADSM-Client being able to access the volume, but now it complains about the access to the objects being denied, but not by all of them, although there is now visible difference in the file properties. This confuses me, because the ADSM-Client runs as an Administratorprocess and all files in the volume are readable and accessable by the Administrator. I am sure it's just a silly thing, but I don't get. Could you please give me some advice? Sincerely, Christian Huber
Re: capture output from prescheduled command
Lisa, I have successfully captured the output of the following pre/post commands when shutting down and restarting an Oracle database prior to running a scheduled backup. I am running a Windows NT Version 4.0 backup Server and TSM version 4.1.1.0 In the clients DSM.OPT file the following commands have been entered: preschedulecmd "c:\oracle\admin\bat\shutdownoracle.cmd" postschedulecmd "c:\oracle\admin\bat\startuporacle.cmd" the following are the command files that redirects the shutdown and startup to a text file: shutdownoracle.cmd set ORACLE_SID=XYDEV set ORACLE_HOME=c:\oracle\ora81 c:\oracle\ora81\bin\svrmgrl.exe @c:\oracle\admin\sql\shutdown.sql > c: \oracle\admin\bat\pre_cmd_results.txt net stop oracleserviceBVDEV /y startuporacle.cmd set ORACLE_SID=XYDEV set ORACLE_HOME=c:\oracle\ora81 net start oracleserviceBVDEV /y c:\oracle\ora81\bin\svrmgrl.exe @c:\oracle\admin\sql\startup.sql > c: \oracle\admin\bat\post_cmd_results.txt Hope this helps!! Regards Russell Walsh Professional Server Specialist, IBM GSA, Australia Phone:+61 3 9627.0158 Desk +61 3 9627.0340 Fax 0411.263.409 Mobile Internet: [EMAIL PROTECTED] Lisa Cabanas <[EMAIL PROTECTED]>@VM.MARIST.EDU> on 06/03/2001 07:48:08 Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] cc: Subject: capture output from prescheduled command I am trying to figure out how to capture the output of an ncompact.exe -B command (a Domino server command that reassigns new DBIIDs to the compacted databases) that is run as a prescheduled command in a special dsm_sel.opt. The scheduler picks up the schedule, and the selective TDP backup occurs, (and says it is using the c:\progra~1\tivoli\tsm\domino\dsm_sel.opt) but I can not tell whether the compact was successful. I have tried putting the statement in the dsm_sel.opt file preschedcommand d:\domino\ncompact.exe -B 10 >> c:\progra~1\tivoli\tsm\domino\compact.log with all sorts of variations of where the quotes are-- no out put. I have also tried putting these commands into another command file that is called by the prescheduled command, and no go on it, either. Has anyone done this? thanks!! lisa
Win2000 system objects
Greetings, I'm new to the forum. I am upgrading my clients to TSM 4.1 from ADSM 3.1.8. A Win2000 client with three partitions C: D: P: backs up successfully. I'm using a domain statement, nothing else special in the options file. Since upgrading to TSM 4.1 client, I now see filespace 'System Object'. The documentation says servers at 3.7.3 and higher support the "feature" to backup system objects as a group. Fine by me, but when I query filespace for this node, there is no start time, no completion time, no capacity utilization, etc. for filespace 'System Object'. We run e-mail notification scripts off these date/time fields, and they're going to fail without these completion statistics. Nothing unusual in the dsmsched.log. In fact, the last message is "Successful incremental backup of Registry". Thanks to anyone for any input to this problem. John Bremer LANL
Henrik Hansson is out of the office.
I will be out of the office starting 2001-03-05 and will not return until 2001-03-16. I will respond to your message when I return. In urgent cases contact Stig-Arne Carlsson
Re: ANS1312E Server media mount not possible
Check drive status and media access property. If drive status is unavailable, update drive following method. ex)update drive libraryname drivenumber online=yes If media access property is readonly, change it to readwrite.. I had the same problem yesterday,now I solved problem .. Good luck.. From South Korea Cddata co.ltd. - Original Message - From: "Bo Nielsen" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Monday, March 05, 2001 6:17 PM Subject: ANS1312E Server media mount not possible > Hi > > Can somebody help me. > > A W2K Server TSM Client vers. 4.1.1 > TSM server OS/390 4.1.1.0 > StorageTek VSM tape library. > > When I run a backup, I receive the follow error message: > > ANS1312E Server media mount not possible > > Can any tell me what the problem is. > > Regards, > Bo Nielsen > > FDB dataPhone: +45 4386 4671 > Roskildevej 65 Fax: +45 4386 4990 > DK-2620 AlbertslundE-mail: [EMAIL PROTECTED] > Denmark
LTO Ultriums Drives with TSM?
We are looking to possibly upgrade our ADIC Scalar libraries, replacing our DLT 7000 drives with LTO Ultriums. I was looking for any real world feedback(overall satifaction, issues...etc)? Thanks, Jeff
Re: LTO Ultriums Drives with TSM?
I recently helped a client install an IBM 3584 LTO Library. We connected it to the SAN. Throughput is great. You just need to deal with the fact that tape capacity is huge compared to most other tape products. You might want to look at how you do collocation. Adolph - Original Message - From: "Jeffery Carroll" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Monday, March 05, 2001 7:19 PM Subject: LTO Ultriums Drives with TSM? > We are looking to possibly upgrade our ADIC Scalar libraries, replacing our > DLT 7000 drives with LTO Ultriums. I was looking for any real world > feedback(overall satifaction, issues...etc)? > > > Thanks, > Jeff
Re: LTO Ultriums Drives with TSM?
On Mon, Mar 05, 2001 at 07:34:00PM -0500, Adolph Kahan wrote: > I recently helped a client install an IBM 3584 LTO Library. We connected it > to the SAN. Throughput is great. You just need to deal with the fact that > tape capacity is huge compared to most other tape products. You might want > to look at how you do collocation. We are only drip feeding tapes into scratch proportionally to the total storage growth. Ours is going well so far (less than a third Capacity) Cheers, Suad -- > > Adolph > > - Original Message - > From: "Jeffery Carroll" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Monday, March 05, 2001 7:19 PM > Subject: LTO Ultriums Drives with TSM? > > > > We are looking to possibly upgrade our ADIC Scalar libraries, replacing > our > > DLT 7000 drives with LTO Ultriums. I was looking for any real world > > feedback(overall satifaction, issues...etc)? > > > > > > Thanks, > > Jeff
Re: Win2000 system objects
I opened a PMR with Tivoli for this very same problem. I was told "working as designed". If you peruse the dsmsched.log, you will see that all the different pieces of the system object are getting successfully backed up. I honestly can't remember the reasoning I was given by Tivoli support that explained this as working as designed...but at the time it seemed to make sense, though I disagree that this is not a problem with this version of the client. To report that something is not getting backed up when it clearly is, should be considered a problem and not a design change! Anne Short Lockheed Martin Enterprise Information Systems Gaithersburg, Maryland 301-240-6184 CODA/I Storage Management -Original Message- From: John Bremer [mailto:[EMAIL PROTECTED]] Sent: Monday, March 05, 2001 6:16 PM To: [EMAIL PROTECTED] Subject: Win2000 system objects Greetings, I'm new to the forum. I am upgrading my clients to TSM 4.1 from ADSM 3.1.8. A Win2000 client with three partitions C: D: P: backs up successfully. I'm using a domain statement, nothing else special in the options file. Since upgrading to TSM 4.1 client, I now see filespace 'System Object'. The documentation says servers at 3.7.3 and higher support the "feature" to backup system objects as a group. Fine by me, but when I query filespace for this node, there is no start time, no completion time, no capacity utilization, etc. for filespace 'System Object'. We run e-mail notification scripts off these date/time fields, and they're going to fail without these completion statistics. Nothing unusual in the dsmsched.log. In fact, the last message is "Successful incremental backup of Registry". Thanks to anyone for any input to this problem. John Bremer LANL
Re: Netware/NAV-CE
What do you mean by something adverse? What symptoms ? Are you using the latest TSA files from Novell ? Mike > -Original Message- > From: Suad Musovich [SMTP:[EMAIL PROTECTED]] > Sent: â îøõ 06 2001 0:28 > To: [EMAIL PROTECTED] > Subject: Netware/NAV-CE > > We are trying to find out the deadly cocktail between NLMs on Novell. > > So far we have noted there seems to be something adverse when the > TSM 4.1.x client and NAV CE is running concurrently. (Note: we have > not seen the same problems running the ADSM 3.1.x clients) > > The server is running Netware 4.11, Service Pack 8a. > > Anyone experience similar problems? > > Cheers, Suad > --
Re: Client 4.1.1 for Netware not accepting login parameters
And so it is. Manuall states it was asking for a user id and not a node name. Thanks, Mike > -Original Message- > From: Remeta, Mark [SMTP:[EMAIL PROTECTED]] > Sent: á îøõ 05 2001 17:21 > To: [EMAIL PROTECTED] > Subject: Re: Client 4.1.1 for Netware not accepting login parameters > > It is not asking for a NetWare ID, it is asking for a TSM nodename and > node > password. Look at what is in <>, this is the default... > > Mark > > > -Original Message- > From: Mike Glassman - Admin [mailto:[EMAIL PROTECTED]] > Sent: Monday, March 05, 2001 10:18 AM > To: [EMAIL PROTECTED] > Subject: Client 4.1.1 for Netware not accepting login parameters > > > Anyone, > > I have just installed the 4.1.1 Netware client on one of my servers, after > we shifted from ADSM to TSM server. > > After I enter the line to start a scheduled backup, I get the following > prompt : > > Please enter NetWare user for "nwserver": > > In the previous clients, If this happened, I entered the user who has > rights > for backup, using the full contextual name, ie, .backup.organization > > When I do that now, it throws me out, and the log file (error) shows the > following : > > 03/05/2001 17:08:10 sessOpen: Error 137 from signon authentication. > 03/05/2001 17:08:19 cuSignOnResp: Server rejected session; result code: 53 > 03/05/2001 17:08:19 sessOpen: Error 53 receiving SignOnResp verb from > server > 03/05/2001 17:08:19 ANS1353E Session rejected: Unknown or incorrect ID > entered > > The log file shows : > > 03/05/2001 17:08:10 Querying server for next scheduled event. > 03/05/2001 17:08:10 Node Name: MASKORET > 03/05/2001 17:08:10 Please enter your user id : ANS1353E Session > rejected: Unknown or incorrect ID entered > 03/05/2001 17:08:19 Scheduler has been stopped. > > Does anyone have any idea what format the user name should take to be > accepted ? > > I have only one user who has backup rights, and I do not want to create a > user for backups on each server. > > Anyone ? > > Mike Glassman > System & Security Admin > Israeli Airports Authority > Ben-Gurion Airport > http://www.ben-gurion-airport.co.il > > Tel : 972-3-9710785 > Fax : 972-3-9710939 > Email : [EMAIL PROTECTED] > > Usage of this email address or any email address at iaa.gov.il for the > purpose of sales pitches, SPAM or any other such unwanted garbage, is > illegal, and any person, whether corporate or alone doing so, will be > prosecuted to the fullest possible extent.
Re: LTO Ultriums Drives with TSM?
Jeff, I have same kind of issue. Moving from STK9714 4xDLT7000 to STK L700 6xLTO. Now we start with DLT because LTO (Non IBM) are not available on TSM The only information that I have is LTO (HP, Seagate) on TSM 4.1 for Q2 2001 Regards, Eric -Original Message- From: Jeffery Carroll [mailto:[EMAIL PROTECTED]] Sent: Tuesday, March 06, 2001 1:19 AM To: [EMAIL PROTECTED] Subject: LTO Ultriums Drives with TSM? We are looking to possibly upgrade our ADIC Scalar libraries, replacing our DLT 7000 drives with LTO Ultriums. I was looking for any real world feedback(overall satifaction, issues...etc)? Thanks, Jeff
Re: TDP for SQL server login problem
Hello David, I remember a similar problem (may be the same) after upgrading the client. I tried a lot and after I enter a command like this SQLDSMC /BACKUPFULL: * /SQLUSER:sa /SQLPWD:"your_database_pwd" it works. hope this helps you joachim David Longo <[EMAIL PROTECTED]> on 05.03.2001 16:28:24 Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] cc:(bcc: Schwabe Gorbit/GE-Europe/3M/US) Subject: TDP for SQL server login problem We have an NT4.0 SP5 system with SQL 6.5. Recently upgraded from TSM client 3.1.0.6 and TDP MSSQL 1.1.1 to TSM 4.1.0.0 and TDP 1.1.1.01. After we did, the SQL databases weren't being backed up. We use the sqlfull.cmd for backups. When I checked logs I found this in sqlfull.log. —-- 03/01/2001 21:01:45,COMMAND LINE : C:\Progra~1\Tivoli\TSM\Mssql\sqldsmc /sqluser:sa /sqlpwd:pwd /backupfull:* /adsmoptfile:C:\Progra~1\Tivoli\TSM\Mssql\dsm.opt /logfile:C:\Progra~1\Tivoli\TSM\Mssql\sqlfull.log 03/01/2001 21:01:45,Logging on to the TSM server... 03/01/2001 21:01:51,Logging on to the SQL server... 03/01/2001 21:01:51,ACO4210E -- Failed to connect to SQL server. —- I can use the GUI and it connects to SQL server and backs up databases o.k. I can run the sqlfull.cmd on an NT window and it runs o.k. there. When this sqlfull.cmd is run from TSM Server, it does run because the ADSM autodelete, which is the last line in cmd does run successfully. (We did have problems deleting the "old" *SM stuff from the NT machine before installing new versions. The uninstall didn't work at all and our NT Admin, who is really good, had a difficult time deleting files and Registry entries for old stuff. There had apparently been some ODBC installed sometime in the past and that may have been part of problem.) I checked Tivoli Web site and can't find any relevant info. Why can't it connect to SQL when run as CMD from TSM Server? Thanks for ideas, David B. Longo System Administrator Health First, Inc. 3300 Fiske Blvd. Rockledge, FL 32955-4305 PH 321.434.5536 Pager 321.634.8230 Fax:321.434.5525 [EMAIL PROTECTED] "MMS " made the following annotations on 03/05/01 10:34:15 -- This message is for the named person's use only. It may contain confidential, proprietary, or legally privileged information. No confidentiality or privilege is waived or lost by any mistransmission. If you receive this message in error, please immediately delete it and all copies of it from your system, destroy any hard copies of it, and notify the sender. You must not, directly or indirectly, use, disclose, distribute, print, or copy any part of this message if you are not the intended recipient. Health First reserves the right to monitor all e-mail communications through its networks. Any views or opinions expressed in this message are solely those of the individual sender, except (1) where the message states such views or opinions are on behalf of a particular entity; and (2) the sender is authorized by the entity to give such views or opinions. ===
