>
>> I am having an issue where when I use the REST API to connect a snapshot from
>> another VM to a Backup-Appliance-VM, after the clone when I remove the Disk
>> and delete the Snapshot, the disk remains in the Backup-Appliance-VM as
>> /dev/sdb ot /dev/vdb.
>>
>> If I reboot the Bakup-Applic
On Jan 22, 2018 5:32 PM, "Zip" wrote:
I am having an issue where when I use the REST API to connect a snapshot
> from another VM to a Backup-Appliance-VM, after the clone when I remove the
> Disk and delete the Snapshot, the disk remains in the Backup-Appliance-VM
> as /dev/sdb ot /dev/vdb.
>
>
> I am having an issue where when I use the REST API to connect a snapshot from
> another VM to a Backup-Appliance-VM, after the clone when I remove the Disk
> and delete the Snapshot, the disk remains in the Backup-Appliance-VM as
> /dev/sdb ot /dev/vdb.
>
> If I reboot the Bakup-Applicance-VM t
On Mon, Jan 22, 2018 at 7:21 AM, Zip wrote:
> I am having an issue where when I use the REST API to connect a snapshot
> from another VM to a Backup-Appliance-VM, after the clone when I remove the
> Disk and delete the Snapshot, the disk remains in the Backup-Appliance-VM
> as /dev/sdb ot /dev/vd
I am having an issue where when I use the REST API to connect a snapshot
from another VM to a Backup-Appliance-VM, after the clone when I remove the
Disk and delete the Snapshot, the disk remains in the Backup-Appliance-VM as
/dev/sdb ot /dev/vdb.
If I reboot the Bakup-Applicance-VM the disk disap
5 matches
Mail list logo