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\c$", 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
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
|
