The formula for calculating the maximum space used by IO logs: average write IO speed * 3600 (1 hour and seconds) * retention time (hours) / 1024 = GB. For example, if the average writes IO speed of the business system is 10MB/s, the retention time is 1 day, and the interval is 1 hour, the maximum space used by the IO log is 10 * 3600 * 24 / 1024 = 844 GB.
The backup space ≈ Initial full backup size + (daily data change volume × backup retention days).
The destination storage supports aSAN, FC storage, iSCSI storage, local storage, and NFS storage (io log not support NFS storage).
It is recommended to start with three HCI cluster nodes.
CDP protection of physical disks mapped in virtual machines is not supported.
Only the destination storage of CDP is supported to be configured on iSCSI, FC, and aSAN.
Only NTFS and FAT32 file systems support file retrieval functions, and the Linux system does not support file retrieval operations.
Using the CDP function, if the backup and I/O logs are placed on the external storage and because the I/O logs and backups occupy space, the I/O logs cannot be stored in time, and the I/O log buffer is exhausted. Resulting in CDP interruption. It is recommended not to place backups and logs in the same storage.
The default retention time for IO logs is 24 hours, with a maximum configurable retention of 3 days. Space usage should be reserved based on the business write IO speed, and it is recommended to reserve an additional 50% buffer space.
Virtual machines using virtual shared disks support CDP backup but will automatically exclude shared disk data.
1.It is prohibited to store CDP IO logs and backup data on the same single-host EDS or two-host VS.
2.CDP backup is not supported for physical disks, Oracle RAC shared disks, USB disks, or virtual machines with Turbo mode enabled.
3.Policy conflict: A virtual machine can only belong to one backup policy or CDP policy at a time.