Hello,
I have a problem with TSM Server 5.3.1.4 on z/Linux Suse SLES 9.
I recently updated from SLES 8 TSM 5.2.x to that version.
The server seems to run fine, except for two things:
- server 5.3 or SLES9 seems to cause much more load than TSM 5.2 under
SLES8 during nightly backups. (Scripts
In the past we had a package called: TIVguid.pkg [Tivoli Global Unique
Identifier for Solaris 7/8/9]..
Do we still need this pkg for solaris10 ?? I didn't find it on the
website ?
Regards,
Dave Seibel
Vice President, Backup and Restore Product Engineering
Office: 201-671-3253
Cell:
TSM 5.1.9.0 server on win2K server. I've got a very confusing problem,
and our server is totally dead at the moment so I'm in a bit of an
emergency.
We've been running TSM 5.1.6.5 for 2-3 years, I recently (8 months ago)
upgraded to 5.1.9.0, no problems. Last night, we ran out a tapes, and
Not sure whether this relates to the problem, but you need to recreate
that file anyway:
Your reclog size is already 12GB (12000 mB).
The size of your formatted extra space is 8GB (8000 mb).
Max log size is 13GB.
Try creating a log extension that is only 800MB.
See if you get a different error.
On Tue, 23 Aug 2005, Alexander Lazarevich wrote:
TSM 5.1.9.0 server on win2K server. I've got a very confusing problem,
and our server is totally dead at the moment so I'm in a bit of an
emergency.
We've been running TSM 5.1.6.5 for 2-3 years, I recently (8 months ago)
upgraded to
I had this happen on my AIX server.
Not sure where the options are at in Win2k but you need to put sessions to
zero
and backups to none.
Its kind of like booting tsm up in safe mode
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of
Rainer Schöpf
Sent:
This could be because of the typo:
dsmserv extend log extrareeclogspace 8000
Correct it to:
dsmserv extend log extrareclogspace 8000
Regards,
Ramakrishna Choudarapu
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Alexander Lazarevich
Sent:
On Tue, 23 Aug 2005, Rainer Sch?pf wrote:
On Tue, 23 Aug 2005, Alexander Lazarevich wrote:
TSM 5.1.9.0 server on win2K server. I've got a very confusing problem,
and our server is totally dead at the moment so I'm in a bit of an
emergency.
We've been running TSM 5.1.6.5 for 2-3 years, I
13GB maximum? Really? Why?
Anyway, same error as before, thanks for the tip though.
Alex
On Tue, 23 Aug 2005, Prather, Wanda wrote:
Not sure whether this relates to the problem, but you need to recreate
that file anyway:
Your reclog size is already 12GB (12000 mB).
The size of your
This probably doesn't apply to you but sometimes when we just restart
the TSM Server Service on Windows we get messages that volumes are in
use by another server. Rebooting solves the problem.
If you have not rebooted, I would give that a try.
-Original Message-
From: ADSM: Dist Stor
Hi Aleksandre,
I think that you have log file already 12GB in size, and maximum size
for log file is 13GB. You are trying to extend it for 8GB which will not
work. Try something that will give you 13GB in total.
I hope this will help,
Joe Crnjanski
Infinity Network Solutions Inc.
Phone:
Quick observation. Look at the two commands...
dsmftm -log D:\tsmdata\server1\extrareclogspace
dsmserv extend log extrareeclogspace
The name of the log changes from 'extrareclogspace' to
'extrareeclogspace'.
There is an additional 'e' in the extend command. Please verify your
command syntax,
Hello,
I have Created/Generated backup sets, does anyone
know how to schedule a backup set to automatically run
at a specific given time? I can't find a option in the drop
down menu's or commands to schedule one.
Thanks for any help, advice in advance!
Novell client 5.2.2
TSM 5.3.1.2
Ouch. That was it. I didn't specify the full path. I feel very stupid
right now, I'm going to sit in the corner with a dunce hat.
Thanks for the help though...
Alex
On Tue, 23 Aug 2005, David McClelland wrote:
Alex,
Be more explicit in your dsmserv extend log command - give the full path,
Good evening all
We are currently attempting to recover our TSM
DB the initial recovery was unsuccessful using the following cmd.
D:\tivoli\tsm\server\dsmserv restore db todate=today totime=now
With the following error msg
NR4643I Processed 168960 log records.
Oh Wise Ones,
I am a bit perplexed. I have 64 volumes that are in one of my copypools
that are not in the drmedia table. I noticed the problem when looking
through last night's dr recovery plan. Server is 5.1.9 running on aix
5.1.
All of these volumes show up in the copystgpool.volumes.destroyed
First you create server command script, and than you run it by creating
Administrative command schedule
Joe Crnjanski
Infinity Network Solutions Inc.
Phone: 416-235-0931 x26
Fax: 416-235-0265
Web: www.infinitynetwork.com
-Original Message-
From: ADSM: Dist Stor Manager
Make the copypool in question is still defined within DRManager
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Cory Heikel
Sent: Tuesday, August 23, 2005 12:07 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Volumes in copypool, but not in DRM?
Oh Wise
Thanks Joe you to Joe C.
Joe Pendergast wrote:
Administrative command schedule handles this very well.
Schedule Name BACKUPSET_MANFACT
Description Daily Backup of Man-Fact Data
Command GEN BACKUPSET WPCORIBM1 wpcoribm1 DEVCLASS=LTODEV1 RETENTION=28
SCRATCH=YES
Priority 5
.
.
.
I have a local primary storage pool that gets backed up to a copy
storage pool that gets sent off site. In addition, I have started
backing up the primary storage pool to virtual volumes at our DR
location. This is working fine and I was able to backup all previous
tapes in the primary pool to
I'm trying to query the summary table, but, I don't want any information
for schedules with 0 bytes. I've tried , !=, and ^=. None of these work.
This is the error I receive:
ANR2916E The SQL data types DECIMAL(18,0) and CHAR(1) are incompatible for
operator ''.
Debbie, if you examine the attributes of the BYTES column from the COLUMNS
table:
select * from columns where tabname='SUMMARY' and colname='BYTES'
you will see that BYTES is a decimal field. So the single quotes are not
necessary, and your syntax should otherwise work. These all do the same
It's not the operator -
what the message is telling you is that bytes is a decimal number, not
a character field.
So you need to write the zero as a number, not a 'char'
select * from summary where bytes 0
The best ref I found is the TSM Version 5.1 Technical Guide Redbook,
Appendix A.
Go
That will work, no problems.
A backup stgpool is always incremental.
You can kill the process, restart it whenever you want, it will just
pick up and copy whatever data wasn't copied the previous run.
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
select * from summary where bytes != 0
select * from summary where bytes 0
select * from summary where not bytes = 0
select * from summary where not bytes == 0
select * from summary where bytes 0
Before someone catches me out... yes, the last example is an inadvertent
I did see the decimal field, with a (p,s) of (18,0). However, I didn't
realize the quotes were not needed,,,
I'll also check out the redbook that Wanda suggested
Thanks to all,
Debbie
Andrew Raibeck [EMAIL PROTECTED]
Sent by: ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU
08/23/2005
I'm having a problem getting the TSM mt driver to recognize an STK
9940B tape drive. Setup:
Sun V880 UltraSPARC server
Solaris 9 8/03 release
TSM 5.1.5.4
The 9940B is directly attached via a dual-port 2gb fibre-channel
card. A Sun T3 disk array is connected to the other port. The card
is not
27 matches
Mail list logo
