Re: [Ceph | Quency ]The scheduled snapshots are not getting created till we create a manual backup.

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi!

I noticed the same that the snapshot scheduler seemed to do nothing , but after a manager fail over the creation of snapshots started to work (including the retention rules)..

Best regards,
Sake

________________________________
From: Lokendra Rathour <lokendrarathour@xxxxxxxxx>
Sent: Monday, May 29, 2023 10:11:54 AM
To: ceph-users <ceph-users@xxxxxxx>; Ceph Users <ceph-users@xxxxxxxxxxxxxx>
Subject:  [Ceph | Quency ]The scheduled snapshots are not getting created till we create a manual backup.

Hi Team,



*Problem:*

Create scheduled snapshots of the ceph subvolume.



*Expected Result:*

The scheduled snapshots should be created at the given scheduled time.



*Actual Result:*

The scheduled snapshots are not getting created till we create a manual
backup.



*Description:*

*Ceph version: 17(quincy)*

OS: Centos/Almalinux





The scheduled snapshot creation is not working and we were only able to see
the following logs in the file "ceph-mgr.storagenode3.log":



*2023-05-29T04:59:35.101+0000 7f4cd3ad8700  0 [snap_schedule INFO mgr_util]
scanning for idle connections..*

*2023-05-29T04:59:35.101+0000 7f4cd3ad8700  0 [snap_schedule DEBUG
mgr_util] fs_name (cephfs) connections ([])*

*2023-05-29T04:59:35.101+0000 7f4cd3ad8700  0 [snap_schedule INFO mgr_util]
cleaning up connections: [*





The command which we were executing to add the snapshot schedule:

*ceph fs snap-schedule add /volumes/<subvolume_group>/<subvolume>
<frequency_of_snapshot> <Timeinformat_yyyymmddTHH:MM:ss>*

*eg.*

*ceph fs snap-schedule add /volumes/xyz/test_restore_53 1h
2023-05-26T11:05:00*



We can make sure that the schedule has been created using the following
commands:

*#ceph fs snap-schedule list / --recursive=true*

*#ceph fs snap-schedule status /volumes/xyz/test_restore_53*



Even though we created the snapshot schedule, snapshots were not getting
created.

We then tried creating a manual snapshot for one of the sub-volumes using
the following command:

*#ceph fs subvolume snapshot create cephfs <subvolume> <snapshot-name>
--group_name <subvolume_group>*

*eg. ceph fs subvolume snapshot create cephfs test_restore_53 snapshot-1
--group_name xyz*



To check the snapshots created we can use the following command:

*ceph fs subvolume snapshot ls cephfs <subvolume> <snapshot-name>
<subvolume_group>*

*eg. ceph fs subvolume snapshot ls cephfs test_restore_53 snapshot-1 xyz*



To delete the manually created snapshot:

*ceph fs subvolume snapshot rm cephfs <subvolume> <snapshot-name>
<subvolume_group>*

*eg. ceph fs subvolume snapshot rm cephfs test_restore_53 snapshot-1 xyz*



To our surprise, the scheduled snapshots started working. We also applied
the retention policy and seems to be working fine.

We re-tested this understanding for another subvolume. And the scheduled
snapshots only started once we triggered a manual snapshot.



Could you please help us out with this?



--
~ Lokendra
skype: lokendrarathour
_______________________________________________
ceph-users mailing list -- ceph-users@xxxxxxx
To unsubscribe send an email to ceph-users-leave@xxxxxxx
_______________________________________________
ceph-users mailing list -- ceph-users@xxxxxxx
To unsubscribe send an email to ceph-users-leave@xxxxxxx



[Index of Archives]     [Information on CEPH]     [Linux Filesystem Development]     [Ceph Development]     [Ceph Large]     [Ceph Dev]     [Linux USB Development]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [xfs]


  Powered by Linux