{"id":1586,"date":"2010-01-06T06:41:26","date_gmt":"2010-01-05T20:41:26","guid":{"rendered":"http:\/\/nsrd.info\/blog\/?p=1586"},"modified":"2010-01-06T06:41:26","modified_gmt":"2010-01-05T20:41:26","slug":"the-top-10-for-2009","status":"publish","type":"post","link":"https:\/\/nsrd.info\/blog\/2010\/01\/06\/the-top-10-for-2009\/","title":{"rendered":"The top 10 for 2009"},"content":{"rendered":"

Looking at the stats both for this new site and the previous site, I’ve compiled a list of the top 10 read articles on The NetWorker Blog<\/em> for 2009. The top 3 of course match the three articles that routinely turn out to be the most popular on any given month, which speaks something of their relevance to the average NetWorker administrator.<\/p>\n

(Note: I’ve excluded non-article pages<\/em> from the top 10.)<\/p>\n

Number 10 \u2013 Instantiating Savesets<\/h3>\n

The very first article on the blog, Instantiating Savesets<\/a> detailed the importance of distinguishing between all instances of a saveset<\/em> and a specific instance of a saveset<\/em>.<\/p>\n

This distinction between using just the saveset ID, and using a saveset ID\/clone ID combination becomes particularly important when staging from disk backup units. If clones exist and you stage using just<\/em> the saveset ID, when NetWorker cleans up at the end of the staging operation it will remove reference to the clones as well as deleting the original from the disk backup unit. (Something you really<\/em> don’t want to have happen.)<\/p>\n

Recommendation to EMC<\/strong>: Perhaps it would be worthwhile requiring a “-y” argument to nsrstage<\/em> if staging savesets from disk backup units and specifying only the saveset ID.<\/p>\n

Recommendation to NetWorker administrators<\/strong>: Always be careful when staging that you specify both the saveset and the clone ID.<\/p>\n

Number 9 \u2013 Basics \u2013 Important mminfo fields<\/h3>\n

In May I wrote about a few key mminfo<\/a> fields \u2013 notably:<\/p>\n