I didn't read, thoroughly, the original note, but my two cents is to remember
the KISS principal when configuring these things: Keep It Simple Stewpid.
Always leave the Standard domain behind. That way you can use open
registration.
Kelly Lipp
CTO, VP Manufacturing
STORServer, Inc.
485-B E
I agree with Paul.
There are 2 technical reasons to split clients into domains:
1) Dividing authority: you can create TSM administrators with "Policy" or
domain-level authority. They don't have the ability to modify TSM storage
pools or devices, but they can create nodes, passwords, and schedul
I'm sure there are many ways to organize and use TSM Policy Domains,
and I look forward to seeing the responses to your inquiry. Here at
Cornell, we make heavy use of Policy Domains as you are thinking of
doing - along organizational lines. Each department here who makes
any significant use of T
I inherited two TSM servers whose Policy Domains were named for
client operating systems (AIX and NT) and the enterprise database
(Oracle). When the TSM servers were originally built they were used
exclusively to backup clients belonging to the technical team that
maintained TSM. So, those Policy
Hi TSM'ers,
A colleague has asked me to post;
How would you explain the fact that running dsmadmc -console has a
neligible impact on server performance, given that the explanation 'It
just a very simple session that is essentially echoing text out to an
admin client' is not good enough?
Explain
yes, but there is no need to do that. TSM will migrate them fine. Have
done it myself.
>>> [EMAIL PROTECTED] 08/14/2007 2:14:15 PM >>>
I'm sorry, I guess you didn't bother to read what he wrote. He was
talking
about doing dbcopy volumes, which have to be the same size (I believe
any
extra is wast
I'm sorry, I guess you didn't bother to read what he wrote. He was talking
about doing dbcopy volumes, which have to be the same size (I believe any
extra is wasted if you make them bigger) as the "primary" volumes.
On 8/14/07, Lawrence Clark <[EMAIL PROTECTED]> wrote:
>
> no, the volumes you are
I was incorrect in regards to the RMAN catalog. In our case the catalog
still exists, however the backups are past our recovery time. Here are the
notes our dba provided...
"Backups past our recovery time. "Orphaned" backups; rman can't "see" them.
Still in recovery catalog. diff.db key and still
Hi,
you have to skip the "extend db", otherwise you cannot remove the old
volumes.
Just create the volumes for the new DB location, then make TSM remove
the old ones. Data will get copied to the new volumes.
When you've completed the remove procedure, you can extend the db (if
DB is larger n
no, the volumes you are migrating to do not have to match in size.
-just create new ones. do an extend db so they are in play, and begin removing
the old ones and tsm will
auto migrate the pages to the new volumes.
>>> [EMAIL PROTECTED] 08/14/2007 11:17 AM >>>
Thedownside to this solution is th
Thedownside to this solution is that the new volumes have to match in size
to the old volumes - may not be a problem, but if you wanted to take this
chance to change the layout and size of the volumes, this solution would not
work.
On 8/13/07, Wojtek Pięcek <[EMAIL PROTECTED]> wrote:
>
> Another s
Kelly,
I'm using TS1120 drives and wrestled with the same issues. I ended
up using system encryption with the EKM because:
1. It provides the greatest level of granularity - Individual tape
drives and volumes may be designated for encryption
2. TSM is oblivious to this type of encryption thus
select node_name, date(lastacc_time) as "LAST ACCESS", -
current date - date(lastacc_time) as "DAYS SINCE" -
from nodes where (days(current date) - days(lastacc_time)) < 30
Based on this easy-going example I just want to add a notice
to always returning comparision of TSM to another products.
This is for me on of example of strengths of TSM - performing many critical
tasks simply and with little to no risk.
Task like this do not appear in comparisions,
But i somet
You can use the TDPO utility tdposync to get rid of backups in TSM that RMAN
no longer knows.
"The tdposync utility checks for items on the Tivoli Storage Manager server
that are not in the RMAN catalog. This utility allows you to repair such
discrepancies between the Tivoli Storage Manager serv
15 matches
Mail list logo
