Re: TDP for SQL question
Paul, If you need to restore from the new node name, you would launch the CLI or GUI specifying the alternate options file name. For example, in the example below: GUI: TDPSQL /TSMOPTFILE=DSMARCH.OPT CLI: TDPSQLC RESTORE dbname full /TSMOPTFILE=DSMARCH.OPT This will tell Data Protection for SQL to connect to the TSM Server using the alternate options file, thus the alternate NODENAME. Del ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU wrote on 01/22/2008 11:54:12 PM: OK - I have done this and it is working as far as backing up the SQL database goes. Now what do I do if I need to restore from this new node name back onto the client? Do I need to do anything with the dsm.opt and dsmarch.opt files before starting the restore? -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Del Hoobler Sent: Saturday, 4 August 2007 2:37 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] TDP for SQL question Paul, Typically... I see that people will name their node the same as their primary SQL node with an extension. Something like: Primary: SQLSRV23_SQL Archive: SQLSRV23_SQL_ARCH And they will have a separate DSM.OPT file, something like DSMARCH.OPT that has the archive nodename. Thanks, Del
Re: TDP for SQL question
OK - I have done this and it is working as far as backing up the SQL database goes. Now what do I do if I need to restore from this new node name back onto the client? Do I need to do anything with the dsm.opt and dsmarch.opt files before starting the restore? Regards Paul Dudley Senior IT Systems Administrator ANL IT Operations Dept. ANL Container Line [EMAIL PROTECTED] 03-9257-0603 http://www.anl.com.au -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Del Hoobler Sent: Saturday, 4 August 2007 2:37 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] TDP for SQL question Paul, Typically... I see that people will name their node the same as their primary SQL node with an extension. Something like: Primary: SQLSRV23_SQL Archive: SQLSRV23_SQL_ARCH And they will have a separate DSM.OPT file, something like DSMARCH.OPT that has the archive nodename. Thanks, Del ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU wrote on 08/03/2007 12:53:23 AM: I have been told that if I want to create an archive backup of an SQL database via TDP for SQL, then I should create a separate node name in TSM (such as SQL_Archive) and then backup using that node name once a month (for example) and make sure to bind those backups to a management class that has the long term settings that meet our requirements. What else is involved in setting this up? On the client do I have to create another dsm.opt file with the new node name to match what I set up on the TSM server? Regards Paul Dudley ANL DISCLAIMER This e-mail and any file attached is confidential, and intended solely to the named addressees. Any unauthorised dissemination or use is strictly prohibited. If you received this e-mail in error, please immediately notify the sender by return e-mail from your system. Please do not copy, use or make reference to it for any purpose, or disclose its contents to any person.
Re: TDP for SQL question
Paul, Typically... I see that people will name their node the same as their primary SQL node with an extension. Something like: Primary: SQLSRV23_SQL Archive: SQLSRV23_SQL_ARCH And they will have a separate DSM.OPT file, something like DSMARCH.OPT that has the archive nodename. Thanks, Del ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU wrote on 08/03/2007 12:53:23 AM: I have been told that if I want to create an archive backup of an SQL database via TDP for SQL, then I should create a separate node name in TSM (such as SQL_Archive) and then backup using that node name once a month (for example) and make sure to bind those backups to a management class that has the long term settings that meet our requirements. What else is involved in setting this up? On the client do I have to create another dsm.opt file with the new node name to match what I set up on the TSM server? Regards Paul Dudley
TDP for SQL question
I have been told that if I want to create an archive backup of an SQL database via TDP for SQL, then I should create a separate node name in TSM (such as SQL_Archive) and then backup using that node name once a month (for example) and make sure to bind those backups to a management class that has the long term settings that meet our requirements. What else is involved in setting this up? On the client do I have to create another dsm.opt file with the new node name to match what I set up on the TSM server? Regards Paul Dudley ANL IT Operations Dept. ANL Container Line [EMAIL PROTECTED] ANL - CELEBRATING 50 YEARS ANL DISCLAIMER This e-mail and any file attached is confidential, and intended solely to the named addressees. Any unauthorised dissemination or use is strictly prohibited. If you received this e-mail in error, please immediately notify the sender by return e-mail from your system. Please do not copy, use or make reference to it for any purpose, or disclose its contents to any person.
Re: TDP for SQL question
On 03/08/2007, at 2:53 PM, Paul Dudley wrote: I have been told that if I want to create an archive backup of an SQL database via TDP for SQL, then I should create a separate node name in TSM (such as SQL_Archive) and then backup using that node name once a month (for example) and make sure to bind those backups to a management class that has the long term settings that meet our requirements. What else is involved in setting this up? On the client do I have to create another dsm.opt file with the new node name to match what I set up on the TSM server? In the context of the BA client, you can create multiple server stanzas in dsm.sys to point at different TSM instances and/or node names - eg, we do this with one particular system so that we can hold an image backup for ten days normally, but once a week, put one aside for eight weeks. The dsm.sys for this node looks like: servername (instance)_8WR commmethod tcpip tcpport(port) tcpserveraddress (server) passwordaccess generate [...] nodename (client)_8wr servername (instance) commmethod tcpip tcpport(port) tcpserveraddress (server) passwordaccess generate [...] nodename (client) All that is in dsm.opt is a line servername (instance), so that backups by default go to the client's standard node; for the 8 week retention, we add a -se=(instance)_8WR, and TSM does the right thing. (The '[...]' signals where I've cut out a number of TCP/IP options, along with other client-side options.) How to do this for a TDP client is left as an exercise for the reader. :-) Hopefully, it should give you some ideas. Good luck.
Re: TDP for SQL question
Eric, I would have them check again to make sure they are using the NODENAME they think they are using. Have them check their DP for SQL logs files as well. Also, check the TSM Server activity log to see what messages are being logged for that NODENAME. DP for SQL will log ending statistics that summarize the backups. Thanks, Del I have got two TDP for SQL 2.2 clients. On one of them I see two filespaces: Nodename\meta\ Nodename\data\ Both filespaces have a backup date 1, so that seems ok. The other node however has both filespaces listed with a backup date of 31 days ago. So I was thinking that the backup is not running on this client. The owner however says everything is running fine. If that's the case, why isn't the backup date updated for this node? Thanks in advance for any reply!
TDP for SQL question
Hi *SM-ers! I have got two TDP for SQL 2.2 clients. On one of them I see two filespaces: Nodename\meta\ Nodename\data\ Both filespaces have a backup date 1, so that seems ok. The other node however has both filespaces listed with a backup date of 31 days ago. So I was thinking that the backup is not running on this client. The owner however says everything is running fine. If that's the case, why isn't the backup date updated for this node? Thanks in advance for any reply! Kindest regards, Eric van Loon KLM Royal Dutch Airlines ** For information, services and offers, please visit our web site: http://www.klm.com. This e-mail and any attachment may contain confidential and privileged material intended for the addressee only. If you are not the addressee, you are notified that no part of the e-mail or any attachment may be disclosed, copied or distributed, and that any other action related to this e-mail or attachment is strictly prohibited, and may be unlawful. If you have received this e-mail by error, please notify the sender immediately by return e-mail, and delete this message. Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its employees shall not be liable for the incorrect or incomplete transmission of this e-mail or any attachments, nor responsible for any delay in receipt. **
TDP for SQL question
We have a situation where we are trying setup a test SQL database on a server. The server (WinNT4 w/TSM client 3.7.2 and SQL client 1.1.2 and MS-SQL 6.5) itself is cramped for space and we need to make a copy of the database so that we can do some testing and still keep the production database running. Our database guy says that MS-SQL has a way to dump the database to a flat file and then you can just import it into a new database. Unfortunately, he says that you can only dump the file to a drive on the server itself and not another network drive. The server doesn't have enough drive space to do the dump on to its self. Now the question, can we tell the TDP client to do a restore of the production database but then redirect it to another server running SQL? We have a spare server that has plenty of space that can be used for this. Thanks David Tyree Microcomputer Specialist South Georgia Medical Center 229.333.1155 Confidential Notice: This e-mail message, including any attachments, is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message.
Re: TDP for SQL question
Now the question, can we tell the TDP client to do a restore of the production database but then redirect it to another server running SQL? We have a spare server that has plenty of space that can be used for this. If you are using TDP for SQL 1.1.2, refer to the TDP for SQL 1.1.2 Installation and User's Guide, Appendix B, under section titled: Restoring an SQL Database from an Alternate SQL Server. Thanks, Del Del Hoobler IBM Corporation [EMAIL PROTECTED] It's a beautiful day. Don't let it get away. -- Bono
TDP for SQL Question
We are looking into starting to use TDP for SQL. Question from our DBA's: When configuring the SQL Server backups is it possible to configure a backup that will backup ALL the SQL Server databases (master, msdb, and user created) with one command such that if additional databases are added to SQL Server they are automatically backed up? OR does TDP have to be configured every time a new database is added in SQL Server? Curt Magura Lockheed Martin EIS Gaithersburg, Md. 301-240-6305
Re: TDP for SQL Question
Yes, by default that is the way it is done. After you install TDP on the client, look in the ..Tivoli/TSM/Mssql directory. The file sqlfull.smp is designed to be copied to sqlfull.cmd. You need to edit the bat file for directories etc. The backup command in it wil do a full backup of ALL DB's, even tempdb even thought this is not valid for restore. Note also last line in file for doing autodelete of backups, you can specify how many copies you want to keep. This info is valid for TDP MSSQL 1.1.2, I use here on about a dozen NT 4.0 machines with SQL 6.5, 7.0 and 2000. 1.1.1 does not have autodelete, may be similar info for ver 2.2. David B. Longo System Administrator Health First, Inc. 3300 Fiske Blvd. Rockledge, FL 32955-4305 PH 321.434.5536 Pager 321.634.8230 Fax:321.434.5525 [EMAIL PROTECTED] [EMAIL PROTECTED] 05/10/01 04:29PM We are looking into starting to use TDP for SQL. Question from our DBA's: When configuring the SQL Server backups is it possible to configure a backup that will backup ALL the SQL Server databases (master, msdb, and user created) with one command such that if additional databases are added to SQL Server they are automatically backed up? OR does TDP have to be configured every time a new database is added in SQL Server? Curt Magura Lockheed Martin EIS Gaithersburg, Md. 301-240-6305 MMS health-first.org made the following annotations on 05/10/01 16:51:55 -- This message is for the named person's use only. It may contain confidential, proprietary, or legally privileged information. No confidentiality or privilege is waived or lost by any mistransmission. If you receive this message in error, please immediately delete it and all copies of it from your system, destroy any hard copies of it, and notify the sender. You must not, directly or indirectly, use, disclose, distribute, print, or copy any part of this message if you are not the intended recipient. Health First reserves the right to monitor all e-mail communications through its networks. Any views or opinions expressed in this message are solely those of the individual sender, except (1) where the message states such views or opinions are on behalf of a particular entity; and (2) the sender is authorized by the entity to give such views or opinions. ==
Re: TDP for SQL Question
TDP for Sql supports the use of wildcard characters in the command line backup commands. Thanks, Bill William Degli-Angeli IGS TDP Development Endicott, NY (607) 752-6749 TieLine: 852-6749 Internet: [EMAIL PROTECTED] Magura, Curtis To: [EMAIL PROTECTED] curtis.magura cc: @LMCO.COM Subject: TDP for SQL Question Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] IST.EDU 05/10/2001 16:29 Please respond to ADSM: Dist Stor Manager We are looking into starting to use TDP for SQL. Question from our DBA's: When configuring the SQL Server backups is it possible to configure a backup that will backup ALL the SQL Server databases (master, msdb, and user created) with one command such that if additional databases are added to SQL Server they are automatically backed up? OR does TDP have to be configured every time a new database is added in SQL Server? Curt Magura Lockheed Martin EIS Gaithersburg, Md. 301-240-6305
Re: TDP for SQL Question
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 statements in the dsm.opt file. TDP for SQL 2.2 uses TSM policy management so you don't have to use autodelete. The policy management settings can control how many versions to keep and for how long. For more details you can get the TDP for SQL 2.2 manual at http://www.tivoli.com/support/public/Prodman/public_manuals/storage_mgr/v1_html/mssql/v2/ab5mtfrm.htm Bob King [EMAIL PROTECTED] David Longo [EMAIL PROTECTED]@VM.MARIST.EDU on 05/10/2001 04:50:13 PM Please respond to ADSM: Dist Stor Manager [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: Subject: Re: TDP for SQL Question Yes, by default that is the way it is done. After you install TDP on the client, look in the ..Tivoli/TSM/Mssql directory. The file sqlfull.smp is designed to be copied to sqlfull.cmd. You need to edit the bat file for directories etc. The backup command in it wil do a full backup of ALL DB's, even tempdb even thought this is not valid for restore. Note also last line in file for doing autodelete of backups, you can specify how many copies you want to keep. This info is valid for TDP MSSQL 1.1.2, I use here on about a dozen NT 4.0 machines with SQL 6.5, 7.0 and 2000. 1.1.1 does not have autodelete, may be similar info for ver 2.2. David B. Longo System Administrator Health First, Inc. 3300 Fiske Blvd. Rockledge, FL 32955-4305 PH 321.434.5536 Pager 321.634.8230 Fax:321.434.5525 [EMAIL PROTECTED] [EMAIL PROTECTED] 05/10/01 04:29PM We are looking into starting to use TDP for SQL. Question from our DBA's: When configuring the SQL Server backups is it possible to configure a backup that will backup ALL the SQL Server databases (master, msdb, and user created) with one command such that if additional databases are added to SQL Server they are automatically backed up? OR does TDP have to be configured every time a new database is added in SQL Server? Curt Magura Lockheed Martin EIS Gaithersburg, Md. 301-240-6305 MMS health-first.org made the following annotations on 05/10/01 16:51:55 -- This message is for the named person's use only. It may contain confidential, proprietary, or legally privileged information. No confidentiality or privilege is waived or lost by any mistransmission. If you receive this message in error, please immediately delete it and all copies of it from your system, destroy any hard copies of it, and notify the sender. You must not, directly or indirectly, use, disclose, distribute, print, or copy any part of this message if you are not the intended recipient. Health First reserves the right to monitor all e-mail communications through its networks. Any views or opinions expressed in this message are solely those of the individual sender, except (1) where the message states such views or opinions are on behalf of a particular entity; and (2) the sender is authorized by the entity to give such views or opinions. ==
