{"id":6390,"date":"2017-08-03T07:26:45","date_gmt":"2017-08-02T21:26:45","guid":{"rendered":"http:\/\/nsrd.info\/blog\/?p=6390"},"modified":"2018-12-11T08:32:13","modified_gmt":"2018-12-10T22:32:13","slug":"networker-9-2-capacity-measurement","status":"publish","type":"post","link":"https:\/\/nsrd.info\/blog\/2017\/08\/03\/networker-9-2-capacity-measurement\/","title":{"rendered":"NetWorker 9.2 Capacity Measurement"},"content":{"rendered":"

As I’ve mentioned in the past, there’s a few different licensing models<\/a> for NetWorker, but capacity licensing (e.g., 100 TB front end backup size) gives considerable flexibility, effectively enabling all product functionality within a single license, thereby allowing NetWorker usage to adapt to suit the changing needs of the business.<\/p>\n

\"Data<\/a><\/p>\n

In the past, measuring utilisation has typically required either the use of DPA or asking your DellEMC account team to review the environment and provide a report. NetWorker 9.2 however gives you a new, self-managed option \u2013 the ability to run, whenever you want, a capacity measurement report to determine what your utilisation ratio is.<\/p>\n

This is done through a new command line tool, nsrcapinfo<\/em>, which is incredibly simple to run. In fact, running it without any options at all will give the default 60 day report, providing utilisation details for each of the key data types as well as summary. For instance, against my lab server, here’s the output:<\/p>\n

<?xml version=\"1.0\" encoding=\"UTF8\" standalone=\"yes\" ?>\n<!--\n~ Copyright (c) 2017 Dell EMC Corporation. All Rights Reserved.\n~\n~ This software contains the intellectual property of Dell EMC Corporation or is licensed to\n~ Dell EMC Corporation from third parties. Use of this software and the intellectual property\n~ contained therein is expressly limited to the terms and conditions of the License\n~ Agreement under which it is provided by or on behalf of Dell EMC.\n-->\n<Capacity_Estimate_Report>\n<Time_Stamp>2017-08-02T21:21:18Z<\/Time_Stamp>\n<Clients>13<\/Clients>\n<DB2>0.0000<\/DB2>\n<Informix>0.0000<\/Informix>\n<IQ>0.0000<\/IQ>\n<Lotus>0.0000<\/Lotus>\n<MySQL>0.0000<\/MySQL>\n<Sybase>0.0000<\/Sybase>\n<Oracle>0.0000<\/Oracle>\n<SAP_HANA>0.0000<\/SAP_HANA>\n<SAP_Oracle>0.0000<\/SAP_Oracle>\n<Exchange_NMM8.x>0.0000<\/Exchange_NMM8.x>\n<Exchange_NMM9.x>0.0000<\/Exchange_NMM9.x>\n<Hyper-V>0.0000<\/Hyper-V>\n<SharePoint>0.0000<\/SharePoint>\n<SQL_VDI>0.0000<\/SQL_VDI>\n<SQL_VSS>0.0000<\/SQL_VSS>\n<Meditech>0.0000<\/Meditech>\n<Other_Applications>2678.0691<\/Other_Applications>\n<Unix_Filesystems>599.9214<\/Unix_Filesystems>\n<VMware_Filesystems>360.3535<\/VMware_Filesystems>\n<Windows_Filesystems>27.8482<\/Windows_Filesystems>\n<Total_Largest_Filesystem_Fulls>988.1231<\/Total_Largest_Filesystem_Fulls>\n<Peak_Daily_Applications>2678.0691<\/Peak_Daily_Applications>\n<Capacity_Estimate>3666.1921<\/Capacity_Estimate>\n<Unit_of_Measure_Bytes_per_GiB>1073741824<\/Unit_of_Measure_Bytes_per_GiB>\n<Days_Measured>60<\/Days_Measured>\n<\/Capacity_Estimate_Report><\/pre>\n
That’s in XML by default – and the numbers are in GiB<\/a>.<\/p>\n
If you do fulls on longer cycles than the default of a 60 day measurement window you can extend the data sampling range by using -d nDays<\/em> in the command (e.g., “nsrcapinfo -d 90” would provide a measurement over a 90 day window). You can also, if you wish for further analysis, generate additional reports (see the command reference guide or, man nsrcapinfo<\/em> if you’re on Linux for the full details). One of those reports that I think will be quite popular with backup administrators will be the client report. An example of that is below:<\/p>\n
[root@orilla ~]# nsrcapinfo -r clients<\/strong>\n\"Hostname\", \"Client_Capacity_GiB\", \"Application_Names\" \n\"abydos.turbamentis.int\", \"2.3518\", \"Unix_Filesystems\"\n\"vulcan\", \"16.0158\", \"VMware_Filesystems\"\n\"win01\", \"80.0785\", \"VMware_Filesystems\"\n\"picon\", \"40.0394\", \"VMware_Filesystems\"\n\"win02\", \"80.0788\", \"VMware_Filesystems\"\n\"vega\", \"64.0625\", \"VMware_Filesystems\"\n\"test02\", \"16.0157\", \"VMware_Filesystems\"\n\"test03\", \"16.0157\", \"VMware_Filesystems\"\n\"test01\", \"16.0157\", \"VMware_Filesystems\"\n\"krell\", \"32.0314\", \"VMware_Filesystems\"\n\"faraway.turbamentis.int\", \"27.8482\", \"Windows_Filesystems\"\n\"orilla.turbamentis.int\", \"1119.5321\", \"Other_Applications Unix_Filesystems\"\n\"rama.turbamentis.int\", \"2156.1067\", \"Other_Applications Unix_Filesystems\"<\/pre>\n
That’s a straight-up simple view of the FETB estimation for each client you’re protecting in your environment.<\/p>\n
There you have it – capacity measurement in NetWorker as a native function in version 9.2.<\/p>\n","protected":false},"excerpt":{"rendered":"
As I’ve mentioned in the past, there’s a few different licensing models for NetWorker, but capacity licensing (e.g., 100 TB…<\/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":true,"jetpack_social_options":{"image_generator_settings":{"template":"highway","default_image_id":0,"font":"","enabled":false},"version":2},"jetpack_post_was_ever_published":false},"categories":[14,16,20],"tags":[195,1391,1392,1249,822],"class_list":["post-6390","post","type-post","status-publish","format-standard","hentry","category-licensing","category-networker","category-scripting","tag-capacity","tag-fetb","tag-measurement","tag-networker","tag-reporting"],"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