Mirror-back-source is mainly used to seamlessly migrate data to KS3, that is, when your service has been running on the origin established by yourself or on other cloud products, you need to migrate data to KS3, but you cannot stop the service. At this time, you can use the Mirror-back-source.
When the bucket is configured with Mirror-back-source, the user accesses a object to KS3, and the object is not saved in KS3, KS3 will return a 302 redirection request with location pointing to the origin to the user;meanwhile, KS3 will asynchronously request the object from the origin and save it to KS3.
- Use the Mirror-back-source Service for data migration, and the maximum support for a single object is 50GB.
- When a user accesses a object that does not exist on KS3, KS3 will download the object asynchronously from the origin, and KS3 will download the object and save it in KS3 as soon as possible, but KS3 does not guarantee the time and success rate.
- KS3 supports the configuration of multiple origins at the same time. The origins are separated by the separator ";".KS3 will pull data according to the configuration sequence of the origin. After the pull is successful, it will not attempt to pull data from the remaining origin.
After setting up the origin, the origin resources will be automatically and smoothly migrated to KS3.The access format is as follows:
(Note: the storage space of KS3 cannot be used as a origion).The data from origion will be synchronized to the setting space by default.
After the origin is configured, because the content of the origin and ks3 storage space are basically the same, the origin may be blocked by the search engine. You can configure the search engine configuration file
robots.txtto avoid this situation.
You can set the objects uploaded to KS3 as public or private.
Note: when the origin source is configured, the File-pre-push configuration will appear
According to the list of resources in the template, you can pull data from the origin to KS3 and store it according to the set rules.