ADSM-L

AW: NT Client V3 PTF5 Warning

1998-08-19 12:15:49
Subject: AW: NT Client V3 PTF5 Warning
From: Michael Bartl <michael.bartl AT ZENTRALE.ADAC DOT DE>
Date: Wed, 19 Aug 1998 18:15:49 +0200
Andrew,
let me try to answer your questions:

odbc errormessage:

An alertbox came up a few minutes after I had installed the new client. It
has following content (in german):
FEHLER
Die Indexerstellung konnte die Datei "C:\ADSM32\odbc\Adsm\odbcadsm.txt"
nicht indizieren. Um die Indexerstellung erneut zu starten, müssen Sie die
Datei löschen und anschließend auf Indexerstellung in der
Windows-Systemsteuerung doppelklicken.

I'll try some translation:
Indexcreation could not index the file. In order to restart the indexing
process you have to delete the file and doubleclick on indexing in Windows
control panel.

I clicked OK and up to now I not delete the file nor restart indexing in
control panel. I also did not run into further odbc problems but I don't
want to get this message on every high loaded server, as I can not tell our
NT system crew what is going on.


Expiring of Unicode filenames:
I get following message in dsmsched.log:
08/19/1998 09:55:02 Retry # 1  Expiring-->                  391
\\pc2049\c$\WINNT\Profiles\tkntest\StartmenǬ\programmE\ZubehÆôR\Multimedia\
Audiorecorder.lnk  ** Unsuccessful **

08/19/1998 09:55:02 ANS1228E Sending of object
'\\pc2049\c$\WINNT\Profiles\tkntest\StartmenǬ\programmE\ZubehÆôR\Multimedia
\Audiorecorder.lnk' failed

08/19/1998 09:55:02 ANS1304W Active object not found

All those files remain active as one can see in the dsmc picklist:
  1510. |           387  A
\\pc2049\c$\WINNT\Profiles\ivsfr\Startmenü\programmE\zubehör\multi
  1511. |             0  A
\\pc2049\c$\WINNT\Profiles\ivsfr\Startmenü\Programme
  1512. |             0  I
\\pc2049\c$\WINNT\Profiles\ivsfr\Startmenü\Programme
  1513. |             0  A
\\pc2049\c$\WINNT\Profiles\ivsfr\Startmenü\Programme\Autostart
When restoring after one completed backup with Unicode OFF there should not
be any unicode files left, marked active in the picklist.

I read through the new readme files and must say that the UNC naming really
seems to work as designed. I just didn't expect such heavy changes from one
PTF to another (I would have expected similar changes from V2 to V3 or maybe
from 3.1 to 3.2, but not from 0.3 to 0.5...).
Going through our manuals for the storage team think the changes are
manageable.

Thank you for your help,
regards,
Michael
--
Michael H. Bartl
Michael H. Bartl
ADAC e.V. (Rechenzentrum, Produktionsplanung und Organisation)
Tel.: (089) 7676-4063, Fax: (089) 7676-8161
EMail: Michael.Bartl AT Zentrale.ADAC DOT de

> ----------
> Von:  Andrew Raibeck[SMTP:storman AT US.IBM DOT COM]
> Gesendet:     Mittwoch, 19. August 1998 12:57
> An:   ADSM-L AT VM.MARIST DOT EDU
> Betreff:      Re: NT Client V3 PTF5 Warning
> 
> Hello,
> 
> I am very sorry that you are having problems right out of the gate with
> this
> new client! I am very interested in understanding what the problems are.
> 
> First the easy issue: the change to UNC names for the filespaces is
> deliberate,
> and documented in the BACLIENT.TXT file. A big warning appears at the top
> of
> the README.FTP file and very near the top of the README.1ST file in the
> "Warnings" section. The restore command syntax hasn't really changed,
> except
> that you use the UNC name as the filespace name instead of the volume
> label if
> the filespace has been migrated (BACLIENT.TXT has the details). I urge you
> to
> refer to these README files about this issue, as well as other changes.
> 
> I have installed the PTF 5 client on my own machine at work, and have not
> seen
> any error messages related to ODBC. Can you describe for me in more detail
> what
> is happening when these messages occur, and what the specific messages
> are?
> Also, what version/SP of NT are you running?
> 
> Messages encountered when expiring files previously back up with unicode
> filenames: what messages are you getting?
> 
> I will investigate the performance issue with the scheduler and the blank
> lines
> in dsmsched.log.
> 
> I am not in the office this week (I'm at SHARE) so I won't be able to do
> anything immediately. However, when I get back to the office I'll start
> checking these things out.
> 
> If you like, you can respond to me privately at storman AT us.ibm DOT com
> 
> Best regards,
> 
> Andy
> 
> Andy Raibeck
> IBM Storage Systems Division
> ADSM Client Development
> e-mail: storman AT us.ibm DOT com
> 
> Please respond to ADSM-L AT VM.MARIST DOT EDU
> To: ADSM-L AT VM.MARIST DOT EDU
> cc:
> Subject: NT Client V3 PTF5 Warning
> 
> 
> Yesterday I downloaded the new V3 Client for NT (PTF5)...
> 
> We're glad not having installed the code on any server with heavy
> production
> load as it caused lots of problems on the test machine:
> 
> - The ADSM scheduler service nearly blocks the machine after every
> scheduled
> backup session. It consumes 100% of available CPU power and slows down the
> machine into a state of "impossible to work with". After stopping and
> restarting the service the problem gets solved temporarily.
> 
> - All filespaces get renamed
> A filespace previously labeled "SRV123_D" now gets renamed into
> "\\srv123\d$", the name of the volumelabel is not used any longer.
> 
> - DSMC restore syntax changed
> Following the change in filespace labelling the syntax of most restores
> also
> has changed. We saw the great advantage of the new possibility to enter
> national characters (e.g. german umlauts) in the commandline, but have to
> edit all manuals for our storage administrators that are involved into
> restore activity.
> 
> - Problem when expiring files previously backed up using unicode
> filenames.
> The client runs into an error when trying to expire such files. As a
> consequence all those files remain active until this gets fixed or you
> create a new filespace and delete the old one.
> 
> - Errormessage from odbc
> After having installed the new PTF an alert box appears stating an Error.
> There seems to be a problem with odbc support files. We didn't do any
> further investigation on this.
> 
> - DSMSCHED.LOG
> In DSMSCHED.LOG the new client spits out a blank line after every line
> written. This is not a very hard error but the logfile doesn't really get
> more readable...
> 
> 
> I think the developers should sit down again and do some work to get the
> fixes fixed before the client gets usable,
> 
> Regards,
> Michael
> --
> Michael H. Bartl
> ADAC e.V. (Rechenzentrum, Produktionsplanung und Organisation)
> Tel.: (089) 7676-4063, Fax: (089) 7676-8161
> EMail: Michael.Bartl AT Zentrale.ADAC DOT de
> 
> 
> 
> 
<Prev in Thread] Current Thread [Next in Thread>
  • AW: NT Client V3 PTF5 Warning, Michael Bartl <=