Hey Benoit,
I am also interested is such integration to external vendor for XCP
hypervisor.
Lately my attention is in other matters but I do begun thinking on an
external solution for a cold backup. Here is a design concept:
Backup:
1. ACS framework does occasional volume backups and keeps them
on NFS share (hot backup)
2. Veeam collects the backup folder structure and contents once
every X and keeps it on tape (cold backup)
In this case ACS framework is what the backup solution for hot backup
and Veeam is for cold.
Hot restore:
1. Happens through ACS Framework and is done by the end user.
Cold restore:
1. admin dumps a cold backup to a NFS
2. in an automated manner single or all volumes are imported
into ACS and assigned to the proper account owners of the original VMs.
3. ACS user restore VMs from volumes as Hot restore.
From everything above what is not possible is how the restored folder structure
and volumes can be automatically imported and assigned to the proper accounts?
What I came up it as least effort solution that also is resilient is on the
backup NFS server to make a cron script that executes once an hour and scans
the /backup partition.
ACS NFS backup partition has the following structure
/<shared paritition>/snapshots/account_id/VOLUME_ID
/master_and_delta_files
In each VOLUME_ID directory a YAML file will be created listing:
- owner acc id
- origin volume id
- origin volume name (taken from ACS DB)
- list of mater and delta files
Consecutive runs of the script will compare if VOLUME_ID folder
contents are different than the YAML and will update it. Usually that will
before Veeam backup occurs.
Then Veeam backup will occur.
There is one caveat here - hot backups can occur anytime depending on
user settings while cold backup happens once per time frame. There can be the
case where cold backup occurs while hot backup jobs are running. This should be
avoided.
When restore is required specific volume will be restored from Veeam
and with restore shell script it will take the volume YAML conif:
- converge deltas
- set new volume name as RESTORED_<original_volume_name>
- import the volume to ACS under the origin account ID
Moreover a secondary script can create VMs from volumes for a case of
mass cold restore but that will be at later stage.
Again that is just a concept and if anyone has an idea on how to
improve or simplify that will be great!
Best regards,
Jordan
-----Original Message-----
From: benoit lair <kurushi4...@gmail.com>
Sent: 02 септември 2021 г. 18:36
To: users@cloudstack.apache.org
Subject: Re: XCP-ng Backup Cloudstack 4.15
[X] This message came from outside your organization
Is there a way to implement ourself a custom external provider in order to
backup VMs ?
Le jeu. 2 sept. 2021 à 15:52, benoit lair <kurushi4...@gmail.com> a écrit :
> Hello,
>
> I am interested too in doing Backup VM for Xcp-NG Would you have a
> solution for using Veeam like Yordan aims ?
>
> Le lun. 12 juil. 2021 à 13:30, Abishek Budhathoki <abckd...@gmail.com>
> a écrit :
>
>> Thank You for the response. Really apricated.
>>
>> On 2021/07/12 09:41:07, Rohit Yadav <rohit.ya...@shapeblue.com> wrote:
>> > Hi Abishek,
>> >
>> > That's right, the current Backup & Recovery framework only supports
>> Veeam provider on VMware.
>> >
>> > For XenServer/xcpng, we don't have a plugin/provider, however
>> > volume
>> snapshots can be used to backup snapshots on secondary storage.
>> >
>> > Regards.
>> >
>> > Regards,
>> > Rohit Yadav
>> >
>> > ________________________________
>> > From: Abishek Budhathoki <abckd...@gmail.com>
>> > Sent: Saturday, July 10, 2021 7:42:12 PM
>> > To: users@cloudstack.apache.org <users@cloudstack.apache.org>
>> > Subject: XCP-ng Backup Cloudstack 4.15
>> >
>> > Hello EveryOne,
>> >
>> > I am trying cloudstack with xen environment. I was trying out the
>> backup feature of the cloudstack and was not able to achieve it. Does
>> the backup work in xen environment or it strictly only works with vmware
>> only.
>> >
>> >
>> >
>> >
>> >
>> >
>>
>
