The natural way to achieve this, would be a dsmmigfs remove, but
this process recalls all files ...
So maybe you try something like the following (which I did not test):
- unmount the filesystems
- kill the HSM processes (and prevent them from being started again
-- rc.adsmhsm in inittab)
-
Hello tsm-world,
I updatet several hundred NT4 SP 6 boxes with no problems. But there is one
that drives me crazy. I`m not able to update to any 4.x Version. I tried
4.1.16, 4.1.3 and 4.2.1. I get always an error saying
the wizard was interupted before TSM Client could be installed. Your
system
[EMAIL PROTECTED]
Met vriendelijke groet,
With kind regards,
Christian Bults
Hello, this should be an easy one...
The TSM Server has schedmode set to any. What can I run from the server to
see what mode a client is using? I have been selecting from various tables
but have not had any luck in finding the answer.
Thanks,
Jon
Hi
You can check the activity log to see how the client contacts the server.
You should be able to read if the client contacts the server(polling), or
if the server contacts the client(polling).
Best Regards
Daniel Sparrman
---
Daniel Sparrman
Exist i Stockholm
Sorry, that should be polling and prompted, not polling and polling... :)
Best Regards
Daniel Sparrman
---
Daniel Sparrman
Exist i Stockholm AB
Bergkällavägen 31D
192 79 SOLLENTUNA
Växel: 08 - 754 98 00
Mobil: 070 - 399 27 51
Jon,
Bad news, you can not see what the schedmode for the
client on the server.
Because the parameter is set in the dsm.sys file
(Unix) or the dsm.opt file (Windows).
If you do not see the schedmode parameter in the
file then the default is being used.
I believe the default is polling.
Sias
I've been using TSM for quite a few years on AIX, and surprisingly, this
issue hasn't come up before.
My customer is using TSM in conjunction with Content Manager OnDemand. The
config looks like this:
AIX 4.3.3 on H70
OnDemand, DB2, TSM
Data is cached on disk (by OnDemand, not TSM), and also
As was suggested, check the activity log. You will have to associate the
messages yourself, TSM does not do a very good job tying messages logically
together. The session below that has a summary record is 955.
01/23/2002 10:00:01 ANR2561I Schedule prompter contacting NORBERTSTA
(session 952)
Sias,
What you are saying is accurate but if the client is using prompted, the
server somehow needs to know that. The point being if you tell me to call
you I would need to have a system for remembering that. If the client
requests to be prompted then the server must also have a way of
I'd suggest using TSM to back the data up to LTO, then back up the LTO
storage pool to a copy pool and send the copies off-site. Run reclaims and
only bring back empty or pending empty off-site tapes. My worst case sends
off a tape that is 5% full daily. The reclaim actually kicks in just after
Justin,
TSM isn't really designed for a regular offsite rotation. The intention is
to send the copy storagepool tape offsite each day, regardless of how full
it is. You then perform offsite reclamation, which uses primary storage
pool tapes (or optical) to recombine the data from several
As Tom mentioned, the key here is the reusedelay parameter on the copy
storage pool. You don't bring a tape back from off-site until you are sure
that its replacement is off-site as well. If you assume it takes two days
for a newly created copy storage pool tape to arrive safely offsite, then
You can sort of tell this on the server side by doing a query like this:
q actlog begind=-1 search=nodename
By looking that time entries for the hits you get if you see a definite time
pattern, say every six hours, you can probably assume polling. If you see
only a single hit or perhaps none,
28 GB database, AIX 4.3.3, TSM Server 4.2.1.9: UNLOADDB took about 9 hours,
LOADDB took about 3 hours. Database shrunk by 30%.
-Original Message-
From: Christo Heuer [mailto:[EMAIL PROTECTED]]
Sent: Monday, January 21, 2002 4:16 AM
To: [EMAIL PROTECTED]
Subject: Re: How long does a
I continue to get the following error on all my systems that have the
/usr/bmc/lost+found directory/path:
01/23/02 00:47:15 PrivIncrFileSpace: Received rc=106 from
fioGetDirEntries: /usr/bmc /lost+found
I was pretty sure that the PrivIncrFileSpace was a permission issue
Had an issue a few weeks ago where our TANDEM client appeared to lockup when
our ADSM ( Yes - Version 3.1 ) server crashed due to a log file over commit.
Has anyone encounter a similar problem with the TANDEM client and were you
able to diagnose it. I think the tandem may have had an active
Well, I thank ye for the kind words!
Glad to give something back.
(And hopefully make up for the occasional muffed answer...)
-Original Message-
From: Kelly Lipp [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, January 23, 2002 7:07 PM
To: [EMAIL PROTECTED]
Subject: Re: Rebinding
Jeff,
WOW! Thanks Andy -- That new feature slipped by me, Im turning it on now!
-Original Message-
From: Andrew Raibeck [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, January 22, 2002 9:12 AM
To: [EMAIL PROTECTED]
Subject:
I forgot to mention:
Starting with the 4.2 client, you can now use
I cannot help with the problem, but I would like to know how you turned on
the logging!
-Original Message-
From: Holger Bitterlich [mailto:[EMAIL PROTECTED]]
Sent: Thursday, January 24, 2002 4:54 AM
To: [EMAIL PROTECTED]
Subject: Win NT 4 Installer Problems with several TSM Clients
Set Access
The set access command gives users at other nodes access to your backup
versions, archived copies, or backup images. You can give another user
access to a specific file or image, multiple files or images, or all files
or images in a directory. When you give access to another user,
Hi
I am sure that this is another easy answer that's actually right under my
nose somewhere, but here goes...
Does anyone know the process for restoring to another client in AIX?
Thanks in Advance!
_
MSN Photos is the easiest
Are there any files/dirs in the lost+found directory that may have names
that begin with ??
-Original Message-
From: George Lesho [mailto:[EMAIL PROTECTED]]
Sent: Thursday, January 24, 2002 10:20 AM
To: [EMAIL PROTECTED]
Subject: TSM error log question
I continue to get the following
Change the nodename in dsm.sys to the node you want to restore.
Or use virtualnodename.
Regards,
Wouter.
-Oorspronkelijk bericht-
Van: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]Namens TSM
Group
Verzonden: donderdag 24 januari 2002 18:17
Aan: [EMAIL PROTECTED]
Onderwerp:
There are two ways to do this, depending on whether you want to just do it
once or whether you want to do this routinely. For one-off restores, I
usually just create a dsm.opt on the target file with a virtualnodename
parameter pointing to the source data, then say dsmc -optfile=...
I have run into this before. You probably have a session of msiexec.exe
still running in the background. If you start Task Manager, and view
Processes, you will probably see msiexec.exe running. You will need to kill
this. By doing this, I have sometimes gotten around the problem. But
dsmc -virtualnode=nodename
or
modify the client's dsm.sys nodename to the client you wish to restore
-Original Message-
From: TSM Group [mailto:[EMAIL PROTECTED]]
Sent: Thursday, January 24, 2002 12:17 PM
To: [EMAIL PROTECTED]
Subject: Restoring to another client
Hi
I am sure that this
What in the world is this? TSM Client on HP-UX 4.2.x. This has been asked
before but never really answered so I'll try again.
Thanks,
Kelly J. Lipp
Storage Solutions Specialists, Inc.
PO Box 51313
Colorado Springs, CO 80949
[EMAIL PROTECTED] or [EMAIL PROTECTED]
www.storsol.com or
Use the -fromnode option in your restore/retrieve command.
Steve Argersinger
Ruan Transportation
-Original Message-
From: TSM Group [mailto:[EMAIL PROTECTED]]
Sent: Thursday, January 24, 2002 11:17 AM
To: [EMAIL PROTECTED]
Subject: Restoring to another client
Hi
I am sure that this is
Hi Kelly,
This is coming from the part of TSM that parses your include/exclude list.
Besides the obvious fact that a better message is needed... what does this
client's include/exclude list look like (including any client options
defined on the server)? This problem could be coming from a
Hello everybody,
TSM does a pretty good job on the tape management by space reclamation and copying the
primary pools to copy pools.
But I'm wondering how I can estimate the size of the library (number of slots, type of
drive) to reach this steady state of tape usage. Of course I've got the
I posted this stuff a while back... might be useful:
1. q actl begindate=-30 search=ANR1214
add up the daily archive and backup copy from primary to copypool
storage and divide by 30; now you have a per day
average that is being backed up. Double the value because we have
primary and
Wouter,
I have seen the Windows service crash from two different reasons:
1) corrupted file on the disk; use CHKDSK to fix any corrupted files.
2) wrong version of certain DLLs included with the client; check the DLLs
in the client directory. There are tools that display the version of the
DLL
Wouter,
You didn't provide info on your disk pool setup, but a few months back on
the forum there was a discussion on whether it was better to use one big
volume or carve up the disks into multiple smaller volumes.
If you encounter media wait status during migrations at the low migration
Just call setup /v/l setup.log
If you want to see all of the setup switsches look at
http://support.microsoft.com/newsgroups/
--
Holger Bitterlich
Stadtsparkasse Köln
Organisation und Datenverarbeitung
Telefon: (0221) 226 - 54 18
Fax: (0221) 226 - 51 00
mailto:[EMAIL PROTECTED]
35 matches
Mail list logo
