volser-restore-create-timestamp-not-touched-on-incremental-20031114
authorKris Van Hees <aedil-afs@alchar.org>
Sat, 15 Nov 2003 04:02:37 +0000 (04:02 +0000)
committerDerrick Brashear <shadow@dementia.org>
Sat, 15 Nov 2003 04:02:37 +0000 (04:02 +0000)
commit76d2b6dabbf251a0e4e4149ba2da1395d9db9954
tree9acd186dd4ab0947748cbaa06f8d312f131bb5c6
parente0d79ffeb6f456bbd6cc506752c7b166f43308eb
volser-restore-create-timestamp-not-touched-on-incremental-20031114

FIXES 2521

        The issue: when you restore an incremental dump to an existing volume,
the creation timestamp of the target volume gets reset to the current timestamp
(literally the timestamp of when the 'vos restore' command is being executed).
That messes things up for any subsequent 'vos release' operation, because such
operation then needs to do a full release rather than an incremental one.  For
large volumes that can be quite an issue.
src/volser/vsprocs.c