Automated Backups

It is useful to have both textual and binary backups since the textual backup (without sensitive data, such as passwords) can be read by a human to understand the router configuration, while the latter (binary) can be used to restore configuration (with sensitive data) with ease. However, the binary configuration is more prone to corruption.

Schedule: Textual Backup
/system scheduler add comment="Backup running config in textual format without sensitive data" interval=1w name=runningConfigDump on-event="export file=/flash/mtikconf-nosensitive terse" policy=ftp,reboot,read,write,policy,test,password,sniff,sensitive,romon start-date=apr/10/2000 start-time=12:00:00

Schedule: Binary Backup
/system scheduler add comment="Backup config as binary" interval=1w name=binBackup on-event="system backup save name=/flash/mtikAP.backup" policy=ftp,reboot,read,write,policy,test,password,sniff,sensitive,romon start-date=apr/10/2000 start-time=12:00:00

Script: Email the backup file with system resource and health report (can be scheduled to run periodically)
#Local Strings
:local rPrint [:tostr [/system resource print as-value]];
:local hPrint [:tostr [/system health print as-value]];

#Merged Strings
:local strMerged ("Resource: \n".$rPrint."\n\nHealth: \n".$hPrint);
:local strSplit value="";

:if ([:find $strMerged ";" -1] > 0) do={
 :for i from=0 to=([:len $strMerged] -1) step=1 do={
  :local escapeChar value=[:pick $strMerged $i];
  :if ($escapeChar = ";") do={ :set escapeChar value="\n" };
  :set strSplit value=($strSplit.$escapeChar);

/tool e-mail send to="[email protected]" subject="Router backup - $[/system identity get name] - $[/system clock get date]" body="$strSplit" file=mtik.backup