由 SuKai November 21, 2024
Velero阿里云OSS插件不再维护，并且只支持阿里云官方平台，不支持私有阿里云平台。Velero AWS插件能够备份Kubernetes资源，但由于阿里云OSS不兼容S3协议，不支持aws-chunked encoding，存储卷快照数据不能上传。本文记录使用AWS插件备份Kubernetes资源。
- 创建OSS访问密钥和Bucket
- Helm安装Velero
- 创建备份
安装ossutil工具，查看Bucket文件
sukai@rack1-master34:~/ossutil$ curl -O curl https://gosspublic.alicdn.com/ossutil/install.sh
sukai@rack1-master34:~/ossutil$ sudo bash install.sh
sukai@rack1-master34:~/ossutil$ more /home/sukai/.ossutilconfig
[Credentials]
language=CH
accessKeyID=HoOY11111oVQd2
accessKeySecret=etwTS11111111111fUI
endpoint=http://oss-cn-lasa-xzns-d01-a.ops.sukai.com.cn
skipVerifyCert
sukai@rack1-master34:~$ ossutil ls oss://jingxiang
LastModifiedTime Size(B) StorageClass ETAG ObjectName
2024-11-20 11:36:31 +0000 UTC 3500 Standard 48CA775C38F20878964AA5088324F21C oss://jingxiang/backups/vms-202411201932/velero-backup.json
2024-11-20 11:35:52 +0000 UTC 471 Standard 7B61AF0F32290A5B39D5881F986D0957 oss://jingxiang/backups/vms-202411201932/vms-202411201932-csi-volumesnapshotclasses.json.gz
2024-11-20 11:35:52 +0000 UTC 6238 Standard 6ACC5E93B590EE6422D38F4A674FC18F oss://jingxiang/backups/vms-202411201932/vms-202411201932-csi-volumesnapshotcontents.json.gz
2024-11-20 11:35:52 +0000 UTC 5033 Standard 997FE590407EFA5E3C286E68066B1D87 oss://jingxiang/backups/vms-202411201932/vms-202411201932-csi-volumesnapshots.json.gz
2024-11-20 11:35:52 +0000 UTC 2373 Standard 6E0C20DB395F60DB5F45403E5B30A026 oss://jingxiang/backups/vms-202411201932/vms-202411201932-itemoperations.json.gz
2024-11-20 11:35:52 +0000 UTC 37568 Standard C8CD7B454911092848B55AF7068710B6 oss://jingxiang/backups/vms-202411201932/vms-202411201932-logs.gz
2024-11-20 11:35:52 +0000 UTC 29 Standard 6848CB8D5F3669EF603F87E48ECE8567 oss://jingxiang/backups/vms-202411201932/vms-202411201932-podvolumebackups.json.gz
2024-11-20 11:35:52 +0000 UTC 5736 Standard B041BC38F6C2E0A802DA386BA0B9DF90 oss://jingxiang/backups/vms-202411201932/vms-202411201932-resource-list.json.gz
2024-11-20 11:35:52 +0000 UTC 49 Standard 4B8F571A28628DF1F222EE56C3673550 oss://jingxiang/backups/vms-202411201932/vms-202411201932-results.gz
2024-11-20 11:36:30 +0000 UTC 3643 Standard 7AC324D869C428B77AB616D93A2BB1E9 oss://jingxiang/backups/vms-202411201932/vms-202411201932-volumeinfo.json.gz
2024-11-20 11:35:52 +0000 UTC 29 Standard 6848CB8D5F3669EF603F87E48ECE8567 oss://jingxiang/backups/vms-202411201932/vms-202411201932-volumesnapshots.json.gz
2024-11-20 11:36:31 +0000 UTC 478433 Standard 014E1FD1AAA535C434995DB7559C9F68 oss://jingxiang/backups/vms-202411201932/vms-202411201932.tar.gz
Object Number is: 12
0.006800(s) elapsed
sukai@rack1-master34:~$
sukai@rack1-master34:~/velero-v1.15.0-linux-amd64$ velero uninstall
You are about to uninstall Velero.
Are you sure you want to continue (Y/N)? Y
Waiting for resource with attached finalizer to be deleted
Waiting for velero namespace "velero" to be deleted
............................................
Velero namespace "velero" deleted
Velero uninstalled ⛵
sukai@rack1-master34:~/velero-v1.15.0-linux-amd64$
安装Velero，查看Velero日志后端存储可用BackupStorageLocations is valid, marking as available。
sukai@rack1-master34:~/velero-helm-charts/charts/velero$ more values.yaml
namespace:
labels: {}
image:
repository: reg.sukai.com:7443/velero/velero
tag: v1.15.0
pullPolicy: IfNotPresent
imagePullSecrets: []
nameOverride: ""
fullnameOverride: ""
annotations: {}
secretAnnotations: {}
labels: {}
podAnnotations: {}
podLabels: {}
resources: {}
upgradeJobResources: {}
upgradeCRDsJob:
extraVolumes: []
extraVolumeMounts: []
extraEnvVars: {}
dnsPolicy: ClusterFirst
initContainers:
- name: velero-plugin-for-alibabacloud
image: reg.sukai.com:7443/velero/velero-plugin-for-aws:v1.10.0
imagePullPolicy: IfNotPresent
volumeMounts:
- mountPath: /target
name: plugins
podSecurityContext: {}
containerSecurityContext: {}
lifecycle: {}
priorityClassName: ""
terminationGracePeriodSeconds: 3600
livenessProbe:
httpGet:
path: /metrics
port: http-monitoring
scheme: HTTP
initialDelaySeconds: 10
periodSeconds: 30
timeoutSeconds: 5
successThreshold: 1
failureThreshold: 5
readinessProbe:
httpGet:
path: /metrics
port: http-monitoring
scheme: HTTP
initialDelaySeconds: 10
periodSeconds: 30
timeoutSeconds: 5
successThreshold: 1
failureThreshold: 5
tolerations: []
affinity: {}
nodeSelector: {}
dnsConfig: {}
extraVolumes: []
extraVolumeMounts: []
extraObjects: []
metrics:
enabled: true
scrapeInterval: 30s
scrapeTimeout: 10s
service:
annotations: {}
labels: {}
podAnnotations:
prometheus.io/scrape: "true"
prometheus.io/port: "8085"
prometheus.io/path: "/metrics"
serviceMonitor:
autodetect: true
enabled: false
annotations: {}
additionalLabels: {}
nodeAgentPodMonitor:
autodetect: true
enabled: false
annotations: {}
additionalLabels: {}
prometheusRule:
autodetect: true
enabled: false
additionalLabels: {}
spec: []
kubectl:
image:
repository: reg.sukai.com:7443/bitnami/kubectl
containerSecurityContext: {}
resources: {}
annotations: {}
labels: {}
upgradeCRDs: true
cleanUpCRDs: false
configuration:
backupStorageLocation:
- name: default
provider: aws
bucket: jingxiang
caCert:
prefix:
default: true
validationFrequency:
accessMode: ReadWrite
credential:
name: aliyun-oss
key: cloud
config:
region: cn-lasa-xzns-d01-a
s3ForcePathStyle: false
s3Url: "http://oss-cn-lasa-xzns-d01-a.ops.sukai.com.cn"
insecureSkipTLSVerify: true
annotations: {}
volumeSnapshotLocation:
- name:
provider: aws
credential:
name: aliyun-oss
key: cloud
config:
region: oss-cn-lasa-xzns-d01-a
annotations: {}
uploaderType:
backupSyncPeriod:
fsBackupTimeout:
clientBurst:
clientPageSize:
clientQPS:
defaultBackupStorageLocation:
defaultItemOperationTimeout:
defaultBackupTTL:
defaultVolumeSnapshotLocations:
disableControllers:
disableInformerCache: false
garbageCollectionFrequency:
logFormat:
logLevel:
metricsAddress:
pluginDir:
profilerAddress:
restoreOnlyMode:
restoreResourcePriorities:
storeValidationFrequency:
terminatingResourceTimeout:
defaultSnapshotMoveData: false
features: EnableCSI
repositoryMaintenanceJob:
requests:
limits:
latestJobsCount: 3
namespace:
extraArgs: []
extraEnvVars: {}
defaultVolumesToFsBackup:
defaultRepoMaintainFrequency:
rbac:
create: true
clusterAdministrator: true
clusterAdministratorName: cluster-admin
serviceAccount:
server:
create: true
name:
annotations:
labels:
imagePullSecrets: []
credentials:
useSecret: true
name: aliyun-oss
existingSecret:
secretContents:
cloud: |
[default]
aws_access_key_id=j211111111H4Sp
aws_secret_access_key=dZz8111111111111111XMSu
extraEnvVars: {}
extraSecretRef: ""
backupsEnabled: true
snapshotsEnabled: true
deployNodeAgent: yes
nodeAgent:
podVolumePath: /var/lib/kubelet/pods
priorityClassName: ""
resources: {}
tolerations: []
annotations: {}
labels: {}
useScratchEmptyDir: true
extraVolumes: []
extraVolumeMounts: []
extraEnvVars: {}
extraArgs: []
dnsPolicy: ClusterFirst
podSecurityContext:
runAsUser: 0
containerSecurityContext: {}
lifecycle: {}
nodeSelector: {}
affinity: {}
dnsConfig: {}
schedules: {}
configMaps: {}
sukai@rack1-master34:~/velero-helm-charts/charts$ helm upgrade --install velero velero --create-namespace --namespace velero
Release "velero" does not exist. Installing it now.
NAME: velero
LAST DEPLOYED: Wed Nov 20 09:11:06 2024
NAMESPACE: velero
STATUS: deployed
REVISION: 1
TEST SUITE: None
NOTES:
Check that the velero is up and running:
kubectl get deployment/velero -n velero
Check that the secret has been created:
kubectl get secret/velero -n velero
Once velero server is up and running you need the client before you can use it
1. wget https://github.com/vmware-tanzu/velero/releases/download/v1.15.0/velero-v1.15.0-darwin-amd64.tar.gz
2. tar -xvf velero-v1.15.0-darwin-amd64.tar.gz -C velero-client
More info on the official site: https://velero.io/docs
sukai@rack1-master34:~$ kubectl -n velero get pods
NAME READY STATUS RESTARTS AGE
node-agent-565s2 1/1 Running 0 15h
node-agent-59fkl 1/1 Running 0 15h
node-agent-6s7mq 1/1 Running 0 15h
node-agent-94qh2 1/1 Running 0 15h
node-agent-dtrlj 1/1 Running 0 15h
node-agent-fq2kx 1/1 Running 0 15h
node-agent-fw8jq 1/1 Running 0 15h
node-agent-hrp2r 1/1 Running 0 15h
node-agent-hwp56 1/1 Running 0 15h
node-agent-kbztc 1/1 Running 0 15h
node-agent-m4l4g 1/1 Running 0 15h
node-agent-nxcz7 1/1 Running 0 15h
node-agent-p2f26 1/1 Running 0 15h
node-agent-pl7c4 1/1 Running 0 15h
node-agent-q4prv 1/1 Running 0 15h
node-agent-rtwtg 1/1 Running 0 15h
node-agent-shxgt 1/1 Running 0 15h
node-agent-sxbp5 1/1 Running 0 15h
node-agent-t5vvg 1/1 Running 0 15h
node-agent-tllqt 1/1 Running 0 15h
node-agent-zwms9 1/1 Running 0 15h
velero-7cfb8c77c5-vg8wn 1/1 Running 0 15h
sukai@rack1-master34:~$
sukai@rack1-master34:~$ kubectl -n velero logs velero-7cfb8c77c5-vg8wn
time="2024-11-21T03:00:18Z" level=info msg="Validating BackupStorageLocation" backup-storage-location=velero/default controller=backup-storage-location logSource="pkg/controller/backup_storage_location_controller.go:142"
time="2024-11-21T03:00:18Z" level=info msg="BackupStorageLocations is valid, marking as available" backup-storage-location=velero/default controller=backup-storage-location logSource="pkg/controller/backup_storage_location_controller.go:127"
time="2024-11-21T03:00:18Z" level=info msg="plugin process exited" backup-storage-location=velero/default cmd=/plugins/velero-plugin-for-aws controller=backup-storage-location id=22759 logSource="pkg/plugin/clientmgmt/process/logrus_adapter.go:80" plugin=/plugins/velero-plugin-for-aws
创建备份
sukai@rack1-master34:~$ velero create schedule cluster-a-bj-vms --schedule="@every 24h" --include-namespaces beijing
Schedule "cluster-a-bj-vms" created successfully.
sukai@rack1-master34:~$ velero schedule get
NAME STATUS CREATED SCHEDULE BACKUP TTL LAST BACKUP SELECTOR PAUSED
cluster-a-bj-vms Enabled 2024-11-21 03:17:46 +0000 UTC @every 24h 0s n/a <none> false
sukai@rack1-master34:~$ velero schedule delete cluster-a-bj-vms
Are you sure you want to continue (Y/N)? Y
Schedule deleted: cluster-a-bj-vms
sukai@rack1-master34:~$
sukai@rack1-master34:~$ velero create schedule cluster-a-bj-vms --schedule="@every 24h" --include-namespaces beijing --ttl 72h
Schedule "cluster-a-bj-vms" created successfully.
sukai@rack1-master34:~$ velero schedule get
NAME STATUS CREATED SCHEDULE BACKUP TTL LAST BACKUP SELECTOR PAUSED
cluster-a-bj-vms Enabled 2024-11-21 03:18:36 +0000 UTC @every 24h 72h0m0s n/a <none> false
sukai@rack1-master34:~$ velero schedule describe cluster-a-bj-vms
Name: cluster-a-bj-vms
Namespace: velero
Labels: <none>
Annotations: <none>
Phase: Enabled
Paused: false
Schedule: @every 24h
Backup Template:
Namespaces:
Included: beijing
Excluded: <none>
Resources:
Included: *
Excluded: <none>
Cluster-scoped: auto
Label selector: <none>
Or label selector: <none>
Storage Location:
Velero-Native Snapshot PVs: auto
Snapshot Move Data: auto
Data Mover: velero
TTL: 72h0m0s
CSISnapshotTimeout: 0s
ItemOperationTimeout: 0s
Hooks: <none>
Last Backup: <never>
root123@rack1-master34:~$
查看备份，卷快照。
sukai@rack1-master34:~$ velero backup get
NAME STATUS ERRORS WARNINGS CREATED EXPIRES STORAGE LOCATION SELECTOR
vms-202411201932 Completed 0 0 2024-11-20 11:32:34 +0000 UTC 29d default <none>
sukai@rack1-master34:~$ velero backup describe vms-202411201932
Name: vms-202411201932
Namespace: velero
Labels: velero.io/storage-location=default
Annotations: velero.io/resource-timeout=10m0s
velero.io/source-cluster-k8s-gitversion=v1.30.4
velero.io/source-cluster-k8s-major-version=1
velero.io/source-cluster-k8s-minor-version=30
Phase: Completed
Namespaces:
Included: beijing
Excluded: <none>
Resources:
Included: *
Excluded: <none>
Cluster-scoped: auto
Label selector: <none>
Or label selector: <none>
Storage Location: default
Velero-Native Snapshot PVs: auto
Snapshot Move Data: false
Data Mover: velero
TTL: 720h0m0s
CSISnapshotTimeout: 10m0s
ItemOperationTimeout: 4h0m0s
Hooks: <none>
Backup Format Version: 1.1.0
Started: 2024-11-20 11:32:34 +0000 UTC
Completed: 2024-11-20 11:36:31 +0000 UTC
Expiration: 2024-12-20 11:32:34 +0000 UTC
Total items to be backed up: 448
Items backed up: 448
Backup Item Operations: 35 of 35 completed successfully, 0 failed (specify --details for more information)
Backup Volumes:
Velero-Native Snapshots: <none included>
CSI Snapshots:
beijing/bj-test01-os:
Snapshot: included, specify --details for more information
Pod Volume Backups: <none included>
HooksAttempted: 28
HooksFailed: 0
sukai@rack1-master34:~$ velero backup describe vms-202411201932 --details
Name: vms-202411201932
Namespace: velero
Labels: velero.io/storage-location=default
Annotations: velero.io/resource-timeout=10m0s
velero.io/source-cluster-k8s-gitversion=v1.30.4
velero.io/source-cluster-k8s-major-version=1
velero.io/source-cluster-k8s-minor-version=30
Phase: Completed
Namespaces:
Included: beijing
Excluded: <none>
Resources:
Included: *
Excluded: <none>
Cluster-scoped: auto
Label selector: <none>
Or label selector: <none>
Storage Location: default
Velero-Native Snapshot PVs: auto
Snapshot Move Data: false
Data Mover: velero
TTL: 720h0m0s
CSISnapshotTimeout: 10m0s
ItemOperationTimeout: 4h0m0s
Hooks: <none>
Backup Format Version: 1.1.0
Started: 2024-11-20 11:32:34 +0000 UTC
Completed: 2024-11-20 11:36:31 +0000 UTC
Expiration: 2024-12-20 11:32:34 +0000 UTC
Total items to be backed up: 448
Items backed up: 448
Backup Item Operations:
Operation for volumesnapshots.snapshot.storage.k8s.io beijing/velero-bj-tyht05-os-tdv8z:
Backup Item Action Plugin: velero.io/csi-volumesnapshot-backupper
Operation ID: beijing/velero-bj-tyht05-os-tdv8z/2024-11-20T11:32:41Z
Items to Update:
volumesnapshots.snapshot.storage.k8s.io beijing/velero-bj-tyht05-os-tdv8z
volumesnapshotcontents.snapshot.storage.k8s.io /snapcontent-63f8ce58-790d-41e7-a4b9-6aa73fb7f450
Phase: Completed
Created: 2024-11-20 11:32:41 +0000 UTC
Started: 2024-11-20 11:32:41 +0000 UTC
Updated: 2024-11-20 11:35:52 +0000 UTC
Operation for volumesnapshots.snapshot.storage.k8s.io beijing/velero-vm-w2k16-clone-os-72lw8:
Backup Item Action Plugin: velero.io/csi-volumesnapshot-backupper
Operation ID: beijing/velero-vm-w2k16-clone-os-72lw8/2024-11-20T11:35:49Z
Items to Update:
volumesnapshots.snapshot.storage.k8s.io beijing/velero-vm-w2k16-clone-os-72lw8
volumesnapshotcontents.snapshot.storage.k8s.io /snapcontent-bb4aac7c-15ae-4315-8d71-6e0b60bef048
Phase: Completed
Created: 2024-11-20 11:35:49 +0000 UTC
Started: 2024-11-20 11:35:49 +0000 UTC
Updated: 2024-11-20 11:35:52 +0000 UTC
Resource List:
apiextensions.k8s.io/v1/CustomResourceDefinition:
- datavolumes.cdi.kubevirt.io
- virtualmachineinstances.kubevirt.io
- virtualmachinerestores.snapshot.kubevirt.io
- virtualmachines.kubevirt.io
- virtualmachinesnapshotcontents.snapshot.kubevirt.io
- virtualmachinesnapshots.snapshot.kubevirt.io
- volumeimportsources.cdi.kubevirt.io
- volumesnapshots.snapshot.storage.k8s.io
apps/v1/ControllerRevision:
- beijing/revision-start-vm-29917b40-52ad-442d-9a4b-68041dae5bd6-4
cdi.kubevirt.io/v1beta1/DataVolume:
- beijing/bj-test01-os
- beijing/vm-w2k16-clone-os
cdi.kubevirt.io/v1beta1/VolumeImportSource:
- beijing/volume-import-source-8f6ac103-8bd2-4d93-9867-261865899c91
kubevirt.io/v1/VirtualMachine:
- beijing/bj-test01
- beijing/vm-w2k16-clone
kubevirt.io/v1/VirtualMachineInstance:
- beijing/bj-tyht05
- beijing/tyht-w2k12-02
snapshot.kubevirt.io/v1beta1/VirtualMachineRestore:
- beijing/restore-vm-w2k12-clone
snapshot.kubevirt.io/v1beta1/VirtualMachineSnapshot:
- beijing/snap-bj-tyht05
- beijing/snap-vm-w2k12-clone-20241025
snapshot.kubevirt.io/v1beta1/VirtualMachineSnapshotContent:
- beijing/vmsnapshot-content-0e51c947-78e8-4272-b4b7-7852ad205986
- beijing/vmsnapshot-content-c38b077d-5ada-4445-9316-ffccab3aef98
snapshot.storage.k8s.io/v1/VolumeSnapshot:
- beijing/velero-bj-test01-os-85bl9
- beijing/vmsnapshot-c38b077d-5ada-4445-9316-ffccab3aef98-volume-datadisk
- beijing/vmsnapshot-c38b077d-5ada-4445-9316-ffccab3aef98-volume-osdisk
snapshot.storage.k8s.io/v1/VolumeSnapshotClass:
- csi-rbdplugin-snapclass
snapshot.storage.k8s.io/v1/VolumeSnapshotContent:
- snapcontent-02cbc079-81fb-4305-b9e3-5464d73fb23a
- snapcontent-fbda0930-9c5b-4102-b34b-f427bf4db785
v1/ConfigMap:
- beijing/kube-root-ca.crt
v1/Event:
- beijing/velero-bj-test01-os-pkfld.1809a87edd35a28e
- beijing/velero-vm-w2k16-clone-os-bb42m.1809a887daac501e
v1/Namespace:
- beijing
v1/PersistentVolume:
- pvc-0aeb8df6-4993-411e-b44e-7812c759fc57
- pvc-fea23527-5573-47ba-9d47-254b57521fd1
v1/PersistentVolumeClaim:
- beijing/bj-test01-os
- beijing/tyht-w2k12-02-os
- beijing/vm-w2k16-clone-os
v1/Pod:
- beijing/virt-launcher-bj-tyht05-7hfnk
- beijing/virt-launcher-tyht-w2k12-02-5bzgd
v1/Secret:
- beijing/export-vm-token
v1/ServiceAccount:
- beijing/default
Backup Volumes:
Velero-Native Snapshots: <none included>
CSI Snapshots:
beijing/bj-test01-os:
Snapshot:
Operation ID: beijing/velero-bj-test01-os-85bl9/2024-11-20T11:35:13Z
Snapshot Content Name: snapcontent-a1ea783c-d3df-4830-95b7-b9d3d7cc7a12
Storage Snapshot ID: 0001-0009-rook-ceph-0000000000000002-97d4ff2c-99da-4aa3-8137-3b06461d4785
Snapshot Size (bytes): 0
CSI Driver: rook-ceph.rbd.csi.ceph.com
Result: succeeded
beijing/vm-w2k16-clone-os:
Snapshot:
Operation ID: beijing/velero-vm-w2k16-clone-os-72lw8/2024-11-20T11:35:49Z
Snapshot Content Name: snapcontent-bb4aac7c-15ae-4315-8d71-6e0b60bef048
Storage Snapshot ID: 0001-0009-rook-ceph-0000000000000002-f4cd2d09-de8e-4008-ac0a-1f02cac38665
Snapshot Size (bytes): 0
CSI Driver: rook-ceph.rbd.csi.ceph.com
Result: succeeded
Pod Volume Backups: <none included>
HooksAttempted: 28
HooksFailed: 0
sukai@rack1-master34:~$
sukai@rack1-master34:~$ kubectl -n beijing get volumesnapshot
NAME READYTOUSE SOURCEPVC SOURCESNAPSHOTCONTENT RESTORESIZE SNAPSHOTCLASS SNAPSHOTCONTENT CREATIONTIME AGE
velero-bj-tyht05-data-xt5vp true bj-tyht05-data csi-rbdplugin-snapclass snapcontent-1df06ad8-144c-40b1-ab57-54a1f4c4d511 16h 16h
velero-bj-tyht05-os-j7wk2 true bj-tyht05-os csi-rbdplugin-snapclass snapcontent-05af486c-c121-415a-ae74-e33fbeb54a7f 16h 16h
查看OSS文件
sukai@rack1-master34:~$ ossutil ls oss://jingxiang
LastModifiedTime Size(B) StorageClass ETAG ObjectName
2024-11-20 11:36:31 +0000 UTC 3500 Standard 48CA775C38F20878964AA5088324F21C oss://jingxiang/backups/vms-202411201932/velero-backup.json
2024-11-20 11:35:52 +0000 UTC 471 Standard 7B61AF0F32290A5B39D5881F986D0957 oss://jingxiang/backups/vms-202411201932/vms-202411201932-csi-volumesnapshotclasses.json.gz
2024-11-20 11:35:52 +0000 UTC 6238 Standard 6ACC5E93B590EE6422D38F4A674FC18F oss://jingxiang/backups/vms-202411201932/vms-202411201932-csi-volumesnapshotcontents.json.gz
2024-11-20 11:35:52 +0000 UTC 5033 Standard 997FE590407EFA5E3C286E68066B1D87 oss://jingxiang/backups/vms-202411201932/vms-202411201932-csi-volumesnapshots.json.gz
2024-11-20 11:35:52 +0000 UTC 2373 Standard 6E0C20DB395F60DB5F45403E5B30A026 oss://jingxiang/backups/vms-202411201932/vms-202411201932-itemoperations.json.gz
2024-11-20 11:35:52 +0000 UTC 37568 Standard C8CD7B454911092848B55AF7068710B6 oss://jingxiang/backups/vms-202411201932/vms-202411201932-logs.gz
2024-11-20 11:35:52 +0000 UTC 29 Standard 6848CB8D5F3669EF603F87E48ECE8567 oss://jingxiang/backups/vms-202411201932/vms-202411201932-podvolumebackups.json.gz
2024-11-20 11:35:52 +0000 UTC 5736 Standard B041BC38F6C2E0A802DA386BA0B9DF90 oss://jingxiang/backups/vms-202411201932/vms-202411201932-resource-list.json.gz
2024-11-20 11:35:52 +0000 UTC 49 Standard 4B8F571A28628DF1F222EE56C3673550 oss://jingxiang/backups/vms-202411201932/vms-202411201932-results.gz
2024-11-20 11:36:30 +0000 UTC 3643 Standard 7AC324D869C428B77AB616D93A2BB1E9 oss://jingxiang/backups/vms-202411201932/vms-202411201932-volumeinfo.json.gz
2024-11-20 11:35:52 +0000 UTC 29 Standard 6848CB8D5F3669EF603F87E48ECE8567 oss://jingxiang/backups/vms-202411201932/vms-202411201932-volumesnapshots.json.gz
2024-11-20 11:36:31 +0000 UTC 478433 Standard 014E1FD1AAA535C434995DB7559C9F68 oss://jingxiang/backups/vms-202411201932/vms-202411201932.tar.gz
Object Number is: 12
0.006532(s) elapsed
sukai@rack1-master34:~$