@jzhou thanks for your help on this issue! I have tried the -t option, but the problem still exists:
fdbrestore start --dest_cluster_file /etc/foundationdb/fdb.cluster -w -r file:///data/fdbbak/backup-2022-09-07-07-26-49.129822 -k a (here a is one test key)
...
Tag: default UID: 564836a4ed6519615050bc91c194164f State: starting Blocks: 0/0 BlocksInProgress: 0 Files: 0 BytesWritten: 0 CurrentVersion: -1 FirstConsistentVersion: 0 ApplyVersionLag: 0 LastError: ''Backup before 6.3 cannot be filtered with key ranges' on 'restore_start'' 4s ago.
...
And the -k operation can only support a specific key or key range? If customer has many key ranges, such as 300G data, how can we restore it to a higher version db?
I think restore old versions of backup to newer versions of FDB cluster is something not tested. In your case, it’s probably better to restore the backup to 6.2 cluster, then upgrade the cluster from 6.2 to 6.3.
@jzhou thanks for your suggestion! Now we still encounter some problem when upgrade fdb cluster from 6.2 to 6.3. After upgrade, I encounter the following error message:
...
Time="1662460973.975867" Severity="40" LogGroup="mdm-foundationdb-ibm" Process="fdbserver.1": Warning: FDBD has not joined the cluster after 5 seconds.
...
@jzhou I have not found any guide to introduce how to upgrade fdb cluster on k8s/ocp environment, so I just tried some way myself I just replaced the docker image for the fdb pod from 6.2 to 6.3. Before upgrade I set the skip to true for foundationdbcluster cr and delete all fdb pods, then I changed the cluster yaml file by replacing the image from 6.2 to 6.3, then set skip to false in cluster yaml file and reapply the yaml file, then the cluster rebuilt with 6.3 image. I have checked all fdb pods are running with 6.3 images now. Is there any additional steps need to do? Or you have any formal guide to introduce upgrade fdb on k8s environment? Thanks!
@jzhou@johscheuer I have checked the foundationdb code and found the following code:
...
// Old backup does not have metadata about key ranges and can not be filtered with key ranges.
if (keyRangesFilter.size() && results.second.empty() && !results.first.empty()) {
throw backup_not_filterable_with_key_ranges();
}
...
It seems fdb 6.2 backup does not have metadata about key ranges and can not be filtered with key ranges, right?
Is there any workaround to restore 6.2 backup into 6.3 database. Any more suggestion? Thanks!
I just replaced the docker image for the fdb pod from 6.2 to 6.3. Before upgrade I set the skip to true for foundationdbcluster cr and delete all fdb pods, then I changed the cluster yaml file by replacing the image from 6.2 to 6.3, then set skip to false in cluster yaml file and reapply the yaml file, then the cluster rebuilt with 6.3 image. I have checked all fdb pods are running with 6.3 images now. Is there any additional steps need to do? Or you have any formal guide to introduce upgrade fdb on k8s environment? Thanks!