That's what "versions" are all about in V/Seg-Plus. A new version is ... well, when one "appears". That may not happen for weeks, months, or years! It sounds like V/Seg-Plus already does what you're saying it would be nice to have ...
JR JR (Steven) Imler CA Senior Software Engineer Tel: +1 703 708 3479 Fax: +1 703 708 3267 [EMAIL PROTECTED] -----Original Message----- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Rob van der Heij Sent: Sunday, September 10, 2006 06:22 PM To: [email protected] Subject: Re: Saving a backup copy of NSSs with no tape drive On 9/10/06, Imler, Steven J <[EMAIL PROTECTED]> wrote: > As mentioned previously, CA V/Seg-Plus is configurable to keep as many > previous versions as you want for potential restore ... I believe the > default is 3 to accommodate Rob's suggested scenario, but again it's > configurable. The idea to keep "a number of versions" works for conventional backup schemes where backups are made on a regular basis (e.g. daily, weekly, whatever works) because the number also implies a minimum retention period. The neat idea that Alan suggested (which probably just came up while writing his post ;-) ) to notify a virtual machine of the new SDF is a bit different because it does not have that fixed timing anymore. You would need to have some additional rules to avoid running through your versions very fast, and in the end you're not so different from the daily backup again. Rob
