apache / apache/cloudstack

Backup provider improvements

Ouverte
#12,280 1 commentaire 0 réactions 0 personnes assignées Voir sur GitHub
component:backup type:enhancement
Langage dominant
Java
Étoiles
3.1k
Forks
1.4k
Merge moyen
6 j 19 h
PR mergées (30 j)
32

Description

### The required feature described as a wish

Currently, with the backup implementation, I found the following issues/limitations

**Issue 1**

**Allow multiple backup framework providers at zone level**

**Steps to reproduce the issue**

1. Have a CloudStack environment with One zone and multiple clusters ( KVM. VMware)

2. Configure VEEAM for vmare cluster

https://docs.cloudstack.apache.org/en/4.22.0.0/adminguide/veeam_plugin.html

3. Configure NAS for KVM cluster

https://docs.cloudstack.apache.org/en/4.22.0.0/adminguide/nas_plugin.html#nas-backup-and-recovery-plugin

4. Configure the Global setting "backup.framework.provider.plugin" = veeam.nas

Image

5. Navigate to Service offering > Backup offering

Image

```

2025-12-17 07:24:28,644 ERROR [c.c.a.AlertManagerImpl] (CapacityChecker:[ctx-96786e18]) (logid:0203c46c) Exception in CapacityChecker com.cloud.utils.exception.CloudRuntimeException: Failed to find backup provider by the name: veeam,nas
at org.apache.cloudstack.backup.BackupManagerImpl.getBackupProvider(BackupManagerImpl.java:1656)
at org.apache.cloudstack.backup.BackupManagerImpl.getBackupProvider(BackupManagerImpl.java:1648)
at org.apache.cloudstack.backup.BackupManagerImpl.getBackupStorageUsedStats(BackupManagerImpl.java:2262)
at org.apache.cloudstack.backup.BackupManagerImpl.getBackupStorageUsedStats(BackupManagerImpl.java:176)
at jdk.internal.reflect.GeneratedMethodAccessor417.invoke(Unknown Source)
at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.base/java.lang.reflect.Method.invoke(Method.java:569)
at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:344)

```

**Current behaviour**

Currently, only one Backup framework is allowed per zone, it would be

**Expected behaviour**

It would be great if we could configure the "backup.framework.provider.plugin" at cluster level rather than zone level or support multiple backup providers at zone level

---------------
**Issue 2**

**Associate the backup offerings based on the hypervisor or cluster**

**Steps to reproduce the issue**

1. Have multiple backup offerings one for kvm and one for vmware

Image

2. Navigate to deploy vm form Compute > Select a KVM host or KVM template , all the backup offering are displayed

Similarly, select a VMWare host or vmware template , all the backup offering are displayed

Image

3. Similarly, in the instance view all the backup offerings are displayed

Image

**Expected behaviour**

It would be great if we could display the backup offerings based on the hypervisor or cluster type ( KVM or vmware)

Guide de contribution

Ouvrir le guide de contribution

Piste de recherche

Commencez par les emplacements de BackupManagerImpl.java indiqués dans la stack trace et lisez la documentation liée des plugins Veeam et NAS. Reproduisez la configuration de la zone et examinez les vues de déploiement et d’instance de Compute décrites dans l’issue. C’est terminé lorsque plusieurs providers peuvent coexister comme requis et que les offres de backup sont filtrées selon l’hyperviseur ou le type de cluster.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Évaluation

Stack technique
java
Domaine
backend, cloud, infrastructure
Type d'issue
Fonctionnalité
Difficulté
5/5
Temps estimé
Plus d'une semaine
Activité
Active
Clarté
Plutôt claire
Accessibilité débutants
35/100

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.