Will these be only .backup files i.e. only restorable to the same piece of hardware? Or will it take config exports too? Even better, are .backup files being worked on so you can safely restore them across devices (same device type but different MACs etc)
I only use config expoorts myself at the moment but I hear of people having a lot of trouble trying to restore .backup files to a direct replacement device
This is a nice feature, but it has one weakness: You have to remove the backup before uploading a new one. In case the removal succeeds but the upload fails you do not have a backup at all (at least in cloud). So you should consider to either
provide two upload slots, so one backup can be removed while the other is still available or
change the upload that removal is not necessary and backup is replaced on successful upload only.
Back is for restore on the same device. If you restore a backup file on a different unit it will rewrite some configuration that might create issues for you.
I have a nightly backup script that sends e-mail. I get a backup file encrypted and also a export. Backup in case I F**k up and need to restore and export in case I need to change the unit.
Is the serial number the identifier for access to files? So only that unit can access the file?
at winbox window (where is cpu,memory info etc) would be nice to show last backup date (if exist) or saying “this device is not backup to mikrotik servers”.
when upload a backup for second time or more there should be a parameter “replace=yes” to overwrite current backup that exist on server. no need to apply the command “/system backup cloud remove-file number=0” before.
Yes here they are. I have switched from E-mail backups to FTP. So now all routers upload to a FTP server that then send the backup offsite. The reason is that the ISP I have thinks the backup generated e-mail where a sign that my SMTP account had been hacked and changed the password all the time. Here are both script.
I which I could say that I’m smart enough to take credit for these but I’m not I found the e-mail script on this forum and would credit the author if I remembered the name. FTP is just a slight rewrite which I did manage myself.
+1. Without two slots or a way to atomically replace the old backup with a successful new one, this feature is very limited in its usefulness. action=create-and-upload-replace would be the ideal way to do this.
when you upload file and print the information IP Cloud backup will return secret-download-key, using that you can get the file from anything running RouterOS
My rb760 is dead, yesterday a thunder killed him, I made a backup using the mikrotik cloud but I lost my key to download it,Can I recover my backup? or can you send it to me? with my serial number and my mac address
Now that we have a replace mechanism since version 6.45beta42 one culprit remains:
If the cloud server is not accessible for any reason the commands in “/ system backup cloud” give fatal errors. You can not catch these as runtime errors from a script:
On error the script will terminate in do-block. Any chance to fix that, janisk? (Already opened a ticket (Ticket#2019052022003204), but support told me this is not a runtime error. Meh!)
Hello, quick question, the change-log states that a “replace” command was added in 6.45.1, however if i do “action=replace” or if i just do action=tab no replace command is available.