Originally from the User Slack
@Phil_GebhardtPhil_Gebhardt**:** Hi everyone,
I’m new to ScyllaDB, and I’m trying to restore all keyspaces from a backup, but receiving an error I’m having trouble getting past.
This is how I’m attempting the backup using ScyllaDB Manager’s sctool
kubectl exec deployment/scylla-manager -n scylla-manager -- \
sctool restore --cluster scylladb/scylla \
--location $LOCATION \
--snapshot-tag $TAG \
--keyspace '*' --restore-tables
When I try this, I receive:
Error: get restore target, units and views: init target: find not restored tables: get all tables: GET /column_family/name: expected exactly 1 colon in '<keyspace>:<table>', got 2
I’ve tried all sorts of different inputs for --keyspace with no luck. Any help would be greatly app@Felipe_Cardeneti_Mendeseciated!
@Felipe_Cardeneti_Mendes**:** hmm this is a ScyllaDB API (as in port 10000 through the reserve proxy) call. I wonder if the scylla version is incompatible with the request issued by the Manager? Though I dont re@Phil_Gebhardtall seeing this endpoint change
@Phil_Gebhardt**:** Thanks for looking at this Felipe, I suspected versions as well but according to the compatibility matrix, I think what I am running should be compatible.
scylla-manager:3.4.0@sha256:6424c36929b39ef4e679ee7d61578b1070e28c186b23b278147fde8e391d9db1
scylla-manager-agent:3.4.0@sha256:441403aed8880cad1feef68aa7a8ee9ffd99a458dc1dcff3dc54ce5bf3cb07b7
scylla:6.1.4@sha256:bce2034bae63d1a1669aa4f82ef78f327747fa88ee9f166e69099eca0277b620
I should also mention that I am using alternator. I did just find this epic #4509. Is it possible that my restore problems stem @Felipe_Cardeneti_Mendesrom being on a version before these ch@Phil_Gebhardtnges?
@Felipe_Cardeneti_Mendes**:**@Felipe_Cardeneti_Mendesgood catch, so that explains it.
@Phil_Gebhardt**:** Thanks for your eyes on this
@Felipe_Cardeneti_Mendes**:** IIRC alternator follows a specific naming convention which was known to fail when calling the API.
btw you miiiight be able to get it running with a recent Manager - we literally stopped updating the compatibility list and running regression tests on older releases as – well, we no longer support them
docker is probably your best friend here just to assess it quickly :))
@Phil_Gebhardt**:** thanks for the info, I might give that a try before upgrading