Thankfully, NetWorker supports this (and has done for quite some time), via the interval<\/em> setting in groups. By default, this is set to “24:00” \u2013 24 hours. It can however be set to a smaller value, which will trigger the group to run more frequently.<\/p>\n Before we consider smaller intervals, lets first revisit the key timing settings involved in a traditional group:<\/p>\n Now, all these options are still used (and required) under higher frequency backups, with their meaning as follows:<\/p>\n So, let’s go back to that sample requirement \u2013 Oracle archived redo log backups run every 4 hours. Let’s consider setting up a new group that does this, with the backups starting at 00:01 initially, then running every 4 hours after that \u2013 i.e.,<\/p>\n Here’s what this group configuration would look like in NMC:<\/p>\n In the first pane, it looks fairly standard \u2013 setting a start time of 00:01, and enabling autostart. It’s the second pane where things are a little different:<\/p>\n Here, we set the interval to 4 hours, and the restart window to 2 hours.<\/p>\n — For the most part we run standard backups once every 24 hours \u2013 daily. A lot of the time if…<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_feature_clip_id":0,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_publicize_message":"","jetpack_publicize_feature_enabled":true,"jetpack_social_post_already_shared":false,"jetpack_social_options":{"image_generator_settings":{"template":"highway","default_image_id":0,"font":"","enabled":false},"version":2},"jetpack_post_was_ever_published":false},"categories":[6,16],"tags":[413,494,828,854,936],"class_list":["post-654","post","type-post","status-publish","format-standard","hentry","category-basics","category-networker","tag-group","tag-interval","tag-restart-window","tag-savegroup","tag-start-time"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n
\n
\n
![\"Group](\"http:\/\/nsrd.files.wordpress.com\/2009\/07\/nmc1.png\" "\\"Group")
![\"Group](\"http:\/\/nsrd.files.wordpress.com\/2009\/07\/nmc2.png\" "\\"Group")
\n* I’m told that there were some ‘fun’ numbers used by early NetWorker programmers. E.g., one of the original index checks used to run every ? weeks (or more correctly, every 22\/7 weeks). It’s possible that the critical situation engineer who told me this may have been pulling my leg however. I do<\/em> think though that given how so many people dislike backups, 03:33 may have been chosen as a start time as a play on 6:66!<\/p>\n","protected":false},"excerpt":{"rendered":"