How can I retrieve all the information about the what kind of encryption method
or type is using on my TSM server?
What I mean is how to check the backup data and store into a tape whether
encrypted or not?
Isn't it related to the default encrypted method AES 128 or alternative
encrypted method
Zoltan,
Try running reconcile volumes from both ends. When we do that, it deletes a
surprising quantity of orphan virtual volumes.
Keith
TSM client encryption can be verified per IBM Technote 1303197.
Tape drive encryption is a hardware topic addressed by the documentation for
the particular drive model, as in recent 3592 model variants.
Richard Sims
Hi Everyone!
I am using the dsmadmc command to do: q drm * against an AIX 5.5.5.0 TSM server
and I am getting ANS8001I return code 14. Would anyone happen to know what
could be causing this to occur? Or what I can look into to determine the root
cause of the problem?
Just let me know.
Thank
Hi Joni,
The TSM Server Administrator's Reference has an appendex on the return
codes, so you check there for the meaning of the "14".
Off-hand I'm not sure what would cause this, can you post complete output
showing the command as well as the messages you are seeing? I would
normally expect at l
Hmm - is the RECONCILE command I should run, regularly? I just ran
it on all 5.5 servers (they perform daily DBSNAPSHOT backups to an offsite
server) and all of them had errors to "reconcile". The 6.x servers didn't
have any errors.
As for these ghost volumes/storage, reconciling its devcla
In addition - in case of using TDP for Oracle you can inspect TSM Server logs
for TDP nodes. I think for other TDPs it is the same.
Be careful with encryption for TDP backups - some additional configuration
efforts are required .
From: ADSM: Dist Stor Man
Hi Andy,
It looks like return code 14 says:
RC_NOTAVAILABLE
ERROR
14
The command failed because the object to be operated upon is not available
Here is the output from the last page of the output of the q drm * command:
T19047 Vault03/01/11 10:25:24
T19055
Joni, this doesn't look right to me, so PMR route is probably the best way
to go.
One more thing to check, however: After issuing the query, check the TSM
server activity log for any anomalous messages from around the time you
issued the query. That might provide a further clue to the problem.
Be
We have two TSM 6.2.2.0 servers running under mainframe Linux. Both
report 'DB Backup Series Expiration Days: 3 Day(s)' when I execute
'query drmstat' commands.
One of the systems is configured as a library manager. It performs
a database snapshot and a full database backup daily. These are
writte
Hi Thomas,
Virtual volumes are considered "remote" by DRM as soon as they're created, so
the expiration of "DB backup series expiration days" is immediatly taken into
account whereas "real" volumes (tapes or files) needs to be in a "vault" state
by DRM.
So, you'll need to run "move drmedia" (w
Most places I know simply script the del volhost todate=-3 t=dbb
and/or t=dbs as appropriate, into their regular daily processing.
Indeed as mentioned above, regular database media is not considered
safe to delete until it's known to be out of the library an presumably
offsite, so in your case it'
So What you mean is TSM server don't has its own encryption instead help by the
driver or client side encryption?
1) What i mean is that when data store inside the storage, any encryption step
will run in this stage before it backup into a tape?
2) Will it possible a TSM server using both encryp
13 matches
Mail list logo
