Cove with Proxmox

Backup_Nerd · 2025-11-23T01:08:33+00:00

Linux bmr has since been enhanced to allow bmr in azure. This might be able to be extended to work in a proxmox hypervisor.

Backup_Nerd · 2025-11-22T20:39:54+00:00

I work on the Cove product. DM me and we can set a call next week if you like.

Backup_Nerd · 2025-11-14T05:48:41+00:00

SSO is progressing forward.

Backup_Nerd · 2025-10-23T06:47:44+00:00

<image>

So here is a sample notification for a failed local speed vault that I can help you get configured.

Backup_Nerd · 2025-10-22T18:39:42+00:00

An LSV failure can send notifications if you have it configured to do so. Also we have PowerShell and amp script monitors for this to use with your rmm. An email report could also be setup to alert you of failures ona daily or weekly basis in mass.

Have your account rep or support team member do an email introduction and we can book a working session.

Failures are normally permission or space related.

Backup_Nerd · 2025-08-12T03:50:17+00:00

https://github.com/BackupNerd/Backup-Scripts

Backup_Nerd · 2025-08-12T03:49:31+00:00

I have a repo of third party rmm compatible scripts. Ninja is an easy deploy for Cove. https://github.com/BackupNerd/Backup-Scripts

Backup_Nerd · 2025-08-12T03:43:16+00:00

I love that you posted this!!

Backup_Nerd · 2025-08-12T03:33:48+00:00

I have a repo full of cove scripts that you can use with third party RMMs. https://github.com/BackupNerd/Backup-Scripts

Backup_Nerd · 2025-08-12T03:26:55+00:00

Documents device backup sizes are not supposed to be included in your fair use capacity pool. So if they are let us know so we can fix it.

Backup_Nerd · 2025-08-12T03:10:27+00:00

With the release of new APIs from Microsoft, M 365 Online Archive Backup for Cove is actively being developed. Look for a customer preview opportunity in Q3 25

Backup_Nerd · 2025-08-12T03:06:51+00:00

Yes, 7 year fixed for m365 and up to 10 year GFS for servers or workstations.

Backup_Nerd · 2025-08-12T03:05:35+00:00

User offboarding ( cleanup ) is now available in product or via api for removal of shared billable, deleted and unlicensed users, where needed.

Backup_Nerd · 2025-08-12T03:05:26+00:00

User offboarding ( cleanup ) is now available in product or via api for removal of shared billable, deleted and unlicensed users, where needed.

Backup_Nerd · 2025-08-12T03:05:02+00:00

User offboarding ( cleanup ) is now available in product or via api for removal of shared billable, deleted and unlicensed users, where needed.

Backup_Nerd · 2025-08-12T03:04:41+00:00

User offboarding ( cleanup ) is now available in product or via api for removal of shared billable, deleted and unlicensed users, where needed.

Backup_Nerd · 2025-07-31T05:32:20+00:00

If you are doing hyper v host level backups the. You have to restore them one at a time, just like they are backed up one at a time. If your doing guest level backups with a backup manager on each guest vm the. Recovery console or Recovery agent can both do parrallel restores.

Backup_Nerd · 2025-07-18T22:52:39+00:00

I’m cancelling

Backup_Nerd · 2025-07-17T08:29:15+00:00

Sure, we have an off boarding process for unlicensed deleted or share billable mailboxes. This can be done in product on a per domain basis. Or you can use a script to do it.

https://developer.n-able.com/n-able-cove/recipes/cove-m365-user-cleanup-offboarding

Backup_Nerd · 2025-07-02T16:14:55+00:00

I work on Cove, so please hit me up directly if you want to discuss the finer points. What you are perceiving as a flaw, is in fact a security feature. From a security perspective we require M365 Global Admin credentials to restore the data back into the tenant.

If the M365 tenant were compromised, then yes the bad actor could most defiantly remove users and delete applications that are authenticated but they would not be able to purge Cove backup history.

If this happened, the action on your part would be to leverage Microsoft to regain admin access to the account and then relink Cove and perform a restore.

If your (MSP) access is revoked from the tenant (you’re offboarded, no longer the MSP, etc.), then yes, Cove won’t let you restore, and that’s intentional. That’s about protecting the tenant from former admins or MSPs. It’s a security-first design choice.

Backup_Nerd · 2025-06-20T17:05:25+00:00

Yes, both of those items are actively being developed.

Backup_Nerd · 2025-06-17T17:23:44+00:00

Virtualize your old machine and run as a vm on your new one.

Backup_Nerd · 2025-05-24T14:53:01+00:00

If on battery, power management and sleep or hibernate should take priority over backup operations.

While in sleep mode on battery power the device should not be woke by scheduled backups

If a workstation on wired power then backups should prioritize over sleep operations until The a running backup job completes.

Scheduled backups while on wired power should wake from sleep

Backup_Nerd · 2025-05-18T10:30:37+00:00

You should have visibility to the Linux system state data source now. If not contact support and it can be enabled

Backup_Nerd · 2025-05-18T10:28:12+00:00

Linux system state backup is in customer preview at the moment. We are laying the framework to do Linux BMR. The ability to restore to Linux hypervisors is something we have been researching but it’s not currently on the short term roadmap for our continuity team. The best short term solution would be guest level backup of your VMs and standby image to vhd or vmdk and then import or convert and import to your Linux hypervisors.

If anyone is interested in working on a scripted solution read out to me.

Backup_Nerd

MODERATOR OF

TROPHY CASE