that looks pretty good. i'd probably change the following:

8) Stop jobs on old database cluster
9) Validate CF is working and connected to new database
10) Validate old database files are not changed since last backup and
back-up to new set of backup files just in case
11) Remove old database instance from the manifest

On Mon, Feb 15, 2016 at 10:46 AM, Jeff Weber <jweber(a)cofront.net> wrote:

I've got a monolithic CF deployment that has become quite a burden to
upgraded because of it's all releases in one manifest nature. I'm currently
working on a plan to cleanup and disaggregate and the first step is to
migrate my core database into its own separate deployment.

After putting my plan together I wanted to confirm it's as simple as it
seems:

1) Deploy new database cluster
2) Stop CF services
3) Perform backup of databases on old cluster
4) Restore backups to new cluster
5) Reconfigure manifest to point to new database cluster
6) Redeploy / Start CF services with new manifest
7) Validate
8) Remove old database instance from the manifest

Is there anything outside of these basic steps to watch out for as
gotchas or should this be a straight forward set of tasks?

--
Thank you,

James Bayer