Domino TDP leaves old databases, second try
I need your help! I posted the following, but Michael was the only one with ideas. But unfortunately that was no solution to my problem. So, has anybody an idea? Here `s the full story: Hi *sm`ers the amount of data pertaining our Lotus Domino Servers is enlarging enormous. The domino guys tell me that they can restore very old databases although the domino db`s are deleted a long time ago. When we try to restore such an old database which on the domino server has been deleted a long time ago, we still see the last version of this db. How can this happen ? Since we backup the transaction logs every hour there is a second problem. The transaction log backups are retained - no deletion happened ! Why is no Log inactivated ? We use TSM 3.7.3 on server side, and tsm 4.1.16 with TDP for Domino 1.1.2 on Client side. Our translog backup script looks like this: set domlogdir=c:\ssw\tivoli\tsm\log\online_nt_dom_tlog.log domdsmc arch /logfile=%domlogdir% domdsmc inactivate /logfile=%domlogdir% The log output is: Total Domino transaction log files ready for archive: 4 Total Domino transaction log files archived: 4 Throughput rate: 5,193.11 Kb/Sec Total bytes transferred: 268,439,552 Elapsed processing time: 50.48 Secs Tivoli Storage Manager Tivoli Data Protection for Lotus Domino - Version 1, Release 1, Level 2.0 (C) Copyright IBM Corporation 1999, 2001. All rights reserved. License file exists and contains valid license data. ACD5221I The C:\ssw\Tivoli\TSM\domino\domdsm.log log file has been pruned successfully. Number of Logs Inactivated: 0 The weekly online backup script is like that: set logdir=c:\ssw\tivoli\tsm\log\domdsm.log domdsmc selective * /subdir=yes /logfile=%domlogdir% %logdir% domdsmc inactivate /logfile=%domlogdir% %logdir% and the output reads like this: Total Domino databases inspected: 4,433 Total Domino databases backed up: 4,433 Total Domino databases excluded: 0 Throughput rate: 4,820.92 Kb/Sec Total bytes transferred: 99,557,318,730 Elapsed processing time: 20,167.09 Secs Tivoli Storage Manager Tivoli Data Protection for Lotus Domino - Version 1, Release 1, Level 2.0 (C) Copyright IBM Corporation 1999, 2001. All rights reserved. License file exists and contains valid license data. ACD5221I The c:\ssw\tivoli\tsm\log\domdsm.log log file has been pruned successfully. Number of Logs Inactivated: 0 Thank you ! ADSM: Dist Stor Manager [EMAIL PROTECTED] schrieb am 09.07.2002 15:50:45: Hi Holger, with TDP for Lotus Domino every database is treated as if it was one filespace. On your TSM Server you can see this using q files nodename. Like with the ba-client TSM updates the filespace when you perform an incremental backup and otherwise leaves the filespace as it is. So when you stop backing up a certain filespace (=domino database), this filespaces active files (documents) will stay unchanged in TSM forever. When you want to discontinue backing up a database and you don't want to keep this db in TSM, just delete it using delete files nodename filespacename in the admin interface (dsmadmc). Good luck, regards, Michael -- Michael Bartl, Dipl. Inform. (FH) mailto:[EMAIL PROTECTED] Backup Services, IT Ops Germany/Austria Tel: +49-89-92699-806 Cable Wireless Deutschland GmbH. Fax: +49-89-92699-302 Landsberger Str. 155, D-80687 Muenchen http://www.cw.com/de - Hi Michael, when we do a 'q files nodename' the result looks like This: Node Name Filespace Platform Filespace CapacityPct Name Type(MB) Util -- --- - - X_LN\\Y\d$WinNT NTFS 138,927.73.60 X_LN\\Y\c$WinNT NTFS 4,044.1 55.1 X_LNZ4.DOMLOGSWinNT API:DominoData 0.0 0.0 X_LNZ4.DOMDBS WinNT API:DominoData0.0 0.0 So it looks like all databases together are treated as one filespace. Is this a bug, misconfiguration or is it normal? Greetings Gisbert Schneider -- Holger Bitterlich Stadtsparkasse Köln Organisation und Datenverarbeitung Telefon: (0221) 226 - 54 18 Fax: (0221) 226- 51 00 mailto:[EMAIL PROTECTED] http://www.sk-koeln.de Da E-Mails leicht unter fremdem Namen erstellt oder
Expire data on a server that doesnt exist any longer.
Hello ! If I have backup of a server which is out of production. What can I do and how, if I want to expire all extra backup copies (versions data exist) except the last backup (versions data deleted)? I can change mgmtclass but I still have to do a backup to rebind my files. If I use a client and log on with 'dsmc -virtualnodename=xyz' and exclude E:\...\* , what happens then? Will it expire xyz´s E:\ files or the client node E:\ files? tia Henrik --- The information contained in this message may be CONFIDENTIAL and is intended for the addressee only. Any unauthorised use, dissemination of the information or copying of this message is prohibited. If you are not the addressee, please notify the sender immediately by return e-mail and delete this message. Thank you.
Re: AIX Question!
Hi. Not quite a tsm question, but try: ls | xargs rm though, it might take a while Ran. -Original Message- From: Al'shaebani, Bassam [mailto:Bassam.Al'[EMAIL PROTECTED]] Sent: Wednesday, July 10, 2002 2:26 PM To: [EMAIL PROTECTED] Subject: AIX Question! Hello All, I'm came across an issue yesteday, does anyone know a way around deleting a large number of files without getting the 'parameter too long' message. i.e. I was trying to delete all the file that began with program*. There were too many files, so I had to actually cut my search down, to something like program01* and so forth, to avoid the error message. Thanks.. Regards, Bassam
Re: restore asking for offsite copy instead of primary
Hi, I had a user trying to restore a database and found data unavailable to server. The restore was asking for a volume that was offsite. Why wouldn't it ask for the primary copy and how do I know what primary volume the data is on? You can use an SQL statement, like select distinct volume_name,stgpool_name from volumeusage - where node_name='YOUR_CLIENT_NODE_NAME' - order by volume_name Maybe the volume has been disabled or changed to readonly due to a write or read error. Dirk
Re: restore asking for offsite copy instead of primary
Dirk, node_name is not recognized. ANR2940E The reference 'NODE' is an unknown SQL column name. | .V. _name from volumeusage where node-name=ABC order by volume_name ANS8001I Return code 3. -Original Message- From: Dirk Kastens [mailto:[EMAIL PROTECTED]] Sent: Thursday, July 11, 2002 5:01 PM To: [EMAIL PROTECTED] Subject: Re: restore asking for offsite copy instead of primary Hi, I had a user trying to restore a database and found data unavailable to server. The restore was asking for a volume that was offsite. Why wouldn't it ask for the primary copy and how do I know what primary volume the data is on? You can use an SQL statement, like select distinct volume_name,stgpool_name from volumeusage - where node_name='YOUR_CLIENT_NODE_NAME' - order by volume_name Maybe the volume has been disabled or changed to readonly due to a write or read error. Dirk CAUTION - This message may contain privileged and confidential information intended only for the use of the addressee named above. If you are not the intended recipient of this message you are hereby notified that any use, dissemination, distribution or reproduction of this message is prohibited. If you have received this message in error please notify AMCOR immediately. Any views expressed in this message are those of the individual sender and may not necessarily reflect the views of AMCOR.
Re: solaris experts plz help
Hello Gerald, you have to change your conf files like this: lb.conf if the scsi target and luns for your libraries are OK, you do not have to change this file. op.conf replace all lb with op (in this file you define only optical drives, not changer). For each optical drive create one stanza with correct target and lun of each drive (so you will have 10 stanzas in your conf file). Example Name=op class=scsi Target=X lun=Y; X is SCSI target ID of optical drive and Y is LUN of that drive mt.conf here replace lb with mt (in this file you define only tape drives, not changer). For each tape drive create one stanza with correct target and lun of each drive (so you will have 4 stanzas in your conf file). Example Name=mt class=scsi Target=X lun=Y; X is SCSI target ID of tape drive and Y is LUN of that drive Ing. Jozef Zatko Login a.s. Dlha 2, Stupava tel.: (421) (2) 60252618 Gerald Wichmann [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] 11.07.2002 01:14 Please respond to ADSM: Dist Stor Manager To: [EMAIL PROTECTED] cc: Subject:solaris experts plz help Below is the output of my server's probe-scsi-all.. I have 2 ATL M1500 LTO libraries with 2 drives each, and one HP 1200ex optical library with 10 optical drives. I need to populate the mt.conf, lb.conf, and op.conf files accordingly but what I've done doesn't seem to be working. When doing the add_drv command, it loads the device driver but then fails to attach. When I do add_drv for op it works but I only get a 0op and 1op so I'm not sure why it didn't pick up 10 drives. So my first question is, what do I put in the various conf files? I'm not as familiar with solaris so could use some help. Currently my files look like this: Lb.conf Name=lb class=scsi Target=5 lun=0; Name=lb class=scsi Target=4 lun=0; Name=lb class=scsi Target=4 lun=1; Op.conf Name=lb class=scsi Target=4 lun=0; Name=lb class=scsi Target=4 lun=1; Mt.conf Name=lb class=scsi Target=5 lun=0; Name=lb class=scsi Target=4 lun=0; Probe-scsi-all: /pci@1f,2000/pci@1/scsi@5 Target 0 Unit 0 Removable Medium changerM4 DATA MagFile 2.10 Target 1 Unit 0 Removable Tape HP Ultrium 1-SCSI E15V Target 2 Unit 0 Removable Tape HP Ultrium 1-SCSI E15V /pci@1f,2000/pci@1/scsi@4 Target 0 Unit 0 Removable Medium changerM4 DATA MagFile 2.10 Target 1 Unit 0 Removable Tape HP Ultrium 1-SCSI E15V Target 2 Unit 0 Removable Tape HP Ultrium 1-SCSI E15V /pci@1f,4000/scsi@4,1 Target 2 Unit 0 Removable Device type 7 HP C1113J 1.10 Target 3 Unit 0 Removable Device type 7 HP C1113J 1.10 Target 4 Unit 0 Removable Device type 7 HP C1113J 1.10 Target 5 Unit 0 Removable Device type 7 HP C1113J 1.10 Target 6 Unit 0 Removable Device type 8 HP C1107J 1.40 /pci@1f,4000/scsi@4 Target 1 Unit 0 Removable Device type 7 HP C1113J 1.10 Target 2 Unit 0 Removable Device type 7 HP C1113J 1.10 Target 3 Unit 0 Removable Device type 7 HP C1113J 1.10 Target 4 Unit 0 Removable Device type 7 HP C1113J 1.10 Target 5 Unit 0 Removable Device type 7 HP C1113J 1.10 Target 6 Unit 0 Removable Device type 7 HP C1113J 1.10 Gerald Wichmann Senior Systems Development Engineer Zantaz, Inc. 925.598.3099 (w)
TDP Sql error
Hi I got today trying to run a a backup from a TDP MsSql 2.2.0 gui: ACO5422E Received the following from the MS SQL Server Try to find explanation without any success .. I success from the gui to do a restore. Please help !! Regards Robert Ouzen
Re: restore asking for offsite copy instead of primary
node_name is not recognized. ANR2940E The reference 'NODE' is an unknown SQL column name. | .V. _name from volumeusage where node-name=ABC order by volume_name Seems, that you typed node-name instead of node_name. Dirk
Re: Domino TDP leaves old databases, second try
Hi Holger what is your policy settings for data from Domino server (copy group setting from management class under which is Domino data backuped)? Ing. Jozef Zatko Login a.s. Dlha 2, Stupava tel.: (421) (2) 60252618 Holger Bitterlich [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] 11.07.2002 09:15 Please respond to ADSM: Dist Stor Manager To: [EMAIL PROTECTED] cc: Subject:Domino TDP leaves old databases, second try I need your help! I posted the following, but Michael was the only one with ideas. But unfortunately that was no solution to my problem. So, has anybody an idea? Here `s the full story: Hi *sm`ers the amount of data pertaining our Lotus Domino Servers is enlarging enormous. The domino guys tell me that they can restore very old databases although the domino db`s are deleted a long time ago. When we try to restore such an old database which on the domino server has been deleted a long time ago, we still see the last version of this db. How can this happen ? Since we backup the transaction logs every hour there is a second problem. The transaction log backups are retained - no deletion happened ! Why is no Log inactivated ? We use TSM 3.7.3 on server side, and tsm 4.1.16 with TDP for Domino 1.1.2 on Client side. Our translog backup script looks like this: set domlogdir=c:\ssw\tivoli\tsm\log\online_nt_dom_tlog.log domdsmc arch /logfile=%domlogdir% domdsmc inactivate /logfile=%domlogdir% The log output is: Total Domino transaction log files ready for archive: 4 Total Domino transaction log files archived: 4 Throughput rate: 5,193.11 Kb/Sec Total bytes transferred: 268,439,552 Elapsed processing time: 50.48 Secs Tivoli Storage Manager Tivoli Data Protection for Lotus Domino - Version 1, Release 1, Level 2.0 (C) Copyright IBM Corporation 1999, 2001. All rights reserved. License file exists and contains valid license data. ACD5221I The C:\ssw\Tivoli\TSM\domino\domdsm.log log file has been pruned successfully. Number of Logs Inactivated: 0 The weekly online backup script is like that: set logdir=c:\ssw\tivoli\tsm\log\domdsm.log domdsmc selective * /subdir=yes /logfile=%domlogdir% %logdir% domdsmc inactivate /logfile=%domlogdir% %logdir% and the output reads like this: Total Domino databases inspected: 4,433 Total Domino databases backed up: 4,433 Total Domino databases excluded: 0 Throughput rate: 4,820.92 Kb/Sec Total bytes transferred: 99,557,318,730 Elapsed processing time: 20,167.09 Secs Tivoli Storage Manager Tivoli Data Protection for Lotus Domino - Version 1, Release 1, Level 2.0 (C) Copyright IBM Corporation 1999, 2001. All rights reserved. License file exists and contains valid license data. ACD5221I The c:\ssw\tivoli\tsm\log\domdsm.log log file has been pruned successfully. Number of Logs Inactivated: 0 Thank you ! ADSM: Dist Stor Manager [EMAIL PROTECTED] schrieb am 09.07.2002 15:50:45: Hi Holger, with TDP for Lotus Domino every database is treated as if it was one filespace. On your TSM Server you can see this using q files nodename. Like with the ba-client TSM updates the filespace when you perform an incremental backup and otherwise leaves the filespace as it is. So when you stop backing up a certain filespace (=domino database), this filespaces active files (documents) will stay unchanged in TSM forever. When you want to discontinue backing up a database and you don't want to keep this db in TSM, just delete it using delete files nodename filespacename in the admin interface (dsmadmc). Good luck, regards, Michael -- Michael Bartl, Dipl. Inform. (FH) mailto:[EMAIL PROTECTED] Backup Services, IT Ops Germany/Austria Tel: +49-89-92699-806 Cable Wireless Deutschland GmbH. Fax: +49-89-92699-302 Landsberger Str. 155, D-80687 Muenchen http://www.cw.com/de - Hi Michael, when we do a 'q files nodename' the result looks like This: Node Name Filespace Platform Filespace CapacityPct Name Type(MB) Util -- --- - - X_LN\\Y\d$WinNT NTFS 138,927.73.60 X_LN\\Y\c$
Re: q sched
For the admin schedules try: select schedule_name,active from admin_schedules regards, Alexander Hi , IS there a single command I can use to query the schedule and find the schedules that are not active. I did q sched type=admin f=d but I just want to see the name of the schedule and active?=yes/ no is it possible ? I'm sure it is and I believe some SQL statement can do it - wondering if anyone is having handy statement...? with regards, CAUTION - This message may contain privileged and confidential information intended only for the use of the addressee named above. If you are not the intended recipient of this message you are hereby notified that any use, dissemination, distribution or reproduction of this message is prohibited. If you have received this message in error please notify AMCOR immediately. Any views expressed in this message are those of the individual sender and may not necessarily reflect the views of AMCOR. --- Alexander Verkooijen([EMAIL PROTECTED]) Senior Systems Programmer SARA High Performance Computing
Re: optimising tcpwindowsize and tcpbuffsizes
Hi, here is an excerpt of the knowledge base article Description of Windows 2000 TCP Features (Q224829). As I understand, the maximum value IS 64 UNLESS the RFC1323 option is used. I'm not a network expert, but why should I set the TCPWINDOWSIZE option to 63? The receive window size is determined in the following manner: 1. The first connection request sent to a remote host advertises a receive window size of 16K (16,384 bytes). 2. When the connection is established, the receive window size is rounded up to an even increment of the MSS. 3. The window size is adjusted to 4 times the MSS, to a maximum size of 64K, unless the window scaling option (RFC 1323) is used. Dirk
Re: Backup a W2K Domain Controller?
Thank you Jim. I will add this to the followong reasons I just learned a few moments ago: Botched Schema update Accidental deletion of OU (or any other object) Database corruption System State Accidentally deletion of a DNS zone Some DC's are also File/Print servers, DHCP, etc. Some of these scenarios would require an authoritative restore or a complete rebuild of the Active Directory, as some changes are replicated immediately. ...and as you mentioned Jim, time to synch. verses restore. -Original Message- From: Jim Smith [mailto:[EMAIL PROTECTED]] Sent: Wednesday, July 10, 2002 5:57 PM To: [EMAIL PROTECTED] Subject: Re: Backup a W2K Domain Controller? Jon, I'm sure there are a number of pros and cons and I'll let others chime in ... one advantage of having a backup of the Active Directory on a given DC is time to recovery. While you can bring an active directory back by simply installing it and letting it synchronize to catch-up to the rest of the organization, this synchronization can take quite a long time depending on the size of the directory. In this case, a backup product can give you a point-in-time copy of the active directory such that the synchronization process only has to catch-up from a time in the recent past. The time to restore from a tape can be much quicker then doing a synchronization from ground-zero. - Jim J.P. (Jim) Smith TSM Client Development Here's an interesting question: why would you want to backup a DC, especially where you have a DC (W2K) or two in every remote site of the WAN? Why/what would you ever restore that you wouldn't get from the other domain controllers if one or even a few are down? I ask this because my theory is when in doubt, backup it up. At a couple hundred dollars a license it seems a reasonable assurance policy (depending on the budget, of course). Another theory applies here as well, backup everything, exclude only as needed, even if that client options set gets pretty big. Jon R. Adams IT IPS BST Infrastructure Premera Blue Cross Mountlake Terrace, WA 425-670-5770 [EMAIL PROTECTED]
Antwort: Re: Domino TDP leaves old databases, second try
Hi Josef, this is the policy setting: Policy Domain Name NT_NOTES Policy Set Name ACTIVE Mgmt Class Name MC_NT_NOTES Copy Group Name STANDARD Versions Data Exists 5 Versions Data Deleted 1 Retain Extra Versions30 Retain Only Version 60 Copy Mode MODIFIED Copy Serialization SHRDYNAMIC Copy Frequency 0 In my opionion the last backuped file should go away at the 60th day after beeing deleted at Domino Server. But it does not ,... . Have you got an idea ? Thank you ! -- Holger Bitterlich Stadtsparkasse Köln Organisation und Datenverarbeitung Telefon: (0221) 226 - 54 18 Fax: (0221) 226- 51 00 mailto:[EMAIL PROTECTED] http://www.sk-koeln.de ADSM: Dist Stor Manager [EMAIL PROTECTED] schrieb am 11.07.2002 11:53:59: Hi Holger what is your policy settings for data from Domino server (copy group setting from management class under which is Domino data backuped)? Ing. Jozef Zatko Login a.s. Dlha 2, Stupava tel.: (421) (2) 60252618 Holger Bitterlich [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] 11.07.2002 09:15 Please respond to ADSM: Dist Stor Manager To: [EMAIL PROTECTED] cc: Subject:Domino TDP leaves old databases, second try I need your help! I posted the following, but Michael was the only one with ideas. But unfortunately that was no solution to my problem. So, has anybody an idea? Here `s the full story: Hi *sm`ers the amount of data pertaining our Lotus Domino Servers is enlarging enormous. The domino guys tell me that they can restore very old databases although the domino db`s are deleted a long time ago. When we try to restore such an old database which on the domino server has been deleted a long time ago, we still see the last version of this db. How can this happen ? Since we backup the transaction logs every hour there is a second problem. The transaction log backups are retained - no deletion happened ! Why is no Log inactivated ? We use TSM 3.7.3 on server side, and tsm 4.1.16 with TDP for Domino 1.1.2 on Client side. Our translog backup script looks like this: set domlogdir=c:\ssw\tivoli\tsm\log\online_nt_dom_tlog.log domdsmc arch /logfile=%domlogdir% domdsmc inactivate /logfile=%domlogdir% The log output is: Total Domino transaction log files ready for archive: 4 Total Domino transaction log files archived: 4 Throughput rate: 5,193.11 Kb/Sec Total bytes transferred: 268,439,552 Elapsed processing time: 50.48 Secs Tivoli Storage Manager Tivoli Data Protection for Lotus Domino - Version 1, Release 1, Level 2.0 (C) Copyright IBM Corporation 1999, 2001. All rights reserved. License file exists and contains valid license data. ACD5221I The C:\ssw\Tivoli\TSM\domino\domdsm.log log file has been pruned successfully. Number of Logs Inactivated: 0 The weekly online backup script is like that: set logdir=c:\ssw\tivoli\tsm\log\domdsm.log domdsmc selective * /subdir=yes /logfile=%domlogdir% %logdir% domdsmc inactivate /logfile=%domlogdir% %logdir% and the output reads like this: Total Domino databases inspected: 4,433 Total Domino databases backed up: 4,433 Total Domino databases excluded: 0 Throughput rate: 4,820.92 Kb/Sec Total bytes transferred: 99,557,318,730 Elapsed processing time: 20,167.09 Secs Tivoli Storage Manager Tivoli Data Protection for Lotus Domino - Version 1, Release 1, Level 2.0 (C) Copyright IBM Corporation 1999, 2001. All rights reserved. License file exists and contains valid license data. ACD5221I The c:\ssw\tivoli\tsm\log\domdsm.log log file has been pruned successfully. Number of Logs Inactivated: 0 Thank you ! ADSM: Dist Stor Manager [EMAIL PROTECTED] schrieb am 09.07.2002 15:50:45: Hi Holger, with TDP for Lotus Domino every database is treated as if it was one filespace. On your TSM Server you can see this using q files nodename. Like with the ba-client TSM updates the filespace when you perform an incremental backup and otherwise leaves the filespace as it is. So when you stop backing up a certain filespace (=domino database), this filespaces active files (documents) will stay unchanged in TSM forever. When you want to discontinue backing up a database and you don't want to keep this db in TSM, just delete it using delete files nodename filespacename in the admin interface (dsmadmc). Good luck, regards, Michael -- Michael Bartl, Dipl. Inform. (FH) mailto:[EMAIL PROTECTED] Backup Services, IT Ops Germany/Austria Tel: +49-89-92699-806
Backing Up Windows XP, a multi-user system...
Perhaps, I wasn't clear enough in a previous message. My organization is planning a rollout of Windows XP and would like to take advantage of its multi-user capabilities. (do I hear laughter??). Attached are some screen dumps of the BA GUI and the prospective file layout should be apparent. In a perfect world, the data directories, (Data, Documents and Settings), will be backed up incrementally each day using the central scheduling service. Additionally each user should be able to backup and restore his files and his files only. Can this be achieved and, if so, how? From the feedback I've already received, it seems that from a practical viewpoint, this scheme might be unrealistic to implement - (multiple dsm.opts, use of nodename parameter, licensing issues, etc.). Other implementations could be acceptable if these basic requirements are respected: (1) Data is backed up by somebody/anybody daily (2) Individual useres can back up and restore their own data and, perhaps, other users'data as well. My current situation in the lab is as such: The administrator can backup and restore any file he so desires. John Smith, can run dsm.exe but cannot see, let alone, backup any subdirectories under: Distributed File System Local Network Removable John Smith can, however, backup entries under System Object such COM+ DB, Event Log, Registry, System Files and WMI. Any suggestions are welcome. Thank you. __ Post your ad for free now! http://personals.yahoo.ca
dsm.opt / dsmerror.log / incl/excl oddity
Envirionment A: Client OS: NT 4 Client Version: Version 4, Release 2, Level 1.20 Server: Storage Management Server for MVS - Version 4, Release 2, Level 1.11 Environment B: Client OS: NT 4 Client Version: Version 4, Release 2, Level 1.20 Server: Storage Management Server for MVS - Version 4, Release 1, Level 3.0 These clients are cookie cutter builds Starting from the OS down to the dsm.opt (with the exception of the TSM server they point to). Question: Why is my dsmerror.log filling up with the following messages in environmet B and not A when the directory structure and dsm.opt are identical for both servers? ANS1115W File '\\l06101s001\e$\Services\BUEXECV7\NT\reports\saved\empty' excluded by Include/Exclude list Any help would be appreciated. Regards, Joe
Re: q sched
Hi try this select schedule_name,active from admin_schedules bye raghu
Re: optimising tcpwindowsize and tcpbuffsizes
We have actually seen better throughput here by setting ours to 128. This has doubled and in some tests tripled our throughput. Tony Garrison I/T Sr. Systems Programmer USAA 210-913-9836 -Original Message- From: Gianluca Mariani1 [mailto:[EMAIL PROTECTED]] Sent: Wednesday, July 10, 2002 11:42 AM To: [EMAIL PROTECTED] Subject: Re: optimising tcpwindowsize and tcpbuffsizes I refer to our position as on the perf site. that is what I consider official as those are the recommendations of the perf team based on real tests. as I wrote in the other post. I'll quote again: TCP/IP Window Size Use the Tivoli Storage Manager option TcpWindowSize 63 on both the Tivoli Storage Manager Windows NT client and Tivoli Storage Manager Windows NT server. Since Windows 2000 supports TCP window scaling, it may be beneficial to use a larger TCP window size for Windows 2000 systems that are communicating exclusively with other Windows 2000 or UNIX systems. Why? Because the maximum tcpwindowsize WITHOUT RFC 1323 (scaling windowsize support) is 65535 bytes, that's 64KB -1. TSM option tcpwindowsize 64 means 64*1024 or 65536 - one byte too big if the client doesn't support RFC 1323. win2000 does support rfc1323, but you have to set a registry entry to take advantage of it. the tcp windowsize sets the SO_RCVBUF option on the socket connection, which is the size of the total data buffered on the connection. MS docs say this size needs to be a multiple of the MTU for best results, but this is basically garbage. For standard Ethernet MTU of 1500 bytes, the difference in the number of packets that can be buffered between 63KB and 64KB is a nit. There is a difference between saying 64KB and meaning 65535 bytes. this does not mean that you can't put the parameter to 64 and actually see an improvement. I gave a general answer. I would be more careful with absolute assertions in this field. I'm somewhat disturbed that a certified TSM consultant is not aware of this. Cordiali saluti Gianluca Mariani Tivoli TSM Global Response Team, Roma Via Sciangai 53, Roma phones : +39(0)659664598 +393351270554 (mobile) [EMAIL PROTECTED] Mark Stapleton stapleto@BERBEE.To: [EMAIL PROTECTED] COM cc: Sent by: ADSM: Subject: Re: optimising tcpwindowsize and tcpbuffsizes Dist Stor Manager [EMAIL PROTECTED] .EDU 10/07/2002 15:35 Please respond to ADSM: Dist Stor Manager From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of Gianluca Mariani1 TCPWINDOWSIZE should be set to 63 on Win2k. Cordiali saluti Gianluca Mariani Tivoli TSM Global Response Team, Roma You need to check your documentation. Windows 2K machines should have TCPWINDOWSIZE set to 64 (assuming 10 or 100Mb Ethernet). I'm somewhat disturbed that a member of the Tivoli TSM Global Response Team isn't aware of this. -- Mark Stapleton ([EMAIL PROTECTED]) Certified TSM consultant Certified AIX system engineer MCSE
how to find
Is there a way to find quickly which storagepool each client belongs to .? The 'query occupancy' command will provide information on which storage pools a client is currently using. If you use migration to shift backup files from an initial destination pool to a long term pool, the query command won't necessarily report the initial destination pool. The query command won't warn of cases where a client could start using a new pool any time because of changes in the include/exclude statements or because of new files that match an include that did not apply to any previously existing files.
Re: Delayed Schedule Start
Only this schedule has a priority of 'one', it is for testing the backup of one specific filesystem. There were no other events scheduled to run at this time, however, since the backup of this filesystem takes 14 hours (4.2 million objects/ 108 Gb) I assigned it higher priority over events occurring later in the day. Randomization is probably the answer. I did not realize that randomization would be used when no other sessions/processes were active on the TSM Server and/or client. Thanks, Jon Martin -Original Message- From: Schaub Joachim Paul ABX-PROD-ZH [mailto:[EMAIL PROTECTED]] Sent: Thursday, July 11, 2002 6:44 AM To: [EMAIL PROTECTED] Subject: AW: Delayed Schedule Start your sched has priority 1, does all the other scheds have the same priority? If yes, why? greets joachim -Ursprüngliche Nachricht- Von: Jon Adams [mailto:[EMAIL PROTECTED]] Gesendet: Mittwoch, 10. Juli 2002 17:27 An: [EMAIL PROTECTED] Betreff: Re: Delayed Schedule Start Perhaps a combination of the randomization, the backup window or the available sessions at the time of backup? If there are no sessions available, the backup will start anytime a session is available within that schedule window. Jon Adams Systems Engineer IT IPS, Premera Blue Cross -Original Message- From: Etienne Brodeur [mailto:[EMAIL PROTECTED]] Sent: Tuesday, July 09, 2002 11:49 AM To: [EMAIL PROTECTED] Subject: Re: Delayed Schedule Start What's your Schedule Randomization percentage and what is the backup window for this schedule? If I recall correctly randomization is for every schedule even if it only runs on one node. And the ramdomization starts from the moment the nodes connect to the server not from the start of the window. backup window is 4 hours. schedule starts at 1 AM randomization is set to 25% node connects at 230 AM schedules will start between 230 and 330 AM. Could this be it? Etienne Brodeur Martin, Jon R. [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] 07/09/2002 01:33 PM Please respond to ADSM: Dist Stor Manager To: [EMAIL PROTECTED] cc: Subject:Delayed Schedule Start The below schedule was scheduled for 1 PM. The client scheduler is polling and at 1:05 PM it updated, and said the schedule would start in 33 minutes. What causes a schedule to execute a time later than scheduled? I am aware of staggered starts for scheduled events, but this is the only thing scheduled at this time and nothing else is running on the server. Any ideas? Thanks, Jon Martin Policy Domain Name: SOLARIS Schedule Name: REBUILD_MR Description: Daily backup for Solaris Clients Action: Incremental Options: Objects: /rebuild_mr/ATX1/ Priority: 1 Start Date/Time: 05/16/01 13:00:00 Duration: 12 Hour(s) Period: 1 Day(s) Day of Week: Tuesday Expiration: Last Update by (administrator): ADMIN Last Update Date/Time: 07/09/02 10:57:07 Managing profile: 07/09/02 13:05:12 07/09/02 13:05:12 Schedule Name: REBUILD_MR 07/09/02 13:05:12 Action:Incremental 07/09/02 13:05:12 Objects: /rebuild_mr/ATX1/ 07/09/02 13:05:12 Options: 07/09/02 13:05:12 Server Window Start: 13:00:00 on 07/09/02 07/09/02 13:05:12 07/09/02 13:05:12 Command will be executed in 33 minutes. 07/09/02 13:05:12
Re: TSM DBBackup
Sorry I didn't make that clear, it's any directory you want. On a Windows TSM server, I've even sent the DB backup to a network shared disk that is physically on another machine (that involves some Windows account/permissions manipulation though). -Original Message- From: Bill Wheeler [mailto:[EMAIL PROTECTED]] Sent: Wednesday, July 10, 2002 4:50 PM To: [EMAIL PROTECTED] Subject: Re: TSM DBBackup Can you specify any directory that you want to or is it specific to the /var/adsmpool directory? Bill Wheeler PDM Administrator -Original Message- From: Prather, Wanda [mailto:[EMAIL PROTECTED]] Sent: Wednesday, July 10, 2002 4:43 PM To: [EMAIL PROTECTED] Subject: Re: TSM DBBackup You have to start out by creating a DEVCLASS with devtype=file. That specifies the directory you want the file sent to. Here's an example: DEFINE DEVCLASS dbbkuptodisk DEVTYPE=FILE FORMAT=DRIVE MAXCAPACITY=204800K MOUNTLIMIT=1 DIRECTORY=/var/adsmpool SHARED=NO dbbkuptodisk is a made up name, use anything you like. MAXCAPACITY should be large enough to hold one DBBACKUP (although the DB backup will work OK if TSM has to break it into pieces). Then when you do your DB backup, it should look like this: backup db type=full devclass=dbbkuptodisk scratch=yes TSM will create, on the fly, a new file in the /var/adsmpool directory to contain the db backup. If the db backup is larger than maxcapacity, TSM will create a more file and the db backup will span the two files. You can find out what TSM calls the file by looking in the activity log or in the volumehistory file. (Or just looking in the directory) The older db backups go away when you run DELETE VOLHISTORY (same as if your DB backups were going to tape). -Original Message- From: Bill Wheeler [mailto:[EMAIL PROTECTED]] Sent: Wednesday, July 10, 2002 4:09 PM To: [EMAIL PROTECTED] Subject: Re: TSM DBBackup How do you define where the flat file goes while the DBBackup is running? Bill Wheeler PDM Administrator -Original Message- From: Prather, Wanda [mailto:[EMAIL PROTECTED]] Sent: Wednesday, July 10, 2002 3:27 PM To: [EMAIL PROTECTED] Subject: Re: TSM DBBackup Yes, TSM DB restore is the same no matter if you are restoring from disk or tape. If you rely on TSM to restore the DB itself, it looks in the volhistory file to find the last good DB backup. It will see the pointer in volhistory to the disk file and use it. (I recommend you put a copy of devconfig and volhistory in your rootvg, also.) If you specify yourself which volume TSM uses for the DB restore, you just give it the name of the file. It all works. -Original Message- From: Bill Wheeler [mailto:[EMAIL PROTECTED]] Sent: Wednesday, July 10, 2002 3:14 PM To: [EMAIL PROTECTED] Subject: Re: TSM DBBackup Here is the scenario that I was planning if I can get the DBBackup to go to a flat file. Run nightly archive to LTO device Run DBBackup to flat file located on rootvg of AIX box Run Mksysb of rootvg to 4mm tape. If this is sufficient, my only other question is how do you restore the DBBackup, is it the same as if you are restoring it from a tape? Bill Wheeler PDM Administrator -Original Message- From: Michael Benjamin [mailto:[EMAIL PROTECTED]] Sent: Monday, July 08, 2002 9:53 PM To: [EMAIL PROTECTED] Subject: Re: TSM DBBackup Hi Alex, If you've tarred the file to LTO, how do you utilise it quickly? It's almost easier to let TSM perform the dbbackup to LTO, and then you have a dbbackup volume you can utilise straight away. The dbbackup takes a few minutes to complete, time is a non-issue here. Yes it's a shame you have to waste a lot of space on the dbbackup volume, but it's the same type of volume and that's worth a lot... I guess you have to work out how much your data is worth, if it's more than about $1000 AU then it's definately worth buying some more tape volumes to rotate your DB offsite. The DB is simply too important to mess around with and lose... that single volume represents the entire contents of your server, if you lose that and your db/mirrors on the filesystems your 10,000 tapes aren't worth a thing to you come recovery time they are just a massive collection of ones and zeros... Mike. -Original Message- From: Alex Paschal [SMTP:[EMAIL PROTECTED]] Sent: Tuesday, July 09, 2002 1:26 AM To: [EMAIL PROTECTED] Subject: Re: TSM DBBackup You can do a dbbackup devc=file_class, which will put the dbbackup into a file on disk. The only thing is you'd then have to script a process that somehow backs up that file, or do it manually. Possibilities include: FTP to remote site tar to 4mm tape tar to LTO Personally, I'd rather not run so tight on scratches that I don't have 7 tapes I can spare for dbbackups. Alex -Original Message- From: Bill Wheeler [mailto:[EMAIL PROTECTED]] Sent: Monday, July 08, 2002 6:30 AM To: [EMAIL PROTECTED] Subject: Re: TSM DBBackup Currently we run our archive to a
Re: Expire data on a server that doesnt exist any longer.
If I have backup of a server which is out of production. What can I do and how, if I want to expire all extra backup copies (versions data exist) except the last backup (versions data deleted)? I can change mgmtclass but I still have to do a backup to rebind my files. If I use a client and log on with 'dsmc -virtualnodename=xyz' and exclude E:\...\* , what happens then? Will it expire xyz´s E:\ files or the client node E:\ files? A dsmc command as such won't affect file retentions at all. You will need to run an incremental backup. A 'dsmc inc' with the exclude statement and virtualnodename option shown would affect files from xyz. However, that approach would make me very nervous about the possibility of an incremental backup with the exclude statement but not the option. I would be inclined to copy the options file, put the special exclude statement and a 'nodename xyz' statement in the copy, and run dsmc with an 'optfile' option telling it to use the copy. It is easier to describe the effect of a backup that excludes everything on the E drive in terms of what happens to backups of a file than in terms of what happens to backups of an entire population of files. Consider an active backup of a file that was on xyz's E drive. A backup with the exclude statement described above would cause this backup to switch to inactive status. If the number of versions of the file was greater than the verdeleted parameter of the relevant copy group the next 'expire inventory' on the TSM server would delete enough of the oldest versions to get the number of versions down to the verdeleted parameter value. If there was still more than one version of the file subsequent 'expire inventory' operations would remove each extra version after it reached the age limit set by the retextra parameter. Eventually, 'expire inventory' would remove the last backup version when it passed the age limit set by the retonly parameter.
Re: Delayed Schedule Start (On Vacation)
I am out of the office until July 29. C U then!
AW: Delayed Schedule Start
your sched has priority 1, does all the other scheds have the same priority? If yes, why? greets joachim -Ursprüngliche Nachricht- Von: Jon Adams [mailto:[EMAIL PROTECTED]] Gesendet: Mittwoch, 10. Juli 2002 17:27 An: [EMAIL PROTECTED] Betreff: Re: Delayed Schedule Start Perhaps a combination of the randomization, the backup window or the available sessions at the time of backup? If there are no sessions available, the backup will start anytime a session is available within that schedule window. Jon Adams Systems Engineer IT IPS, Premera Blue Cross -Original Message- From: Etienne Brodeur [mailto:[EMAIL PROTECTED]] Sent: Tuesday, July 09, 2002 11:49 AM To: [EMAIL PROTECTED] Subject: Re: Delayed Schedule Start What's your Schedule Randomization percentage and what is the backup window for this schedule? If I recall correctly randomization is for every schedule even if it only runs on one node. And the ramdomization starts from the moment the nodes connect to the server not from the start of the window. backup window is 4 hours. schedule starts at 1 AM randomization is set to 25% node connects at 230 AM schedules will start between 230 and 330 AM. Could this be it? Etienne Brodeur Martin, Jon R. [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] 07/09/2002 01:33 PM Please respond to ADSM: Dist Stor Manager To: [EMAIL PROTECTED] cc: Subject:Delayed Schedule Start The below schedule was scheduled for 1 PM. The client scheduler is polling and at 1:05 PM it updated, and said the schedule would start in 33 minutes. What causes a schedule to execute a time later than scheduled? I am aware of staggered starts for scheduled events, but this is the only thing scheduled at this time and nothing else is running on the server. Any ideas? Thanks, Jon Martin Policy Domain Name: SOLARIS Schedule Name: REBUILD_MR Description: Daily backup for Solaris Clients Action: Incremental Options: Objects: /rebuild_mr/ATX1/ Priority: 1 Start Date/Time: 05/16/01 13:00:00 Duration: 12 Hour(s) Period: 1 Day(s) Day of Week: Tuesday Expiration: Last Update by (administrator): ADMIN Last Update Date/Time: 07/09/02 10:57:07 Managing profile: 07/09/02 13:05:12 07/09/02 13:05:12 Schedule Name: REBUILD_MR 07/09/02 13:05:12 Action:Incremental 07/09/02 13:05:12 Objects: /rebuild_mr/ATX1/ 07/09/02 13:05:12 Options: 07/09/02 13:05:12 Server Window Start: 13:00:00 on 07/09/02 07/09/02 13:05:12 07/09/02 13:05:12 Command will be executed in 33 minutes. 07/09/02 13:05:12
Re: dsm.opt / dsmerror.log / incl/excl oddity
In both environments A and B, try the QUERY INCLEXCL command to see the output differences. Maybe your MVS server has a client options set with the EXCLUDE statement you are asking about. Regards, Andy Andy Raibeck IBM Software Group Tivoli Storage Manager Client Development Internal Notes e-mail: Andrew Raibeck/Tucson/IBM@IBMUS Internet e-mail: [EMAIL PROTECTED] (change eye to i to reply) The only dumb question is the one that goes unasked. The command line is your friend. Good enough is the enemy of excellence. Wholey, Joseph (TGA\\MLOL) [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] 07/11/2002 06:57 Please respond to ADSM: Dist Stor Manager To: [EMAIL PROTECTED] cc: Subject:dsm.opt / dsmerror.log / incl/excl oddity Envirionment A: Client OS: NT 4 Client Version: Version 4, Release 2, Level 1.20 Server: Storage Management Server for MVS - Version 4, Release 2, Level 1.11 Environment B: Client OS: NT 4 Client Version: Version 4, Release 2, Level 1.20 Server: Storage Management Server for MVS - Version 4, Release 1, Level 3.0 These clients are cookie cutter builds Starting from the OS down to the dsm.opt (with the exception of the TSM server they point to). Question: Why is my dsmerror.log filling up with the following messages in environmet B and not A when the directory structure and dsm.opt are identical for both servers? ANS1115W File '\\l06101s001\e$\Services\BUEXECV7\NT\reports\saved\empty' excluded by Include/Exclude list Any help would be appreciated. Regards, Joe
web admin interface: problem with install
ladies, gentlemen, i just subscribed to this list, since i found no clues on the problem i am facing - i would be very happy if anybody could provide me with some hints as to how to troubleshoot the following: installing the 5.1.1.0 version of the tsm server on a dell multiprocessor computer running win2k advanced server and going through the init-process after setup gives me a running server, which i can administrate using the mmc-commandline and wizards included with the mmc. i cannot, however, use the web admin interface (neither locally nor from another machine), since the frame on the left hand of the browser window gives me 404. i can, however, logon to the server and have a command line in my webbrowser - also the show events option seems to work fine. installing the same server on a win2kpro machine (with no backup device) in the same manner as before shows me the left frame with all the options, so i suppose the install-file is good. both os are german, and the version of tsm server i chose is german as well (hoping to thus avoid lang problems - why i would choose to install german in the first place might be discussed elsewhere...). if anybody could provide me with info concerning how to troubleshoot why i get a 404 for the admin tools, and where the settings for the webserver are stored (paths?), i would be very happy. background: after having tried to install the last version 4 tsm server on this machine, which even refused to initialise the server, and going through a couple of install/uninstall/registry_clean/..., i succeeded in installing the new 5.1.1.0 only after killing the windows installation (which was only set up for backup, and had things like change admin account name - security policy here - and some shut down services) and do a plain vanilla reinstall, so that it at least works now with my library and we can do some backups. i would like to avoid going through that reinstall circle again, if possible. the above makes me think if there is something peculiar about the way either dell has you install the server or our win2kadvanced installation material, since all these problems did not arise on a test install on my win2kpro workstation. maybe it could also be possible that deactivating services like - dhcp - print spool - licence protocol - remote registry service - smtp - snmp - phone - iis-admin and - www-publishing might keep the admin tools from working? thanks in advance for any input, kind regards from germany, tobi hofmann -- Dipl.-Ing. Tobias Hofmann Bauhaus-Universitaet Weimar D99423 Weimar Professur fuer Graphische Datenverarbeitung Projekt medienquadrat SnailMail: Bauhaus-Universitaet Weimar, Fak. Medien, D99421 Weimar Location: D99423 Weimar Karl-Haussknechtstr. 7 Zimmer 111 Fon: ++49-(0)3643-58-3780 Fax : -3701 e-mail: mailto:[EMAIL PROTECTED] --
Re: solaris experts plz help
Yes that's actually a typo (the lb in places where it should be op or mt). My conf files are correct in that sense (i.e. I wasn't cutting/pasting them). The problem I'm having is I'm not sure how to interpret what LUN a device is on or what the TARGET is by looking at the output from probe-scsi-all.. Gerald Wichmann Senior Systems Development Engineer Zantaz, Inc. 925.598.3099 (w) -Original Message- From: Jozef Zatko [mailto:[EMAIL PROTECTED]] Sent: Thursday, July 11, 2002 1:23 AM To: [EMAIL PROTECTED] Subject: Re: solaris experts plz help Hello Gerald, you have to change your conf files like this: lb.conf if the scsi target and luns for your libraries are OK, you do not have to change this file. op.conf replace all lb with op (in this file you define only optical drives, not changer). For each optical drive create one stanza with correct target and lun of each drive (so you will have 10 stanzas in your conf file). Example Name=op class=scsi Target=X lun=Y; X is SCSI target ID of optical drive and Y is LUN of that drive mt.conf here replace lb with mt (in this file you define only tape drives, not changer). For each tape drive create one stanza with correct target and lun of each drive (so you will have 4 stanzas in your conf file). Example Name=mt class=scsi Target=X lun=Y; X is SCSI target ID of tape drive and Y is LUN of that drive Ing. Jozef Zatko Login a.s. Dlha 2, Stupava tel.: (421) (2) 60252618 Gerald Wichmann [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] 11.07.2002 01:14 Please respond to ADSM: Dist Stor Manager To: [EMAIL PROTECTED] cc: Subject:solaris experts plz help Below is the output of my server's probe-scsi-all.. I have 2 ATL M1500 LTO libraries with 2 drives each, and one HP 1200ex optical library with 10 optical drives. I need to populate the mt.conf, lb.conf, and op.conf files accordingly but what I've done doesn't seem to be working. When doing the add_drv command, it loads the device driver but then fails to attach. When I do add_drv for op it works but I only get a 0op and 1op so I'm not sure why it didn't pick up 10 drives. So my first question is, what do I put in the various conf files? I'm not as familiar with solaris so could use some help. Currently my files look like this: Lb.conf Name=lb class=scsi Target=5 lun=0; Name=lb class=scsi Target=4 lun=0; Name=lb class=scsi Target=4 lun=1; Op.conf Name=lb class=scsi Target=4 lun=0; Name=lb class=scsi Target=4 lun=1; Mt.conf Name=lb class=scsi Target=5 lun=0; Name=lb class=scsi Target=4 lun=0; Probe-scsi-all: /pci@1f,2000/pci@1/scsi@5 Target 0 Unit 0 Removable Medium changerM4 DATA MagFile 2.10 Target 1 Unit 0 Removable Tape HP Ultrium 1-SCSI E15V Target 2 Unit 0 Removable Tape HP Ultrium 1-SCSI E15V /pci@1f,2000/pci@1/scsi@4 Target 0 Unit 0 Removable Medium changerM4 DATA MagFile 2.10 Target 1 Unit 0 Removable Tape HP Ultrium 1-SCSI E15V Target 2 Unit 0 Removable Tape HP Ultrium 1-SCSI E15V /pci@1f,4000/scsi@4,1 Target 2 Unit 0 Removable Device type 7 HP C1113J 1.10 Target 3 Unit 0 Removable Device type 7 HP C1113J 1.10 Target 4 Unit 0 Removable Device type 7 HP C1113J 1.10 Target 5 Unit 0 Removable Device type 7 HP C1113J 1.10 Target 6 Unit 0 Removable Device type 8 HP C1107J 1.40 /pci@1f,4000/scsi@4 Target 1 Unit 0 Removable Device type 7 HP C1113J 1.10 Target 2 Unit 0 Removable Device type 7 HP C1113J 1.10 Target 3 Unit 0 Removable Device type 7 HP C1113J 1.10 Target 4 Unit 0 Removable Device type 7 HP C1113J 1.10 Target 5 Unit 0 Removable Device type 7 HP C1113J 1.10 Target 6 Unit 0 Removable Device type 7 HP C1113J 1.10 Gerald Wichmann Senior Systems Development Engineer Zantaz, Inc. 925.598.3099 (w)
Re: Need TSM 3.7
My IBM rep was the first person I contacted. However, since TSM 3.7 is no longer an availabel product, my rep has not been able to help, as of yet. I have the license but not the media. The AIX CD is the only one we cannot find. Ray Pratts Senior Systems Engineer Mark III Systems, Inc 6575 West Loop South, Suite 675 Bellaire, TX 77401 713-664-9850 ext. 29 Andy Raibeck [EMAIL PROTECTED] To: [EMAIL PROTECTED] COM cc: Sent by: ADSM: Subject: Re: Need TSM 3.7 Dist Stor Manager [EMAIL PROTECTED] T.EDU 07/10/2002 05:43 PM Please respond to ADSM: Dist Stor Manager I would be remiss if I didn't caution against doing anything that might violate the TSM licensing agreement. Ray, while 3.7 is no longer supported, I would recommend that you contact your IBM rep for assistance if you have lost your original installation media. Regards, Andy Andy Raibeck IBM Software Group Tivoli Storage Manager Client Development Internal Notes e-mail: Andrew Raibeck/Tucson/IBM@IBMUS Internet e-mail: [EMAIL PROTECTED] (change eye to i to reply) The only dumb question is the one that goes unasked. The command line is your friend. Good enough is the enemy of excellence. Gene Greenberg [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] 07/10/2002 13:58 Please respond to ADSM: Dist Stor Manager To: [EMAIL PROTECTED] cc: Subject:Re: Need TSM 3.7 I'm not sure if there is another solution because I didn't encounter this last week when I upgraded to 5.1, but I'm pretty sure I have a copy of 3.7 for AIX. You can contact me if you don't find another solution. Gene Greenberg Jr. Lead, System Administrator, DBA, SMA 512-464-5162 Round Rock ISD Round Rock TX Ray Pratts ray.pratts@MARKITo: [EMAIL PROTECTED] IISYS.COM cc: Sent by: ADSM: Subject: Need TSM 3.7 Dist Stor Manager [EMAIL PROTECTED] .EDU 07/10/02 03:27 PM Please respond to ADSM: Dist Stor Manager Can I obtain TSM 3.7 Server for AIX. I have a system that I was about to upgrade to TSM 5.1. Well crashed and I need to restore the TSM database with 3.7 before I can upgrade. Any ideas. Thanks. Ray Pratts Senior Systems Engineer Mark III Systems, Inc 6575 West Loop South, Suite 675 Bellaire, TX 77401 713-664-9850 ext. 29
expiration
The situation is we have a node that is going to have it's daily backups to TSM stopped. They don't want to delete the filespaces at this time. The question is, do all the versions remain available since nothing has triggered the system to think files were deleted? Or will older version roll off at some point and leave only the latest version of very file on the server. Remember the server has only been removed from a daily backup schedule. Thanks for the help. Geoff Gill TSM Administrator NT Systems Support Engineer SAIC E-Mail:mailto:[EMAIL PROTECTED] [EMAIL PROTECTED] Phone: (858) 826-4062 Pager: (877) 905-7154
Re: Need TSM 3.7
I've got one in my hand. At 11:42 AM 7/11/2002 -0500, you wrote: My IBM rep was the first person I contacted. However, since TSM 3.7 is no longer an availabel product, my rep has not been able to help, as of yet. I have the license but not the media. The AIX CD is the only one we cannot find. Ray Pratts Senior Systems Engineer Mark III Systems, Inc 6575 West Loop South, Suite 675 Bellaire, TX 77401 713-664-9850 ext. 29 Andy Raibeck [EMAIL PROTECTED] To: [EMAIL PROTECTED] COM cc: Sent by: ADSM: Subject: Re: Need TSM 3.7 Dist Stor Manager [EMAIL PROTECTED] T.EDU 07/10/2002 05:43 PM Please respond to ADSM: Dist Stor Manager I would be remiss if I didn't caution against doing anything that might violate the TSM licensing agreement. Ray, while 3.7 is no longer supported, I would recommend that you contact your IBM rep for assistance if you have lost your original installation media. Regards, Andy Andy Raibeck IBM Software Group Tivoli Storage Manager Client Development Internal Notes e-mail: Andrew Raibeck/Tucson/IBM@IBMUS Internet e-mail: [EMAIL PROTECTED] (change eye to i to reply) The only dumb question is the one that goes unasked. The command line is your friend. Good enough is the enemy of excellence. Gene Greenberg [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] 07/10/2002 13:58 Please respond to ADSM: Dist Stor Manager To: [EMAIL PROTECTED] cc: Subject:Re: Need TSM 3.7 I'm not sure if there is another solution because I didn't encounter this last week when I upgraded to 5.1, but I'm pretty sure I have a copy of 3.7 for AIX. You can contact me if you don't find another solution. Gene Greenberg Jr. Lead, System Administrator, DBA, SMA 512-464-5162 Round Rock ISD Round Rock TX Ray Pratts ray.pratts@MARKITo: [EMAIL PROTECTED] IISYS.COM cc: Sent by: ADSM: Subject: Need TSM 3.7 Dist Stor Manager [EMAIL PROTECTED] .EDU 07/10/02 03:27 PM Please respond to ADSM: Dist Stor Manager Can I obtain TSM 3.7 Server for AIX. I have a system that I was about to upgrade to TSM 5.1. Well crashed and I need to restore the TSM database with 3.7 before I can upgrade. Any ideas. Thanks. Ray Pratts Senior Systems Engineer Mark III Systems, Inc 6575 West Loop South, Suite 675 Bellaire, TX 77401 713-664-9850 ext. 29
Re: expiration
Geoff, Inactive version will be expired from the server according to the RETEXTRA and RETONLY parameters. Eventually, only the active set will remain. If you want to keep all the inactive versions, you can copy the domain to a new domain, update the copygroups to have all 9's, activate the policy set, and then update the node to be in the new domain. Hope this helps, Bill At 12:23 PM 7/11/2002, you wrote: The situation is we have a node that is going to have it's daily backups to TSM stopped. They don't want to delete the filespaces at this time. The question is, do all the versions remain available since nothing has triggered the system to think files were deleted? Or will older version roll off at some point and leave only the latest version of very file on the server. Remember the server has only been removed from a daily backup schedule. Thanks for the help. Geoff Gill TSM Administrator NT Systems Support Engineer SAIC E-Mail:mailto:[EMAIL PROTECTED] [EMAIL PROTECTED] Phone: (858) 826-4062 Pager: (877) 905-7154 -- Bill Colwell C. S. Draper Lab Cambridge Ma.
Maximum Size Threshold: on Primary Disk Pool
Hi, As amount of data and number of clients are growing in our environment. I have updated the Maximum Size Threshold: 60 G on one of my main disk storage pool. Reason is to utilize the available space for small files. Now I have question regarding that. 1- How can I find the biggest file size I ever backed up. 2- How can I find the file list I backed up last night 3- How can I track which client and what file (effected by maxsize parameter) is going to tape storage pool, instead of disk storage pool. Quick environment over view, TSM 4.1.4.0 AIX 4.3.3 on SP node 3494 ATL with 7 Drives. Any help would be appreciated
Re: Need TSM 3.7
Me too, let me know if I need to set on ftp for you. Peter At 11:55 11-07-2002 -0500, you wrote: I've got one in my hand. At 11:42 AM 7/11/2002 -0500, you wrote: My IBM rep was the first person I contacted. However, since TSM 3.7 is no longer an availabel product, my rep has not been able to help, as of yet. I have the license but not the media. The AIX CD is the only one we cannot find. Ray Pratts Senior Systems Engineer Mark III Systems, Inc 6575 West Loop South, Suite 675 Bellaire, TX 77401 713-664-9850 ext. 29 Andy Raibeck [EMAIL PROTECTED] To: [EMAIL PROTECTED] COM cc: Sent by: ADSM: Subject: Re: Need TSM 3.7 Dist Stor Manager [EMAIL PROTECTED] T.EDU 07/10/2002 05:43 PM Please respond to ADSM: Dist Stor Manager I would be remiss if I didn't caution against doing anything that might violate the TSM licensing agreement. Ray, while 3.7 is no longer supported, I would recommend that you contact your IBM rep for assistance if you have lost your original installation media. Regards, Andy Andy Raibeck IBM Software Group Tivoli Storage Manager Client Development Internal Notes e-mail: Andrew Raibeck/Tucson/IBM@IBMUS Internet e-mail: [EMAIL PROTECTED] (change eye to i to reply) The only dumb question is the one that goes unasked. The command line is your friend. Good enough is the enemy of excellence. Gene Greenberg [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] 07/10/2002 13:58 Please respond to ADSM: Dist Stor Manager To: [EMAIL PROTECTED] cc: Subject:Re: Need TSM 3.7 I'm not sure if there is another solution because I didn't encounter this last week when I upgraded to 5.1, but I'm pretty sure I have a copy of 3.7 for AIX. You can contact me if you don't find another solution. Gene Greenberg Jr. Lead, System Administrator, DBA, SMA 512-464-5162 Round Rock ISD Round Rock TX Ray Pratts ray.pratts@MARKITo: [EMAIL PROTECTED] IISYS.COM cc: Sent by: ADSM: Subject: Need TSM 3.7 Dist Stor Manager [EMAIL PROTECTED] .EDU 07/10/02 03:27 PM Please respond to ADSM: Dist Stor Manager Can I obtain TSM 3.7 Server for AIX. I have a system that I was about to upgrade to TSM 5.1. Well crashed and I need to restore the TSM database with 3.7 before I can upgrade. Any ideas. Thanks. Ray Pratts Senior Systems Engineer Mark III Systems, Inc 6575 West Loop South, Suite 675 Bellaire, TX 77401 713-664-9850 ext. 29
Re: Expire data on a server that doesnt exist any longer.
To trim out the extra versions, I would copy the domain the node is now in to a new domain. Update the copygroups to these values - verexists 1 verdeleted 1 retextra 0 retonly Activate the poilcyset and then update the node to be in the new domain. The next expiration will trim all the inactive versions except for the last version of a deleted file. Hope this helps, Bill At 10:17 AM 7/11/2002, you wrote: If I have backup of a server which is out of production. What can I do and how, if I want to expire all extra backup copies (versions data exist) except the last backup (versions data deleted)? I can change mgmtclass but I still have to do a backup to rebind my files. If I use a client and log on with 'dsmc -virtualnodename=xyz' and exclude E:\...\* , what happens then? Will it expire xyz´s E:\ files or the client node E:\ files? A dsmc command as such won't affect file retentions at all. You will need to run an incremental backup. A 'dsmc inc' with the exclude statement and virtualnodename option shown would affect files from xyz. However, that approach would make me very nervous about the possibility of an incremental backup with the exclude statement but not the option. I would be inclined to copy the options file, put the special exclude statement and a 'nodename xyz' statement in the copy, and run dsmc with an 'optfile' option telling it to use the copy. It is easier to describe the effect of a backup that excludes everything on the E drive in terms of what happens to backups of a file than in terms of what happens to backups of an entire population of files. Consider an active backup of a file that was on xyz's E drive. A backup with the exclude statement described above would cause this backup to switch to inactive status. If the number of versions of the file was greater than the verdeleted parameter of the relevant copy group the next 'expire inventory' on the TSM server would delete enough of the oldest versions to get the number of versions down to the verdeleted parameter value. If there was still more than one version of the file subsequent 'expire inventory' operations would remove each extra version after it reached the age limit set by the retextra parameter. Eventually, 'expire inventory' would remove the last backup version when it passed the age limit set by the retonly parameter. -- Bill Colwell C. S. Draper Lab Cambridge Ma.
Re: Need TSM 3.7
ftp://service.boulder.ibm.com/storage/tivoli-storage-management/maintenance/server/v3r7/AIX/ Peter Pijpelink - P.L.C.S. BV Storage Consultants wrote: Me too, let me know if I need to set on ftp for you. Peter At 11:55 11-07-2002 -0500, you wrote: I've got one in my hand. At 11:42 AM 7/11/2002 -0500, you wrote: My IBM rep was the first person I contacted. However, since TSM 3.7 is no longer an availabel product, my rep has not been able to help, as of yet. I have the license but not the media. The AIX CD is the only one we cannot find. Ray Pratts Senior Systems Engineer Mark III Systems, Inc 6575 West Loop South, Suite 675 Bellaire, TX 77401 713-664-9850 ext. 29 Andy Raibeck [EMAIL PROTECTED] To: [EMAIL PROTECTED] COM cc: Sent by: ADSM: Subject: Re: Need TSM 3.7 Dist Stor Manager [EMAIL PROTECTED] T.EDU 07/10/2002 05:43 PM Please respond to ADSM: Dist Stor Manager I would be remiss if I didn't caution against doing anything that might violate the TSM licensing agreement. Ray, while 3.7 is no longer supported, I would recommend that you contact your IBM rep for assistance if you have lost your original installation media. Regards, Andy Andy Raibeck IBM Software Group Tivoli Storage Manager Client Development Internal Notes e-mail: Andrew Raibeck/Tucson/IBM@IBMUS Internet e-mail: [EMAIL PROTECTED] (change eye to i to reply) The only dumb question is the one that goes unasked. The command line is your friend. Good enough is the enemy of excellence. Gene Greenberg [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] 07/10/2002 13:58 Please respond to ADSM: Dist Stor Manager To: [EMAIL PROTECTED] cc: Subject:Re: Need TSM 3.7 I'm not sure if there is another solution because I didn't encounter this last week when I upgraded to 5.1, but I'm pretty sure I have a copy of 3.7 for AIX. You can contact me if you don't find another solution. Gene Greenberg Jr. Lead, System Administrator, DBA, SMA 512-464-5162 Round Rock ISD Round Rock TX Ray Pratts ray.pratts@MARKITo: [EMAIL PROTECTED] IISYS.COM cc: Sent by: ADSM: Subject: Need TSM 3.7 Dist Stor Manager [EMAIL PROTECTED] .EDU 07/10/02 03:27 PM Please respond to ADSM: Dist Stor Manager Can I obtain TSM 3.7 Server for AIX. I have a system that I was about to upgrade to TSM 5.1. Well crashed and I need to restore the TSM database with 3.7 before I can upgrade. Any ideas. Thanks. Ray Pratts Senior Systems Engineer Mark III Systems, Inc 6575 West Loop South, Suite 675 Bellaire, TX 77401 713-664-9850 ext. 29
Re: expiration
The situation is we have a node that is going to have it's daily backups to TSM stopped. They don't want to delete the filespaces at this time. The question is, do all the versions remain available since nothing has triggered the system to think files were deleted? Or will older version roll off at some point and leave only the latest version of very file on the server. Remember the server has only been removed from a daily backup schedule. The active backups (the current versions of files that existed on the node at the time of its last backup) will be kept indefinitely. The inactive backups (older versions of files with active backups, and all backups of files deleted from the node before its last backup) will eventually age off unless the relevant copy group has retonly, retextra, or both set to 'nolimit'.
Ordering client licenses
We have a TSM 4.2.1.9 server running under OS/390. We pay for it on a monthly charge basis. We are currently attempting to order additional client licenses. We are being told that it is not possible to order these on a monthly charge basis. We are being quoted a one-time charge based on the numbers of various client types. Each of the major Unix implementations is a separate type in this context. Somewhat incredibly Windows NT and Windows 2000 are two separate types. We have not so far been asked about the numbers of processors on our client system, or about servers versus workstations. Our organization's policies on budgeting make it essentially impossible to purchase anything with money originally budgeted for leasing things, which makes the claimed change in policy a significant problem. Are we being told the whole truth about our options for acquiring additional client licenses?
[no subject]
get LOG0207
Need help with ADSM3.1 and WIN NT 4.0 SCSI
Hello, i have to reactivate an old 3.1 installation which used a tape library with 6 cartridges. We do not have the old tape library anymore so i am currently trying to get an ordenary HP 1537A 4mm DAT to work. The Windows driver works fine and i can use the Windows backup program to backup and restore data to the tape but the ADSM SCSI just does not want to start. Is does not find the specific drive.. It is configured under Windows and the ADSM Wizard does find it, but the ADSM SCSI does not start. In the devconfig.out it says GENLIB1 and GENERIC_TAPE and \\.\tape0 Any suggestions or help is higly appreciated Kind regards O. Oexmann
Re: Need TSM 3.7
Peter, I would greatly appreciate you setting it up on ftp. I tried the servcie.boulder site, but that only has upgrades to the base 3.7. Ray Pratts Senior Systems Engineer Mark III Systems, Inc 6575 West Loop South, Suite 675 Bellaire, TX 77401 713-664-9850 ext. 29 Peter Pijpelink - P.L.C.S. BVTo: [EMAIL PROTECTED] Storage cc: Consultants Subject: Re: Need TSM 3.7 [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] T.EDU 07/11/2002 12:49 PM Please respond to ADSM: Dist Stor Manager Me too, let me know if I need to set on ftp for you. Peter At 11:55 11-07-2002 -0500, you wrote: I've got one in my hand. At 11:42 AM 7/11/2002 -0500, you wrote: My IBM rep was the first person I contacted. However, since TSM 3.7 is no longer an availabel product, my rep has not been able to help, as of yet. I have the license but not the media. The AIX CD is the only one we cannot find. Ray Pratts Senior Systems Engineer Mark III Systems, Inc 6575 West Loop South, Suite 675 Bellaire, TX 77401 713-664-9850 ext. 29 Andy Raibeck [EMAIL PROTECTED] To: [EMAIL PROTECTED] COM cc: Sent by: ADSM: Subject: Re: Need TSM 3.7 Dist Stor Manager [EMAIL PROTECTED] T.EDU 07/10/2002 05:43 PM Please respond to ADSM: Dist Stor Manager I would be remiss if I didn't caution against doing anything that might violate the TSM licensing agreement. Ray, while 3.7 is no longer supported, I would recommend that you contact your IBM rep for assistance if you have lost your original installation media. Regards, Andy Andy Raibeck IBM Software Group Tivoli Storage Manager Client Development Internal Notes e-mail: Andrew Raibeck/Tucson/IBM@IBMUS Internet e-mail: [EMAIL PROTECTED] (change eye to i to reply) The only dumb question is the one that goes unasked. The command line is your friend. Good enough is the enemy of excellence. Gene Greenberg [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] 07/10/2002 13:58 Please respond to ADSM: Dist Stor Manager To: [EMAIL PROTECTED] cc: Subject:Re: Need TSM 3.7 I'm not sure if there is another solution because I didn't encounter this last week when I upgraded to 5.1, but I'm pretty sure I have a copy of 3.7 for AIX. You can contact me if you don't find another solution. Gene Greenberg Jr. Lead, System Administrator, DBA, SMA 512-464-5162 Round Rock ISD Round Rock TX Ray Pratts ray.pratts@MARKITo: [EMAIL PROTECTED] IISYS.COM cc: Sent by: ADSM: Subject: Need TSM 3.7 Dist Stor Manager [EMAIL PROTECTED] .EDU 07/10/02 03:27 PM Please respond to ADSM: Dist Stor Manager Can I obtain TSM 3.7 Server for AIX. I have a system that I was about to upgrade to TSM 5.1. Well crashed and I need to restore the TSM database with 3.7 before I can upgrade. Any ideas. Thanks. Ray Pratts Senior Systems Engineer Mark III Systems, Inc 6575 West Loop South, Suite 675 Bellaire, TX 77401 713-664-9850 ext. 29
Re: AIX restore from one client to another
Be careful when using -node instead of -virtualnode. Especially on other platforms - on Windows this might upgrade filespace to unicode and cause headaches. Use 'dsmc restore -fromnode' or 'dsmc -virtualnodename' as already suggested. Zlatko Krastev IT Consultant Please respond to ADSM: Dist Stor Manager [EMAIL PROTECTED] Sent by:ADSM: Dist Stor Manager [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: Subject:AIX restore from one client to another I want to be able to restore directories from a production client to a test client. I know with the other platforms you just put the other clients node name in the path, but being unfamiliar with AIX I was not sure if this would be the same. I have not tried this yet, just looking for some direction. This is how I assume it would go: restore nodeA /usr/xyz/* -su=yes nodeB/usr/xyz/ I guess my question is, is this possible and do I have the right syntax. Any help would be appreciated Mike Anderson [EMAIL PROTECTED] CONFIDENTIALITY 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.
solaris expert needed
Well I'm making progress but something is clearly still wrong. I started a call with Tivoli but I'm waiting to hear back from them. If anyone see's anything obvious that I'm doing wrong let me know as I'm not very good with solaris specific device driver configuration: bash-2.03# cat lb.conf | grep -v # name=lb class=scsi target=0 lun=0; name=lb class=scsi target=6 lun=1; bash-2.03# cat mt.conf | grep -v # name=mt class=scsi target=1 lun=0; name=mt class=scsi target=2 lun=0; bash-2.03# cat op.conf | grep -v # name=op class=scsi target=1 lun=0; name=op class=scsi target=2 lun=0; name=op class=scsi target=3 lun=0; name=op class=scsi target=4 lun=0; name=op class=scsi target=5 lun=0; name=op class=scsi target=6 lun=0; name=op class=scsi target=2 lun=1; name=op class=scsi target=3 lun=1; name=op class=scsi target=4 lun=1; name=op class=scsi target=5 lun=1; bash-2.03# /usr/sbin/add_drv lb devfsadm: driver failed to attach: lb Warning: Driver (lb) successfully added to system but failed to attach bash-2.03# /usr/sbin/add_drv mt devfsadm: driver failed to attach: mt Warning: Driver (mt) successfully added to system but failed to attach bash-2.03# /usr/sbin/add_drv op bash-2.03# ls /dev/rmt 0op 0opt 1op 1opt 2op 2opt 3op 3opt 4op 4opt 5op 5opt 6op 6opt 7op 7opt 8op 8opt 9op 9opt bash-2.03# Gerald Wichmann Senior Systems Development Engineer Zantaz, Inc. 925.598.3099 (w)
Re: reclamation of unavailable primary tapes (was: w/o subject)
For working disaster recovery your customer will need a *compatible* device to read off-site tapes. In your case if we assume primary tapes are held only on 3575 and DLT autochanger is used only for off-site: - primary pool will use 3575. Library might be small but TSM does have 'MOVE MEDIA' command for that exact purpose. - copypool tapes will be DLT. Whenever set of tapes is built they are checked out and sent off-site. Thus no problems with capacity. - DR site must have DLT drive (not necessarily a library, manual one is just fine) which should be able to read tapes written by autoloader. If autoloader is DLT7000 drive might be either DLT7000 or DLT8000 but if the autoloader is DLT8000 the drive must be the same. If some primary pools are backed up to a copypool on 3575 then DR site must have 3570! Doublecheck which is backed up where. - do not forget to create (and send off-site) DB backups or snapshots after backup stg finishes. Zlatko Krastev IT Consultant Please respond to ADSM: Dist Stor Manager [EMAIL PROTECTED] Sent by:ADSM: Dist Stor Manager [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: Subject:Re: reclamation of unavailable primary tapes (was: w/o subject) Hi, First, sorry for sending the message without subject, I guess the human brain is not supposed to to more than one thing at the same time (especially mine ;-) ). I already knew the question of why sending primary tapes offsite will pop up. The only thing that came to my mind was that the library is not big enough to hold copies of all the important storage pools. The customer already uses a DLT-Autochanger as copy destination for some of the primary storage pools. We are currently busy redesigning the implementation. I am sure we will not get the customer convinced to buy a bigger library. So what else could possibly be done to prevent removing tapes from a primary pool? The customer's environment consists of: 1x 3575-L18 with 3x3570 (C-Drives) 1x DLT Autochanger 7 Slots with 70GB per tape Client data is about 800GB I am not expecting a detailed draft but hints are very welcome Thanks Lars On 10.07.2002 03:53:31 ADSM: Dist Stor Manager wrote: Lars, I do not know what is the idea behind sending primary tapes off-site (DR ??) but this does not help at all in case tape gets somehow damaged. You will learn it the hard way - when you need to restore from the broken tape. Migration threshold set to anything between 0 and 100% will not force/prevent reclamation. They are just different You already gave the answer: update the volumes to readonly or readwrite, check them in the library and lower reclamation threshold (in any order). BTW: Subjects are very useful to track answers on a mail list with many posts (like this one). Burak, offsite is for copypool volumes only (look at note 3 for UPD VOL). Primary ones have to be unavailable. Zlatko Krastev IT Consultant Please respond to ADSM: Dist Stor Manager [EMAIL PROTECTED] Sent by:ADSM: Dist Stor Manager [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: Subject: yes, you may change the accesses to readwrite and then reclaim but you should normally use offsite not unavailable access regards, burak [EMAIL PROTECTED] Sent by: [EMAIL PROTECTED] 09.07.2002 16:23 Please respond to ADSM-L To: [EMAIL PROTECTED] cc: Subject: Hi TSM Guys, I have a customer who moves volumes from a primary storage pool to an offsite location by setting the volumes to UNAVAILABLE. The storage pool's migration threshold is set to 100% for spacerclamation to be prevented. What do I have to consider if I want to manually start space reclamation on the unavailable volumes? Will it be enough to just check-in the volumes, change their access to ReadWrite, and then start the space reclamation by lowering the reclamation threshhold gradually? Thanx a lot Lars
Re: Need help with ADSM3.1 and WIN NT 4.0 SCSI
Did you try shutting down the Windows driver before starting the ADSMSCSI driver? Regards, Andy Andy Raibeck IBM Software Group Tivoli Storage Manager Client Development Internal Notes e-mail: Andrew Raibeck/Tucson/IBM@IBMUS Internet e-mail: [EMAIL PROTECTED] (change eye to i to reply) The only dumb question is the one that goes unasked. The command line is your friend. Good enough is the enemy of excellence. O. Oexmann [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] 07/11/2002 15:03 Please respond to ADSM: Dist Stor Manager To: [EMAIL PROTECTED] cc: Subject:Need help with ADSM3.1 and WIN NT 4.0 SCSI Hello, i have to reactivate an old 3.1 installation which used a tape library with 6 cartridges. We do not have the old tape library anymore so i am currently trying to get an ordenary HP 1537A 4mm DAT to work. The Windows driver works fine and i can use the Windows backup program to backup and restore data to the tape but the ADSM SCSI just does not want to start. Is does not find the specific drive.. It is configured under Windows and the ADSM Wizard does find it, but the ADSM SCSI does not start. In the devconfig.out it says GENLIB1 and GENERIC_TAPE and \\.\tape0 Any suggestions or help is higly appreciated Kind regards O. Oexmann
Re: Expire data on a server that doesnt exist any longer.
then after expiration takes place update the node back to original domain and delete the copy. Zlatko Krastev IT Consultant Please respond to ADSM: Dist Stor Manager [EMAIL PROTECTED] Sent by:ADSM: Dist Stor Manager [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: Subject:Re: Expire data on a server that doesnt exist any longer. To trim out the extra versions, I would copy the domain the node is now in to a new domain. Update the copygroups to these values - verexists 1 verdeleted 1 retextra 0 retonly Activate the poilcyset and then update the node to be in the new domain. The next expiration will trim all the inactive versions except for the last version of a deleted file. Hope this helps, Bill At 10:17 AM 7/11/2002, you wrote: If I have backup of a server which is out of production. What can I do and how, if I want to expire all extra backup copies (versions data exist) except the last backup (versions data deleted)? I can change mgmtclass but I still have to do a backup to rebind my files. If I use a client and log on with 'dsmc -virtualnodename=xyz' and exclude E:\...\* , what happens then? Will it expire xyz´s E:\ files or the client node E:\ files? A dsmc command as such won't affect file retentions at all. You will need to run an incremental backup. A 'dsmc inc' with the exclude statement and virtualnodename option shown would affect files from xyz. However, that approach would make me very nervous about the possibility of an incremental backup with the exclude statement but not the option. I would be inclined to copy the options file, put the special exclude statement and a 'nodename xyz' statement in the copy, and run dsmc with an 'optfile' option telling it to use the copy. It is easier to describe the effect of a backup that excludes everything on the E drive in terms of what happens to backups of a file than in terms of what happens to backups of an entire population of files. Consider an active backup of a file that was on xyz's E drive. A backup with the exclude statement described above would cause this backup to switch to inactive status. If the number of versions of the file was greater than the verdeleted parameter of the relevant copy group the next 'expire inventory' on the TSM server would delete enough of the oldest versions to get the number of versions down to the verdeleted parameter value. If there was still more than one version of the file subsequent 'expire inventory' operations would remove each extra version after it reached the age limit set by the retextra parameter. Eventually, 'expire inventory' would remove the last backup version when it passed the age limit set by the retonly parameter. -- Bill Colwell C. S. Draper Lab Cambridge Ma.
