Re: Unsubscribe
Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [172.16.150.26] Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 MIME-Version: 1.0 X-Virus-Scanned: by bsmtpd at solixinc.com X-Barracuda-Connect: email.solixinc.com[65.51.251.220] X-Barracuda-Start-Time: 1512061200 X-Barracuda-Encrypted: ECDHE-RSA-AES256-GCM-SHA384 X-Barracuda-URL: https://148.100.49.28:443/cgi-mod/mark.cgi X-Barracuda-Scan-Msg-Size: 1023 X-Virus-Scanned: by bsmtpd at marist.edu X-Barracuda-BRTS-Status: 1 X-Barracuda-Spam-Score: 0.00 X-Barracuda-Spam-Status: No, SCORE=0.00 using global scores of TAG_LEVEL=3.5 QUARANTINE_LEVEL=1000.0 KILL_LEVEL=5.5 tests= X-Barracuda-Spam-Report: Code version 3.2, rules version 3.2.3.45377 Rule breakdown below pts rule name description -- -- UGxlYXNlIHJlbW92ZSBteSBhZGRyZXNzIGZyb20gdGhpcyBMaXN0DQoNClRo YW5rIHlvdSANCg0KDQoNCgotLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0NCkNvbmZpZGVu dGlhbGl0eSBOb3RpY2U6IFRoZSBpbmZvcm1hdGlvbiBpbiB0aGlzIGUtbWFp bCBhbmQgYW55IA0KYXR0YWNobWVudHMgdGhlcmV0byBpcyBpbnRlbmRlZCBm b3IgdGhlIG5hbWVkIHJlY2lwaWVudChzKSBvbmx5DQouICBUaGlzIGUtbWFp bCwgaW5jbHVkaW5nIGFueSBhdHRhY2htZW50cywgbWF5IGNvbnRhaW4gaW5m b3JtYXRpb24gDQp0aGF0IGlzIHByaXZpbGVnZWQgYW5kIGNvbmZpZGVudGlh bCAgYW5kIHN1YmplY3QgdG8gbGVnYWwgcmVzdHJpY3Rpb25zIA0KYW5kIHBl bmFsdGllcyByZWdhcmRpbmcgaXRzIHVuYXV0aG9yaXplZCBkaXNjbG9zdXJl IG9yIG90aGVyIHVzZS4NCiAgSWYgeW91IGFyZSBub3QgdGhlIGludGVuZGVk IHJlY2lwaWVudCwgeW91IGFyZSBoZXJlYnkgbm90aWZpZWQgDQp0aGF0IGFu eSBkaXNjbG9zdXJlLCBjb3B5aW5nLCBkaXN0cmlidXRpb24sIG9yIHRoZSB0 YWtpbmcgb2YgYW55IA0KYWN0aW9uIG9yIGluYWN0aW9uIGluIHJlbGlhbmNl IG9uIHRoZSBjb250ZW50cyBvZiB0aGlzIGUtbWFpbCBhbmQNCiBhbnkgb2Yg aXRzIGF0dGFjaG1lbnRzIGlzIFNUUklDVExZIFBST0hJQklURUQuICBJZiB5 b3UNCiBoYXZlIHJlY2VpdmVkIHRoaXMgZS1tYWlsIGluIGVycm9yLCBwbGVh c2UgaW1tZWRpYXRlbHkgbm90aWZ5DQogdGhlIHNlbmRlciB2aWEgcmV0dXJu IGUtbWFpbDsgZGVsZXRlIHRoaXMgZS1tYWlsIGFuZCBhbGwgYXR0YWNobWVu dHMgDQpmcm9tIHlvdXIgZS1tYWlsICBzeXN0ZW0gYW5kIHlvdXIgY29tcHV0 ZXIgc3lzdGVtIGFuZCBuZXR3b3JrOw0KIGFuZCBkZXN0cm95IGFueSBwYXBl ciBjb3BpZXMgeW91IG1heSBoYXZlIGluIHlvdXIgcG9zc2Vzc2lvbi4gDQpU aGFuayB5b3UgZm9yIHlvdXIgY29vcGVyYXRpb24uDQoK
Unsubscribe
Please remove my address from the list.
Re: UNSUBSCRIBE
Please remove my address from the listserv as the company has chosen a different package for backing up data Marshael Morris (morris.marsh...@navicenthealth.org) 353 First Street Suite 100 Macon, GA 31201 (478) 633-2160 CONFIDENTIALITY NOTICE: The information transmitted in this e-mail message, including any attachments, is for the sole use of the intended recipient(s) or entity to which it is addressed and may contain confidential, privileged, and/or proprietary information. Any unauthorized review, retransmission, use, disclosure, dissemination, or other use of, or taking any action in reliance upon this information by persons or entities other than the intended recipient is prohibited. If you are not the intended recipient, you are hereby notified that any reading, dissemination, distribution, copying, or other use of this message or its attachments is strictly prohibited. If you have received this message in error, please notify the sender immediately by reply e-mail, or by calling (478) 633-7272, and destroy the original message, attachments, and all copies thereof on all computers and in any other form. Thank you. Navicent Health. http://www.navicenthealth.org/
Unsubscribe
Please remove my address from this listing. Steve DeGroat Manager, Enterprise Storage Foundational Services Yale University 203.436.4540 "If you build it, they will come." "There is no such thing as the cloud.it is simply someone else's computer."
UNSUBSCRIBE
Please remove my address from the listserv. Best regards, Lisa Seay | Systems Analyst l Florida Lottery | Systems, Network and Client Services 250 Marriott Drive, Tallahassee, FL 32301 (850) 487- 7704 | (850) 487- ext. 2059 flalottery.com PLEASE NOTE: Florida has a very broad public records law. Most written communications to or from state officials regarding state business are considered to be public records and will be made available to the public and the media upon request. Your email messages may, therefore, be subject to public disclosure.
Re: Moving archive data to a directory container
Hi Eric, I'd look into the replication first though. It 'should' work going from 6.3 to 7.1 (the other direction would not). Try with a small test node. - Thanks, Marc... Marc Lanteigne Accelerated Value Specialist for Spectrum Protect 416.478.0233 | marclantei...@ca.ibm.com Office Hours: Monday to Friday, 7:00 to 16:00 Eastern Follow me on: Twitter, developerWorks, LinkedIn -Original Message- From: Loon, Eric van (ITOPT3) - KLM [mailto:eric-van.l...@klm.com] Sent: Thursday, November 30, 2017 7:22 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Moving archive data to a directory container Hi Marc, I didn't know you can convert a storagepool into an already existing containerpool, thanks. I think I will remove some directories from the containerpool to make room for a new filepool. I will export all archives in there and convert it to the existing containerpool afterwards. As soon as all nodes are moved, I will delete the filepool and add the disks back to the containerpool. Thanks for your help! Kind regards, Eric van Loon Air France/KLM Storage Engineering -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Marc Lanteigne Sent: woensdag 29 november 2017 17:42 To: ADSM-L@VM.MARIST.EDU Subject: Re: Moving archive data to a directory container Hi, You might be able to use node replication to move the data from the old server into the new server. If you go with the import into a filepool method, you don't need two directory container pools, you can convert the filepool into the existing container pool. - Thanks, Marc... Marc Lanteigne Accelerated Value Specialist for Spectrum Protect 416.478.0233 | marclantei...@ca.ibm.com Office Hours: Monday to Friday, 7:00 to 16:00 Eastern Follow me on: Twitter, developerWorks, LinkedIn -Original Message- From: Loon, Eric van (ITOPT3) - KLM [mailto:eric-van.l...@klm.com] Sent: Wednesday, November 29, 2017 12:18 PM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Moving archive data to a directory container Hi guys! We are migrating our clients from a version 6 server to a new 7.1.7 server with a directory container pool. Switching clients is easy, just updating the option files and they will start a new backup cycle on the new TSM server. But a lot of clients also store long term archives. I can't think of a way to move the archives from the v6 server to the v7 server since import is not supported to a directory pool. The only trick I can come up with is defining a file pool on the v7 server, moving all archives in here and converting it to a directory container afterwards, but I need extra storage for it and I end up with two directory pools (at least until all archives are gone) and that is not what I want... Does anybody else know some trick to move these archives? Thanks for any help in advance! Kind regards, Eric van Loon Air France/KLM Storage Engineering For information, services and offers, please visit our web site: https://urldefense.proofpoint.com/v2/url?u=http-3A__www.klm.com=DwIFAg=jf_iaSHvJObTbx-siA1ZOg=hMBqtRSV0jXgOdXEmlNk_-O9LHkPCGSh9PJBRSlL8Q4=MHcroyMTlfnvImqh8Xh27U_KSsiOrHx1DbJnIMM3kLo=7tfcdgEk2ax4u5oKCXjTNUIys5evvzyXrdwJ2_hzr0o=. This e-mail and any attachment may contain confidential and privileged material intended for the addressee only. If you are not the addressee, you are notified that no part of the e-mail or any attachment may be disclosed, copied or distributed, and that any other action related to this e-mail or attachment is strictly prohibited, and may be unlawful. If you have received this e-mail by error, please notify the sender immediately by return e-mail, and delete this message. Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its employees shall not be liable for the incorrect or incomplete transmission of this e-mail or any attachments, nor responsible for any delay in receipt. Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal Dutch Airlines) is registered in Amstelveen, The Netherlands, with registered number 33014286 For information, services and offers, please visit our web site: https://urldefense.proofpoint.com/v2/url?u=http-3A__www.klm.com=DwIFAg=jf_iaSHvJObTbx-siA1ZOg=hMBqtRSV0jXgOdXEmlNk_-O9LHkPCGSh9PJBRSlL8Q4=ZIo2Q36FB054tvsgN9ytqNgLBt4MMY4kQ8gS6xSWfKs=24Xd0oBFBLBUtfWaXQv33MthMAHIDvk-E2xGlG4cGTo=. This e-mail and any attachment may contain confidential and privileged material intended for the addressee only. If you are not the addressee, you are notified that no part of the e-mail or any attachment may be disclosed, copied or distributed, and that any other action related to this e-mail or attachment is strictly prohibited,
Re: Moving archive data to a directory container
Hi Marc, I didn't know you can convert a storagepool into an already existing containerpool, thanks. I think I will remove some directories from the containerpool to make room for a new filepool. I will export all archives in there and convert it to the existing containerpool afterwards. As soon as all nodes are moved, I will delete the filepool and add the disks back to the containerpool. Thanks for your help! Kind regards, Eric van Loon Air France/KLM Storage Engineering -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Marc Lanteigne Sent: woensdag 29 november 2017 17:42 To: ADSM-L@VM.MARIST.EDU Subject: Re: Moving archive data to a directory container Hi, You might be able to use node replication to move the data from the old server into the new server. If you go with the import into a filepool method, you don't need two directory container pools, you can convert the filepool into the existing container pool. - Thanks, Marc... Marc Lanteigne Accelerated Value Specialist for Spectrum Protect 416.478.0233 | marclantei...@ca.ibm.com Office Hours: Monday to Friday, 7:00 to 16:00 Eastern Follow me on: Twitter, developerWorks, LinkedIn -Original Message- From: Loon, Eric van (ITOPT3) - KLM [mailto:eric-van.l...@klm.com] Sent: Wednesday, November 29, 2017 12:18 PM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Moving archive data to a directory container Hi guys! We are migrating our clients from a version 6 server to a new 7.1.7 server with a directory container pool. Switching clients is easy, just updating the option files and they will start a new backup cycle on the new TSM server. But a lot of clients also store long term archives. I can't think of a way to move the archives from the v6 server to the v7 server since import is not supported to a directory pool. The only trick I can come up with is defining a file pool on the v7 server, moving all archives in here and converting it to a directory container afterwards, but I need extra storage for it and I end up with two directory pools (at least until all archives are gone) and that is not what I want... Does anybody else know some trick to move these archives? Thanks for any help in advance! Kind regards, Eric van Loon Air France/KLM Storage Engineering For information, services and offers, please visit our web site: https://urldefense.proofpoint.com/v2/url?u=http-3A__www.klm.com=DwIFAg=jf_iaSHvJObTbx-siA1ZOg=hMBqtRSV0jXgOdXEmlNk_-O9LHkPCGSh9PJBRSlL8Q4=MHcroyMTlfnvImqh8Xh27U_KSsiOrHx1DbJnIMM3kLo=7tfcdgEk2ax4u5oKCXjTNUIys5evvzyXrdwJ2_hzr0o=. This e-mail and any attachment may contain confidential and privileged material intended for the addressee only. If you are not the addressee, you are notified that no part of the e-mail or any attachment may be disclosed, copied or distributed, and that any other action related to this e-mail or attachment is strictly prohibited, and may be unlawful. If you have received this e-mail by error, please notify the sender immediately by return e-mail, and delete this message. Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its employees shall not be liable for the incorrect or incomplete transmission of this e-mail or any attachments, nor responsible for any delay in receipt. Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal Dutch Airlines) is registered in Amstelveen, The Netherlands, with registered number 33014286 For information, services and offers, please visit our web site: http://www.klm.com. This e-mail and any attachment may contain confidential and privileged material intended for the addressee only. If you are not the addressee, you are notified that no part of the e-mail or any attachment may be disclosed, copied or distributed, and that any other action related to this e-mail or attachment is strictly prohibited, and may be unlawful. If you have received this e-mail by error, please notify the sender immediately by return e-mail, and delete this message. Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its employees shall not be liable for the incorrect or incomplete transmission of this e-mail or any attachments, nor responsible for any delay in receipt. Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal Dutch Airlines) is registered in Amstelveen, The Netherlands, with registered number 33014286
Re: Moving archive data to a directory container
Hi Stefan! In my case I can't upgrade the old source server since it's running a too old RedHat release... Kind regards, Eric van Loon Air France/KLM Storage Engineering -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Stefan Folkerts Sent: woensdag 29 november 2017 19:47 To: ADSM-L@VM.MARIST.EDU Subject: Re: Moving archive data to a directory container That's a way to do it, you do need to reduce max and offline reorg the database after the conversion to get everything to run at 100% speed without wasted database space after the conversion I prefer to upgrade the old server to 7.1.7 and replicate the data from tape/VTL/whatever to the new server running the containerpool, it works much beter than an export in my opinion, you have more control and it's much faster. If an upgrade isn't an option I would export to a filepool as Matthew suggested and convert that to a containerpool, be sure you have enough database space to hold the filepool metadata since it's about twice as much as the containerpool data and when you convert you need space for both types of metadata until you do your reorg and reduce max. Oh, you can reduce max at certain points during the conversion to reclaim some slack space on the database. On Wed, Nov 29, 2017 at 6:40 PM, Matthew McGeary < matthew.mcge...@potashcorp.com> wrote: > Node replication would be the only real way to go directly to the > container pool. > > You could define the file-class pool on the same storage directories > as the new container pool, so that once you land everything and > convert, you have two pools but don't waste any storage. > > __ > Matthew McGeary > Senior Technical Specialist - Infrastructure Management Services > PotashCorp > T: (306) 933-8921 > www.potashcorp.com > > > -Original Message- > From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf > Of Loon, Eric van (ITOPT3) - KLM > Sent: Wednesday, November 29, 2017 10:01 AM > To: ADSM-L@VM.MARIST.EDU > Subject: [EXT SENDER] [ADSM-L] Moving archive data to a directory > container > > Hi guys! > We are migrating our clients from a version 6 server to a new 7.1.7 > server with a directory container pool. Switching clients is easy, > just updating the option files and they will start a new backup cycle > on the new TSM server. But a lot of clients also store long term > archives. I can't think of a way to move the archives from the v6 > server to the v7 server since import is not supported to a directory > pool. The only trick I can come up with is defining a file pool on the > v7 server, moving all archives in here and converting it to a > directory container afterwards, but I need extra storage for it and I > end up with two directory pools (at least until all archives are gone) and > that is not what I want... > Does anybody else know some trick to move these archives? > Thanks for any help in advance! > Kind regards, > Eric van Loon > Air France/KLM Storage Engineering > > > For information, services and offers, please visit our web site: > https://urldefense.proofpoint.com/v2/url?u=http-3A__www.klm. > com=DwIFAg=tBK9IFHToo3Ip4kInV6npfSphg9iMZSnuvLLtDL_h5E= > 9B53f9OJCAaZMdwQs8Rx4OInzZ1vusLF8Ft4jfrywjo=S9QLT9cTnOfkB2BTaZyDF_ > kGAtfzMnQibS2mOIu3TwA=rv0g65y9vujKE7SdQFc7zspq6wHCYNRQ94RdB4lUYFE=. > This e-mail and any attachment may contain confidential and privileged > material intended for the addressee only. If you are not the > addressee, you are notified that no part of the e-mail or any > attachment may be disclosed, copied or distributed, and that any other > action related to this e-mail or attachment is strictly prohibited, > and may be unlawful. If you have received this e-mail by error, please > notify the sender immediately by return e-mail, and delete this message. > > Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or > its employees shall not be liable for the incorrect or incomplete > transmission of this e-mail or any attachments, nor responsible for any delay > in receipt. > Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal > Dutch > Airlines) is registered in Amstelveen, The Netherlands, with > registered number 33014286 > > For information, services and offers, please visit our web site: http://www.klm.com. This e-mail and any attachment may contain confidential and privileged material intended for the addressee only. If you are not the addressee, you are notified that no part of the e-mail or any attachment may be disclosed, copied or distributed, and that any other action related to this e-mail or attachment is strictly prohibited, and may be unlawful. If you have received this e-mail by error, please notify the sender immediately
