Bonjour Eric, One thing that might help:
On the old server: - use COPY DOMAIN to copy the existing domain to a new domain - use UPDATE NODE to switch the node to be in the new domain - use EXPORT POLICY to export the new domain to the new server On the new server, update the archive copy groups in the new domain to point to the file pool. This will ensure that the new server has all the right retentions for this node, then from the old server, export the node. And I'm like Uwe, I don't think an export should change the ARCHVE_DATE in the ACHIVES table. It's certainly not mentioned in the help. - Thanks, Marc... Marc Lanteigne Spectrum Protect Specialist AVP / SRT IBM Systems, Spectrum Protect / Plus +1-506-460-9074 <- New phone number marclantei...@ca.ibm.com Office Hours: Monday to Friday, 7:00 to 15:30 Eastern IBM -----Original Message----- From: Uwe Schreiber <uwe.h.schrei...@t-online.de> Sent: Wednesday, January 6, 2021 01:58 PM To: ADSM-L@VM.MARIST.EDU Subject: [EXTERNAL] Re: [ADSM-L] Moving long term archives to new server Hi Erik, if the management class which was used at the source server is not defined on the new server, then the default management class on the target server will be used for the imported objects. To keep the retention it is required to define the management classes on the target server as on the source server. Regards, Uwe -----Original Message----- From: ADSM: Dist Stor Manager <ADSM-L@VM.MARIST.EDU> On Behalf Of Loon, Eric van (ITOP NS) - KLM Sent: Mittwoch, 6. Januar 2021 17:31 To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Moving long term archives to new server Hi Uwe, No, they are not. Both the policy domain names and the management class names have changed... I don't think the convert changes the retention, I think they are reset during the export from the old to the new server. The new server seems to treat them as new archives and thus the counter starts at 0. Kind regards, Eric van Loon Air France/KLM Storage & Backup -----Original Message----- From: ADSM: Dist Stor Manager <ADSM-L@VM.MARIST.EDU> On Behalf Of Uwe Schreiber Sent: woensdag 6 januari 2021 16:55 To: ADSM-L@VM.MARIST.EDU Subject: Re: Moving long term archives to new server Hi Eric, are the definitions regarding - Name of policy domain where the node is assigned to - Naming of management classes - Retention setting in achive copy groups identical on both servers? Converting the filepool to a container pool should not reset any retention settings. Regards, Uwe -----Original Message----- From: ADSM: Dist Stor Manager <ADSM-L@VM.MARIST.EDU> On Behalf Of Loon, Eric van (ITOP NS) - KLM Sent: Mittwoch, 6. Januar 2021 16:32 To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Moving long term archives to new server Hi all, I need to move long term archives (10 years+) from an old server (6.3 with virtual tapes) to a new server (8.1.11 with directory containers). The only way to do this is by exporting the data to a temporary filepool and convert this to the containerpool afterwards. The problem is that this resets the archive retention. So an archive file created 5 years ago with a retention of 10 years, will again be stored for 10 years on the new server. Has anybody found a better way to move such data to a new server with a container pool? Thanks in advance for any help! Kind regards, Eric van Loon Air France/KLM Storage & Backup ******************************************************** 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 ******************************************************** ******************************************************** 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 ********************************************************
