Yiannakis
One thought... you should send the meta data to a
disk only storage pool. These meta data objects are always
very small (less than 100K)... and to put them to a
tape is not good for performance. You do that by binding
the meta objects to a management class that points to
a disk only stor
--Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of
Willem Roos
Sent: 09 December 2003 12:55
To: [EMAIL PROTECTED]
Subject: Re: SQL TDP configurations
[servername:] set accounting on
q status will tell you whether its on, i'm not sure whether its on by
de
]>
09.12.2003 19:55
Please respond to "ADSM: Dist Stor Manager"
To: [EMAIL PROTECTED]
cc:
Subject: Re: SQL TDP configurations
Dave,
I find this to be a mix. That is, there are some customers
backing their SQL databases to disk first, then migrati
Dave,
I find this to be a mix. That is, there are some customers
backing their SQL databases to disk first, then migrating
them to tape. There are other customers backing them up
directly to tape. There is no "correct" answer, because it
depends on your service level agreements, your TSM Server
in
Del,
It looks like our particular problem is with the machine itself.
I guess the origin of the question start because, is backing up the SQL
databases straight to tape the correct thing to do? What is everyone
else doing?
Thanks,
Dave
>>> [EMAIL PROTECTED] 12/9/2003 8:58:30 AM >>>
David,
Th
Hi William
Can you email me a copy of you Excel spead sheet that interprets the
dsmaccnt.log?
Thanks in advance,
James
-Original Message-
From: Willem Roos [mailto:[EMAIL PROTECTED]
Sent: Tuesday, December 09, 2003 3:55 AM
To: [EMAIL PROTECTED]
Subject: Re: SQL TDP configurations
David,
There are many factors that could slow a backup down.
You should by trying to find out if this is a slow-down
in the network, TSM Server, tape mount wait, SQL Server, etc.
If you happen to be running Windows 2000 SP4, there is a known
problem that causes SQL Server backups to slow down and
55
To: [EMAIL PROTECTED]
Subject: Re: SQL TDP configurations
[servername:] set accounting on
q status will tell you whether its on, i'm not sure whether its on by
default. The file is in /usr/tivoli/tsm/server/bin or Program
Files\tivoli\tsm\. It is described in the administrators
guide a
h for
dsmaccnt.log.
I have an Excel spread sheet which sort-of interprets such a file if you
want it.
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Yiannakis Vakis
Sent: 09 December 2003 12:37
To: [EMAIL PROTECTED]
Subject: Re: SQL TDP configurations
Willem
wait, comms wait, idle wait), maybe the one backup suffers lots of media
wait?
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Yiannakis Vakis
Sent: 09 December 2003 07:46
To: [EMAIL PROTECTED]
Subject: Re: SQL TDP configurations
Hi,
I have the
wait, idle wait), maybe the one backup suffers lots of media
wait?
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Yiannakis Vakis
Sent: 09 December 2003 07:46
To: [EMAIL PROTECTED]
Subject: Re: SQL TDP configurations
Hi,
I have the same situation
configuration, database reorganisation - all is fine.
Any input would be welcome.
Yiannakis
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of
David Benigni
Sent: 09 December 2003 04:58
To: [EMAIL PROTECTED]
Subject: SQL TDP configurations
Simple
Simple question. What is the optimal why to back up MS SQL databases?
Whats the ideal pool configuration etc?
Right now I'm running into trouble with the way Tivoli was originally
figured for our systems. The SQL tdp's sit on the client and back up to
a tape pool just for sql backups. The tape
13 matches
Mail list logo
