Re: dsmcad/dsmsched.log showing wrong times
Hi Michiel, I'm pretty sure that you have already thought of this, but have you tried entering the Accept Date command to synchronize the TSM server date/time with the OS Date/Time? Jim Neal -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Vlijmen, M. van Sent: Friday, March 24, 2006 12:39 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] dsmcad/dsmsched.log showing wrong times Goodday, We have IBM Tivoli Storage Manager 5.3.2.0 running on a ppc64 redhat machine One of the clients is a hp 9000 with hpux 11.i V1. The problem I have is that the times shown in the dsmsched.log do not match the (actual ?) time. I stopped and started dsmcad manually which solved the problem. That's nice but I like to know what the reason was since I don't want it to happen again. Anyone any idea? Thanks in advance. Michiel Time on RedHat TSM server: [EMAIL PROTECTED] etc]$ date Thu Mar 23 15:46:31 CET 2006 Time on HP/UX 11i TSM client: hp date Thu Mar 23 15:48:33 MET 2006 Note that MET = CET 03/23/06 03:34:59 Querying server for next scheduled event. 03/23/06 03:34:59 Node Name: HPL4 03/23/06 03:34:59 Session established with server SERVER1: Linux/ppc64 03/23/06 03:34:59 Server Version 5, Release 3, Level 2.0 03/23/06 03:34:59 Server date/time: 03/23/06 09:32:44 Last access: 03/23/06 09:30:07 03/23/06 03:34:59 --- SCHEDULEREC QUERY BEGIN 03/23/06 03:34:59 --- SCHEDULEREC QUERY END 03/23/06 03:34:59 Next operation scheduled: 03/23/06 03:34:59 03/23/06 03:34:59 Schedule Name: CS_HPUX_DAILY_0100 03/23/06 03:34:59 Action:Incremental 03/23/06 03:34:59 Objects: / 03/23/06 03:34:59 Options: 03/23/06 03:34:59 Server Window Start: 01:00:00 on 03/24/06 03/23/06 03:34:59 03/23/06 03:34:59 Scheduler has been stopped. (here I did a stop and start) 03/23/06 13:39:29 Scheduler has been started by Dsmcad. 03/23/06 13:39:29 Querying server for next scheduled event. 03/23/06 13:39:29 Node Name: HPL4 03/23/06 13:39:29 Session established with server SERVER1: Linux/ppc64 03/23/06 13:39:29 Server Version 5, Release 3, Level 2.0 03/23/06 13:39:29 Server date/time: 03/23/06 13:37:14 Last access: 03/23/06 13:36:13 Disclaimer : Aan de inhoud van dit bericht kunnen geen rechten worden ontleend. De informatie is uitsluitend bestemd voor de geadresseerde. Gebruik door anderen is verboden. Openbaarmaking, vermenigvuldiging en verstrekking van deze informatie aan derden is niet toegestaan.
Re: HELP! MAJOR ISSUE!: NEW Info. Please help!
Hi Joni, Just thought I would add my 2 cents into the mix as well. Have you checked to find out if you have any scratch tapes available in the library? I know this is a basic question and that you have probably already done it, but I have seen that type of message when migration starts to go to tape, fills up the very end of the last tape, and then can't locate any available scratch volumes in the library to continue the process. Jim Neal -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Joni Moyer Sent: Thursday, March 23, 2006 7:19 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] HELP! MAJOR ISSUE!: NEW Info. Please help! Hello Everyone, I just keep seeing the below messages and I can't seem to figure out why I'm getting them. Any ideas? 03/23/06 10:14:36 ANR2183W dfmigr.c1980: Transaction 0:2575477455 was aborted. (PROCESS: 1177) 03/23/06 10:14:36 ANR1033W Migration process 1177 terminated for storage pool ORACLE - transaction aborted. (PROCESS: 1177) 03/23/06 10:14:36 ANR0985I Process 1177 for MIGRATION running in the BACKGROUND completed with completion state FAILURE at 10:14:36. (PROCESS: 1177) 03/23/06 10:14:36 ANR1002I Migration for storage pool ORACLE will be retried in 60 seconds. Joni Moyer Highmark Storage Systems, Senior Systems Programmer Phone Number: (717)302-9966 Fax: (717) 302-9826 [EMAIL PROTECTED] Das, Samiran (GTI) [EMAIL PROTECTED] To OM ADSM-L@VM.MARIST.EDU Sent by: ADSM:cc Dist Stor Manager Subject [EMAIL PROTECTED] Re: HELP! MAJOR ISSUE! .EDU 03/23/2006 09:46 AM Please respond to ADSM: Dist Stor Manager [EMAIL PROTECTED] .EDU Joni, (Q stg oracle f=d) output shows that currently migration is in progress. Migration in Progress?: Yes Amount Migrated (MB): 649.67 Elapsed Migration Time (seconds): 2,697 However migration seems to be running very slowly (649 MB migrated in 2697 seconds). As the stgpool is large (737 GB), you are not seeing any Pct Util change. Migration is supposed to run with 4 processes. So please issue (q proc) and see how many migration processes are running. Also please check (q devc lto2 f=d) and see how many mount points are available. Since when this problem started? Do you remember any TSM or hardware environment changes recently? Thanks Regards, Samiran Das -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Joni Moyer Sent: Thursday, March 23, 2006 9:25 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: HELP! MAJOR ISSUE! Hi Samiran Das, Here is the output of those commands. Thanks! Storage Pool Name: ORACLE Storage Pool Type: Primary Device Class Name: DISK Estimated Capacity (MB): 737 G Pct Util: 100.0 Pct Migr: 100.0 Pct Logical: 100.0 High Mig Pct: 0 Low Mig Pct: 0 Migration Delay: 0 Migration Continue: Yes Migration Processes: 4 Next Storage Pool: TAPE_ORACLE Reclaim Storage Pool: Maximum Size Threshold: 9 G Access: Read/Write Description: Oracle Disk Storage Pool Overflow Location: Cache Migrated Files?: No Collocate?: Reclamation Threshold: Maximum Scratch Volumes Allowed: Delay Period for Volume Reuse: Migration in Progress?: Yes Amount Migrated (MB): 649.67 Elapsed Migration Time (seconds): 2,697 Reclamation in Progress?: Volume Being Migrated/Reclaimed: Last Update by (administrator): LIDZR8V Last Update Date/Time: 03/23/06 08:43:16 Storage Pool Data Format: Native Copy Storage Pool(s): Continue Copy on Error?: CRC Data: No Storage Pool Name: TAPE_ORACLE Storage Pool Type: Primary Device Class Name: LTO2 Estimated Capacity (MB): 8,148,058 G Pct Util: 0.5 Pct Migr: 3.8 Pct Logical: 99.3 High Mig Pct: 90 Low Mig Pct: 70 Migration Delay: 0 Migration Continue: Yes Migration Processes:
Re: TSM 5.3 Inst. on MSCS
Hi Pranav! There are two excellent resources available to help you with this. IBM has two redbooks that cover the process pretty well. Go to the IBM website and in the redbooks section do a search for the following: SG24-6844-01 SG24-6761-00 The first SG number is for Disaster Recovery Strategies with Tivoli Storage Management. The second SG number is for Deployment Guide for IBM Tivoli Storage Manager V5.3. I hope this information helps! Jim Neal -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Pranav Parikh Sent: Thursday, March 16, 2006 8:08 PM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] TSM 5.3 Inst. on MSCS Hi, Can any one help me to install TSM5.3 in MSCS cluster enviornment. We have two IBM xseries servers with each having 3584 Library and shared storage. Where can I found resources for this? Regards Pranav
Re: Schedule Repeatation
Hi Pranav! If you really need to back up a client(s) that often with Tivoli, the way to do it is to create three separate schedules that run every hour and run 20 minutes apart. Then assign the client to all three schedules. For example: Start time Runs Schedule 1 09:00Hourly Schedule 2 09:20Hourly Schedule 3 09:40Hourly Please let me know if you need any additional info. Jim Neal -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Pranav Parikh Sent: Friday, March 17, 2006 4:10 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Schedule Repeatation Thanks Richard, Requirement is to backup incremental data contineously every 15 to 20 mins. Regards Pranav Richard Sims [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU 03/17/2006 05:35 PM Please respond to ADSM: Dist Stor Manager To: ADSM-L@VM.MARIST.EDU cc: Subject:Re: [ADSM-L] Schedule Repeatation On Mar 17, 2006, at 5:38 AM, Pranav Parikh wrote: Hi, I had a requirement to backup client data every 15mins. Is it possible? can anyone help how to to do so in ITSM 5.3 enviornment. Given that client backups usually take substantially more than 15 minutes, that doesn't sound realistic with a classic backup product. Your site needs to better define exactly what it is trying to achieve. Your site may want a data protection product like Tivoli Continuous Data Protection for Files (see http://www.ibm.com/software/ tivoli/products/continuous-data-protection/). Richard Sims
Re: scratch tape question
Hi Dave, Actually, I can only see advantages to checking the tapes in as they arrive: 1) The tapes are less likely to be lost or suffer environmental damage 2) At the rate you are using tapes, you won't have to check in any new tapes for quite a while. 3) You won't have to worry about the tapes taking up too much space outside of the silo or getting in the way. Others people may be able to think of something I haven't, but that's my 2 cents. I hope it helps. Jim Neal -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Dave Zarnoch Sent: Friday, March 17, 2006 8:04 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] scratch tape question As a result of expiration, reclamation and removal of a large storage pool. We are getting back approximately 100 scratch tapes/week We run an SL8500 library with 1600 cells of which 600 are free. Is there any difference whether I check these scratch tapes in as they arrive or place them in an inventory outside the silo. Right now we have 250 scratch tapes in the silo and use approximately 15/night. 60 more are coming in today. I can see that placing them in an inventory will require an extra step to keep the tapes in some sort of order. But, is there any disadvantages to have so many scratch tapes available in the silo? AdThanksvance! Dave Zarnoch Nationwide Provident [EMAIL PROTECTED]
Re: Library sharing
Hi Richard! Other than having to redefine the tape paths on each instance, as long as the databases are up to date for each instance, there shouldn't be any problems. I'm sure that you already know to make backups of all the recovery files just prior to doing the upgrade just in case. : ) Jim Neal -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Richard Mochnaczewski Sent: Friday, March 17, 2006 8:09 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Library sharing Hi Everybody, I'll be upgrading from TSM 5.1.6 to 5.2.6.4 this weekend. I will also up updating the tivoli.tsm.devices.aix5.rte fileset ( it was at aix43 because I upgraded from AIX 4.3.3 to 5.2 ML6 a few weeks ago and didn't update it ). From what I've read, updating this fileset will mess up all my tape definitions. If this is the case, do I have to pay any special attention to the library sharing between two instances I have on this server ? Rich
Re: MSL6030 TSM write failure
Glad I could help! -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Kurt Beyers Sent: Tuesday, March 14, 2006 9:25 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] MSL6030 TSM write failure Jim, It looks indeed to be a HW problem with the library (which is brand new, so that cancels option 1 and 2). I was just surprised that the tapes could be labelled as data is wrtten to them then too. But apperantly the HW issues only pop-up when you start sending the backup data, which are larger then a label of course. thanks, Kurt Van: ADSM: Dist Stor Manager namens JN Verzonden: di 3/14/2006 18:53 Aan: ADSM-L@VM.MARIST.EDU Onderwerp: Re: [ADSM-L] MSL6030 TSM write failure Hi Kurt, In my experience, the errors that you are seeing are primarily caused by one of three problems: 1) The tape drive is dirty and needs to be cleaned 2) The tape cartridge is bad and needs to be destroyed 3) The Tape drive has a physical problem that needs to be fixed via replacement or maintenance. I hope one of these solutions works for you. Jim -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Kurt Beyers Sent: Tuesday, March 14, 2006 1:01 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] MSL6030 TSM write failure Hello, A quick (?) question. My setup is the following: TSM 5.3.2 server with a MSL6030 SCSI attached library (2 HP-Ultrium 3 drives). The library has been defined in TSM and the labelling of the tapes went fine. However a migrate of the diskpool towards the LTOPool fails with the following messages: ANR0984I Process 42 for MIGRATION started in the BACKGROUND at 08:45:30. ANR2110I MIGRATE STGPOOL started as process 42. ANR1000I Migration process 42 started for storage pool DISKPOOL manually, highMig=90, lowMig=0, duration=No. ANR8337I LTO volume HK3722L3 mounted in drive DRIVE1 (mt1.0.0.5). ANR1340I Scratch volume HK3722L3 is now defined in storage pool LTOPOOL. ANR0513I Process 42 opened output volume HK3722L3. ANR8302E I/O error on drive DRIVE1 (mt1.0.0.5) with volume HK3722L3 (OP=WRITE, Error Number=1117, CC=208, KEY=0B, ASC=47, ASCQ=03, SENSE=70.00.0B.00.00.00.00.10.00.00.00.00.47.03.00.00.00.00.00.00.00.00., Description=Command aborted). Refer to Appendix D in the 'Messages' manual for recommended action. ANR1411W Access mode for volume HK3722L3 now set to read-only due to write error. ANR0515I Process 42 closed volume HK3722L3. What am I missing here? The library configuration in TSM is as follows: -The TSM device driver is used and the library is detected by the tsmdlst.exe program as follows: Tivoli Storage Manager -- Device List Utility Licensed Materials - Property of IBM 5697-TSM (C) Copyright IBM Corporation 2000, 2005. All rights reserved. U.S. Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corporation. Computer Name: TSM-server OS Version: 5.2 OS Build #: 3790 TSM Device Driver: TSMScsi - Running 2 HBAs were detected. ManufacturerModel Driver VersionFirmware Description QLogic Corporation QLA2340ql2300.sys 9.0.2.11 (w32 IP) 3.03.12 QLogic QLA2340 Fibre Channel Adapter QLogic Corporation QLA2340ql2300.sys 9.0.2.11 (w32 IP) 0.00.00 QLogic QLA2340 Fibre Channel Adapter TSM Name ID LUN Bus Port SSN WWN TSM Type Device Identifier lb0.0.0.50005- - LIBRARY HP MSL6000 Series 0507 mt1.0.0.51005- - LTO HP Ultrium 3-SCSI G24W mt2.0.0.52005- - LTO HP Ultrium 3-SCSI G24W Completed in: 0 days, 0 hours, 0 minutes, 1 seconds. -The library is defined in TSM with: tsm: SRV-SPGR-BACKUP_SERVER1q library f=d Library Name: MSL6030 Library Type: SCSI WWN: 00900D06254B8000 Serial Number: 2U2527002X AutoLabel: No Reset Drives: No Last Update by (administrator): ADMIN tsm: SRV-SPGR-BACKUP_SERVER1q drive f=d Library Name: MSL6030 Drive Name: DRIVE1 Device Type: LTO On-Line: Yes Read Formats: ULTRIUM3C,ULTRIUM3,ULTRIUM2C,ULTRIUM2,ULTRIUMC,ULTRIUM Write Formats: ULTRIUM3C,ULTRIUM3,ULTRIUM2C,ULTRIUM2 Element: 480 Drive State: EMPTY Volume Name: Allocated to: WWN: 50060B34589E Serial Number: HU105252G0 Library Name: MSL6030 Drive Name: DRIVE2 Device Type: LTO On-Line: Yes Read Formats: ULTRIUM3C,ULTRIUM3,ULTRIUM2C,ULTRIUM2,ULTRIUMC,ULTRIUM Write Formats: ULTRIUM3C,ULTRIUM3,ULTRIUM2C,ULTRIUM2 Element: 481 Drive State: EMPTY Volume Name: Allocated to: WWN: 50060B34586E Serial Number
Re: OFFSITE TAPES
Hi Jim, It sounds as if there was a problem somewhere in the process. Were there any errors reported during the restore vol process or did it complete successfully? Were there any problems on the client side? Is the restore just for some files that were accidentally deleted, did the client hard drive fail or was there another issue? (If the client drive failed the problem may be related to the client and not the volume restore). If the volume restore was successful, Tivoli automatically updates the information so that the data on the new volume can be accessed. I guess I'm saying that a little more background info is needed to give you a more specific response unless one of my questions above has helped. Jim Neal -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Lepre, James Sent: Wednesday, March 15, 2006 7:11 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] OFFSITE TAPES Hello, I restore the volume, and made the volume readw. However, I am not seeing the data that was on the other tape eligible for a restore. Infact in the client gui, I am not seeing anything to restore, it looks like it has been deleted. Is there something I am missing, like telling Tivoli this is a new tape, or committing it to the database. Thank you Jim -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Bos, Karel Sent: Tuesday, March 14, 2006 11:46 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] OFFSITE TAPES The restore vol XX command will mark volume XX as destroyed. Upd vol st=reado/readw for the volume(s) brought back will also be needed. Regards, Karel -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Bob Booth - UIUC Sent: dinsdag 14 maart 2006 17:39 To: ADSM-L@VM.MARIST.EDU Subject: Re: OFFSITE TAPES On Tue, Mar 14, 2006 at 11:35:59AM -0500, Lepre, James wrote: Hello Everyone, I need to bring back some offsite tapes for a restore. How do I check them into the library, and then force Tivoli to use them. I have a tape that broke and now I need to bring back the offsite copy, but I am not sure what how to set this up. Should I bring back every tape for that node that is offsite, any help is much appreciated. Mark the tape that is broken as 'destroyed' Run a restore volume XX preview=yes This will give you the list of tapes to return (it could be a long list) Check them into your library as 'private' volumes Run the restore volume XX That *should* do it. cheers, bob
Re: MSL6030 TSM write failure
Hi Kurt, In my experience, the errors that you are seeing are primarily caused by one of three problems: 1) The tape drive is dirty and needs to be cleaned 2) The tape cartridge is bad and needs to be destroyed 3) The Tape drive has a physical problem that needs to be fixed via replacement or maintenance. I hope one of these solutions works for you. Jim -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Kurt Beyers Sent: Tuesday, March 14, 2006 1:01 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] MSL6030 TSM write failure Hello, A quick (?) question. My setup is the following: TSM 5.3.2 server with a MSL6030 SCSI attached library (2 HP-Ultrium 3 drives). The library has been defined in TSM and the labelling of the tapes went fine. However a migrate of the diskpool towards the LTOPool fails with the following messages: ANR0984I Process 42 for MIGRATION started in the BACKGROUND at 08:45:30. ANR2110I MIGRATE STGPOOL started as process 42. ANR1000I Migration process 42 started for storage pool DISKPOOL manually, highMig=90, lowMig=0, duration=No. ANR8337I LTO volume HK3722L3 mounted in drive DRIVE1 (mt1.0.0.5). ANR1340I Scratch volume HK3722L3 is now defined in storage pool LTOPOOL. ANR0513I Process 42 opened output volume HK3722L3. ANR8302E I/O error on drive DRIVE1 (mt1.0.0.5) with volume HK3722L3 (OP=WRITE, Error Number=1117, CC=208, KEY=0B, ASC=47, ASCQ=03, SENSE=70.00.0B.00.00.00.00.10.00.00.00.00.47.03.00.00.00.00.00.00.00.00., Description=Command aborted). Refer to Appendix D in the 'Messages' manual for recommended action. ANR1411W Access mode for volume HK3722L3 now set to read-only due to write error. ANR0515I Process 42 closed volume HK3722L3. What am I missing here? The library configuration in TSM is as follows: -The TSM device driver is used and the library is detected by the tsmdlst.exe program as follows: Tivoli Storage Manager -- Device List Utility Licensed Materials - Property of IBM 5697-TSM (C) Copyright IBM Corporation 2000, 2005. All rights reserved. U.S. Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corporation. Computer Name: TSM-server OS Version: 5.2 OS Build #: 3790 TSM Device Driver: TSMScsi - Running 2 HBAs were detected. ManufacturerModel Driver VersionFirmware Description QLogic Corporation QLA2340ql2300.sys 9.0.2.11 (w32 IP) 3.03.12 QLogic QLA2340 Fibre Channel Adapter QLogic Corporation QLA2340ql2300.sys 9.0.2.11 (w32 IP) 0.00.00 QLogic QLA2340 Fibre Channel Adapter TSM Name ID LUN Bus Port SSN WWN TSM Type Device Identifier lb0.0.0.50005- - LIBRARY HP MSL6000 Series 0507 mt1.0.0.51005- - LTO HP Ultrium 3-SCSI G24W mt2.0.0.52005- - LTO HP Ultrium 3-SCSI G24W Completed in: 0 days, 0 hours, 0 minutes, 1 seconds. -The library is defined in TSM with: tsm: SRV-SPGR-BACKUP_SERVER1q library f=d Library Name: MSL6030 Library Type: SCSI WWN: 00900D06254B8000 Serial Number: 2U2527002X AutoLabel: No Reset Drives: No Last Update by (administrator): ADMIN tsm: SRV-SPGR-BACKUP_SERVER1q drive f=d Library Name: MSL6030 Drive Name: DRIVE1 Device Type: LTO On-Line: Yes Read Formats: ULTRIUM3C,ULTRIUM3,ULTRIUM2C,ULTRIUM2,ULTRIUMC,ULTRIUM Write Formats: ULTRIUM3C,ULTRIUM3,ULTRIUM2C,ULTRIUM2 Element: 480 Drive State: EMPTY Volume Name: Allocated to: WWN: 50060B34589E Serial Number: HU105252G0 Library Name: MSL6030 Drive Name: DRIVE2 Device Type: LTO On-Line: Yes Read Formats: ULTRIUM3C,ULTRIUM3,ULTRIUM2C,ULTRIUM2,ULTRIUMC,ULTRIUM Write Formats: ULTRIUM3C,ULTRIUM3,ULTRIUM2C,ULTRIUM2 Element: 481 Drive State: EMPTY Volume Name: Allocated to: WWN: 50060B34586E Serial Number: HU105252FH tsm: SRV-SPGR-BACKUP_SERVER1q path f=d Source Name: SRV-SPGR-BACKUP_SERVER1 Source Type: SERVER Destination Name: MSL6030 Destination Type: LIBRARY Library: Node Name: Device: LB0.0.0.5 Source Name: SRV-SPGR-BACKUP_SERVER1 Source Type: SERVER Destination Name: DRIVE1 Destination Type: DRIVE Library: MSL6030 Node Name: Device: mt1.0.0.5 Source Name: SRV-SPGR-BACKUP_SERVER1 Source Type: SERVER Destination Name: DRIVE2 Destination Type: DRIVE Library: MSL6030 Node Name: Device: mt2.0.0.5 thanks, Kurt
Re: Question on recommended excludes for TSM-Mac Clients with MacOS 10.4 ?
Hi Rainer, It really depends on a number of factors such as whether or not you are backing up customer installed third party applications, whether or not e-mail is kept on the server or the local system, and how standardized your environment is, to name just a few. If you have a pretty standardized environment then I would strongly recommend excluding everything, then including only the information in the /Users directory. This will preserve the majority of the data that applies only to your customer. After that you may want to consider including only those other directories that contain absolutely essential customer data such as Eudora e-mail folders and the like that live outside of the /Users directory. This should cut down the number of entries considerably. This solution also assumes that your systems have a standard build that includes all necessary software so that if a system completely crashes only the customer specific data will need to be restored. I hope this helps. Jim -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Rainer Wolf Sent: Thursday, March 09, 2006 5:38 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Question on recommended excludes for TSM-Mac Clients with MacOS 10.4 ? Hi TSMers, we have tsm-server/solaris 5.3.2.1 and Macintosh tsm-Klients at 5.3.2.1. since starting with macOS 10.4 those Macintosh - Klients are coming into the tsm-server with quite a lot of tsm-db entries. Doing just normal incremental backups those TSM-Clients are appearing with up to 100.000 Directories and in the range of up to 500.000 Files in tsm-db. No Server - just acting as Labtops. The default-excludes that came with the tsm-Klient Installation are active but don't seem to be very efficient. My question is: Has anyone some tipps how to handle that - are we doing something wrong ? Someone found extended reasonable excludes ? Is there another way recommended for doing backup ? Is it reasonable to propagate something else, for example to backup just and only one Directory like /backup ? We currently don't have very much of those mac-os-10.4 Klients - so it's not a real problem for us - but I wonder how to solve the Backup of lets say 200 MacLabtops ... a new tsm-db ? Regards - and thanks in advance ! Rainer -- Rainer Wolf eMail: [EMAIL PROTECTED] kiz - Abt. Infrastruktur Tel/Fax: ++49 731 50-22482/22471 Universitaet Ulm wwweb:http://kiz.uni-ulm.de
