Preserving SFS last reference date across a restore

[Kris Buelens]

This weekend we have to regenerate an SFS filepool that became much too big.
As we do have processes that use the file creation and last reference
dates, so we'd like to preserve them. When we tested this quite some months
ago we found a problem:
- when we use VM:Backup to do a full restore, the creation date is
kept, but the lastref date is set to the restore date.
- when using FILEPOOL BACKUP/RESTORE, the last reference date is kept
but the creation date gets set to the restore date.
My idea was to save the dates of all files (we have this ready) and using
DMSOPCAT, DMSRDCAT and DMSWRCAT to restore the last reference date. But
when I open the catalog for FILESPACE with intent READ, DMSRDCAT returns the
records in which I can find all file dates, but a DMSWRCAT is forbidden (csl
reasoncode 56400); if I open the catalog for FILESPACE with intent WRITE, a
DMSRDCAT directly fails with reason 56400.

So, I am stuck. ANyone knows a solution?

Kris,
IBM Belgium, VM customer support

[Imler, Steven J]

Kris,

If you run (VM:Backup) HiDRO ... All three dates for *files* are
preserved when they are restored. The only date that end up to be the
date of the restore/rebuild are the Create_Date for Directories. This
is because they are "restored" by issuing the CREATE DIRECTORY COMMAND.

JR (Steven) Imler
CA
Senior Software Engineer
Tel: [phone]
Fax: [phone]
***@ca.com

-----Original Message-----
From: VM/ESA and z/VM Discussions [mailto:VMESA-***@LISTSERV.UARK.EDU] On
Behalf Of Kris Buelens
Sent: Friday, March 10, 2006 08:22 AM
To: VMESA-***@LISTSERV.UARK.EDU
Subject: Preserving SFS last reference date across a restore

This weekend we have to regenerate an SFS filepool that became much too
b=
ig.
As we do have processes that use the file creation and last reference
dates, so we'd like to preserve them. When we tested this quite some
mon=
ths
ago we found a problem:
- when we use VM:Backup to do a full restore, the creation date is
kept, but the lastref date is set to the restore date.
- when using FILEPOOL BACKUP/RESTORE, the last reference date is kept
but the creation date gets set to the restore date.
My idea was to save the dates of all files (we have this ready) and
using=

DMSOPCAT, DMSRDCAT and DMSWRCAT to restore the last reference date. But
when I open the catalog for FILESPACE with intent READ, DMSRDCAT returns
=
the
records in which I can find all file dates, but a DMSWRCAT is forbidden
(=
csl
reasoncode 56400); if I open the catalog for FILESPACE with intent
WRITE,=
a
DMSRDCAT directly fails with reason 56400.

So, I am stuck. ANyone knows a solution?

Kris,
IBM Belgium, VM customer support

[Kris Buelens]

Yesterday I got a private note from Susan Farrel. And so I tested again:
.... and I was proven wrong (or a bit wrong that is)
- FILEPOOL BACKUP/RESTORE preserves all dates
- FILEPOOL UNLOAD/RELOAD does not (the last-ref date is wrong)
So, I'm surprized that the most recent tool is less good than the old one
that exists since VM/SP R6 days.

At the other hand, we already started installing HiDRO too. But I don't
know if we will ever use it as we are somewhat in a hurry. And, FILEPOOL
BACKUP/RESTORE also transparantly backups/restores files migrated by
DFSMS. Does HiDRO supports that too?

Kris,
IBM Belgium, VM customer support




"Imler, Steven J" <***@ca.com>
Sent by: VM/ESA and z/VM Discussions <VMESA-***@LISTSERV.UARK.EDU>
2006-03-10 17:25
Please respond to
VM/ESA and z/VM Discussions


To
VMESA-***@LISTSERV.UARK.EDU
cc

Subject
Re: Preserving SFS last reference date across a restore






Kris,

If you run (VM:Backup) HiDRO ... All three dates for *files* are
preserved when they are restored. The only date that end up to be the
date of the restore/rebuild are the Create_Date for Directories. This
is because they are "restored" by issuing the CREATE DIRECTORY COMMAND.

JR (Steven) Imler
CA
Senior Software Engineer
Tel: [phone]
Fax: [phone]
***@ca.com

-----Original Message-----
From: VM/ESA and z/VM Discussions [mailto:VMESA-***@LISTSERV.UARK.EDU] On
Behalf Of Kris Buelens
Sent: Friday, March 10, 2006 08:22 AM
To: VMESA-***@LISTSERV.UARK.EDU
Subject: Preserving SFS last reference date across a restore

