Raptor on SAN – Supported Clone Scenarios<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } Overview For instances running RaptorDB on SAN, clone supports like‑for‑like database clones. Cross‑database clone combinations are not allowed and will be blocked during clone scheduling. Supported Clones The following clone scenario is supported: RaptorDB on SAN → RaptorDB on SAN This includes production‑to‑non‑production and non‑production‑to‑non‑production clones, as long as both the source and target instances are running Raptor on SAN. Unsupported Clones The following Source → Target clone scenarios are not supported and cannot be scheduled: RaptorDB on SAN → MariaDB on SANMariaDB on SAN → RaptorDB on SAN These combinations are automatically blocked at clone scheduling time and will not proceed. Cross‑database clones between MariaDB on SAN and Raptor on SAN are not supported in either direction. What Happens If You Try an Unsupported Clone If you attempt to schedule an unsupported clone the clone request will be blocked before execution. Recommended Action If you need to clone between instances:Ensure both source and target instances are running Raptor on SAN.If an instance is still on MariaDB, migrate it to Raptor before scheduling a clone.