Why would you need to name savesets?<\/p>
Example: I made use of this in the process I outlined for backups of Linux KVM guests<\/a><\/strong>. (Using the -N savesetName<\/em> option in NetWorker, my script generated saveset names of hypervisor:<\/em>KVM:guestName:diskName<\/em>, making it easy to identify KVM backups in the mminfo output.)<\/p><\/blockquote>\n\n\n\n Let’s have another look at how you can make use of named savesets to beef up your recovery options using Linux.<\/p>\n\n\n\n When I used to be a Unix systems administrator, our team had scripts that ran on all the hosts we were responsible for, building up all the system rebuild data we might need in an emergency \u2013 copies of the filesystem tables, disk layouts, network configuration and a myriad of other details. (At the time, these were printed and stored for several months.)<\/p>\n\n\n\n So in this example, I’m going to outline a scenario of gathering critical rebuild information for systems and sending that data to NetWorker with a saveset name that makes it very clear what it is. The process will look like this:<\/p>\n\n\n\n So let’s start with the backup script:<\/p>\n\n\n\n I’ve called the script ‘nsrcritrebuild.sh’ and symbolically linked it to \/usr\/bin\/nsrcritrebuild.sh<\/strong>. (This puts it in the same directory as the NetWorker save command.) Assuming you have a directory of \/critrebuild on the server, the command generates the following information:<\/p>\n\n\n\n The command should be invoked as follows:<\/p>\n\n\n\n (If you’re wondering why I use -b poolName<\/em> rather than -p poolName<\/em>, it’s because NetWorker uses -b for the pool in commands like save<\/em>.)<\/p>\n\n\n\n So, if I wanted to generate a critical rebuild dataset and write it to the backup server orilla using the pool Backup_01 and keep it for 31 days, I’d invoke the command as follows:<\/p>\n\n\n\n Once the file is in place on the client and the \/critrebuild directory created, I can set it up within NetWorker. To do that, I need to define the pre-command correctly. Using the NWUI, you can see it as follows:<\/p>\n\n\n\n Once the critical rebuild script gathers the data, it fires off a manual saveset to the backup server, naming the saveset hostname<\/em>:CRITREBUILD. For my client, ‘totesrhelly’, that means if I do a mminfo query for its savesets, I get clear details of the rebuild saveset:<\/p>\n\n\n\n#!\/bin\/bash\n\nPATH=\/bin:\/sbin:\/usr\/bin:\/usr\/sbin\nexport PATH\n\nRebuildDir=\/critrebuild\nSERVER=null\nPOOL=null\nEXP=null\nHOST=`hostname`\n\nwhile getopts s:b:e: flag\ndo\n\tcase \"${flag}\" in\n\t\ts) SERVER=${OPTARG};;\n\t\tb) POOL=${OPTARG};;\n\t\te) EXP=${OPTARG};;\n\tesac\ndone\n\nif [ \"$SERVER\" = \"null\" ] || [ \"$POOL\" = \"null\" ] || [ \"$EXP\" = \"null\" ]\nthen\n\techo \"Your must specify -s server -b pool -e expiration\"\n\texit 1\nfi\n\nif [ ! -d $RebuildDir ]\nthen\n\techo You need to create $RebuildDir\n\texit 1\nelse\n\t# Let's get a start on.\n\tenv > $RebuildDir\/run_env.txt\n\trpm --query -a > $RebuildDir\/rpm_query_a.txt\n\tfdisk -l > $RebuildDir\/fdisk_l.txt\n\tmount > $RebuildDir\/mount.txt\n\tcat \/proc\/mdstat > $RebuildDir\/mdstat.txt\n\tifconfig -a > $RebuildDir\/ifconfig_a.txt\n\tnetstat -ar > $RebuildDir\/netstat_ar.txt\n\tlvm fullreport > $RebuildDir\/lvm_fullreport.txt\n\tsystemctl > $RebuildDir\/systemctl_list.txt\n\n\tsave -s $SERVER -b \"${POOL}\" -e \"+${EXP} days\" -N ${HOST}:CRITREBUILD $RebuildDir\nfi<\/code><\/pre>\n\n\n\n# nsrcritrebuild.sh -s backupServer<\/em> -b poolName<\/em> -e expirationInDays<\/em><\/strong><\/pre>\n\n\n\n
# nsrcritrebuild.sh -s orilla -b Backup_01 -e 31<\/strong><\/pre>\n\n\n\n
![\"Creating](\"https:\/\/nsrd.info\/blog\/wp-content\/uploads\/2021\/08\/critrebuildconfig.png\")
<\/a>![\"Special](\"https:\/\/nsrd.info\/blog\/wp-content\/uploads\/2021\/08\/critrebuildmminfo-2.png\")
<\/a>
![\"Special](\"https:\/\/nsrd.info\/blog\/wp-content\/uploads\/2021\/08\/critical-rebuild-saveset-in-NMC.png\")
<\/a>