Hi,
A VTL in primary site copies backup data to remote site asynchronously. If
some backups expire in TSM, what happens to the copy in remote site? Will it
be expired or retained?
Thanks
Thanks Richard. Tried all that and no joy.
What we did discover was the cause of this notoriously misleading error,
was that the paths defined on he library manager for this library client
were OFFLINE. Once we put them online and retried the DB Restore, it
worked like a charm.
Regards
Adrian
Hi,
Which one do you prefer:
1- having a copy of data off-site by disk subsystem copy services:
2- implementing D/R with VTL-to-VTL communication
Number 1:
-needs more disk capacity
-copy services license price
-more bandwidth is needed between sites even in asynchronous mode
-more difficult
Hi,
What happens if I mix different generations of LTO cartridges in a tape
library? Does it matter from TSM's point of view? Let say a library with
LTO4 drives but LTO4 and LTO3 cartridges in a mixture.
Thanks
There's a link for that:
http://publib.boulder.ibm.com/infocenter/tivihelp/v1r1/topic/com.ibm.itsmaix
n.doc/anragd55108.htm#mixdevtype
In fact, there are a few links - another:
http://www.redbooks.ibm.com/redbooks/pdfs/sg246502.pdf (section 5.11 - Mixed
Media Libraries).
Briefly, yes, you can
Hello
I'm assuming you are using the VTL's replication process to do this? If
so, I'd assume it would be expired (though that is TSM terminology rather
than VTL terminology).
Probably best to ask your VTL vendor.
Steven
Steven Langdale
Global Information Services
EAME SAN/Storage Planning
No, we haven't bought VTL, yet. Actually we are analyzing different aspects
of the scenario.
What I mean by expire is the transition from
active-to-inactive-to-expiration.
I'm pretty sure that once you make a VTL to VTL replication TSM wont know about
the copy you created because it wasn't copied by TSM (i.e. not in the TSM DB).
The only way to access is if you are replicating the TSM DB and Logs to the
offsite as well so TSM will be aware of those VTL vols.
For the past 2 days something has been screwing up backups by filling
the log and this morning I remembered the show logpinned command and
found the server that is causing it. I've cancelled the session but as
far as I know am at the mercy of TSM to kill it at some point. I
contacted the
From what I understand, when you cancel the session, TSM rolls back the
transaction. Sometimes it's quick, sometimes it can take quite a while.
but the log won't grow any more from the session while it is rolling back.
Regards,
Shawn
Shawn Drew
- Geoffrey L. Gill geoffrey.l.g...@saic.com wrote:
For the past 2 days something has been screwing up backups by filling
the log and this morning I remembered the show logpinned command and
found the server that is causing it. I've cancelled the session but
as
far as I know am at the
Take a look also at the 'show logpinned cancel' command if that's not
what
you used to cancel the session - sometimes it's helpful. If that
doesn't
work then halting the server will do the trick, but that's not the
most
tidy or convenient way... assuming you're about to run out of log and
From what I understand, when you cancel the session, TSM rolls back
the
transaction. Sometimes it's quick, sometimes it can take quite a
while.
but the log won't grow any more from the session while it is rolling
back.
It may well be that the log isn't 'supposed to grow but that isn't what
I
I think that if the log is growing, it's from other sessions that are
still running. You should be able to cancel those without delay.
Before I halt a server, I always try to cancel all the active sessions and
give it 10-15 minutes to free up, while monitoring the log.
Seems to work for me.
Allen, please submit a FITs requirement on the issue you are outlining so
that it is considered and evaluated for future Admin Center releases.
Thanks!
Regards/Pozdravi, Gergana
| | ~\\ ! //~
| | ( ( 'o . o' ) )Imagination can change the equation . . .
| |( w )
| |
15 matches
Mail list logo
