Unimus forum

Yes, the easiest way is to just delete the unimus.properties file at - Linux - /etc/unimus - Windows - C:\ProgramData\Unimus this will "reset" Unimus and trigger the wizard again. Alternatively, you can just edit relevant properties found in the configuration file above: - changing databas...

This is a good feature to have in future and we do have a ticket for that. I will add this thread to our internal ticket and once we bring this feature out, I will update this thread.

In this case, yes, it is possible to downgrade. When we talk 2.2.4, it is possible to downgrade to whether 2.2.3 or 2.2.2 at most. If you run Unimus on Windows, you could just download an older version of the installer, whether one for 2.2.2 or 2.2.3 https://download.unimus.net/unimus/2.2.2/Installe...

Yes, that is correct https://wiki.unimus.net/display/UNPUB/Discovery#Discovery-Scheduledbackups Also, as for the errors. If the possible reason why would the devices manifesting failing (an outage, etc) is unknown, then feel free to gather debug logs for us and we can take a peek at them to see what...

Hello, My main question would be, what is your schedule like? When Unimus runs a scheduled backup, it first runs a discovery (on all devices using that schedule). If I may, I would like to link to our Wiki article for Unimus' Discovery https://wiki.unimus.net/display/UNPUB/Discovery If the discovery...

I have emailed you back describing a possible temporary solution of setting up a temp VM just to get device backups up and running as soon as possible while we can resolve the issue with the existing instance.

This issue, unfortunately, from looking into logs, seems problematic as it started happening suddenly without any clear indication in the logs of what might be a specific cause. We also see in the logs that since Sep 16th after a restart of Unimus, Unimus doesn't seem to be able to fully start. We s...

Hello,

Let me check up on that with our team and I will get back to you.

Hello,

Thank you for the report. I can confirm this is a bug. We have already identified the cause and fixed it. The fix will be available in the next release (it will be most likely a beta release for 2.3.0). As soon as that happens, I will update this thread.

The current behavior is technically correct as we added the option for an API key to have an access to credentials only recently and mainly for the new Credentials endpoint in API v3, but this is a good point you raised. We will update our current Devices endpoint in v2 to unmask passwords if an API...