After the backup service is down,use the following body to create a backup:
{
"backup": { "container": null, "description": null,
"name": "backup001", "volume_id": "64f5d2fb-d836-4063-b7e2-544d5c1ff607", "snapshot_id": "64h8d5fb-d096-4098-n8y9-j998sj8dh6tg5",
}
}
Backup failure is reasonable. But the volume status has been changed to None, which is problematic.
When there is a "snapshot_id" field in the body, it should be the backup created based on the snapshot. The snapshot status should be changed, and the volume status should not be changed.
After the backup service is down,use the following body to create a backup:
"container" : null,
"description" : null,
"volume_ id": "64f5d2fb- d836-4063- b7e2-544d5c1ff6 07",
"snapshot_ id": "64h8d5fb- d096-4098- n8y9-j998sj8dh6 tg5",
{
"backup": {
"name": "backup001",
}
}
Backup failure is reasonable. But the volume status has been changed to None, which is problematic.
When there is a "snapshot_id" field in the body, it should be the backup created based on the snapshot. The snapshot status should be changed, and the volume status should not be changed.