For TDP for SQL 2.2 you would specify TDPSQLC BACKUP * FULL plus whatever
options you need. This will backup all databases but not tempdb, tempdb is
always excluded from all TDP for SQL operations. The wild card can be
partial, such as abc* and databases can be excluded from backup using
exclude s
Dean, TDP for MS SQL 2.2.0.01 is available at
ftp://ftp.software.ibm.com/storage/tivoli-storage-management/patches/agents/ntsql/2.2.0/
However, as Shekhar said, you must first purchase 2.2.0 to get a valid
license; the download does not have a paid license.
Bob KingIBM Global ServicesTi
Tivoli Data Protection for Microsoft SQL Server 1.1.2.01 supports SQL
Server 7.0 and TSM Server Version 3. See
http://www.tivoli.com/support/storage_mgr/tdp_ms.html#SQL and
http://www.tivoli.com/support/storage_mgr/pubs/v3pubs/v1_html/mssql/ab5mtfrm.htm
The latest version is 2.2.0.01 but it req
Mark, once a MS SQL transaction log sequence is started it is independent
of other backups, until the sequence is ended. SQL Server keeps track of
the logged transactions included in a backup. So, the first transaction log
backup after a full database backup will contain transactions from before,
Jack, TDP for SQL keeps a lot of meta data, such as various names, version
numbers, dates and times, sizes, etc. (TDP for SQL's meta data is separate
from SQL server's meta data.) All of this meta data is contained within the
TSM server database except for the names of the groups and files for a S
Bo,
We've seen this when TDP for SQL has been uninstalled and then another TDP
or TSM product is used. Installing the latest backup/archive client, TSM
API runtime feature, has fixed it. You might try that.
Bob KingIBM Global Services
[EMAIL PROTECTED]
-
>From Bo
cally converting to TDP for SQL Version 2, users should have
analyzed their backup and restore procedures to assess how and where the
new capabilities can be applied.
Bob KingIBM Global Services
[EMAIL PROTECTED]
>From Mark Stapleton:
>Robert L King wrote:
>> However, TDP for MS
David, TDP for MS SQL 2.2.0 is not available for download because it is a
new product, not an upgrade. It is licensed separately from version 1. You
will have to contact a Tivoli sales representative to purchase version 2.
However, TDP for MS SQL 1.1.2 can do full and log backups of SQL 2000
data
This is a SQL Server restriction. The code page and sort order of the
restoring database must be the same as the current database. With SQL
Server 7.0, this means the restoring database must match the SQL server's
code page and sort order.
Either the sort order of the SQL server was changed since
Neil, with your additional information I have recreated the problem. Please
call IBM service, request to go directly to level 2, and have them open a
problem report.
Thanks for your analysis.
Bob KingIBM Global Services
[EMAIL PROTECTED]
Robert, this is a SQL Server restriction. In the SQL Server Books Online
section "Backing Up the master Database" there is "Note Only full database
backups of master can be created".
To use the command "tdpsqlc backup * log" you can enter an exclude
statement in the TSM options file (default "dsm
Bo, this is a known problem. From the fix's readme:
This is FIXTEST Version 1.1.2.01. It includes the following fix:
- IC26111
If a SQL Server 7.0 database is at compatibility level 60 or 65, an
attempt to backup the database or its transaction log would result
in the
David,
You might check the "Log on As:" parameter for the TSM scheduler service
that is running the command type schedule. Is it the same user as when it
worked with the command line in the NT command window?
Do you know if TDP for SQL 1.1.1 also fails now or just 1.1.1.01?
If checking the user
Davide,
To restore into a database you have to make sure you are not restoring to a
physical name that already exists. When the database you are restoring into
is on the same host as the original database, the original physical name
does already exist. To get around this with TDP for SQL Version
I take it that you create a clone by means other than backup/restore
and that you create a snapshot using EMC hardware or the like.
SQL Server won't let you restore transaction logs unless you've first
restored the database, or at least a database file group or file. Then
you have to restore all
15 matches
Mail list logo
