What I do is I run around 4 (this is of course totally dependent on the
configuration of your TSM environment) identify proc's during backup and
morning housekeeping processes as not to increase the time it takes to get
my copypools up to speed to much (or slow down backups).
As soon as my offsite
SQL Express is not supported for TDP (or the other way around). Only
workaround I can think of is backing up the database(s) with T-SQL to the
filesystem and do a regular file backup.
Cheers,
Rick
On Wed, Sep 4, 2013 at 6:01 PM, Del Hoobler hoob...@us.ibm.com wrote:
Chavdar,
Do you mean SQL
Every hour?
Do you use a config manager with a refresh time of 60 mins? The message is
very similar.
On 4 September 2013 21:06, Vandeventer, Harold [BS]
harold.vandeven...@ks.gov wrote:
I'm on Windows, running 6.3.3.100.
Replication runs only in the early morning hours, and I just saw
Hi Del,
SQL is express edition. I see that it is not supported, but tried with
TDP for SQL 5.5.6 (before FCM)
and it works, even it is not supported. So now it is up to client to
decide to be with unsupported config,
or to dump SQL(with maintenance plan) and to backup with BA
Thank you for
Hi Grant,
thankyou for responding; I got a similar answer from IBM level 2, saying
there is really no way to control how stgp volumes are used by tsm.
regards,
Dierk
|
| Von: |
|
Not that I know of...l'll do some more research.
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Steven
Langdale
Sent: Thursday, September 05, 2013 3:48 AM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] Node Replication Sessions
Every hour?
easy way to check: q subscription
On 5 September 2013 13:51, Vandeventer, Harold [BS]
harold.vandeven...@ks.gov wrote:
Not that I know of...l'll do some more research.
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of
Steven Langdale
I am getting this error message when backing up the SQL dump files using the
baclient.
We specify the location of the dump files in the dsm.opt file yet the error
message relates to the actual database file in a different location.
Why would it try to backup the database .mdf file in a different
I am getting this error message when backing up the SQL dump files using the
baclient.
We specify the location of the dump files in the dsm.opt file yet the error
message relates to the actual database file in a different location.
Why would it try to backup the database .mdf file in a different
The message below indicates that the BA client is trying to back up
the actual SQL database file, which is not what you want.
You should exclude these within the DSM.OPT file. Something like:
EXCLUDE *.MDF
EXCLUDE *.LDF
As for the backup of the dumped SQL database backup, did you
This might be IC74758. Go to the Product support link in my sig and
search on the message number (IC688I) and/or IC74758.
- Andy
Andrew Raibeck | Tivoli Storage Manager Level 3 Technical Lead |
stor...@us.ibm.com
IBM
Hi Christian,
For your second question... some excludes are registered by the VSS
writers.
For example, the excludes below where most likely registered by the
SQL VSS Writer.
Thanks,
Del
ADSM: Dist Stor Manager ADSM-L@vm.marist.edu wrote
Hi Brent,
I don't know what your entire include/exclude list looks like
and I don't know the command you are using to run the backup.
Those pieces of information are vital to understanding
why the BA client is trying to back up the SQL database files.
If you can't figure it out, feel free to
Thanks Del
This was my include: F:\Program Files\Microsoft SQL
Server\MSSQL10_50.MSSQLSERVER\MSSQL\Backup\*\*.*
I have since changed it to: F:\Program Files\Microsoft SQL
Server\MSSQL10_50.MSSQLSERVER\MSSQL\Backup\*\*.bak
I will also add the exclude .mdf and .ldf
Why would it try to backup
Hi,
I'm sending out to you all to understand 2 questions that I have and why the BA
Client works the way it does?
I have a Windows Server 2003/2008 and 2012 servers that I want to backup with
TSM BA Client 6.3 and 6.4.
Because of old tradition are we using TSM Client Acceptor to run the TSM
Hi Christian,
Try these commands:
q inclexcl -display=ALL - shows all include exclude statements
q inclexcl -display=VSSEXCLUDE - all excludes that come from VSS
q inclexcl -display=BASIC- default
Thanks,
Del
ADSM:
Thanks Del,
Is it any command/registry key in Windows that can show does excludes?
/Christian
-Ursprungligt meddelande-
Från: Del Hoobler [mailto:hoob...@us.ibm.com]
Skickat: den 5 september 2013 17:28
Till: ADSM-L@VM.MARIST.EDU
Ämne: Re: Windows BA Client Question
Hi Christian,
For
I would never advise a client to run an unsupported configuration. All
kinds of problems will pop up when there is an issue...
Cheers,
Rick
On Sep 5, 2013 10:52 AM, Chavdar Cholev chavdar.cho...@gmail.com wrote:
Hi Del,
SQL is express edition. I see that it is not supported, but tried with
And we won't see support. I submitted a RFE asking for support which was
rejected..
Dan
-Ursprungligt meddelande-
Från: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] För Rick Harderwijk
Skickat: den 6 september 2013 06:16
Till: ADSM-L@VM.MARIST.EDU
Ämne: Re: [ADSM-L] TDP for MS
19 matches
Mail list logo
