Hi Marc,
I think that was indeed the mistake in the past. I performed several tests and
with the default parameters, archives properly expire as expected.
Thanks for your help!
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 Marc Lanteigne
Sent: donderdag 25 februari 2021 15:41
To: ADSM-L@VM.MARIST.EDU
Subject: Re: Moving long term archives to new server
I was working on something today and came across some info about IMPORT and
remembered this thread.
When importing, there is a DATE option and it has 2 possible values, ABSOLUTE
and RELATIVE. Use absolute to keep the backup/archive date and it will expire
as expected. Use relative to reset the backup/archive date to today.
Dates
Specifies whether the dates for the file copies are set as the same date
when the files were exported, or is adjusted to the import date.
This parameter supports the following values:
Absolute
The dates for file copies are set to the values specified when the
files were exported.
Relative
The dates for file copies are adjusted to the import date.
The default value is ABSOLUTE.
-
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: Marcelo Urbano Lima - mul...@br.ibm.com <mul...@br.ibm.com>
Sent: Wednesday, January 6, 2021 02:56 PM
To: ADSM-L@VM.MARIST.EDU
Subject: [EXTERNAL] Re: [ADSM-L] Moving long term archives to new server
It's been a long while since I exported/imported data to remember exactly how
it behaves but just to give another point of view, imagine that you exported
data to a tape and it's sitting there in a rack way past its original
expiration date.
Once it's exported it's no longer bound to a management class in a server with
expiration running everyday. It's like an external entity now, just a bunch of
importable data on a tape.
Now, right after you decide and import it back to a server it would be a weird
behavior if the next expiration removed it right away, just because its
original archive_date/expiration was from years ago, in a server that you no
longer care (thus you exported the data in a more neutral format)...
even though it still remembers its original class name.
Regards
--
Marcelo Urbano Lima
-----Original Message-----
From: Marc Lanteigne
<marclantei...@ca.ibm.com<mailto:marc%20lanteigne%20%3cmarclantei...@ca.ibm.com%3e>>
Reply-To: ADSM: Dist Stor Manager
<ADSM-L@VM.MARIST.EDU<mailto:%22ADSM:%20dist%20stor%20manager%22%20%3cads...@vm.marist.edu%3e>>
To: ADSM-L@VM.MARIST.EDU<mailto:ADSM-L@VM.MARIST.EDU>
Subject: [EXTERNAL] Re: [ADSM-L] Moving long term archives to new server
Date: Wed, 06 Jan 2021 18:19:23 +0000
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
<mailto:marclantei...@ca.ibm.com>
marclantei...@ca.ibm.com
Office Hours: Monday to Friday, 7:00 to 15:30 Eastern
IBM
-----Original Message-----
From: Uwe Schreiber <
<mailto:uwe.h.schrei...@t-online.de>
uwe.h.schrei...@t-online.de
>
Sent: Wednesday, January 6, 2021 01:58 PM
To:
<mailto:ADSM-L@VM.MARIST.EDU>
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 <
<mailto:ADSM-L@VM.MARIST.EDU>
ADSM-L@VM.MARIST.EDU
> On Behalf Of Loon,
Eric van (ITOP NS) - KLM
Sent: Mittwoch, 6. Januar 2021 17:31
To:
<mailto:ADSM-L@VM.MARIST.EDU>
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 <
<mailto:ADSM-L@VM.MARIST.EDU>
ADSM-L@VM.MARIST.EDU
> On Behalf Of Uwe
Schreiber
Sent: woensdag 6 januari 2021 16:55
To:
<mailto:ADSM-L@VM.MARIST.EDU>
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 <
<mailto:ADSM-L@VM.MARIST.EDU>
ADSM-L@VM.MARIST.EDU
> On Behalf Of Loon,
Eric van (ITOP NS) - KLM
Sent: Mittwoch, 6. Januar 2021 16:32
To:
<mailto:ADSM-L@VM.MARIST.EDU>
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:
<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.klm.com&d=DwIGaQ&c=jf_iaSHvJObTbx-siA1ZOg&r=hMBqtRSV0jXgOdXEmlNk_-O9LHkPCGSh9PJBRSlL8Q4&m=ajy424TQR_PTQuPfO4p_vErnEdun20OM75fm7MN3J6k&s=lso9pCkIuOmNJeBytRSZx3iXR-Te5g3P16Bj65suKY0&e=
>
https://urldefense.proofpoint.com/v2/url?u=http-3A__www.klm.com&d=DwIGaQ&c=jf_iaSHvJObTbx-siA1ZOg&r=hMBqtRSV0jXgOdXEmlNk_-O9LHkPCGSh9PJBRSlL8Q4&m=ajy424TQR_PTQuPfO4p_vErnEdun20OM75fm7MN3J6k&s=lso9pCkIuOmNJeBytRSZx3iXR-Te5g3P16Bj65suKY0&e=
.
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&d=DwIGaQ&c=jf_iaSHvJObTbx-siA1ZOg&r=hMBqtRSV0jXgOdXEmlNk_-O9LHkPCGSh9PJBRSlL8Q4&m=ajy424TQR_PTQuPfO4p_vErnEdun20OM75fm7MN3J6k&s=lso9pCkIuOmNJeBytRSZx3iXR-Te5g3P16Bj65suKY0&e=
>
https://urldefense.proofpoint.com/v2/url?u=http-3A__www.klm.com&d=DwIGaQ&c=jf_iaSHvJObTbx-siA1ZOg&r=hMBqtRSV0jXgOdXEmlNk_-O9LHkPCGSh9PJBRSlL8Q4&m=ajy424TQR_PTQuPfO4p_vErnEdun20OM75fm7MN3J6k&s=lso9pCkIuOmNJeBytRSZx3iXR-Te5g3P16Bj65suKY0&e=
.
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
********************************************************
