Basics – No two groups should start simultaneously
One of the most common configuration issues I see is where multiple NetWorker groups are configured to start simultaneously. For example, you might see a situation where say: Daily Servers Monthly...
View ArticleClik here to view.
Basics – Achieving higher frequency backups
For the most part we run standard backups once every 24 hours – daily. A lot of the time if you need to meet recovery point objectives smaller than this, you’ll be looking at complimenting backups with...
View ArticleClient inactivity timeout is not group timeout
One of the settings that can be made within a group is the ‘inactivity timeout’ setting. This refers to client inactivity. This is often erroneously considered to be a group timeout setting, but it’s...
View ArticleClik here to view.
Large group backups
A very traditional approach to configuring automated backups in NetWorker is to make use of the schedule override feature in NetWorker groups. That is, by defining either a schedule or a level at the...
View ArticleClik here to view.
Best Practice – Groups
There’s a few very important rules to follow when it comes to NetWorker groups: Maintain an air-gap: Ensure there’s at least 5, preferably 10 minutes, between the start time for any two NetWorker...
View Article
