I found journaling to be very useful for exactly such problems.
I have a client with only about 25GB's of data, but about 10 million
files. The backups were taking 4-5 days to run, now with journaling,
they complete well within a 24 hour period and I only run weeklies
(customer request)
My company runs TSM 5.1.8.1 on Sun E4500's with 4 procs and 4GB of RAM. I
have tried twice now, once on 4.2 and now on 5.1 to add more processors (either 2 or
4) and TSM performance drops through the floor. Has anyone else seen this behavior?
Normally, starting the server fresh only
select message from actlog where msgno=0986 and
date_time(current_timestamp-(1 hour))
Michael French
Savvis Communications
Enterprise Storage Engineer
(314)628-7392 -- desk
(408)239-9913 -- mobile
-Original Message-
From: Chang, Calvin [mailto:[EMAIL PROTECTED]
Sent: Thursday, May
I have an Oracle cluster running on raw volumes (Solairs box), how would I do
a cold backup of this data?
Michael French
Savvis Communications
IDS01 Santa Clara, CA
(408)450-7812 -- desk
(408)239-9913 -- mobile
I found the answer, use the backup image command, it supports multiple raw
disk types.
Michael French
Savvis Communications
IDS01 Santa Clara, CA
(408)450-7812 -- desk
(408)239-9913 -- mobile
-Original Message-
From: French, Michael
Sent: Wednesday, April 07
Is your TSM server on a different network from the client? Is the GigE card on a
different network then the other interface on the machine? I would assume so, if that
is the case, just set a permenant route that points to the TSM server's network and
tell it to go out the GigE interface to
Would have been nice if you told us what platform you are using...On any flavor of
Unix, just halt TSM, even it you have to do it with a kill. Start again, but run it
manually by just cd'ing to /opt/tivoli/tsm/server/bin and running ./dsmserv. After
TSM starts, you will be at the TSM prompt
How does TSM handle files that are larger then the tape size? I have a DB2 dump file
that is 240GB that I am backing up as a flat file. I can get it into the disk pool
without a problem, but I can't seem to get it to migrate to tape, a few small files
move and then it seems to work on the
I originally did not have ENABLE3590LIBRARY set in the
dsmserv.opt yesterday afternoon so I halted the server and added it,
then restared. I was careful when creating the library definition, I
did this:
DEFINE LIBRARY ids02atl1 libtype=349x scratchcategory=501
privatecategory=500
DEFINE
I couldn't seem to find an explaination in the manual and my magic 8-ball
returned It's a mystery to me to, ask the ADSM mailing list, so here goes. I was
doing a point-in-time restore of a directory tree on a Win2K box with the 5.2.2
client. I was viewing only active files at the
Have you tried the IBM Redbook, Backing Up DB2 Using Tivoli
Storage Manager? I used to to setup mine and had no problems with it,
very straight forward.
http://publib-b.boulder.ibm.com/Redbooks.nsf/9445fa5b416f6e32852569ae006
One of my TSM servers has drives continously going offline over the past few days. I
have 2 servers attached to the same library, server 1 is fine, server 2 keeps getting
drive failures. On Sunday, all 4 drives went down within hours of each other! This
strikes me as suspecious, I see this
Anyone out there with an IBM 3494 library that has ever performed an audit library
have any idea how long it should take? I had about 60 tapes that are in the library
but TSM refuses to mount them stating that they are unavailable (updated the to
read/write and tried to audit them). I
Does anyone know if there is a max size that you can make a disk volume? I am
setting up a new server and using 73GB disks for the storage pool. I tried to add a
RAW volume of this size and after several minutes, I got an error stating:
tsm: TSM3.USWASH6def vol backuppool
The disks are under Veritas control. I made a single concantenated volume on 1 73GB
disk, filling the whole disk. My DB and Log volumes were created the same way, except
they are not taking up the whole disk, but rather 1/4 of each 36GB disk, 2 volumes per
disk, no problems adding all of
One of my customer's boxes has been running the TSM journaling service for
about 2 months now and doing backups with no problems. His box has several million
files on it and the journal has reduced backup times significantly until yesterday
when the journal service hung and blew up.
Got the error log from the customer (box is colo, can't login
myself):
01/14/2004 02:04:03 NpPeek: No data
01/14/2004 02:04:08 NpPeek: No data
01/14/2004 02:04:13 NpPeek: No data
01/14/2004 02:04:18 NpPeek: No data
01/14/2004 02:04:23 NpPeek: No data
01/14/2004 02:04:28 NpPeek: No data
Sorry, it was noted in the previous posting:
Win2K Server (client)
TSM Client 4.2.3
Plenty of free space on both drives
Journal service allowed to grow as large as it needs to
Our setup:
TSM server 5.1.8.1
Solaris 8
Michael French
Savvis Communications
IDS01 Santa Clara, CA
I can't speak to AIX, I use Solaris but I just converted all of
my volumes from mounted, VXFS ones to RAW and the performance difference
has been huge. I converted one of my servers this past Saturday, I have
10 DB vols and 10 mirrors plus 1 large volume and a mirror. I started
I talked to a guy at IBM several months back and his suggestions
were that you should analyze the number of concurrent sessions that you
have going at anyone one time and create an equal number of DB volumes.
I usual have about 20 concurrent backup sessions going during my various
backup
Stupid question, but from the command line can you telnet to the
TSM server port?
Ex:
telnet 10.70.113.60 1500
If you get a black screen, you've got connectivity. Otherwise,
something is block access at the network layer.
Michael French
Savvis Communications
IDS01 Santa Clara, CA
I have been struggling with this issue recently myself, Richard
was kind enough to answer my stupid questions several weeks ago too
*8). I originally looked at the accounting file, but it did not
contain all of the info that my management and customers wanted so I
wrote my own script that
to a file-based device class. A tape
dump will take *way* too long.
--
Mark Stapleton ([EMAIL PROTECTED])
-Original Message-
From: French, Michael [mailto:[EMAIL PROTECTED]
Sent: Mon 1/5/2004 22:33
To: [EMAIL PROTECTED]
Cc:
Subject:Re: Unload/LoadDB question
This was actually
System Info:
Solaris 8
Sun E4500 w/ 4 processors 4GB RAM
TSM 5.1.8.1
TSM DB 119GB (37.1% utilized)
I tried shrinking the DB down to 85GB and at 100GB, ran into the your outta
SQL table space message. Guess it's time for an unloaddb/loaddb. Any ideas at all
how long I can expect
This was actually the first thing I tried. The DB was originally 177GB and 20%
utilized. I reduced the DB by 50GB and then deleted volumes and mirrors. I tried to
shrink it again by another 35-40GB's, but it complained saying that it could not be
reduced by that much, that there was not
Veritas recently commishioned a study of performance between Netbackup, Networker,
and TSM to compare results of snapshot backups. Apparently the new Netbackup 5.0 has
a new advanced client.
For TSM, they threw it in stating that there is no comprable feature, but they wanted
include it
Another possibility, maybe the rpm is corrupt. I don't know how
you got it but if it was via ftp and binary transfer wasn't used, that
could explain why it's complaining about the magic number. If the
commands Frank gave you didn't do the trick, I would download the client
again.
I run a script every day to pull out info out of the TSM servers about backups
and one of my co-workers noticed something odd the other day that I did not see
before. The script is just a Unix shell script that among other things executes a
long select statement on each TSM server.
You can also do a help reg lic and it will list every license
file with a description of what it is.
Michael French
Savvis Communications
IDS01 Santa Clara, CA
(408)450-7812 -- desk
(408)239-9913 -- mobile
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL
At my company, we backup system objects a little differently. Instead of
letting TSM handle it, we have a precommand that backups the system state to a flat
file using NT Backup. Thus when doing a restore, I just reinstall the OS, tell it to
replace files on boot that it can't do
You can also use the undocumented command show ASMounted.
Example:
tsm: TSM2.USWASH6show asm
Mounted (or mount in progress) volumes:
Volume 2C0469(146693) -- SessId=305, Mode=Output, Use=?, ClassId=2,
ClassName=3590,
IsScratch=True, VolSeqNum=1, Pool=(0), Allocated=False, NextSeqNum=0,
I just spoke with an IBM guy about this topic yesterday. There
are several important steps you need to do before hand:
Pre-Migration Steps
1. Ensure that expiration processing has completed.
This can be done a couple of ways. The easiest I have found is
to run expiration
Message-
From: French, Michael [mailto:[EMAIL PROTECTED]
Sent: Wednesday, November 19, 2003 1:56 PM
To: [EMAIL PROTECTED]
Subject: Re: what tape is in a drive?
You can also use the undocumented command show ASMounted.
Example:
tsm: TSM2.USWASH6show asm
Mounted (or mount in progress
Are you using RAW volumes or logical, file system mounted
volumes for DB, log, and disk pool? RAW volumes make a HUGE difference.
You should also have your client's NIC's forced to 100/Full (the ones
using fastethernet), don't let them auto negotiate, kill's backup
performance.
Michael
and network options
Hi *,
I use on both server logical volumes and jfs-filesystems. All (DB, log
and disk pool) are on jfs-filesystems.
Is it better when I change to RAW devices?
Best regards,
Frank Mueller
French, Michael
[EMAIL PROTECTED
Look at the help on export node:
EXPORT NODE (Export Client Node Information)
Use this command to export client node definitions or file data to
sequential media.
Each client node definition includes information such as:
* User ID, password, and contact information
* Name of the
I have a customer who has two DB2 databases on one server and I need to back
them up with TSM. Is it possible to do this with two separate node names to keep them
apart? If so, how would I do this? Since you have to define 3 environment variables
specific to DB2 for TSM and one of
While this error isn't causing any problems on the server, it is setting off
our system monitoring agent which is quite irritating. The prime pool is reporting
itself to be 100% utilized which it is not and the estimated capacity is at 0% (same
thing for the DRM pool). I tried
It's set to 118 right now. I set it to 500 just for giggles,
the only thing it changed was Pct Migr dropped dramatically as
expected. I set it back to 118.
Michael French
Savvis Communications
IDS01 Santa Clara, CA
(408)450-7812 -- desk
(408)239-9913 -- mobile
-Original
If you have anymore questions about my system layout, contact
me:
1. The server is a Sun 4500 with 4 400MHz Sparc III procs and 4GB RAM.
Attached to the system is 1 D100 disk array used to hold the OS. All of
the TSM volumes are held on A5200 fiber channel arrays (3 of them
containing
I ran into this a few weeks ago. I had to format the log and DB
volumes before the restore would work. Something like:
dsmserv format numberoflogfiles logfilenames numberofdbvolumes
dbvolnames
ie
dsmserv format 1 /adsmlog/log1 1 /adsmdb/db1
You only need to do the prime
TSM Server 4.2.4.1 (Solaris)
TSM Client 4.2.3 (Solaris)
TSM DB 83GB (40% util)
TSM Log 4.6GB
I am having a serious problem with 4 Solaris clients hammering the server
during their backups. Each client has a lot of file held on TSM, about 4-5
John's right, there is no industry standard, everyone has to
make their own based on the needs of their environment. My current
settings are:
Versions Data Exists: 8
Versions Data Deleted: 4
Retain Extra Versions: 180
Retain Only Version: 180
The last two
I run TSM 4.2 on Solaris 8. I was in the process of converting all of the
diskpool volumes from OS mounted files to raw partitions to fix some performance
issues we have been experiencing with backups when I hit a little problem. I disabled
sessions and allowed migration to run to
1. How can I tell if expiration has made it all the way through? Right now I am only
running it 2 hours a day and I think it's way behind but I can't prove it.
2. As part of my daily housekeeping on TSM, the script deletes DB backups older then
14 days from the system. The tapes have
1. I looked in the log, expiration is not completing on it's own, it's
being stopped at the end of two hours. There has to be some way to see
how far expiration has gotten to. There has to be some internal way in
which expiration keeps track of where it left off, it doesn't always
just start
46 matches
Mail list logo
