just a thought.
before putting the problem to the HW devices (tapes), SW backup programs
(TSM or whatever), and looking for a technology solution, I would ask
myself exactly *why* I have a 300+ GB file.one file, 300GB? is there
anything I can do to bring it to an acceptable size? how am I producing
On Mon, Aug 11, 2003 at 04:11:04PM +0200, Remco Post wrote:
> and 'q path'? 'help upd path' to fix paths
It's not the problem with paths. We have the same problem with our TSM.
We've opened PMR for this and hope what will come out of it...
--
Przemysław Maciuszko
Agora SA
Je serai absent(e) du 11.08.2003 au 22.08.2003.
Je répondrai à votre message dès mon retour. Voir avec GAD si besoin.Merci.
Hi Tobias,
Windows services by default run as a Local System account and this account usually
does not have access to network resources. I usually create a user for running TSM
services and give appropriate permissions to this user.
Regards,
Imre
> -Original Message-
> From: Tobias Hof
Thank you Troy, I'll double check the variables.
John
-Original Message-
From: Tudor,Troy,VEVEY,GL-IS/IT [mailto:[EMAIL PROTECTED]
Sent: Wednesday, August 06, 2003 1:49 AM
To: [EMAIL PROTECTED]
Subject: Re: 32 and 64 bit API
Hi John
It works (on AIX anyway), you just need to take extra
I ran into this exact problem when I had one 1GB random access DISK based
primary storage pool (about 27% used). I didn't backup it up to it's own
copy storage pool, but I did back it up to the same copy storage pool
where I copied the other management classes. When reclamation occurred, I
would
Lawrence,
We're running TSM 5.1.7.0 on AIX 4.3.3.
What we've seen is that if a TSM process that reserved the drive dies,
those reservations are not cancelled.
I had an export job abort on dismount failure, and *three days* later the
input and output mount point reservations were still listed in
Yes, sorry. Yes, Windows 2K server, 4.2.3.1 server software.
library is SCSI attached 3583 with the same microcode we have
on our production machine (not the latest, but within 6 months).
SCSI used is LVD. Both drives and the library are on a single
SCSI chain.
I have cleaned the tape drives a c
I played around a bit more and found out when issuing a "select * from
summary" i still don't get my nodes. (see org story below) So i'm pretty
sure now it is not a sql problem but a db problem. But in the actlog i
don't find any errors after a node has finished its backup. Anybody able
to give a p
Thanks Andy, that worked very well.
Andrew Raibeck <[EMAIL PROTECTED]> wrote:I think that the VOLUMEUSAGE table is
probably your best bet for this
info. I'd suggest a query like this:
select distinct volume_name, node_name
from volumeusage
where stgpool_name='POOLNAME'
order by volume_name, node
Hi Joni,
Yes, the command
delete filespace nnn *
will remove all file spaces for for node NNN.
Best regards,
Andy
Andy Raibeck
IBM Software Group
Tivoli Storage Manager Client Development
Internal Notes e-mail: Andrew Raibeck/Tucson/[EMAIL PROTECTED]
Internet e-mail: [EMAIL PROTECTED]
The
Hello
I have an erroneous tape reference in my 3494 library. The vol serial number
is 400699 I have tried mtlib -l /dev/lmcp0 -C -t FF10 -V 400699 and get
ther error Change Category operation Failed, ERPA code - 7B, Library
Volume Manually Ejected. When I run mtlib -l /dev/lmcp0 -q I and grep 40
How large is your SAP database?
Is the tsm server on the same physical server as the SAP database?
If not what kind of network do you have between the two?
Are you using multiplexing in TDP for R/3?
Is your CPU maxed on the SAP database server during the backups?
What kind of disk is your SAP datab
13 matches
Mail list logo