---
This email is to be read subject to the disclaimer below.
---
I am trying to create a script to perform an incremental / selective
backup via batch.
During my testing I executed
---
This email is to be read subject to the disclaimer below.
---
In an attempt to negate the mount time issue in the restore process I am
currenlty using move nodedata to co-locate
---
This email is to be read subject to the disclaimer below.
---
We currently have two TSM environments at separate sites.
Each environment has a SAN connected 3494/3590 (via a
Hello,
Running TSM 5.1 on Solaris 8, using IBM 3590's in an ATL over a SAN ( SAN DATA
GATEWAYS)
Does anyone know how to copy a TSM BACKUPSET series of tapes directly to another set
of tapes (1 at a time is fine)
I already know the following: TSM has no way of doing this.
Solaris DD or TAR
Hello,
Running TSM 5.1 on Solaris 8, using IBM 3590's in an ATL over a SAN ( SAN DATA
GATEWAYS)
Does anyone know how to copy a TSM BACKUPSET series of tapes directly to another set
of tapes (1 at a time is fine)
I already know the following: TSM has no way of doing this.
Solaris DD or TAR
A part of our DR procedures is that if we lost a given data centre we
would recover the TSM server onto the same hardware as the alternate
site's TSM server and run both instances in parallel (Both machines are
SUN 450's)
If the TSM servers were at the same release level then we have the
option
I am interested in finding out if anyone is using the supplied TSM API
to back up multiple instances of DB2 on a single Windows platform -
specifically how you manage the association between the instance and the
backup images.
The problem we have is when a restore is invoked thereturned list of
If I was setting this up..
I would use the remote mirroring of the disk (both MVS and Open
systems) using the available disk technologies (ie SRDF for EMC).
Base upon the fact that TSM does appear to recover 99% of the time even
if the server is not shutdown cleanly I also assume the
I had thought I had put my two cents worth in on this subject but when
searching the archives I failed to see my comments so here goes
I agree with Lindsay Morris that simply monitoring the most recent
incremental only gives you half the information you require.
Even if the incremental reports
For the exclusion of 'old' filespaces and for clients not be checked we
utilise the 'Contact' column in the nodes table.
To excluded a filespace(s) the contact details will be prefixed with
XFS1,3,4. where the numeric represents the filespace id.
To exclude the entire clilent from being
Assuming this is UNIX is run in batch, I get around this problem by
grep-ing the TSM responce for a known field within the output. For
example the 'DIX' in your volser.
In some cases I also display another column with a standardised entry
because the info I am actually looking for is not
Suffered the same problem a month or two ago
This is an effect of the unicode processing within the TSM server code.
This problem is resolved in the latest release (4.2.1.8). The actual
filespace name is corrcetly stored within the TSM dbase will be
displayedas expected when you upgrade.
I find the best way to start TSM via TSO is to create a REXX pgm and
allocated the required DDs within the rexx. This is based on the belief
that the that the required DD's are rarely allocated in your TSO logon
proc due to the limitted number of peple requiring access to the server
line command.
Can anyone advise on which order TSM does a restore when Co-location is
turned off.
I performed a 105Gb restore and near the end TSM kept swapping between
two tapes restoring 1-20 files each time. Very frustrating as the first
100Gb was restored in hours and the last 5Gb took just a long.
Help
I would like to run a UNIX script that issues a series of TSM commands
that require SYSTEM access rights ( DEFINE MACHINE INSERT MACHINE).
The problem I have is that I am forced to have a TSM ID and PASSWD
within the script or in an input file therefore accessible to a
multitude of people.
I once used a mainframe based backup product called 'Harbor'. This
product had the feature you mentioned were it used pointers to a single
copy of a file that existed on multiple files.
What I would ask is how does the application store all the 'other' data
associated with the file, ie was it
: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]] On Behalf Of
StorageGroupAdmin StorageGroupAdmin
Sent: Wednesday, February 13, 2002 2:35 AM
To: [EMAIL PROTECTED]
Subject: Multiple tape swaps during restore
Can anyone advise on which order TSM does a restore when Co-location is
turned off.
I
17 matches
Mail list logo
