DBcloudbin is available with a 1-Click custom AMI at AWS! Just follow the instructions on how to easily deploy a DBcloudbin AMI in your AWS account and start saving by moving data from your database (on-premises or cloud) to your object store of choice, including S3 (depends on the license provided).

DBcloudbin has public AMIs for AWS in replicated in several regions. Check here for the current catalog and latest version available.

The setup process is very simple and basically is comprised of three steps: Deployment, Configuration and Job execution.

  • Deployment

    Deployment the AMI as any virtual machine deployment in AWS using the public DBcloudbin AMI of choice based on the target database (either Oracle or SQL Server). Depending on the license used, you will have the ability to store the contents in a variety of object stores, including of course the AWS S3 service. In this case, you need to create an S3 bucket where the DB content will be stored and a role (see IAM roles) allowing read/write access to the created bucket.
    Select the desired DBcloudbin AMI based on region and target database technology and deploy it. In the deployment wizard, select the AMI role (if using a S3 bucket as technology), the keypair used to log into the deployed appliance and add to the security group networking/firewall rules for connecting to the appliance through TCP port 8090 (you can define the network mask for the servers that can connect for management through ssh and the network mask for the database server(s)).
    AMI Launch security group
    AWS will launch the virtual appliance; wait until it is marked as “Running”. 
  • Configuration

    Once deployed the appliance we need to configure it to be used with your specific DB instance and application data model. Your database server(s) may or may not be running in AWS; in any case connectivity from the database server(s) to the appliance by TCP port 8090 and from the appliance to the DB server(s) though the configured service port depending on your DB technology is required (e.g. default values are TCP 1521 for Oracle and TCP 1433 for SQL Server). Connect to the appliance by ssh using the provided keypair and type as user “dbcloudbin”.
    A short menu with two options will appear (option 1 for running a new install and option 2 for configuring the appliance into an already existing configuration; this second option is useful for upgrading to new releases).
    Press 1 and return; wait for the setup to start and follow the detailed instructions provided in the wizard. Just be prepared to provide DB connectivity information and credentials; you will be prompted also for the DNS name or IP for connecting from the DB host(s) to the appliance (the DNS name should be resolved by the DB host(s) pointing to the IP address assigned to the DBcloudbin appliance). We strongly recommend using an abstract DNS name registered into your DNS server (e.g. “dbcloudbin-appliance.mydomain.internal”) instead of directly the IP; this way the setup is much more flexible in the case we want to re-deploy the appliance with a new IP, add a network load balancer in between, …
    In the case of using a license allowing S3 object store configuration, the wizard will present a screen to select the bucket region and name (by default will preset the region where the virtual appliance has been deployed, but this can be changed if the bucket is provisioned in any other region). The wizard will make a short test, to validate that the bucket is correctly configured and the permissions are correctly setup in order to allow read/write access. Otherwise an error will be presented. In that case, press the “Cancel” option and review the IAM role assigned to the appliance and check that this role allows read/write access to the S3 bucket. Check AWS documentation for detailed instructions on AWS authorization management.
    The setup wizard should finish with a success message  (otherwise, please check the error and register a support ticket if necessary). You can execute the command line interface (CLI), e.g. “dbcloudbin info” that should provide information on the running DBcloudbin agent, version number, … In that case, the setup is OK; just check that your application (the one that uses the database) is working properly and everything is OK. Just move to the next step to execute data migration jobs, moving content to the object store configured (your S3 bucket in the case of Standard deployment).
    The setup wizard can be restarted again at any point in time by typing the command “sudo -u dbcloudbin-setup /usr/bin/dbcloudbin-setup.sh”
  • Job execution

    Data migration jobs as executed through the CLI (note: the CLI can be installed in any other server or in a Windows 10 workstation; just download the standard CLI from www.dbcloubin.com and select only the CLI package in the setup). You can run archive jobs interactively or use standard cron commands to schedule job execution. The simplest command for fully archiving one of the tables selected during setup, cleaning the data at the database would be “dbcloudbin archive -clean <table-name>”. Use “dbcloudbin -help” for detailed information of the available commands and “dbcloudbin <command> -help” for command specific instructions. See the Admin Guide for detailed instructions.

 

 

Support is provided using the regular DBcloudbin support ticketing tool at DBcloudbin’s site My account area.

Official DBcloudbin version at AWS public AMI is v.3.01.03.
Check at Release notes additional info about DBcloudbin releases and released versions.