Explanation: Using incremental exports minimizes downtime during migration by transferring only changes since the full export. Unmap an RBD image from the server, delete the image, and verify it is removed from the pool. ee the solution below. Solution: 1. Unmap the image: rbd unmap /dev/rbd/my -pool/my -image 2. Delete the image: rbd rm my -pool/my -image 3. Verify the removal: rbd ls my -pool Explanation: Properly unmapping and deleting RBD images ensures they are removed safely, freeing up storage in the pool. Enable and monitor placement group (PG) auto -scaling for an RBD pool. ee the solution below. Solution: 1. Enable PG auto -scaling: ceph osd pool set my -pool pg_autoscale_mode on 2. Check the autoscaling status: ceph osd pool autoscale -status 3. Verify PG distribution:
ceph pg dump | grep my -pool Explanation: PG auto-scaling ensures efficient data distribution and resource utilization by dynamically adjusting the number of placement groups. Create an RBD image with encryption enabled, map it to a host, and verify secure access using the encryption key. ee the solution below. Solution: 1. Generate an encryption key: openssl rand -base64 32 > /backup/encryption.key 2. Create the encrypted RBD image: rbd create secure -rbd --size 10240 --pool my -pool --image -feature encryption 3. Map the image with the encryption key: rbd map my -pool/secure -rbd --keyfile /backup/encryption.key 4. Verify the mapped device: lsblk | grep rbd Explanation: Encrypted RBD images protect sensitive data by requiring a key for access, ensuring compliance with security standards. Set up and test an RBD pool with automatic snapshot retention for backups. ee the solution below. Solution: 1. Enable snapshot scheduling:
ceph mgr module enable rbd_support 2. Configure snapshot retention: rbd snap -schedule add my -pool/my -image --interval 12h --retention 10 3. Verify snapshot retention policy: rbd snap -schedule status my -pool/my -image Explanation: Automatic snapshot retention reduces manual intervention and ensures consistent backups with limited resource usage. Enable the deep -flatten feature for an RBD image and verify that snapshots and clones can be deleted independently. ee the solution below. Solution: 1. Enable deep -flatten: rbd feature enable my -pool/my -image deep -flatten 2. Verify the feature: rbd info my -pool/my -image 3. Delete snapshots and clones independently: rbd snap rm my -pool/my -image@snapshot Explanation: The deep -flatten feature removes dependencies between snapshots and clones, simplifying image management. Export an RBD image in raw format, compress it using bzip2, and verify the compressed size. ee the solution below.
Solution: 1. Export the RBD image: rbd export my -pool/my -image /backup/my -image.raw 2. Compress the file with bzip2: bzip2 /backup/my -image.raw 3. Verify the compressed file size: ls -lh /backup/my -image.raw.bz2 Explanation: Compressing raw RBD exports reduces file size, optimizing storage for backup and transfer operations. Configure pool -level quotas for a specific RBD pool and enforce a maximum data usage of 5GB. ee the solution below. Solution: 1. Set the maximum data usage quota: ceph osd pool set -quota my -pool max_bytes 5368709120 2. Verify the quota configuration: ceph osd pool get -quota my -pool Explanation: Pool-level quotas ensure resource allocation is controlled, preventing individual pools from consuming excessive resources. Enable and monitor snapshot mirroring for an RBD pool to a remote cluster. ee the solution below. Solution:
1. Enable snapshot mirroring: rbd mirror pool enable my -pool snapshot 2. Add the remote cluster as a peer: rbd mirror pool peer add my -pool client.admin@remote -cluster 3. Monitor the mirroring status: rbd mirror pool status my -pool Explanation: Snapshot mirroring replicates snapshots to remote clusters, ensuring redundancy and disaster recovery for critical data. Perform incremental migration of an RBD image using differential exports and verify the import process. ee the solution below. Solution: 1. Create a base export: rbd export my -pool/my -image /backup/base.img 2. Create and export incremental changes: rbd snap create my -pool/my -image@incremental rbd export -diff my -pool/my -image@incremental /backup/incremental.diff 3. Import the base and incremental exports: rbd import /backup/base.img new -pool/my -image rbd import -diff /backup/incremental.diff new -pool/my -image Explanation: Incremental exports transfer only the changes, minimizing downtime and reducing resource usage during migration. Create and test an RBD clone for a snapshot, enabling fast -diff for efficient backups.
3. Apply the new CRUSH map: crushtool -c crush.txt -o crush.map ceph osd setcrushmap -i crush.map Explanation: CRUSH maps define how data is distributed across OSDs. Customizing these maps allows fine-grained control over data placement. Set up Ceph storage with authentication enabled and verify that clients require keys to access the cluster. ee the solution below. Solution: 1. Enable authentication in the Ceph configuration file: ceph config set mon auth_allow_insecure_global_id_reclaim false 2. Generate a client key: ceph auth get -or-create client.admin 3. Verify client access using the key: ceph -s --keyring /etc/ceph/ceph.client.admin.keyring Explanation: Enabling authentication adds a layer of security, ensuring only authorized clients can interact with the cluster. Deploy Ceph storage and configure BlueStore as the OSD backend for optimal performance. ee the solution below. Solution: 1. Update the playbook with BlueStore settings: osd_objectstore: bluestore
