Hi All,
Hopefully a quick question, if I perform a move node data command for a
client in the primary storage pool, and it moves all the data onto one tape
in that storage pool, will this change be written out to the copy storage
pools? i.e will the copy storage pools, after doing a backup of the
On Wed, Jun 09, 2004 at 08:43:19AM +0100, Copper, Steve wrote:
pools? i.e will the copy storage pools, after doing a backup of the primary,
have all the data for that client on one tape as well,
No, the copypool will not be affected.
or do I have to issue
the move node data command for the
Hi Gordon!
From the messages manual:
ANR9638W (HP-UX) License registration is not supported on this server.
Explanation: The REGISTER LICENSE command fails because the license
authorization module cannot be found.
System Action: Server operation continues; licensing terms are not changed
by the
Hi Arnaud!
The location Daniel pointed you to doesn't seem to be really up-to-date.
I asked IBM the same question a few days ago and I just received an answer.
The most recent library firmware is 2.19 for a library with the multi-path
feature, 1.38 for a library without the multi-path feature.
I think you only need install License files as part of TSM server
installation package from original base (4.1.0) CD, which are not part of
downloadable server patches and updates. Don't install other server code
from CD, but licenses only. I had never installed HPUX TSM server, but I
think that
We were documenting some TSM server recovery scenarios the other day,
and came up with one I haven't seen discussed before. Here's the
scenario:
Client backups finish, storage pool backups finish, TSM DB backup
finishes, prepare run.
Expiration runs.
Primary tapepool reclamation reclaims tapes A
...
The question is, what do we need to put in the recovery procedure to handle
this? I can probably prevent it by setting reusedelay on the tapepool, but
we're short on tape slots most of the time, and letting the reclaimed tapes
pend until the oldest DB backup expires like we do our copypool
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On
Behalf Of Richard Sims
...
The question is, what do we need to put in the recovery
procedure to handle
this? I can probably prevent it by setting reusedelay on the
tapepool, but
we're short on tape slots most of the time, and letting
Solution was rather simple actually. The passwords had changed since
these instances were generated. I went back to the old passwords and all
was well.
Mark
--
Mark Ferraretto
Unix Systems Administrator
Deutsche Bank Hong Kong
ph: +852 2203 6362 Unix support hotline: +852 2203 6369
[EMAIL
I want to upgrade my TSM server on AIX from 5.2.1.3 to 5.2.2.5.
Can I do this jump or do I have to go to 5.2.2.x first ?
Upgrading from 5.2.1 to 5.2.2 is a minor change, and is what IBM considers
a level increase. From my System/370 days, I remember that IBM
classified its software products as Release.Version.Level, so TSM falls
in this category. We have upgraded our TSM Host Server from 3.7 to 5.1.9
and it
Your scenario is EXACTLY what REUSEDELAY is designed to prevent.
Use it or lose it!
-Original Message-
From: Bill Mansfield [mailto:[EMAIL PROTECTED]
Sent: Wednesday, June 09, 2004 8:03 AM
To: [EMAIL PROTECTED]
Subject: Reclamation data loss scenario
We were documenting some TSM server
Read the readme for 5.2.2.5 - it tells you what you need to be running:
ftp://service.boulder.ibm.com/storage/tivoli-storage-management/patches/serv
er/AIX/5.2.2.5/TSMSRVAIX5225.install.txt
This patch requires that you have release 5.2.2.0 installed
-Original Message-
From: Zoltan
you could also declare the corrupted volumes destroyed after you have
restored your db. Then you restore your storagepools from your
copystoragepools and everything is fine again.
True you have lost whatever was backed up after your last backup of your
storagepools, but that should be less then 24
OK, #1 below wouldn't work either without bringing offsite tapes back!
Yes. Keep in mind that MOVE NODEDATA is not very useful for offsite
copypools, since it requires the copypool-volumes to be onsite and
available. (It doesn't work like e.g. MOVE DATA does, which gets the files
from the primary
Is there a way to pass the fromnode parm to an archieve using the GUI?
On NT/2000, Start the GUI from the command line
change into the baclient directory and type dsm -nodename=NAME
(You can also do this from run command on the start menu)
Doug Thorneycroft
County Sanitation Districts of Los Angeles County
(562) 699-7411 Ext. 1058
FAX (562) 699-6756
[EMAIL
Ah.I'm trying to allow a user to do a -fromnode from one AIX to
another without using the command line. They invoke it via the web.
[EMAIL PROTECTED] 06/09/2004 10:56:13 AM
On NT/2000, Start the GUI from the command line
change into the baclient directory and type dsm -nodename=NAME
(You
When you start dsm, check out the Utilities/Access another node... menu
item.
Regards,
Andy
Andy Raibeck
IBM Software Group
Tivoli Storage Manager Client Development
Internal Notes e-mail: Andrew Raibeck/Tucson/[EMAIL PROTECTED]
Internet e-mail: [EMAIL PROTECTED]
The only dumb question is the
ON THE WEB GUI UNDER UTILITIES THERE CHOICES APPEAR:
CHANGE PASSWORD
DELETE ARCHIVE DATA
DELETE FILESPACES
Nothing about accessing another node..
[EMAIL PROTECTED] 06/09/2004 11:45:07 AM
When you start dsm, check out the Utilities/Access another node...
menu
item.
Regards,
Andy
Andy
If you want to pursue this, you'll have to run a select statement
against the VOLUMEUSAGE to find the relevant offsite pool volumes. Check
in the volumes from the resultant list, and run your MOVE NODEDATA.
--
Mark Stapleton
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL
As luck would have it, the nodes I moved were large file servers and my
copy pool is not collocated. I probably have data spread across 600
volumes. I think I'll pass on bringing them back
This is by no means a new frustration for many folks. Any idea why old
big blue hasn't tried to add
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On
Behalf Of David Nicholson
As luck would have it, the nodes I moved were large file servers and my
copy pool is not collocated. I probably have data spread across 600
volumes. I think I'll pass on bringing them back
This is by no
On Wed, Jun 09, 2004 at 12:10:32PM -0500, Stapleton, Mark wrote:
I used to think the same thing, but it occurred to me that, while there
is a one-to-one correspondence between a file in an copy pool and the
copy of the file in a primary pool, there is not necessarily a
one-to-one relationship
Yeah you would think this is easy unless I'm missing something ...
MOVE DATA works properly for offsite data - ie if you issue a move data
for a volume that is offsite, it will move the data to another volume in the
same copy pool using the primary storage pool as input.
Why does MOVE NODEDATA
One thing that appens during that time is that the TSM server is
downloading directory entries to the client, to sort through and decide
what to back up. With millions of entries (which it appears you have),
it can take awhile. We had a situation with a terribly fragmented DB,
where this pause
That is a good question. We just did the same thing, and I was thinking
there should be a better way to do it.
On Wed, 9 Jun 2004, David Nicholson wrote:
As luck would have it, the nodes I moved were large file servers and my
copy pool is not collocated. I probably have data spread across 600
Thanks for the responses. I'm going to implement a cron job tonight to query
the sessions every few minutes to see exactly what the session in question
is doing during the inactive time.
Journaling (as suggested in another message) is currently being tested for
some on one of our servers. We had
Tim,
I tried a MOVE DATA for offsite data...it did not go after the
data in the primary pool...it wanted to mount the volume in the copy
pool...which was offsite.
Am I missing something?
Dave Nicholson
Whirlpool Corporation
Rushforth, Tim [EMAIL PROTECTED]
Sent by: ADSM:
We do this all of the time - it works for us! And the help for move data
says it works this way. We are currently running 5.2.2.4 but were
previously at 5.1.6.4 and it worked there also.
It is basically the same way offsite reclamation works.
From the help:
You can use this command to move
Thanks for the replies. I did forget to install the licensing package from the
original CD, but I've managed to find our CD now and will just install the license
installation program from there. I don't think it should matter that the CD is v4.2, a
lower version then the actual server version I
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On
Behalf Of David Nicholson
I tried a MOVE DATA for offsite data...it did not go after the
data in the primary pool...it wanted to mount the volume in the copy
pool...which was offsite.
Am I missing something?
Something is
32 matches
Mail list logo
