On 02/10/2007, at 2:35 AM, Dollens, Bruce wrote:
I have a question that I feel a little stupid in asking.
What is the difference between migration and backup primary (disk) to
copy (tape)?
Other people have already answered, so I won't bother. :)
I am working on changing my scheduling up
On 04/09/2007, at 10:34 PM, Angus Macdonald wrote:
Many thanks Richard. That looks like it'll do what I need.
Can anyone point me to a redbook or other document that covers
operation of the client command-line? I can't seem to find one
anywhere.
I'm looking right now at the IBM Tivoli
On 23/08/2007, at 12:29 AM, Głębicki Jakub wrote:
Hint :) use short version of path (Progra~1 instead of Program
Files) in P*SCHEDULECMD options, otherwise schedule will fail.
A small trap for young players: the short name is defined by the
order of directory creation. So if the server dies
On 23/08/2007, at 7:29 AM, Nicholas Cassimatis wrote:
And a TSM DB Backup takes (at least) one volume, so with physical
cartridges, that's a whole tape. With VV's, you're only using the
actual
capacity of the backup, which is more efficient on space.
At the cost of some reliability. What
On 03/08/2007, at 2:53 PM, Paul Dudley wrote:
I have been told that if I want to create an archive backup of an
SQL
database via TDP for SQL, then I should create a separate node name in
TSM (such as SQL_Archive) and then backup using that node name
once a
month (for example) and make sure to
On 29/07/2007, at 10:03 PM, Stapleton, Mark wrote:
From: ADSM: Dist Stor Manager on behalf of Craig Ross
TSM is installed on Solaris 10
This is something that popped right out for me. Do you have your
storage pools located on raw logical volumes or mounted
filesystems? If the latter, that
On 27/07/2007, at 1:43 AM, Zoltan Forray/AC/VCU wrote:
Thanks for the reply. I already have things configured like this.
What I was hoping for was zOS/MVS sysplex sharing smarts (for you
mainframe folks). With a properly configured sysplex, the drives are
configured and online to all systems
On 26/07/2007, at 2:54 AM, Schneider, John wrote:
Greetings,
We have been a TSM shop for many years, but EMC came to our
management with a proposal to replace our TSM licenses with Legato
Networker, at a better price than what we are paying for TSM today.
This came right on the heels of
Hi all.
Whilst investigating something else, we discovered a number of nodes
that have old filespaces still stored within TSM - eg:
Node Name: (node name)
Filespace Name: /data
Hexadecimal Filespace
On 31/05/2007, at 3:38 AM, Chris McKay wrote:
Hi all,
I have been told by IBM that fibre LTO2 drives are no longer
available. We
wish to expand the number of drives in our 3584 library from 2 to
5. The
current 2 drives are fibre LTO2 drives, would it pose a problem by
adding
an additional 3
On 18/05/2007, at 5:01 AM, Avy Wong wrote:
Hello,
We have two instances TSM_A and TSM_B, Currently we want to
move some
nodes from TSM_A to TSM_B. Once the nodes are moved to TSM_B, the
filespaces will be backed up over TSM_B. Is there a way to keep
continuity
of the backed up data ? Do
A bit of background: to keep the database size down, we have several
TSM instances. One of these instances acts as a configuration
manager; the others are all configuration clients (so to speak).
For various reasons, we intend to create a new TSM instance dedicated
solely to library management
On 11/08/2005, at 6:21 AM, Mark D. Rodriguez wrote:
Stuart,
I am not a Solaris expert so please bare with me on my suggestions.
First of all you might try backing the filesystem up by using a
virtualmountpoint, this option has worked for me in the past on
unsupported file systems in Linux.
I've done some experimentation. So far, I've found that TSM will not
backup a filesystem image for a fs mounted from /dev/fssnap/N, but it
will backup the image as a raw image. This then raises the question
of consistency -- making sure that a given filesystem is backed up
with the same name
Just wondering: there are a couple of instances within the university
where a system has large filesystems with a large number of small
files. (eg: our mail spools have a single file for each email
message ...) This is, obviously, a worst-case scenario for both
backups and restores. I notice in
Greetings all. This one has me baffled, and whilst I'd normally spend
more time investigating, I'm going on leave tomorrow for three days,
and other parties view this as sufficiently urgent that I want to
resolve it if possible before then. Basically, we have a number of
applications based around
On 09/05/2005, at 1:34 PM, Ian Hobbs wrote:
Make sure you are doing the q archive as the same userid (oracle
perhaps) that performed the archive in the
first place.
Nice try, but I get back the exact same results: absolutely no
mention of the (for instance) CDUT_WEEKLY_07/05/05 01:00 archive,
even
On 09/05/2005, at 2:35 PM, Ian Hobbs wrote:
This could be a really long shot.
try
dsmc q archive {insert the source filespace name here}/* -
subdir=yes | grep CDUT_WEEKLY_07
It appears that the request is for any archive off the root
filespace. Possible. I'm quite away from a unix system at
On 11/03/2005, at 6:25 AM, Ragnar Sundblad wrote:
--On den 10 mars 2005 16:18 +1100 Stuart Lamble
[EMAIL PROTECTED] wrote:
On 10/03/2005, at 8:15 AM, Ragnar Sundblad wrote:
[snipping]
I think that the most logical way to accomplish this with TSM
is to do a complete export like
export server
On 10/03/2005, at 8:15 AM, Ragnar Sundblad wrote:
We don't want to give up storing away a complete snapshot of
our systems off site every few months, over time maybe reusing
the off site tapes so that we finally save a snapshot a year.
I think that the most logical way to accomplish this with TSM
Hey guys.
We have four TSM servers (long story, don't ask) across two sites,
setup with one as a config manager, the other three all subscribing to
the config pushed out by the manager. For various DR reasons, we're
wanting to do data exports from those four servers to a fifth server,
located at a
On 25/01/2005, at 11:31 AM, I wrote:
I've defined the server links and the requisite administrators. I've
also -- by way of experimentation as much as anything else -- set up
the fifth server to subscribe to the same config pushed to the other
servers. I'm now finding that, whenever I try to
Hey ho. Here's the skinny. We will, eventually, have a number of
clients backing up to a TSM server on a regular basis (we're still
setting up the SAN and other ancillary things that are needed to
support the TSM server). Some of them will be filesystem backups;
others will be database backups
(Once more, this time with the _right_ From address. Sigh.)
On 26/08/2004, at 12:40 PM, Steven Pemberton wrote:
On Thursday 26 August 2004 09:19, Stuart Lamble wrote:
Hey ho. Here's the skinny. We will, eventually, have a number of
clients backing up to a TSM server on a regular basis (we're still
24 matches
Mail list logo
