unsubscribe
kind regards, Rowan O'Donoghue Technical Services Manager Unitech Systems Unit 2, First Floor, Bracken Court, Sandyford Industrial Estate, Dublin 18. DDI: + 353 - 1 - 2999357 Tel: + 353 - 1 - 2942300 Fax: + 353 - 1 - 2942319 http://www.unitech-ie.com Unitech Systems announces partnership with Commvault Systems: http://www.unitech-ie.com/view_pr_article.php?pr_id=31
Re: Client acceptor port on multiple NICs on WIN
Hi, Matthew - TCPCLIENTAddress does what you indicate, and the optional Node HLAddress is explicit. But those are for server-client communication, whereas your Windows folk are apparently concerned about user browser access, which is rather arbitrary and beyond your control in a multi- interfaced box. This is where the OS and network administrators take over, to enforce box access restrictions: work for them to do, less work for you. Richard Sims On May 12, 2006, at 10:28 AM, Large, M (Matthew) wrote: Hi Richard, I had my suspicions about that.. Do you think the TCPCLIENTADDRESS option would be of any use? I guess (without looking) this updates the TCP_ADDRESS column on the server to suggest an IP to make next contact with, not to ensure the client only listens on that IP address. Regards, Matthew
Recall: [ADSM-L] Client acceptor port on multiple NICs on WIN
Large, M (Matthew) would like to recall the message, "[ADSM-L] Client acceptor port on multiple NICs on WIN". _ This email (including any attachments to it) is confidential, legally privileged, subject to copyright and is sent for the personal attention of the intended recipient only. If you have received this email in error, please advise us immediately and delete it. You are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited. Although we have taken reasonable precautions to ensure no viruses are present in this email, we cannot accept responsibility for any loss or damage arising from the viruses in this email or attachments. We exclude any liability for the content of this email, or for the consequences of any actions taken on the basis of the information provided in this email or its attachments, unless that information is subsequently confirmed in writing. If this email contains an offer, that should be considered as an invitation to treat. _
Re: Client acceptor port on multiple NICs on WIN
Hi Richard, I had my suspicions about that.. Do you think the TCPCLIENTADDRESS option would be of any use? I guess (without looking) this updates the TCP_ADDRESS column on the server to suggest an IP to make next contact with, not to ensure the client only listens on that IP address. Regards, Matthew -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Richard Sims Sent: 12 May 2006 14:01 To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Client acceptor port on multiple NICs on WIN Matthew _ I'm not aware of any TSM client parameter to limit port listening to a specific computer network interface. Usually, the access is limited by convention, which is to say instructing usage to go through a given network address and thus interface; or, some kind of host-based or external firewall enforces the required access rules. Richard Sims On May 12, 2006, at 6:01 AM, Large, M (Matthew) wrote: > Hi all, > > I've never come across this before so I thought I'd ask you guys.. > > A windows guy came to me a few minutes ago saying that they have a box > which has three NICs - a production NIC, a backup NIC for TSM and > another NIC which faces 'outwards' as it were. > They are complaining that TSM is listening on port 1581 on all the > NICs, not just the Prod/Backup NICs. > I can understand that they would not want the TSM web client service > visible from this outward facing NIC, so does any know of a way round > this? _ This email (including any attachments to it) is confidential, legally privileged, subject to copyright and is sent for the personal attention of the intended recipient only. If you have received this email in error, please advise us immediately and delete it. You are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited. Although we have taken reasonable precautions to ensure no viruses are present in this email, we cannot accept responsibility for any loss or damage arising from the viruses in this email or attachments. We exclude any liability for the content of this email, or for the consequences of any actions taken on the basis of the information provided in this email or its attachments, unless that information is subsequently confirmed in writing. If this email contains an offer, that should be considered as an invitation to treat. _
Re: TDP for Exchange - Management Class
Hi Volker, Are you using separate NODENAMEs for each of the different DSM.OPT files? If not, your solution won't do what you think. Data Protection for Exchange stores objects in the backup pool, not the archive pool. That means, each full backup gets the same TSM Server name (similar to backing the same file name up with the BA Client.) It follows normal TSM Server policy rules. That means, if you are performing FULL backups using the same NODENAME, each time you back up with a different management class, all previous backups will get rebound to that new management class... just like BA Client file backups. Remember, this is standard behavior for BACKUP. You are trying to get ARCHIVE type function, which won't work. Good news... there is a way to do exactly what you want... ... I have two ways to do it. Solution 1: Create a separate NODENAME for your 3 types of backups. For example: EXCHSRV1, EXCHSRV1_MONTHLY, EXCHSRV1_YEARLY Have a separate DSM.OPT for each NODENAME, with the proper management class bindings. Set up your three schedules for your three separate nodenames. Solution 2: Create 2 separate NODENAMEs. Use one for the STANDARD and MONTHLY backups (perform COPY type backups for your MONTHLY backups). Use the other nodename for the YEARLY backups. For example: EXCHSRV1, EXCHSRV1_YEARLY Have one DSM.OPT for your STANDARD and MONTHLY backups and a different DSM.OPT for your YEARLY backups. In the DSM.OPT file for your STANDARD and MONTHLY backups, set up different policy bindings for FULL backups vs. COPY backups (since FULL and COPY get named differently on the TSM Server, they will also get their own policy.) Example DSM.OPT INCLUDE statements are like this: *---* The following example binds all FULL objects *---* to management class EXCH_STANDARD: INCLUDE "*\...\full" EXCH_STANDARD *---* The following example binds all COPY objects *---* to management class EXCH_MONTHLY: INCLUDE "*\...\copy" EXCH_MONTHLY As far as your original question... you can check the management class bindings by bringing up the Data Protection for Exchange GUI... go to the restore tab, click on the storage group you want to look at. It will show the management class bindings. (Make sure to view active and inactive, to see the previous backup bindings as well.) You can also use the SHOW VERSION TSM Server command: SHOW VERSION EXCHSRV1 * SHOW VERSION EXCHSRV1_MONTHLY * SHOW VERSION EXCHSRV1_YEARLY * This will show you the management class bindings. I hope this helps. Let me know if any of this isn't clear. Thanks, Del "ADSM: Dist Stor Manager" wrote on 05/12/2006 03:03:17 AM: > Hi, > > I want to do daily, monthly and yearly backups of our Exchange Server. > Therefore I defined three management classes: > 1) standard (for daily backups - 14 days retention) > 2) monthly (365 days retentions, backup once a month) > 3) yearly (5 years retention, backup once a year) > > I also defined three schedules on the server side, starting three > different command files on our exchange server which are using different > dsm.opt files. > > I now want to check if the backups are bound to the correct management > class. The following command shows me all backups but not the management > classes. > tdpexcc query tsm * /all > > Is there a way to view the management class to each backup? > > regards, > > Volker
Re: Client acceptor port on multiple NICs on WIN
Matthew _ I'm not aware of any TSM client parameter to limit port listening to a specific computer network interface. Usually, the access is limited by convention, which is to say instructing usage to go through a given network address and thus interface; or, some kind of host-based or external firewall enforces the required access rules. Richard Sims On May 12, 2006, at 6:01 AM, Large, M (Matthew) wrote: Hi all, I've never come across this before so I thought I'd ask you guys.. A windows guy came to me a few minutes ago saying that they have a box which has three NICs - a production NIC, a backup NIC for TSM and another NIC which faces 'outwards' as it were. They are complaining that TSM is listening on port 1581 on all the NICs, not just the Prod/Backup NICs. I can understand that they would not want the TSM web client service visible from this outward facing NIC, so does any know of a way round this?
Re: TDP for Exchange - Management Class
>> On Fri, 12 May 2006 09:03:17 +0200, Volker Maibaum <[EMAIL PROTECTED]> said: > I want to do daily, monthly and yearly backups of our Exchange Server. > Therefore I defined three management classes: > 1) standard (for daily backups - 14 days retention) > 2) monthly (365 days retentions, backup once a month) > 3) yearly (5 years retention, backup once a year) > I also defined three schedules on the server side, starting three > different command files on our exchange server which are using different > dsm.opt files. > I now want to check if the backups are bound to the correct management > class. The following command shows me all backups but not the management > classes. > tdpexcc query tsm * /all > Is there a way to view the management class to each backup? Well, you can "select HL_NAME,LL_NAME,CLASS_NAME,[whatever] from BACKUPS where node_name=[foo] order by backup_date" or the equivalent with archives. Redirect it to a file; it's liable to be capacious, but not too nuts. - Allen S. Rout
On the Inversion of the Conventional Relationship between File and Volume Sizes.
Greetings, all. I'm musing about strategies to deal with backups of "files" which are larger than some of my volumes. The DB2 API client stores full backups as single files; so I've got 150, 180, 210GB files rattling around in my stgpools. Now, I'm moving towards virtual volumes as my copy stgpools, and have so far set the virtual volume size at 20G. Rationale there is that I want the files which represent the volumes to be sanely sized for remote management: reclaiming a 2TB tape when your file size is 400G sounds irritating. So this means that, when one of my 20G volumes that contains a snippet of a DB Full comes up for reclamation, I have to move around all 180 G. Eugh. I understand why they reconstruct the fragmented file on reclamation as a general case; but in this case: + I'm going to start with 7 or 8 full volumes, and a head and tail segment; + I'm going to finish with 7 or 8 full volumes and a head and tail segment; So I see three major divisions of response, and I'm wondering which of them have been popular, and what other responses I've missed. 1) Deal with it, whiny-boy. 2) Put your huge files elsewhere (separate copy pool) so they are sanely managed independantly 3) Use bigger volumes so the mismatch between the big-file workload and the normal workload is less severe (if I have 400-500G volumes then moving 210G to reclaim one is less odd) I'd prefer to avoid option 1. ;) Notions? - Allen S. Rout
Re: ANR8301E
John, i favour the choice to correct the labels. So I'll be free for 1000 volsers and more. 1001 Thank Birgit > Look VERY closely at the volume serial numbers. > The UD volumes that are less than the 500 series have a zero '0' in the > third position. Ie UD0499. > The UD volumes that are in the 500 series have an oh 'O' in the the > third position. Ie UDO500. > > Guess you have two choices. Correct the labels or use them with the > non-numeric character in position 3. > > > John G. Talafous > Berbee Information Networks > > -Original Message- > From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of > Birgit Sievers > Sent: Thursday, May 11, 2006 6:51 AM > To: ADSM-L@VM.MARIST.EDU > Subject: [ADSM-L] ANR8301E > > AIX5.x TSM5.2 > > ANR8301E I/O error on library 3494 > > AIX: > mtlib -l /dev/robert -qI q > > ... > UD0262 0190 00 20 00 > UD0263 0190 00 20 00 > UD0264 0190 00 20 00 > ... > UD0498 0190 00 20 00 > UD0499 0190 00 20 00 > UDO500 FF00 00 20 00 > UDO501 FF00 00 20 00 > UDO502 FF00 00 20 00 > UDO503 FF00 00 20 00 > UDO504 FF00 00 20 00 > UDO505 FF00 00 20 00 > UDO506 FF00 00 20 00 > UDO507 FF00 00 20 00 > ... > > > > #mtlib -l /dev/robert -qV -V ud0263 > Volume Data: >volume state.00 >logical volume...No >volume class.3592 1/2 inch cartridge tape >volume type..3592 JA Cartridge >volser...UD0263 >category.0190 >subsystem affinity...01 02 03 04 05 00 00 00 > 00 00 00 00 00 00 00 00 > 00 00 00 00 00 00 00 00 > 00 00 00 00 00 00 00 00 > > > mtlib -l /dev/robert -qV -V ud0500 > Query operation Failed (errno = 5), ERPA code - 66, Requested Volume > Serial not in Library. > > > TSM: > > tsm: TSM_TAPESERVER>label libvolume lib3494 search=yes > volrange=ud0463,ud0522 > checkin=scr overwrite=yes > > didn't work out. q libv genertates the following: > LIB3494 UD0462 Private TSM_SRV1 Data > LIB3494 UD0464 Private TSM_TAPES- > ERVER > LIB3494 UD0465 Private TSM_TAPES- > ERVER > LIB3494 UD0466 Private TSM_TAPES- > ERVER > LIB3494 UD0467 Private TSM_TAPES- > > LIB3494 UD0482 Private TSM_TAPES- > ERVER > LIB3494 UD0483 Private TSM_TAPES- > ERVER > LIB3494 UD0484 Private TSM_TAPES- > ERVER > LIB3494 UD0485 Private TSM_TAPES- > ERVER > LIB3494 UD0486 Private TSM_TAPES- > ERVER > LIB3494 UD0487 Private TSM_TAPES- > ... > LIB3494 UD0496 Private TSM_TAPES- > ERVER > LIB3494 UD0497 Private TSM_TAPES- > ERVER > LIB3494 UD0498 Private TSM_TAPES- > ERVER > LIB3494 UD0499 Private TSM_TAPES- > ERVER > > tsm: TSM_TAPESERVER> > > We have no access to these volsers, they are private and greater than > ud0500 have the category FF00. > > > Thank you for help > > Birgit Sievers > > > 44227 Dortmund /germany > Tel.: 0231/755-2728 > Fax: 0231/755-2731 > email: [EMAIL PROTECTED] >
Client acceptor port on multiple NICs on WIN
Hi all, I've never come across this before so I thought I'd ask you guys.. A windows guy came to me a few minutes ago saying that they have a box which has three NICs - a production NIC, a backup NIC for TSM and another NIC which faces 'outwards' as it were. They are complaining that TSM is listening on port 1581 on all the NICs, not just the Prod/Backup NICs. I can understand that they would not want the TSM web client service visible from this outward facing NIC, so does any know of a way round this? Any assistance appreciated. Many Thanks, Matthew TSM Consultant ADMIN ITI Rabobank International 1 Queenhithe, London EC4V 3RL 0044 207 809 3665 _ This email (including any attachments to it) is confidential, legally privileged, subject to copyright and is sent for the personal attention of the intended recipient only. If you have received this email in error, please advise us immediately and delete it. You are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited. Although we have taken reasonable precautions to ensure no viruses are present in this email, we cannot accept responsibility for any loss or damage arising from the viruses in this email or attachments. We exclude any liability for the content of this email, or for the consequences of any actions taken on the basis of the information provided in this email or its attachments, unless that information is subsequently confirmed in writing. If this email contains an offer, that should be considered as an invitation to treat. _
Re: Redirecting Output of NetWare Console dsmc to a File ?
Hi, thanks a lot ! it worked with dsmc q backup sys:system/tsm/ -sub=yes -ina (CLIB_OPT)/>sys:test.out best regards Rainer Matt Zufelt schrieb: is there a way to put the output of, for example, "dsmc q backup" on the NetWare 6 console into a file? Or, if not, can I use another OS's TSM client? I didn't succeed with Linux and MS Windows TSM clients. Try appending (CLIB_OPT)/>sys:test.out to your command. Something like: dsmc q backup (CLIB_OPT)/>sys:test.out --Matt -- Rainer Wolf eMail: [EMAIL PROTECTED] kiz - Abt. Infrastruktur Tel/Fax: ++49 731 50-22482/22471 Universitaet Ulm wwweb:http://kiz.uni-ulm.de
Re: TDP for Exchange - Management Class
Hi Volker, You could eventually use "show versions" command on TSM server, to find out what mgmt class was used for each file backed up. Syntax for the command is "show version node_name x nametype=fsid" x being the numerical id of the filespace you want to investigate. Hope this helped ! Cheers. Arnaud ** Panalpina Management Ltd., Basle, Switzerland, CIT Department Viadukstrasse 42, P.O. Box 4002 Basel/CH Phone: +41 (61) 226 11 11, FAX: +41 (61) 226 17 01 Direct: +41 (61) 226 19 78 e-mail: [EMAIL PROTECTED] ** -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Volker Maibaum Sent: Friday, 12 May, 2006 09:03 To: ADSM-L@VM.MARIST.EDU Subject: TDP for Exchange - Management Class Hi, I want to do daily, monthly and yearly backups of our Exchange Server. Therefore I defined three management classes: 1) standard (for daily backups - 14 days retention) 2) monthly (365 days retentions, backup once a month) 3) yearly (5 years retention, backup once a year) I also defined three schedules on the server side, starting three different command files on our exchange server which are using different dsm.opt files. I now want to check if the backups are bound to the correct management class. The following command shows me all backups but not the management classes. tdpexcc query tsm * /all Is there a way to view the management class to each backup? regards, Volker
TDP for Exchange - Management Class
Hi, I want to do daily, monthly and yearly backups of our Exchange Server. Therefore I defined three management classes: 1) standard (for daily backups - 14 days retention) 2) monthly (365 days retentions, backup once a month) 3) yearly (5 years retention, backup once a year) I also defined three schedules on the server side, starting three different command files on our exchange server which are using different dsm.opt files. I now want to check if the backups are bound to the correct management class. The following command shows me all backups but not the management classes. tdpexcc query tsm * /all Is there a way to view the management class to each backup? regards, Volker
