to continue (i know i'm boring you to death with this)
i used RESOURCETUIL 10 and MAXNUMMP 3
and started the whole process again, the gain was 6.4 hours less time
to backup 3.4TB
Total number of objects inspected: 250
Total number of objects backed up: 250
Total number of objects
Using 3592/jaguar tapedrives with tsm 5.2 and 5.3.
LANFree backup of a SAP database (1.8TB) using the TDP for R3 writing to
1 tapedrive.
2 HBA's for disk and 2 HBA's for tape (2gbit). Tape and disk go via
different fabrics.
BKI1215I: Average transmission rate was 241.800 GB/h (68.779 MB/sec).
To all Dutch TSM users,
On November 23rd. We will organize a Dutch TSM User Group event with the
following subjects:
- TSM 5.4
- Update TSM products (roadmap)
- Virtual Tape Library or devclass=file?
- HSM Windows demo (Caminosoft)
- Reporting, compliance and TSM (Sox etc.)
Location is not yet
On Oct 27, 2006, at 12:53 AM, Murugan_Pachamallayan wrote:
I was started the TSM Server backup I got the following error message.
Server media mount not possible
Can any one please help me out in this regard
First, do not strip message numbers off of messages you post when
seeking help.
Orin,
By default, Data Protection for Exchange will restore
data back into the live Exchange Server and into the
original storage group and database. The Microsoft
Exchange Server requires that the database be dismounted
for this operation. If that is not what you want,
it would help to
We've begun getting a return code of '1' from a scheduled script.
However, the (database) backups in the script all appear to be
completely successfully.
I don't recall ever seeing a '1' return code.
Any suggestions as to why a vi script would return a '1'?
The information contained in this
On Oct 27, 2006, at 8:38 AM, Lawrence Clark wrote:
We've begun getting a return code of '1' from a scheduled script.
However, the (database) backups in the script all appear to be
completely successfully.
I don't recall ever seeing a '1' return code.
Any suggestions as to why a vi script
I had a similar problem 2 days ago with a TDP for Exchange Client.
It turns out the command line specified the following:
c:\Program Files\Tivoli\tsm\tdpexchange\.. (points to cmd file)
I changed it to :
c:\progra~1\tivoli\tsm\tdp... it worked.
It seems Tivoli does not like
Andy, thanks for the double checking, I'll weed out the other
info and see what I get.
Thanks,
Ben
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Andrew Raibeck
Sent: Thursday, October 26, 2006 4:31 PM
To: ADSM-L@VM.MARIST.EDU
Subject:
We see these every few weeks. We have not had the time to determine the
root cause; however, a 90% fix rate has been achieved by restarting the
Windows host. The very odd thing is the one that happened today is the
same path as yours.
We do know that you cannot exclude the file, because TSM
I see where the issue is
The summary table has the MIGRATION statistics also, so if all
my data is going to disk and then moving to tape, I will count the data
twice. Once I exclude the MIGRATIONS it looks much more realistic as to
what is coming from the clients.
I have a very simple question, when adding the name for a SQL database
in the TDP for SQL's cmd file can the database have a space in the name.
If not can you add quotes or any other sort of marker to allow it.
Thank you
Dan Cyr
Network Specialist
Information Technology and
Hi Andy,
Following the lead Richard Sim threw me in, it could possibly be
caused by the account permission with whcih TSM is trying to acces the
target NTFS.
In order to access the network drive or share via the TSM client GUI
or command line, the Windows account that started TSM must have an
Dan,
Yes, it can have a space. Use quotes around the database name when
specifying Data Protection for SQL commands. For example:
C:\Program Files\Tivoli\TSM\TDPSqltdpsqlc backup Name with a space full
IBM Tivoli
14 matches
Mail list logo
