Re: Schedule Question
Hi Robert I usually handle this by having a schedule that runs every hour, and two subsidiary admin schedules. One sets the hourly schedule to expiration=N to start it running. the second sets the hourly schedule expiration to a date in the past to stop it from running. Regards Steve Steven Harris, TSM Admin Canberra Australia On 13/05/2012 3:29 PM, Robert Ouzen wrote: Hi to all, Im trying to create a schedule in TSM that will run in a specific window, e.g: Im running backup of SSQL Log every hour, but when the Differential/Full Backup is running, the Log files are Missed, My question is can I run schedule from 08:00 untill 21:00 ? Far as I tested, I cant unless I will create 13 schedules, because the duration cant be more than the period, If I could define a schedule the will run from 08:00 period 13 hours every hour it will be great. Amos
Re: Schedule Question
I just have an admin schedule that runs after the last hourly log job and before the dif/full backup job that updates the log backup schedule to a STARTDATE/STARTTIME= to however many hours the diff/full backup runs. Bill -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Robert Ouzen Sent: Sunday, May 13, 2012 1:29 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Schedule Question Hi to all, Im trying to create a schedule in TSM that will run in a specific window, e.g: Im running backup of SSQL Log every hour, but when the Differential/Full Backup is running, the Log files are Missed, My question is can I run schedule from 08:00 untill 21:00 ? Far as I tested, I cant unless I will create 13 schedules, because the duration cant be more than the period, If I could define a schedule the will run from 08:00 period 13 hours every hour it will be great. Amos
Re: Schedule Question
Hi, you can created different dsm.opt files an present SQL server as two different nodes, also create two different management classes: one for transaction logs (every hour) and one for diff/full backup, Use these dsm.opt file witn dsmcutil to create two schedules, and TCPCLIENTPORT to specify different TCP/IP port for each schedule ... Regards Chavdar On Sun, May 13, 2012 at 9:17 PM, Bill Boyer bjdbo...@comcast.net wrote: I just have an admin schedule that runs after the last hourly log job and before the dif/full backup job that updates the log backup schedule to a STARTDATE/STARTTIME= to however many hours the diff/full backup runs. Bill -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Robert Ouzen Sent: Sunday, May 13, 2012 1:29 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Schedule Question Hi to all, Im trying to create a schedule in TSM that will run in a specific window, e.g: Im running backup of SSQL Log every hour, but when the Differential/Full Backup is running, the Log files are Missed, My question is can I run schedule from 08:00 untill 21:00 ? Far as I tested, I cant unless I will create 13 schedules, because the duration cant be more than the period, If I could define a schedule the will run from 08:00 period 13 hours every hour it will be great. Amos
Re: replication issue tsm 6.3.0
Ray, We are on our 3rd E-fix for node replication. 6.3.1.009. There appears to be a lot of high level DB locking in the 6.3.0 code. IBM has made several code fixes for us and is working on a few more issues. Below is what we have on. tsm: TSM02FMshow banner * EFIX Cumulative level 6.3.1.009 * * This is a Limited Availability TEMPORARY fix for * * IC81575 - NODE GROUP COMMANDS CAN HANG WHEN NODE REPLICATION * * IS RUNNING.* * IC81596 - NODE REPLICATION CAN HANG WHEN MULTIPLE THREADS* * PROCESS OBJECTS OF THE SAME PEER GROUP.* * IC81381 - POSSIBLE CRASH DURING REPLICATION OF DEDUPLICATED * * DATA. * * IC80966 - NODE REPLICATION SOURCE VOLUME SELECTION FOR DEDUPD* * DATA MAY SELECT COPY STG VOL EVEN IF VOLUME IS * * UNAVAILABLE. * * IC81370 - POSSIBLE SERVER CRASH WHEN USING VIRTUAL VOLUME* * GREATER THAN 2 GB. * * IC81819 - ANRD WITH NO BUFFER SPACE AVAILABLE TCPIP OUTBOUND * * IC82366 - WHEN DELETING OBJECTS ON THE TARGET SERVER DURING * * REPLICATION, ANR0379W MESSAGES MAY APPEAR * * IC80775 - ANR0538I WHEN GENERATE BACKUPSET IS RUNNING* * IC82162 - SERVER CAN CRASH DURING NODE REPLICATION IF A NODE * * HAS A LARGE NUMBER OF VERSIONS OF SYSTEM STATE BACKUPS * * IC80690 - BACKUP STGPOOL WITH MAXPROCESS GREATER THAN 1 MIGHT* * ENCOUNTER PROCESSING DELAYS OR POSSIBLY RESOURCE ABORT * * Symptom - REPLICATE NODE returns RC 0 when process fails * * IC82159 - SERVER MAY CRASH AT THE END OF A CLIENT DEDUP SESSION. * * IC81212 - NODE REPLICATION FAILS WITH UNEXPECTED COPYTYPE=1. * * IC81832 - ANR8302E I/O READ ERROR ON DRIVE WHEN ENABLING TSM ENC * * IC81437 - INVALID SQL COMMAND MIGHT CRASH TIVOLI STORAGE * * MANAGER SERVER.* * IC79957 - SHOW DEDUPDELETEINFO COMMAND MIGHT CRASH THE TIVOLI ST * * IC82823 - REPLICATION FAILS IF OBJECT IS REMOVED BEFORE IT IS RE * * 81961 - Disable setting INTRA_PARALLEL on server start * * IC79667 - NDMP BACKUP MAY FAIL WITH ANR8381E AND ANR1096E ERRORS * * THERE IS AN AVAILABLE SCRATCH VOLUME IN LIBRARY* * 82128 - Issue error message if replications fails for a filesp * * It is based on fixes made generally * * available with patch level 6.3.1.000 * * * -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Tim Brown Sent: Wednesday, May 02, 2012 12:00 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: replication issue tsm 6.3.0 Thanks!! Tim -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Ray Carlson Sent: Wednesday, 02 May, 2012 11:52 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: replication issue tsm 6.3.0 Tim, I have been fighting this problem for several months now. IBM is looking at it, but haven't come up with a solution. Ray On May 2, 2012, at 10:39 AM, Tim Brown wrote: Error during nodegroup replication, but I cant see any errors on the target server ANR1815W Check target server for storage problems during replication of node MINERVA, PERSEUS, SILVANUS, THESEUS, POKUCMS2, POKXPR1, POKSESAP1, POKOSVMS1, POKXPRSAT2, CRONUS, POKVERINTDB, POKVERINTREC, POKVERINTARC. (SESSION: 51623, PROCESS: 709) Rerun of replicate works Thanks, Tim Brown Supervisor Computer Operations Central Hudson Gas Electric 284 South Ave Poughkeepsie, NY 12601 Email: mailto:tbr...@cenhud.com tbr...@cenhud.com mailto:tbr...@cenhud.com mailto:tbr...@cenhud.com Phone: 845-486-5643 Fax: 845-486-5921 Cell: 845-235-4255 This message contains confidential information and is only for the intended recipient. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, please notify the sender immediately by replying to this note and deleting all copies and attachments. - This message and any included attachments are from NOVANT HEALTH INC. and are intended only for the addressee(s). The information contained herein may include trade secrets or privileged or otherwise confidential information. Unauthorized review, forwarding, printing, copying, distributing, or using such information is strictly
Best practices for Oracle and DB2 Moves
Hi All Like a lot of us, I'm contemplating a TSM 5.5 to 6.3 move for one of my customers. Most clients are not a problem, point the client at the new server, take the first backup, and then after an appropriate length of time either delete the data on the old server or export/import whatever is left. This works fine for the BA client, Domino, MSSQL, SAP, however it does not work for DB2 and Oracle. Since DB2 and Oracle keep track of their own named backups, and delete these when they have expired from the DBMS point of view, and they can only access one TSM node at a time, there will be orphaned backups left on the old server that will never expire, and as their entries are no longer in the DBMS's catalog they will never be deleted if they are imported to the new server. This particular customer likes to keep a periodic backup for a long time so it is a real issue. I just did Butterfly training, and that product solves the problem for oracle by restore/re-backup and fiddle the rman catalog. What are the rest of you doing to address this issue? Regards Steve. Steven Harris TSM Admin, Canberra Australia
Re: Best practices for Oracle and DB2 Moves
- Original Message - From: Steve Harris st...@stevenharris.info Hi All Like a lot of us, I'm contemplating a TSM 5.5 to 6.3 move for one of my customers. Most clients are not a problem, point the client at the new server, take the first backup, and then after an appropriate length of time either delete the data on the old server or export/import whatever is left. This works fine for the BA client, Domino, MSSQL, SAP, however it does not work for DB2 and Oracle. Since DB2 and Oracle keep track of their own named backups, and delete these when they have expired from the DBMS point of view, and they can only access one TSM node at a time, there will be orphaned backups left on the old server that will never expire, and as their entries are no longer in the DBMS's catalog they will never be deleted if they are imported to the new server. This particular customer likes to keep a periodic backup for a long time so it is a real issue. I just did Butterfly training, and that product solves the problem for oracle by restore/re-backup and fiddle the rman catalog. What are the rest of you doing to address this issue? Regards Steve. Steven Harris TSM Admin, Canberra Australia You could 'export node' - however if you want to do that across the LAN it does rely on the new server having a new name so you can do server-server comms, and a password reset. Or you can rename the old server, and reset the passwords on all the nodes you've not yet moved. Or just export/import via media. There is a time issue where you don't want the rman catalog resync'd or it will re-do a full backup depends on the time taken to export/import if that is an issue or not. I still fail to see why it takes so long to insert the database when doing an upgrade.