This weekend we have to regenerate an SFS filepool that became much too
b=
ig.
As we do have processes that use the file creation and last reference
dates, so we'd like to preserve them. When we tested this quite some
mon=
ths
ago we found a problem:
- when we use VM:Backup to do a full restore, the creation date is
kept, but the lastref date is set to the restore date.
- when using FILEPOOL BACKUP/RESTORE, the last reference date is kept
but the creation date gets set to the restore date.
My idea was to save the dates of all files (we have this ready) and
using=

DMSOPCAT, DMSRDCAT and DMSWRCAT to restore the last reference date. But
when I open the catalog for FILESPACE with intent READ, DMSRDCAT returns
=
the
records in which I can find all file dates, but a DMSWRCAT is forbidden
(=
csl
reasoncode 56400); if I open the catalog for FILESPACE with intent
WRITE,=
a
DMSRDCAT directly fails with reason 56400.

So, I am stuck. ANyone knows a solution?

Kris,
IBM Belgium, VM customer support

[Imler, Steven J]

HiDRO supports preserving the "migrated shell" for each file that has
been migrated. Therefore after you RESTORE/REGENERATE your FilePool(s),
touching a migrated file will trigger the RECALL mechanism of DFSMS as
you would expect.

When HiDRO backs up a FileSpace that contains migrated objects, a
message is put out stating that particular domain contains one or more
migrated objects.

JR (Steven) Imler
CA
Senior Software Engineer
Tel: [phone]
Fax: [phone]
***@ca.com

________________________________

From: VM/ESA and z/VM Discussions [mailto:VMESA-***@LISTSERV.UARK.EDU] On
Behalf Of Kris Buelens
Sent: Tuesday, March 14, 2006 06:25 AM
To: VMESA-***@LISTSERV.UARK.EDU
Subject: Re: Preserving SFS last reference date across a restore



Yesterday I got a private note from Susan Farrel. And so I tested
again: .... and I was proven wrong (or a bit wrong that is)
- FILEPOOL BACKUP/RESTORE preserves all dates
- FILEPOOL UNLOAD/RELOAD does not (the last-ref date is wrong)
So, I'm surprized that the most recent tool is less good than the old
one that exists since VM/SP R6 days.

At the other hand, we already started installing HiDRO too. But I don't
know if we will ever use it as we are somewhat in a hurry. And,
FILEPOOL BACKUP/RESTORE also transparantly backups/restores files
migrated by DFSMS. Does HiDRO supports that too?

Kris,
IBM Belgium, VM customer support




"Imler, Steven J" <***@ca.com>
Sent by: VM/ESA and z/VM Discussions <VMESA-***@LISTSERV.UARK.EDU>

2006-03-10 17:25
Please respond to
VM/ESA and z/VM Discussions


To
VMESA-***@LISTSERV.UARK.EDU
cc
Subject
Re: Preserving SFS last reference date across a restore






Kris,

If you run (VM:Backup) HiDRO ... All three dates for *files* are
preserved when they are restored. The only date that end up to be the
date of the restore/rebuild are the Create_Date for Directories. This
is because they are "restored" by issuing the CREATE DIRECTORY COMMAND.

JR (Steven) Imler
CA
Senior Software Engineer
Tel: [phone]
Fax: [phone]
***@ca.com

-----Original Message-----
From: VM/ESA and z/VM Discussions [mailto:VMESA-***@LISTSERV.UARK.EDU] On
Behalf Of Kris Buelens
Sent: Friday, March 10, 2006 08:22 AM
To: VMESA-***@LISTSERV.UARK.EDU
Subject: Preserving SFS last reference date across a restore

This weekend we have to regenerate an SFS filepool that became much too
b=
ig.
As we do have processes that use the file creation and last reference
dates, so we'd like to preserve them. When we tested this quite some
mon=
ths
ago we found a problem:
- when we use VM:Backup to do a full restore, the creation date is
kept, but the lastref date is set to the restore date.
- when using FILEPOOL BACKUP/RESTORE, the last reference date is kept
but the creation date gets set to the restore date.
My idea was to save the dates of all files (we have this ready) and
using=

DMSOPCAT, DMSRDCAT and DMSWRCAT to restore the last reference date. But
when I open the catalog for FILESPACE with intent READ, DMSRDCAT returns
=
the
records in which I can find all file dates, but a DMSWRCAT is forbidden
(=
csl
reasoncode 56400); if I open the catalog for FILESPACE with intent
WRITE,=
a
DMSRDCAT directly fails with reason 56400.

So, I am stuck. ANyone knows a solution?

Kris,
IBM Belgium, VM customer support