With that many files, I think Richard Sims is on target as to where your
problems will arise. Your database will grow quite a bit, but you can
calculate that from the Admin Guide formulas. Our DB is over 100GB and
it runs fine, so just throw some disk space at it and it will be fine.
One thing
Hi,
I'm working in a library sharing env.:
* library manager: TSM 5.1.9.3 on Solaris8
* 5 library clients: TSM 5.1.9.3 on Solaris8
* tape library: IBM 3584 (12 LTO drives)
For testing purposes I added a new TSM library client. It is also a
TSM 5.1.9.3 but it's running on a Linux RedHat
Mark,
Thanks for the hint. We installed the 64 bit base release of tsm and then
put the 5.2.2.4 32 bit maintenance release on over the top of that. That
is probably why moving the 32 bit dsmlicense file from the old machine
corrected the problem. I opened a problem with TSM support on this
Hello List -
We're running TSM 5.2.3 on z/OS 1.2. Current 9840 tape breakdown: TAPECOL = about
400, TAPENON = about 200, TAPEARCHIVE = 22.
Due to competing resources, I was told to convert TSM to use the 3592 tapes (300GB
capacity) rather than the 9840 tapes (20 GB capacity) that we have
I think you want EXCLUDE.Dir /.../.snapshot
Study Include/Exclude doc in the client manual, as it's vital to fully
understand and master their intricacies. TSM Include/Exclude specs are
generic in their formulation, and should not be confused with the
wildcard
specs of any given operating
David,
I assume from your note that you are retaining the 9840 drives and the
problem is just that they are over subscribed.
So assuming you will have still have reduced access to the 9840 drives , I
would have just made your existing 9840 tapes read only and changed your
disk storage pool/s
Create new Primary and Copy storage Pools. Redirect your copygroups to
the new Primary pools. This way all new data will go to the 3592 pools,
the old data will start expiring off the old tapes, and you can move the
data at your leisure to the new pools.
Orville L. Lantto
Datatrend
Hello
I have a simple question. What I must write in objects field of
Schedule definition, if I want backup c:\docs\*.*, including
subdirectories and all files, for example.
WBR,
Sergey
I would use the suggestion of redirecting the destination of your storage pools to the
new devclass for 3592s.
Another option is to create the new pools as orvile sugested, directing all new data
there.
Also, at this point change the reclaim stgpool for your old 9840 pools to the new
pool.
Sergey,
OBJECT field C:\DOCS\*
OPTION field -SUBDIR=YES
Bill
Sergey Chernyaev [EMAIL PROTECTED]
Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED]
14/10/2004 15:30
Please respond to ADSM: Dist Stor Manager
To: [EMAIL PROTECTED]
cc:
Subject:
We are moving our TSM server to a new p570, which requires a minimum OS
level of AIX 5.2 ML4.
I'd like to upgrade just the OS at first without having to upgrade the
TSM version, but I've read a few posts on here that TSM 5.1 isn't
supported on AIX 5.2. Is that accurate? I've looked for
Sanjoy,
Run following two commands and verify that you have valid numbers for
maxscratch and estcap respectively.
Q stg I013590DRM1 f=d and Q stg I013590PRI90 f=d
Q devc 3590 f=d
Regards, Samiran Das
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf
Hi
What are the Estimated Capacity set to in the device class for the 3590?
The Estimated Capacity number on the storage pool is calculated from that
value.
Best Regards
Daniel Sparrman
---
Daniel Sparrman
Chef Utveckling Drift
Exist i Stockholm AB
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On
Behalf Of Thach, Kevin G
We are moving our TSM server to a new p570, which requires a
minimum OS level of AIX 5.2 ML4.
I'd like to upgrade just the OS at first without having to
upgrade the TSM version, but I've read a few posts on
It looks as if 5.2.3.3 is the latest, but history
has proven that the latest version of TSM isn't always stable.
What ever version of TSM you upgrade to was the latest version at the
time it came out!
I'm running TSM 5.2.3.1 on AIX 5.1 64 bit. Will upgrade to 5.2.3.4
when it comes out at the
Kevin - The manual specifies AIX 5.1 or above. Historic postings
verify
that it does indeed run on AIX 5.2.
Richard Sims
On Oct 14, 2004, at 11:16 AM, Thach, Kevin G wrote:
I'd like to upgrade just the OS at first without having to upgrade the
TSM version, but I've read a few posts on
Good morning fellow admins,
Has anyone ever had to break apart a Tivoli DB into smaller DB's? Possibly spreading
those DB's out across different volume groups on different nodes? I'm told this is
possible. I was also told that as your TSM DB approaches 30GB, you might want to
think about
We are currently running TSM v4 r1 l3.0 on the OS390 r2.10 mainframe. We
are attempting to upgrade to TSM v5 r2. The installation of the new
software level was done by NYS Office for Technology, not us at DOH, so I
am not sure of everything that was done. They told us the installation was
done,
Hi
Dont know who told you about the need to break a 30GB database apart. For
what reason?
We have a 160GB database running smoothly. No need to break it apart as we
dont see any performance degradation. Only thing you'll need as your
database grows is hardware that will met up with the
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On
Behalf Of Chris Hund
Has anyone ever had to break apart a Tivoli DB into smaller
DB's? Possibly spreading those DB's out across different
volume groups on different nodes? I'm told this is possible.
I was also told that as your TSM
Hi Chris,
Are you talking about creating new TSM servers with your new splitted DB´s
or is it One TSM server DB volumes?
In first case, do an Export node.
Second, define new db volumes and then delete the big one. TSM will move
your db to the new volumes. Search the archives for instructions
Do you have a steplib pointing to your new loadlib?
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Keene R. Hallenbeck
Sent: Thursday, October 14, 2004 10:52 AM
To: [EMAIL PROTECTED]
Subject: Server upgrade problem
We are currently running TSM v4
What ever version of TSM you upgrade to was the latest version at the
time it came out!
That's true, but I like for other people to be the guinea pigs first
before I take the plunge. =)
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
David E
Currently preparing changes to our tape hardware in the Data Center. Current TSM Server is Version 5, Release 1, Level 7.0 on OS390 2.10 MVS Mainframe. We are moving to ZOS sometime before January. The change at this time is our tape environment. Will probably give too much detail here but I need
I am getting ready to move about 1 TB of data from one SAN environment to
another SAN. When I copy the data from the old SAN to the new SAN, the
creation date is set to the current date, which forces a new full backup
of all the data. Does anyone know of a way to copy the data, and force the
O/S
Create the new disk then mirror the old to new disk and break the mirror.
Remove the old disk and mount the new disk.
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Mike H. Wiederkehr/AT-Austin/3M/US
Sent: Thursday, October 14, 2004 11:23 AM
To:
In our normal start procedure, the SYS1.LINKLIB of the mainframe system is
used for the exec's. We were not given a new linklib, or loadlib, dataset
name by the installers. That is why I asked about DSMSERV in the original
note because I believe there should be an new linklib, or loadlib, with
Hi All,
Does anybody know if there is a way to customize TSM Client GUI.
We have a couple of executives with laptops and very limited knowledge about TSM.
Their IT guy asked us if we can customize the GUI, so when they need to restore
something and they open GUI, they don't want to see
If this was done through regular smpe maint. the executable would probably
be in sys1.linklib on another RES (ipl) volume. Look at the dataset names on
your production and test version for //DSMAMENG and //HLPAMENG and //IMAGES
they should give you some idea of what kind names the installers used
We have a 160GB database running smoothly. No need to break it apart as we
dont see any performance degradation. Only thing you'll need as your
database grows is hardware that will met up with the requirements of TSM.
Agreed!
We have 2 tsm servers with database sizes of 120gb and 140gb.
You
If you copied the files, you are also losing the file permissions.
You can download robocopy from Microsoft, or use xcopy from
a win2003 or XP machine. (I don't think that the Win2K version copied
security)
Be sure to read the help files, both Xcopy and Robocopy need
to be used with switches to
Joe - On the IBM site, see Technote 1109086, which summarizes GUI
configuration
capabilities, to the extent possible, as far as I know.
Alas, there are no Executive configuration capabilities that I'm aware
of. ;-)
Richard Sims
On Oct 14, 2004, at 1:42 PM, Joe Crnjanski wrote:
Hi All,
We should ask IBM to publish new Redbook.
TSM for Executives
Joe Crnjanski
Infinity Network Solutions Inc.
Phone: 416-235-0931 x26
Fax: 416-235-0265
Web: www.infinitynetwork.com
-Original Message-
From: Richard Sims [mailto:[EMAIL PROTECTED]
Sent: Thursday, October 14, 2004 2:31
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On
Behalf Of Joe Crnjanski
We should ask IBM to publish new Redbook.
TSM for Executives
The web administration client for TSM version 5.3 *may* have some of
what you're after. We'll see what comes out of the beta program.
--
Mark
Shannon,
What was the reason for purchasing the VTL? I'd surmise it is probably to do tape
consolidation on your mainframe operations.
*caveat! I have not actually used a 3494 VTL*
Past posts here have indicated that TSM is not a good fit for the VTL because of the
overhead of staging data
I agree that 30GB is a size that doesn't really need to concern anyone. Today with
tape drive speeds maybe a 100 GB isn't that big a deal either. The main point to
consider is how long the DB takes to backup because this will be roughly the amount of
time it takes to restore in the case of a
I at one time had my primary backup pool go into a VTS. Mine is a 3494-B18,
older model. TSM likes to append to tape volumes until they are full. The
recall process to stage a virtual volume from tape back to disk cache will
take from 4 to 6 minutes and then TSM will start appending the tape
Hi all, I have an Exchange server that is running 5.5 SP4. Exchange is
running on a Windows 2000 SP4 with a 5.2.3.0 TSM client installed. The TDP
is 5.2.1.0 and the TSM Server is running 5.1.0.0. I can backup the Exchange
database from the GUI without error. When I try and run a scheduled backup
On Thu, 14 Oct 2004 10:58:54 -0500, Stapleton, Mark wrote:
The magic # I have seen is about 100GB. Even a 100GB database would take days
depending on the
hardware if a full DBAUDIT had to be done.
I wouldn't want to do that G.
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On
Behalf
Hi all,
I'm designing a TSM solution for our enterprise data centre. The EDC consists of two
physical datacentres with appropriate smarts to make them appear as one big logical
entity from both the SAN and LAN perspective
We currently run a single TSM server on AIX which backs up a portion of
40 matches
Mail list logo
