Troubleshooting Backup for VPC

Volume backups were not made according to the backup plan

Volumes are not getting backed up on all scheduled times. For example, you created a schedule for backups in a backup plan to create daily backups. However, after the service created backups for a while as defined in the plan, the backups stop.

The issue can have one of the following causes.

• Your volume might be deattached after the successful backups were made.
• The volume tag that matched the tag for target resources might be deleted.
• The instance might not be running.
• Correct service-to-service authorizations might not be in place.

Verify that the volume wasn't detached from a virtual server instance. Search for the instance to which you last attached the volume from the list of all virtual server instances. Verify that the instance is running. Also, look at the backup policy and verify that the tags are present in the volume, in case the tag was inadvertently deleted. Scheduled backups do not occur instantly, so you might need to look again in an hour or so to verify that the backup was made.

Backup jobs are indicating a failed state

The backup failed, as indicated in the backup job details. When you make a GET /backup_policies/{backup_policy_id}/jobs/{backup_job_id} call, the status property shows failed.

Look at the reason_codes property in the response. It might be an internal error or the snapshot limit is reached.

Contact IBM support if you see an internal error. If the backup snapshot limit is reached, delete the oldest snapshots so new ones can be created. You can create up to 100 backup snapshots of a volume.

Backup policy is not created due to incorrect authorizations

A service authorization error is generated when you try to create a backup policy.

When you attempt to create a backup policy, an s2s service not completed error is generated, which indicates that incorrect service-to-service authorizations were set up. The backup policy creation fails. This behavior is expected, it prevents the backup policy from being created without proper authorization.

Establish correct service-to-service authorizations and try creating a backup policy again. For more information about setting up authorizations for the backup service, see Establishing service-to-service authorizations.

Backup policies are not found

You receive a backup_policies_not_found error with the following message: Backup policy with ID is not found.

The backup policy that you are trying to find is either deleted or never existed.

To address this error, list the policies and see whether the backup policy ID that you're looking for is in the list. If you still need help with the error, contact support.

For more information about viewing your backup policies, see Viewing backup policies.

Backup policy plan is not found

You receive a backup_policy_plan_not_found error with the following message: Backup policy plan with ID <policy_plan_uuid> is not found.

The backup policy plan that you are trying to find is either deleted or never existed.

To address this error, list the backup policy plans and see whether the plan ID that you're looking for is in the list. If you still need help with the error, contact support.

For more information about viewing your backup policies and plans, see Viewing backup policies.

Backup job is not found

You receive a backup_jobs_not_found error with the following message: Job with ID <backup_job_uuid> is not found.

The job that you are trying to find is either deleted or never existed.

To address this error, list the jobs and see whether the job ID that you're looking for is in the list. If you still need help with the error, contact support.

For more information about viewing your backup jobs list, see Viewing backup jobs.