Re: Installing TDP for SQL 2.2
David, Make sure that script name in the schedule is identical to the name of the script on the NT box. Check the .extension of the script. Bill - Original Message - From: Tyree, David [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Monday, April 22, 2002 1:58 PM Subject: Installing TDP for SQL 2.2 We are trying to install the TDP for SQL version 2.2 on to a WinNT4 machine running MS-SQL. So far we have the client (version 4.2.1.20) installed to catch all the non SQL files. It's set up to be called by the TSM server to run and it's doing fine. All the non SQL backups are fine. We have the SQL folders set to be excluded. We are now trying to install the SQL part now and it does not want to play nice. We loaded version 2.2.0.0 and we have gotten it working to point where we can do a SQL backup from the command line and from within the GUI. We can't get it run when it's called from the TSM server. The programs are all installed to the default locations and I ran the dsmcutil install command from the baclient folder to create a new scheduler service for the SQL part. I referred it to the dsm file in the tdpsql folder just like the docs said. I've got a schedule on the TSM server set to kick off at a certain time but nothing happens. I've looked at the assorted log files nothing shows up. If I run tdpsqlc backup * full it runs just fine. Am I missing something here? Do I need to call the sqlfull.cmd from one of the dsm.opt files? 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: TSM network problem
Jim, What is your server platform? I have seen issues with the NIC card being on a slower bus in an AIX box cause problems.Once we moved the NIC card to a 40 MB/sec bus we were fine. - Original Message - From: Alex Paschal [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Wednesday, April 17, 2002 2:28 PM Subject: Re: TSM network problem Jim, What have your network people said when they ran a packet analyzer on that switch? Also, have you tried running a crossover cable from your TSM server to one client to see if that works? It might be a way to prove that the problem doesn't lie with your systems. -Original Message- From: Jim Healy [mailto:[EMAIL PROTECTED]] Sent: Tuesday, April 16, 2002 5:15 AM To: [EMAIL PROTECTED] Subject: Re: TSM network problem Sean, At one point we moved the cable from the TSM Server NIC on the switch to another port with no change in the error. Seay, Paul [EMAIL PROTECTED]@VM.MARIST.EDU on 04/15/2002 11:28:35 PM Please respond to ADSM: Dist Stor Manager [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: Subject: Re: TSM network problem Did you use the same ports on the switch? -Original Message- From: Jim Healy [mailto:[EMAIL PROTECTED]] Sent: Monday, April 15, 2002 2:25 PM To: [EMAIL PROTECTED] Subject: TSM network problem Can any of you network gurus help me out with a TSM problem? We currenty have an isolated 100mb ethernet network for TSM. We have three NICS in the TSM server, each attached to a seperate V-lan We spread the servers backing up across the three v-lans We are having on clients on one of the vlans that intermittently get session lost re-initializing messages in the dsmsched.log When we ping the clients from the TSM server we get no seesion or packet loss When we ping the TSM nic from the client we get intermittent packet losses We replaced the NIC in the TSM server We replaced the cable from the TSM server to the switch We replaced the cable from the client NIC to the switch We've ensured that both NICs are set to 100/full My network guys are out of ideas any body have any suggestions?
Re: upgrade ADSM 3.1 DB to TSM 4.1
Henry, I recently did the same thing at a customer site except it was NT and W2K. I cheated and used DRM to help me. Here are the steps that I did. Created the new 4.2 server on W2K. ( For simplicity sake I kept the same names for the storage pools,library,etc ). Upgraded the existing 3.1 NT Server to 4.2.( Read the release notes carefully ) Performed a DB backup of the upgraded server. Ran prepare Disconnected the NT Server from the Storage Works Library. Connected up the W2K server to the Storage Works Library Loaded the DB on the new 4.2 W2K server using the restore db command from the DRM plan file. Powered off the old NT server. Bill -Original Message- From: Henrry Aranda Sent: Thu 10/25/2001 12:11 PM To: [EMAIL PROTECTED] Cc: Subject: upgrade ADSM 3.1 DB to TSM 4.1 Hello, I'm planning to install an TSM 4.1 server in a client location who already has ADSM 3.1, in fact i have to use another box (both are AIX 4.3.3) How should i do in order to migrate the database? Because the client wants to keep all the backups and policies he has already defined. Could you let me know any experiencies/best practices i should know? Any help would be appreciated Thanks in advance. Henrry Aranda Gonzales _ Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp
