Re: stk 9840

2000-09-10 Thread Walker, Lesley R

Bill Colwell [SMTP:[EMAIL PROTECTED]] wrote:
> We got 9840's very early and 3590 emulation wasn't available.
> At the time we were running adsm 3.1 & tsm 3.7 didn't exist, so
> there was no performance difference.  You should choose 3590
> emulation if there are no strong reasons for doing 3490 emulation.
>
> If your site is os/390 and has dfsms-hsm, you definitely want
> 3590 for block count reasons.
>
Sorry, I guess I didn't frame my question clearly enough.  I'm planning on
using them in their standard STK9840 mode, and was wondering what was the
point of emulating other tape types.  My servers will all be running on
Solaris and your mention of OS/390 is probably enough of a clue for me.

That'll teach me for having OS-tunnel-vision.



Re: stk 9710

2000-09-10 Thread Carl Makin

Hi Kelly,
We're running a StorageTek 9710 direct to ADSM (ie not with ACSLS).

On Sat, 9 Sep 2000, Kelly J. Lipp wrote:

> The syntax of the label libvol command is wrong.  It should be:

> label libvol libname search=yes volrange=1stvol,lastvol checkin=scratch

> You can't use the labelsource parameter.

Yes you can, but you must use the search=bulk command to get the barcodes
from the CAP.

Here is the command we use to label and checkin new tapes.

label libvol stk9710 search=bulk checkin=scratch labelsource=barcode



Carl.



NT client 3.7.2.0 installation

2000-09-10 Thread Eric Tang

Hi all,

I am installing TSM NT client 3.7.2.0 to NT4.0 SP5 for customer today.
During installation, there are a few problems:
1) During installation, there are two prompts of "Severe: The service
cannot be installed due to an unknown error".
2) I uninstall TSM client, and reboot machine. Reinstall TSM client got the
same two prompts of error.
3) I skip these errors and finished installation. in command line, run dsmc
archive (or inc) on a small file (dsm.opt) Dr watson: dsmc.exe Exception:
access violation (0xc005) Address 0x0047b1cb
4) In GUI, archive a file, there is ANS5148W message found in dsmerror.log
as below.
The node is newly registered on TSM server (AIX TSM3.7.3.0) and I don't why
there is such an message.

ANS5148W The server needs to do a one-time conversion of your archive data
before you can continue.
This operation may take a long time, and cannot be canceled once it has
started.
Are you willing to wait for the conversion to complete?

5) I reply this message and archive on GUI works OK. Retrieve is also OK.
6) From "Services" in "Control panel", found that "Client Acceptor" &
"Remote Client Agent" are installed but not
"Central Scheduler Service".
7. Perform "dsmctuil installl scheduler" and scheduler service install OK.
8. In TSM Server, Define schedule to selective backup a small file on NT
client, scheduler is running OK and the file is backup.

Question:
1) how to determine what is the "service" cannot be installed. Does TSM
install the 3 services "CAD, Scheduler,  Remoteagent" by default, if so,
will it be an indicator on scheduler installation error?
2) why command line got Dr watson but not GUI or scheduler?
3) The node is newly created on server, why is there ANS5148W message?
4) MS Exchange & Arcserve (evaluation copy)  are installed on the NT box,
any conflict to TSM? (although I don't think there is)

dsm.opt

COMMMETHOD   TCPIP
TCPSERVERADDRESS 172.20.77.1
TCPPORT  1500
Compression  Yes
* CHAngingretries  0
tcpclientaddress 172.20.68.3
tcpclientport1501
schedmodeprompted
* schedmodepolling
* querysch 1
nodename n7007hmx
password n7007hmx


Thank you in advance.

Regards,
Eric Tang



What's the newest client version that works for FreeBSD

2000-09-10 Thread Steinar Haug

We're running the SCO version of the ADSM command line client, version
2.1 on FreeBSD (3.4 and 4.1). Is there any newer version that works with
FreeBSD? We're only moderately happy with the 2.1 version - it's missing
some important features (ability to backup specific directories/files),
and it core dumps fairly frequently.

Steinar Haug, Enitel Internet, [EMAIL PROTECTED]



Re: MS Exchange Incremental Backups

2000-09-10 Thread Michel Engels

We do use TDP for Exchange V1.1.2 and successfully restored a database with some
incrementals. All this was done on a test environment and we hope we will never
have to do it on a production server. Not that we have a doubt about TSM but
having to restore means problems with the production database and do we find the
cause.

We did not test previous versions.

Hope this help,

Michel Engels
Devoteam - MSB Belgium





Sean McNamara <[EMAIL PROTECTED]> on 09/08/2000 04:43:10 PM

Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>

To:   [EMAIL PROTECTED]
cc:(bcc: Michel Engels/BE/Devoteam)

Subject:  MS Exchange Incremental Backups



Hello Guru's,

Real quick question - Do incremental backups work properly when running
TDP for MS Exchange version 1.1.1 (Exchange Server 5.5 - Service Pack 3)?  Has
anyone been able to restore from a full and incremental backup??

Thanks,

Sean McNamara
Senior Analyst
PJM Interconnection L.L.C.
(610)666-4206



Re: samples..........

2000-09-10 Thread Richard Sims

>Does anyone know of way of telling how many entries you have in a
>database without doing a unloaddb.??

select sum(num_files) as "Total files" from occupancy

will tell you how many filespace objects are in the database
(which does not include administrative objects, log entries, and the like).

   Richard Sims, BU



Re: Monitoring, and Generating alerts from ADSM.

2000-09-10 Thread Suad Musovich

We have some Perl scripts which query the activity logs and report on a
bunch of things, like;
* Tape requests (our Silo fillith over)
* successful/missed scheduled sessions
* Summaries
* System alerts

Most things get emailed to the appropriate person. Redirecting to a logging
server wouldnt be too much of a hassle, I wouldn't think.

Cheers, Suad
--


On Fri, Sep 08, 2000 at 09:56:45AM -0700, Daniel Swan/TM wrote:
> My org has determined that they'd like to incorporate ADSM into our existing
> alert infrastructure.   I figure it's a matter of parsing the event log,
> formatting the
> information, and writing it to a logfile.  The logfile is then read by a
> daemon, and
> forwarded to the Alert/Logging server.  Failed/missed backups will result in
> a late-nite page.
> (Oh goody!).
>
> Before I go about doing this though, I'd like to know about methods you
> folks have
> used for monitoring ADSM, how it is architectured, and any code you'd care
> to share.
>
> No sense re-inventing the wheel.
>
> Best regards,
> Dan.