Furkan,
I understand your use-case. You want to make it possible to configure
a clean installation of NetBackup completely from CloudStack. One
important issue to consider is "How to make it vi-friendly?". I mean
what if people configure the CloudStack side and the NetBackup side?
If they are conflicting, who wins and how is integrity guaranteed.
I think it is possible to implement an initialisation procedure in the
provider that checks if a minimal set of configuration is available
and create it if not. That could be a first step.
I read between the lines that you also want an exportBackupProfile
API. That would be a framework level addition. Ambitious but not
impossible I think.
happy hacking,

On Thu, Aug 14, 2025 at 9:11 AM Furkan Doğmuş
<furkandogmus9...@gmail.com> wrote:
>
> Hi Jithin,
>
> Thanks for your explanation regarding the Backup & Recovery framework
> design.
>
> I’ve been reviewing the existing backup provider integrations (e.g., Veeam)
> and have started working on a similar integration for *NetBackup*,
> targeting the *KVM hypervisor*.
> I understand that in the current design, predefined configurations and
> policies must be set up on the provider side, imported into CloudStack as
> offerings, and then cloned per instance.
>
> While I understand this is intentional in the current framework, I’d like
> to explore if there are ways to make the provider-side setup for NetBackup
> more automated — for example, automatically creating the required storage
> units, policies, or schedules during the plugin’s registration or offering
> creation, instead of requiring these steps to be completed manually
> beforehand.
>
> I’m cc’ing the *dev@cloudstack.apache.org <dev@cloudstack.apache.org>*
> mailing list to see if other developers have attempted similar approaches
> or have suggestions for enhancing automation in the provider integration
> process.
>
> Any guidance or references (including code from existing providers that
> implement similar automation) would be greatly appreciated.
>
> Best regards,
> Furkan Doğmuş
>
> >



-- 
Daan

Reply via email to