Last updated：2021-04-28 11:04:02
Mirroring-based back-to-origin is used to migrate data to KS3 seamlessly. This feature allows you to migrate any service that already runs on a user-created origin or in another cloud service to KS3 without interrupting services. In this case, you can use mirroring-based back-to-origin to migrate data without stopping the service.
After you configure mirroring-based back-to-origin rules for a bucket, and you request to access a file (Object) that does not exist in KS3, KS3 will return a 302 redirect request with the location pointing to the origin server; at the same time, KS3 will also request this file (Object) from the origin server asynchronously and save it to KS3.
- When you use the mirroring-based back-to-origin feature to migrate the data, maximum size of a single file supported is 50 GB.
- When you access a file that does not exist on KS3, the request will trigger KS3 to download the file from the origin server asynchronously. KS3 will download the file as soon as possible and save it in KS3, but KS3 does not guarantee the time duration and success rate.
- You can configure multiple mirroring origins at the same time which will be separated by English “;”. During the back-to-origin operation, the file will be pulled back according to the origin server configuration sequence. After the file is pulled successfully, no try will made to pull the file from the remaining origin servers.
You can pull the file from the mirroring origin to KS3 according to the resource list in the template, and store it according to the predefined rules.
Notes: The file pre-push configuration will appear only after you configure the mirroring-based back-to-origin feature, this is not supported for the bucket of the Archive storage class.
Did you find the above information helpful?
Please give us your feedback.
Thank you for your feedback.