of the clone --to create a new TSM server?
If that is a straight forward process it might save us time in a
deadline-driven hardware upgrade.
If this is well documented somewhere, kindly refer me to that.
With my thanks,
Keith Arbogast
Indiana University
Ron,
Thank you for the references and your advice. I will read the documentation
carefully and consider whether the reward is worth the possible complications.
Maybe not.
Best wishes,
Keith Arbogast
Indiana University
On Mar 4, 2014, at 2:37 PM, Ron Delaware wrote:
Keith,
you can find
.
Best wishes,
Keith Arbogast
Indiana University
,
Keith Arbogast
on the VTL will be
adversely affected. We write those backups to physical tape.
Keith Arbogast
Indiana University
the deduplication process. After that I
deleted the volumes because I need the LDEVs back for another purpose.
Best wishes,
Keith Arbogast
Indiana University
wishes,
Keith Arbogast
Jim,
Re: I found I had to run 'audit licenses' to update the occupancy values. I
have no idea why this would be the case.
One always has to run 'audit lic' to update the auditoccupancy table.
Keith
on these clients, their
next backups ran normally.
No Windows servers on any version of the TSM client had this problem. No Linux
clients on other releases than 6.3 had this problem. No Linux clients running
dsmcad instead of 'dsmc sched' had this problem.
Best wishes,
Keith Arbogast
Indiana University
that were already moribund. There
are about a dozen V5 clients left, but most of them belong to the 'Unix Support
Group' who can roll with the punches.
Best wishes,
Keith Arbogast
system. ..Databases
that were created with server V6.2 server define DB2 9.7 tablespaces with
reclaimable space enabled.
Best wishes,
Keith Arbogast
Indiana University
Can one detect from the TSM server whether client-level encryption is set on or
off for each backup node? Inquiring security admins want to know.
With my thanks and best wishes,
Keith Arbogast
Indiana University
We ask client admins to compress their data if they are encrypting it, since
encrypted data cannot be compressed by tape drives. It's important to note that
certain file types don't compress well, and to exclude them with
exclude.compress statements.
Keith
it?
Thank you,
Keith Arbogast
Ian,
The Technote says, When predefining volumes, the Tivoli Storage Manager server
will use all of the volumes in one directory before using the volumes in
another directory.
Here is the example:
7) Sort list of empty volumes alphabetically: List appears as
c:\.BFS
This question came up again here. If a TSM admin with system authorization
knows the client password for a certain TSM node, what keeps him from restoring
files from that node to another server of his choosing?
Sorry to resuscitate this old horse.
With many thanks,
Keith
When client backups are being deduplicated by the TSM server, does the audit
occupancy table show reporting occupancy or physical space occupied by client
data? Reporting occupancy is the space a client's data would occupy if it were
not in a deduplicated pool. The Occupancy table shows
E06 drives won't write E06 formatted data to a tape that has already been
written to in E05 format. But, once the device driver is updated, the E06
drives will write E06 format to scratch tapes without a re-label.
With my thanks,
Keith
checked-out tapes.
Or, is there a simpler, more efficient way to do this? Would new storage pools
help in the transition?
With my thanks,
Keith Arbogast
Robert et al;
Will updating the device class make the new drives write files to tapes in E06
format which have previously been formatted and written to in E05 format?
Filling volumes would then have a mixture of E05 and E06 formats. Will TSM do
that? Are the device drivers, or what not, smart
Robert,
Thank you, I just did. We're on 6.2.2 also. I'll update the thread when they
respond.
Best wishes,
Keith
what backed up etc.
Anyway, I guess I say all that to say I prefer the generic TSM Node name
approach.
Good luck!
Ray
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of
Keith Arbogast
Sent: Wednesday, August 31, 2011 1:59 PM
To: ADSM
of backup
instances.
Thank you,
Keith Arbogast
to hear if I have missed the point somewhere in absorbing the
TSMVE documentation.
With best wishes,
Keith Arbogast
I'm in syntax purgatory trying to get output from query volume on a
devclass=file storage pool. If I add the reported volume name as an argument,
'No match' is returned to the query. If I omit the Volume name, and append
'deviceclass=file' or 'stg=stgpool_name', with format=detailed, normal
HI Andrew et al;
Thank you for helping with that. I had not made the mental adjustment that
something in a TSM query could be case-sensitive. I have now.
Best wishes,
Keith
Zoltan,
I run 'reconcile volumes virtual volume devclass_name fix=yes' once a month.
Our TSM servers are both running version 6.2.2.2, and reconcile finds hundreds
of invalid volumes each time it runs. Others' experience may be different. In
our situation, I should have opened a PMR long
Zoltan,
Try running reconcile volumes from both ends. When we do that, it deletes a
surprising quantity of orphan virtual volumes.
Keith
Remco and Stefan,
Thank you for your interesting replies.
Best wishes,
Keithy
and the Library, or between
the Library Manager and the Library?
With many thanks,
Keith Arbogast
I thought a setup step was required on the 3584 to: [+] Library / Logical
Libraries / Modify Encryption Method / Application-Managed Apply
Yes/No?
Keith
. So
we do not use drive-based encryption, and tell our customers to use
client-based encryption, specifying 'encryptkey save'.
I cannot guarantee that TSM will never lose an application managed encryption
key. Am I missing something?
With my thanks,
Keith Arbogast
Is there a way a TSM client admin can preview what an incremental backup is
going to do? That is, without copying the new/changed files to a storage pool?
Someone here would like to do that. The only ideas I could offer were 'query
inclexcl' and comparing the timestamps on files and
My age is a closely guarded secret, until days like this.
K.
David,
We have done that. Please send me your full e-mail address. We tried something,
but it bounced. We need more hints.
Thank you,
Keith Arbogast
Indiana University
For what it's worth, we run 6.2.2.2 on RHEL5, and have had no trouble with
macros.
Keith
this technique depends on Randomization working as well with long
Schedule Durations as with shorter, does anyone have experience with Durations
of four hours or more? Did it go alright?
Any reactions to these ideas would be gratefully accepted.
With my thanks and best wishes,
Keith Arbogast
Wanda,
Thank you. It's helpful to know you have been doing that routinely.
Best wishes,
Keith
Jim,
Thanks for the new idea. I'll have to ponder that one.
Best wishes,
Keith
They are reclaimed the same as physical volumes. Just like physical volumes,
they need to be 100% empty before they return space and can be reused.
The reclamation process will move the data off eligible volumes (volumes under
the reclamation threshhold) in order to make them 100% empty.
' on a
virtual volume recover empty space like it does on a physical cartridge? Or,
does the empty space get moved too?
Move data is not an efficacious solution to this problem. Is there a better one?
With my thanks,
Keith Arbogast
Indiana University
Jim,
You must mean FULL rather than FILLING, and PENDING rather than SCRATCH,
yes/no?
Thanks again,
Keith
Sorry. Move data does send volumes to 'scratch'. In the case of virtual
volumes they are not reused.
Keith
My specific problem is with a tape pool that is a target for virtual volumes
created by a remote TSM server. The number of cartridges in use by the pool
goes up and up, at a faster rate than the data growth on the remote server. I
suspect there are many virtual volumes in the target pool with
Shawn,
Your mention of the 50 GB MAXCAP on the device class was a jolt. Ours is 1 TB,
and I see that could be exacerbating the problem. The bigger virtual volumes
are, the more space they lock and the greater chance they contain active files,
which results in longer lifespans for them.
What
Joerg,
The nut of the problem, if I have this right, is that virtual volumes aren't
reclaimed the same way as physical volumes. They have to be 100% reclaimable
before they return any space. Their pct_utilization does go down, but the empty
space in them is locked until they are completely
Neil and Steve et al;
I appreciate your comments, though I am not the seer that dreamed of this.
...
The intention behind it could be to share tape drives without using a Library
Manager, and to add TSM servers without buying more hardware. Our TSM server
databases and boot disk are on the
restore files come from? How would that be managed?
Our TSM license is based on TB in primary storage, so extra licenses are not a
factor.
Please, don't be shy.
Thank you,
Keith Arbogast
Indiana University
I should clarify that client backups would be written to primary pools on disk.
So, my subject line is misleading. There would be primary pools on disk, but
no primary pools on tape.
Hope that clears up any confusion I created in the way I stated my question.
Thank you,
Ketih
Andy,
I omitted from my original problem statement that the TSM servers on virtual
machines would have primary pools on disk, just no primary pools on tape.
Client backups would be written to the disk pools, then copied to the two copy
pools.
The total backup workload would not be reduced,
Hi Gary,
I used the Server Upgrade Guide as a task list, and did the 'Scenario 2: Same
system, network method'. I took the defaults everywhere except for the
instance name and such as. I did ask Support about the location of the instance
directory, and, if I recall correctly, was told it can
Eric,
This may not apply to your case, but in hopes that it does... We had orphan
entries in our database that were confined to storage records. I believe TSM
Support was able to discern that from the error messages we were seeing in the
Activity Log. That allowed us to do the audit on the
We are upgrading two TSM 5.5.4.3 servers on RHEL 5 to TSM 6.2.2.0 soon. In the
event that one of the upgrades has to be backed out, will server-to-server
communications work normally between a V5.5 TSM server and a V6.2 server? If
someone has actually been doing that for a period of time, I
Skylar and Zoltan,
Thank you both,
Keith
Correction: the INSERTDB step took 10 hours, 8 minutes. The EXTRACTDB step
took 2 hours 8 minutes.
Liberal egg on face,
Keith
The fix for this problem, under Redhat Linux follows: I don't know whether
these remedies apply to other OS.
Contrary to the Server Upgrade Guide run the extractdb step as root, not as
the instance owner.
Before starting the extractdb step, set the environment variable DSMSERV_DIR to
I am running the extractdb step to migrate from TSM 5.5 to TSM 6.2.2.0. The
errors below were written to extract.out early in the extractdb process.
Should I stop the extractdb to fix this, or let it run? No other messages have
been written to extract.out.
If I should stop, what's the best
performing action ActivateDatabase.
ANR0162W Supplemental database diagnostic information: -1031:**No State
Information Available (76)**:-1031 (**No Other Information Available (96)**).
On Nov 19, 2010, at 9:55 AM, Keith Arbogast wrote:
I am running the extractdb step to migrate from TSM 5.5
My thanks to all who shared their advice. It has been an outpouring of
knowledge and experience.
Best wishes,
Keith
We are running TSM 5.5.4.3 on RHEL 5.5. Our tape library is a 3584 with ALMS
and twelve 3592-E05 drives.
Expiration and reclamation are not producing enough scratch tapes to stay ahead
of their usage, so our scratch tape supply is dwindling (#18). More tapes are
on the way, but only 15 empty
John,
Thank you for those details. It sounds doable.
When I return private volumes to the 3584, I run 'checkin libv library_name
volume_name search=bulk checklabel=yes. Then; update volume volume_name
access=readw.
If I'm misunderstanding something, please let me know.
Best wishes,
Keith
This issue also affects the 6.2.1.0 client. I received the note below from a
client admin. His is a LinuxX86 node running TSM 6.2.1.0. Has this been fixed
in a later client?
Thank you,
Keith
--
dsmc segfaults on startup:
[r...@i136 ~]# dsmc sched
Yann,
The client admin doesn't want to delete the whole filespace in question, which
is all I could do. The short story is that he backed up a NAS's ~snapshot
files by mistake. I believe the set of remedies in this case is limited to
user executed deletes which have more flexibility than mine
Is there a backup delete syntax that avoids the Y/N prompt after examining all
the files to be deleted? A customer has millions of files to delete, and it can
be hours before the Y/N prompt appears. He is doing the deletes with this
syntax, from the command line. Is there a faster, better way?
Bill,
Thank you very much.
Keith
I'm having a bad memory day. How does a client admin monitor the progress of a
restore run from the command line? Are messages written to a TSM client log
during a restore?
Thank you,
Keith Arbogast
Indiana University
)
NODE_NAME STATUS
-- --
I135Missed
JTRAIN3 Failed
BL-CHEM-ISOMissed
Thank you,
Keith Arbogast
for details:
http://publib.boulder.ibm.com/infocenter/tsminfo/v6r2/topic/com.ibm.itsm.client.doc/r_cmd_bkupsystemstate.html
Best wishes to all,
Keith Arbogast
WITH DEFAULT SYSTEM
STATE WRITERS ON WIN 7 AND 2008 R2 MAY GET FULL SYSTEM STATE BACKUPS
The Activity Log says it is 'Performing a full', see below. What am I missing?
Thank you,
Keith Arbogast
tsm: TSMBL01q node iu-uits-crmat2 f=d
Node Name: IU-UITS-CRMAT2
that error was a
thing of the past.
Thank you,
Keith Arbogast
a standalone TSM server to a Library Client, I
would be grateful to hear of it. If this idea looks like Swiss cheese, and
smells like Limburger I would like to know that too.
With my thanks and best wishes,
Keith Arbogast
Indiana University
Wanda and Remco,
My sincere thanks to you both.
Keith
,
Files
Backed Up: 0, Bytes Backed Up: 0,
Unreadable
Files: 0, Unreadable Bytes: 0. Current
Physical
File (bytes): None
Best wishes,
Keith
The server has 16 processors and 128 GB ram.
From Michael Green: Have you actually configured queue depth...?
No, we haven't. It is set at the default of '16'. It can be as high as
256. The HBA's are HP FC1242SR, which are re-branded QLogic QLE2462.
All best wishes,
Keith
Allen,
Thank you for that bit of advice. It was just what I needed. The
question of how small to make the TSM volumes was on my mind.
Our disk pools are on Hitachi AMS2300 SAS drives. We have use of six
2 TB LUNs. One volume group is defined per LUN, then 14 TSM volumes
per VG at 125 GB. The
this condition in TSMManager and
the Pct Mediawait field, and all during the same period of the night.
All tape drives would have been busy during this time, writing offsite
backups of disk pools at our other data center.
With hopeful best wishes,
Keith Arbogast
is like sweeping sand back into the ocean. We are always eager to
learn of a better broom.
I'll redefine smaller, more plentiful TSM volumes for this pool, and
see if that keeps the sand out of my socks.
With my thanks and best wishes,
Keith Arbogast
Robert,
Thank you. It is a mix of Windows and Linux clients. And, we impose
a cloptset on all clients that includes a dirmc that writes to disk.
Best wishes,
Keith
thanks,
Keith Arbogast
Indiana University
server is at Linux
version 5.5.4.1.
What circumstances could be causing this? I am baffled. The primary
disk pool is not hitting HighMig, and it wouldn't migrate to
SPACEMGPOOL if it were.
Thank you,
Keith Arbogast
Wanda,
Thank you for your reply. It got me on the right track to find the
problem.
Best wishes,
Keith
Zoltan,
We use 'dsnlookup no' in dsmserv.opt. When a client ip number changes
the Activity Log reports it, but does not stop the backup.
Best wishes,
Keith Arbogast
major backup partners have already released VADP integrated backup
products and we expect most of the major backup partners to have VADP
integrated backup software by the upcoming feature release of the
vSphere platform in 2010.
Best wishes,
Keith Arbogast
Indiana University
and the library. Could someone provide the missing
information, please?
tsm: TSMIN01def path tsmin01 3584-01 srct=serv autod=y destt=libr
devi=/dev/IBMchanger0
ANR8418E DEFINE PATH: An I/O error occurred while accessing library
3584-01.
ANS8001I Return code 15.
Thank you,
Keith Arbogast
and best wishes,
Keith Arbogast
Indiana University
a management class to a NFS mounted NAS device on Linux I
would most grateful to receive them.
Best wishes,
Keith Arbogast
Indiana University
(Session: 20869, Node: ESDBD10)
Elapsed
processing time:00:00:17
(SESSION: 20869)
What is special about NFS mounts or NAS devices that might be
resulting in this behavior?
Best wishes,
Keith Arbogast
options file. Otherwise, it's a simple solution.
Keith Arbogast
Indiana University
Zoltan et al;
I am receiving mail from ADSM-L again. Are you receiving mail from
ADSM-L now also?
Thank you,
Keith Arbogast
fixed.
Best wishes,
Keith Arbogast
, one doesn't know
whether UPGRADEDB is doing something needed, or not. In the meantime a
Production system is out of service.
Best wishes,
Keith Arbogast
Correction: TSM Support says this APAR will be fixed, Deo volente, in
5.5.5.
Best wishes,
Keith
. I
have found no other abnormal conditions.
A core file was created when I started the rpm installation. It did
not grow during the next 3 1/2 hours. The core file has not yet been
analyzed. If something comes of that I will post it to this thread.
Best wishes,
Keith Arbogast
Hi Christian,
I forgot to explain my question. I meant to be asking whether others
had experienced UPGRADEDB running long during a 5.3.0.0 to 5.5.4.1
upgrade. I lost heart, and opened a Service Request.
Best wishes,
Keith
That should be the SCSI Command Descriptor Block.
Invalid content suggests the possibility of the wrong device driver in
effect.
Richard,
Thank you. Deleting and redefining the paths and drives fixed that.
Best wishes,
Keith
seconds or minutes?
Thank you,
Keith Arbogast
Indiana University
The answer to this question, in our case, is 'No'. I found a core
file in /opt/tivoli/tsm/server/bin that was created when the upgradedb
began, and now have a sev 1 service request open.
Keith
.
Best wishes,
Keith Arbogast
Hi Andy,
Thank you. The cause of those numbers is now clear.
Best wishes,
Keith Arbogast
What does it mean when Pct. Idle Wait and Pct. Comm Wait are large
numbers greater than 100 as in the node below? The TSM server is at
version 5.5.2.1, running on RHEL.
Thank you,
Keith Arbogast
tsm: TSMIN01q node bl-sdd-internal f=d
Node Name: BL-SDD-INTERNAL
Platform
1 - 100 of 182 matches
Mail list logo
