/save is an important command, even if you have access to the ui console, as often you want to force a save before the server is stopped. If you are using a hosting service it totally depends on how they have things configured and set up as to where a save is done when you click a 'stop' or 'restart command'. If they don't have command scripts that run before the shutdown is executed that send the command to save you could risk losing back to the last auto save the game did. This has been an issue for some server admin with hosted servers. Now they have a way to send a save command before they live the game and click the stop clink/button in they game control panel. The most they will lose at that point would be the time between when they issue that command and when they clicked stop. For those with hosts that already send a save command to the server before sending the shutdown command, this really is not that important but its nice to have in other cases. If for some reason you server started acting up and lagging very badly or showing other errors, being able to tell it to save from in the game in case its thinking about crashing is always helpful. This is the same command that is run by what you set in the Storage.eco for saving the game.
the /backup command is what is run by the configuration you have set in the Backup.eco which backups your Game.eco, the db files and makes a backup file in the Storage./Backups/. You will have set how many backups to retain, say 10 for example, but if you to a /backup from in game you will see an extra backup in the Storage/Backup folder unless the next time autobackup runs, and removes the files that exceed the number you said to save - but its a way to know the command is working.
I have been listed as Admin all the time, and had several log in/out 's and a few server restarts.
I can use the /give command by now, but it happened after we had to generate a new world and a server restart efter the meteor hit..