{"id":6178,"date":"2026-08-13T12:16:00","date_gmt":"2026-08-13T12:16:00","guid":{"rendered":"https:\/\/www.easydcim.com\/blog\/?p=6178"},"modified":"2026-08-13T12:31:11","modified_gmt":"2026-08-13T12:31:11","slug":"easydcim-v1-27-0","status":"publish","type":"post","link":"https:\/\/www.easydcim.com\/blog\/easydcim-v1-27-0","title":{"rendered":"Take control of your backups with EasyDCIM v1.27.0"},"content":{"rendered":"

A few days ago, we published our Security Hardening Guide<\/strong><\/a>, a practical checklist to help you keep EasyDCIM in good shape over time. Putting it together also got us thinking: what if we can turn some of that advice into tools you can use directly in EasyDCIM?<\/p>\n

Backup and recovery gave us the perfect place to start. In the guide, we encouraged you to test recovery, not just backups<\/strong>, so we took that advice a step further and built an all-new extension: Backup Manager<\/strong><\/a> that brings backup creation, storage, protection, verification and recovery preparation into one place.<\/p>\n

And this is how we arrive at EasyDCIM v1.27.0<\/strong>. Backup Manager takes center stage, joined by device change notifications, LDAP directory login, more flexible IPv4 allocation, and plenty of other improvements. Let’s get into it!<\/p>\n

A backup is only as good as what happens next<\/strong><\/p>\n

Getting data into a backup is one thing. Getting the right data back out, from the right copy, in a form you can trust and restore, is a much better measure of how solid your backup process really is.<\/p>\n

Backup Manager For EasyDCIM<\/strong><\/a> brings that entire process into the EasyDCIM Admin Area. You can schedule backups or run them on demand and decide what goes into each one: the SQL database<\/strong>, application files<\/strong>, InfluxDB data<\/strong>, or all three. Backup history keeps previous runs in view, while health checks and file checksums help verify that the copies you expect to have are really there.<\/p>\n\n\n

\"Backup<\/a><\/figure>\n\n\n

Keeping every backup next to the system it protects would rather defeat the purpose, so copies can also be sent to multiple SFTP<\/strong> and S3-compatible storage destinations<\/strong>. Local and remote backups have independent retention policies, and optional age encryption<\/strong> protects the archives wherever you decide to keep them.<\/p>\n\n\n

\"Backup<\/a><\/figure>\n\n\n

Of course, all of this leads to the moment that puts every backup to the test: recovery<\/strong>. Backup Manager lets you download a complete archive or individual files, retrieve a remote copy back to the EasyDCIM host and follow a guided workflow that walks you through the required decryption and restore commands. EasyDCIM gets everything ready, while the final restore stays under administrator control.<\/p>\n\n\n

\n
\"Backup<\/a><\/figure>\n\n\n\n
\"Backup<\/a><\/figure>\n<\/figure>\n\n\n

The new extension also happens to address a very real weak spot in backup strategies.<\/p>\n

\n
BACKUP REALITY CHECK<\/div>\n\n\n\n
\n
90%<\/div>\n
of organizations were confident they could recover from a cyber incident within their recovery objectives<\/div>\n<\/td>\n
\n
28%<\/div>\n
of ransomware victims actually managed to fully restore all affected data<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

That is a sizeable gap between having confidence in your recovery plan and watching it work when it has to, as shown by Veeam’s 2026 research<\/span><\/a>.<\/p>\n<\/blockquote>\n

With Backup Manager, that test becomes easier to prepare for before you actually need it.<\/p>\n

Changes worth passing on<\/strong><\/p>\n

A changed inventory status or device field can mean much more than a different value in a database. It may matter to an automation, an external platform or another team, and waiting for the next synchronization or manual check is not always good enough.<\/p>\n

EasyDCIM v1.27.0 adds two new events for exactly this purpose: Device Field Changed<\/strong> and Device Metadata Changed<\/strong>. They can trigger notification actions whenever selected device fields or metadata are updated.<\/p>\n\n\n

\n
\"Device<\/a><\/figure>\n\n\n\n
\"Device<\/a><\/figure>\n<\/figure>\n\n\n

It is a small distinction with plenty of room for automation behind it, especially when EasyDCIM is already exchanging data with other systems across your infrastructure.<\/p>\n

\n
For example<\/div>\n
Instead of telling an integration that a device is currently
\nassigned<\/strong>
\nEasyDCIM can pass the actual change:<\/div>\n

\navailable<\/span>\u2192<\/span>assigned<\/span>
\n<\/span><\/div>\n
Result:<\/strong> The receiving system gets both sides of the change, giving automations enough context to trigger the right action immediately.<\/div>\n<\/div>\n

Let your directory do the login<\/strong><\/p>\n

If your users already have accounts in Active Directory, OpenLDAP or FreeIPA, there is little joy in giving them another password to remember and giving administrators another set of credentials to manage.<\/p>\n

With LDAP Authentication 1.0.1<\/strong><\/a>, synchronized directory users can now sign in to both the Admin Area and Client Area with their existing credentials. Secure LDAPS and StartTLS connections<\/strong> are supported, while local authentication remains available alongside LDAP.<\/p>\n

We have also added priorities to LDAP group-to-role mappings, so when a user belongs to several directory groups, EasyDCIM has a clear way to decide which role mapping should take precedence.<\/p>\n

<\/p>\n

For environments where directory services already handle identity across the rest of the infrastructure, EasyDCIM can now fit into the same setup instead of running beside it with its own login rules.<\/p>\n

Not every IP request needs a subnet<\/strong><\/p>\n

With IP Address Management 1.8.11<\/strong><\/a>, you can now request a specific number of individual IPv4 addresses and have EasyDCIM allocate them from selected source pools or from all eligible IPv4 pools. The allocation remains consistent when provisioning runs again, while the existing subnet mode continues to work exactly where you need it.<\/p>\n

We have tightened up the surrounding logic too. Excluded IPv4 addresses are now kept out of primary, additional and custom IP metadata assignments, and existing subnets can be moved to a different parent through the GUI or API without recreating them and losing their data.<\/p>\n

Network information exposed to customers and integrations has become more complete as well. API v3 and the Client Area can now return the subnet in CIDR notation, gateway and netmask<\/strong> alongside assigned IP addresses, giving consumers of that data more context without requiring additional lookups.<\/p>\n

Better behaved metrics, VLANs and polling<\/strong><\/p>\n

Long-running systems tend to expose problems that are hard to see in a fresh installation, so a good part of version 1.27.0 deals with keeping accumulated infrastructure data tidy.<\/p>\n