NetWorker Blog

Commentary from a long term NetWorker consultant and Backup Theorist

  • This blog has moved!

    This blog has now moved to nsrd.info/blog. Please jump across to the new site for the latest articles (and all old archived articles).
  •  


     


     

  • Enterprise Systems Backup and Recovery

    If you find this blog interesting, and either have an interest in or work in data protection/backup and recovery environments, you should check out my book, Enterprise Systems Backup and Recovery: A Corporate Insurance Policy. Designed for system administrators and managers alike, it focuses on features, policies, procedures and the human element to ensuring that your company has a suitable and working backup system rather than just a bunch of copies made by unrelated software, hardware and processes.
  • This blog has moved!

    This blog has now moved to nsrd.info/blog. Please jump across to the new site for the latest articles (and all old archived articles).
  •  


     


     

  • Twitter

    Error: Twitter did not respond. Please wait a few minutes and refresh this page.

NetWorker 7.5 and changes to browse/retention times

Posted by Preston on 2009-06-20

Documented in the NetWorker 7.5 release notes, and a topic of much discussion at the moment on the NetWorker mailing list is the topic of browse/retention times in NetWorker 7.5.

The change that has occurred is that browse and retention times are now always set to 23:59:59 on the day of expiry.

So, in 7.4.x and below, if you a backup completed at 09:00 on Monday, and the browse/retention time was set for 1 day, the backup would expire at 09:00 Tuesday.

Under 7.5.x however, that same backup will instead expire on Tuesday at 23:59:59.

While this may be an unexpected behaviour for a lot of sites (assuming the release notes haven’t been read…) for the most part it shouldn’t cause too much of an issue in an environment with adequately resourced media. However, if you’re suddenly finding now that you’ve upgraded to 7.5 that some backups aren’t being released quite when you expect, this may be an alternate explanation to standard dependency checking issues…

Advertisements

Sorry, the comment form is closed at this time.

 
%d bloggers like this: