![]() ![]() These cookies ensure basic functionalities and security features of the website, anonymously. failureReason: The reason for failure if the state is FAILED.Necessary cookies are absolutely essential for the website to function properly.details: Gives the state of each partition's backup.IN_PROGRESS if at least one partition's backup is in progress.INCOMPLETE if at least one partition's backup does not exist.In this case, failureReason contains a string describing the reason for failure. FAILED if at least one partition has failed.COMPLETED if all partitions have completed the backup.state: Gives the overall status of the backup.When the response is 200 OK, the response body consists of a JSON object describing the state of the backup. Zeebe failed to process the request within a pre-determined timeout. Zeebe has encountered issues while communicating to different brokers. Refer to the returned error message for more details. Refer to the returned error message for details.Īll other errors. Request īackup state could be determined and is returned in the response body (see example below). The following request can be used to start a backup. Client-side encryption keys are not supported.Customer-supplied encryption keys are not supported.Customer-managed encryption keys are supported if they are set as.This is enabled by default for all GCS buckets. Default server-side encryption is fully supported.There are multiple data encryption options, some of which are supported by Zeebe: If you need more control, you can customize authentication by setting environment variable GOOGLE_APPLICATION_CREDENTIALS. In many cases, these credentials are automatically provided by the runtime environment. This can be any string that is a valid object name, for example the name of your cluster.Īuthentication is handled by Application Default Credentials. When basePath is set, Zeebe will only create and access objects under this path. Setting a basePath is not required but useful if you want to use the same bucket for multiple Zeebe clusters. To prevent misconfiguration, Zeebe will check at startup that the specified bucket exists and can be accessed. The bucket specified with bucketName must already exist, Zeebe will not try to create one for you. More compression algorithms are available check commons-compress for a full list. We recommend using zstd as it provides a good trade off between compression ratio and resource usage. You can enable compression by specifying a compression algorithm to use. Compression and buffering of compressed files can have a negative effect if Zeebe is heavily resource constrained. Zeebe compresses backup data immediately before uploading to S3 and buffers the compressed files in a temporary directory. To reduce S3 storage costs and upload times, you can enable backup compression. Backup compression īackups can be large depending on your usage of Zeebe. Other S3 compatible services might have similar features that should work as well. Using default bucket encryption gives you control over the encryption keys and algorithms while being completely transparent with Zeebe.Ĭombined with TLS between Zeebe and the S3 API, backups are fully encrypted in transit and at rest. For AWS S3, this means enabling default bucket encryption. Zeebe does not support backup encryption natively, but it can use encrypted S3 buckets. ZEEBE_BROKER_DATA_BACKUP_S3_SECRETKEY - Specify the secret key.ZEEBE_BROKER_DATA_BACKUP_S3_ACCESSKEY - If either accessKey or secretKey is not provided, the credentials are determined from the environment. ![]() ZEEBE_BROKER_DATA_BACKUP_S3_REGION - If no region is provided, it is determined from the environment.ZEEBE_BROKER_DATA_BACKUP_S3_ENDPOINT - If no endpoint is provided, it is determined based on the configured region.ZEEBE_BROKER_DATA_BACKUP_S3_BASEPATH - If the bucket is shared with other Zeebe clusters, a unique basePath must be configured.ZEEBE_BROKER_DATA_BACKUP_S3_BUCKETNAME - The backup is stored in this bucket.ZEEBE_BROKER_DATA_BACKUP_STORE - Set this to S3 to store backups in S3 buckets.Alternatively, you can configure backup store using environment variables: ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |