As part of migrating OnBase to AWS, we also had to migrate the database itself. This proved to be a much less complicated task than moving all of the document files, somewhat of an anti-climax.
A Bit of History
When we first implemented OnBase, we chose to use Oracle as the database engine. In order to improve operational stability, we switched database platforms to Microsoft SQL Server in 2014. Our primary reason for the switch was to align us with Hyland’s main line of development. We felt good about getting that work done prior to our move to AWS.
It’s important to understand what purpose the OnBase database serves. It contains the metadata and user annotations, while the underlying documents reside on a file system. As such, the database doesn’t take up much space. A compressed backup of our database is only 16 GB.
Transfer the Data
Transferring a 16 GB file to AWS is a relatively straightforward task. The most important feature you to be aware of is multi-part upload. This feature takes a single large file and splits it into multiple parts. These parts are then uploaded in parallel to S3.
Initially, we looked into using CrossFTP. CrossFTP is a third party, GUI tool which allows you to specify parameters to the S3 copy command, including thread count and chunk size. That said, CrossFTP simply takes what you can do natively using the AWS Command Line Interface (CLI) and gives you a graphical front end. The graphical interface abstracts the messiness of a command line and is quite approachable for a novice. However, that was not necessary in this case. We just used AWS CLI to transfer the data from here to S3. It couldn’t be much more straightforward, as the syntax is:
aws s3 cp <fileName> s3://<bucketName>/<fileName>
In order to get the performance to an acceptable level, we made the following configuration adjustments in the ~/.aws/config file:
[profile xferonbase] aws_access_key_id=<serviceId> aws_secret_access_key=<serviceKey> s3 = max_concurrent_requests = 40 multipart_threshold = 512MB multipart_chunksize = 512MB
Appropriately configured, transferring our 16 GB database backup took just under 17 minutes. Once the file was in S3, we simply transferred it to our SQL Server database instance and performed a restore. Simple and easy. Highly advisable if you have the luxury of bringing your system entirely down when migrating.
A look to the future
In fact, the simplicity of this backup/transfer/restore approach is influencing how we think about migrating our ERP. We use Banner running on Oracle. While our database size is a bit over 1 TB, the compressed backup is 175 GB. Conservatively, that’s a 3 hour segment of time to get the file to S3. Once the data is in S3, we’re using an S3 VPC endpoint for private connectivity and speed.
Thinking about migration weekend and the need to build in sleep time, the backup, validate, copy to S3, copy to EC2, restore process is something easy to script and test. And a great way to build in sleep time! We’ve all done enough migrations to know that people don’t make good decisions when they are exhausted.