-
The backup failure is because GCS could not handle the number of request at that specific point in time. This is because if the rate-limiting on the GCS side. But, in this particular scenario, there c…
-
3 remaining in 'failure type' state. attempting to resend them to the backup path has not worked, failing with the same EVSS502 error (yes, on the backup path).
[[2927910,
["1721752973",
{"time…
-
### Description
As written in the title, Vorta does not turn off the computer after running the backup. I use the following code:
Post-backup: `shutdown -h now`
I use the following operating system…
-
### Report
Performance degradation in large deployments after upgrade from PSMDB operator 1.14.0 to 1.16.1
* we tested the upgrade in our DEV environment and did not see any issues with performance
…
-
### Report
We're running several psmdb clusters in multiple kubernetes clusters. For most of them the psmdb-backup failed at least once during their lifetime. We have three psmdb clusters where the b…
-
backport https://github.com/longhorn/longhorn/issues/9168
-
Even though the database is clustered and the underlying volumes are replicated by Longhorn, there should be a regular backup job for the stored data.
There is a [backup job](https://github.com/bit…
-
**Describe the problem**
A backup job remains in 'running' status indefinitely.
```
> show job 964456310328033281; …
-
### Describe the bug
az backup vault update --name {vault-name} --resource-group {rg} --classic-alert disable
When I enter the command, I get a python error message. The items in the brackets are ju…
-
## Describe the bug
> Hello everyone,
We are running Longhorn version 1.6.1 on multiple clusters, with 6-10 nodes each. We have set up a RecurringJob of type backup to run on each cluster once a d…