CAPABILITIES

Database Virtualization or Cloning 

Writable copies of databases are delivered in seconds to new Docker containers or existing database instances. Databases are delivered from a database image, created from backups or a replicated instance of production. Windocks database virtualization includes near real-time image updates and the ability to commit an environment to create a new (updated) image. On delivery clones use no incremental storage as they read data from the image.   On writes data is copied from the image (Copy on Write), expanding the clone storage incrementally.

The ability to clone database environments in seconds enables Continuous Integration of database development and testing, fast delivery of databases for ETL jobs, reporting, and other needs.

The benefits of database virtualization include:

  • Over 95% reduction in storage, and a typical 50% reduction in infrastructure
  • Faster, more thoroughly tested database updates
  • Improved customer experience with fast provisioning of point-in-time production database environments, for fast production debug and support
  • Improved compliance with a centralized repository of lower level database environments, with security policies applied, and audit log support.
Meet with us
Windocks database timeline 900x700

Database, Volume, and VM Cloning

Database cloning Volume cloning VM cloning
Specific database files are cloned Entire disk volumes are cloned An entire VM with all its volumes is cloned
Windocks Actifio, Cohesity, others PureStorage and others
Ideal for database delivery for devops, testing, development, reporting, ML Suitable for database backups, disaster recovery. Requires substantial code for database delivery Suitable for backups of entire production machines with applications and data
Inexpensive, using standard Linux and Windows file systems Expensive, Proprietary storage Expensive, Proprietary storage

In addition to the advantages above, Windocks allows for near real-time database image updates, and is readily implemented by DBAs or DevOps engineers.  Windocks is simple to implement, and drives real ROI in storage and compute savings.  

Let's chat!

Database refresh

Database refresh is the process of getting incremental changes from the primary / production database and making the current primary / production databases available for testing, development, DevOps, machine learning model test and training. Windocks database refresh is available for SQL Server and Oracle. Build an image once from the full primary databases or backups just once. After that Windocks automatically refreshes the image with incremental changes from primary / production.

Database refresh for SQL Server - video

Database refresh for Oracle

Windocks provides database refresh for Oracle using an Oracle Docker container that stays in sync with the primary / production. Windocks builds point in time images instantaneously using the synced data in this container. From these point in time images, you may self service Oracle database clones in docker containers or Oracle instances. This unique architecture provides point in time database clones for testing, DevOps, and MLOps without requiring complex infrastructure with staging servers.

Steps to get started on DevOps pipelines and databases

1. Install Windocks

Download the Windocks Community Edition or email support@windocks.com for a full featured evaluation edition.

 

Provision a Windows Server VM (Server 2016, 2019, or 2022), install SQL Server (for SQL database delivery) and then install Windocks using the instructions provided with the download. 

 

For Oracle database delivery, also install the Windocks service for Linux as described in the download instructions. 

2. Create the dockerfile to build the image

Refer to the windocks\samples folder, using clonefromfullbackup as one example: 

  • enter the path to one or more SQL backup or database files, which are restored to create a database image
  • sample dockerfiles are included that deliver database clones to either new containers or existing instances
  • Scripts are copied to apply user permissions on the database, as well as masking
  • Build the image via a web application, command line or REST API.

 

Tutorial for SQL Server   

Tutorial for Oracle  

Tutorial for PostgreSQL, MySQL

3. Deliver database clones on demand from the image

From the image, deliver database clones to containers or instances.  To deliver containers and clones, use the web application or use the docker command line or the REST API.

4. Use the writeable clones

Database clones are delivered either to containers or instances based on the image.  If you delivered to an instance, then connect to that instance for the database clone. Clones are writeable. Containers are delivered on the Windocks server at specified ports. Access these containers with regular database tools or command lines or connection strings.

SQL Server containers are accessed with SQL Management Studio or Azure Data Studio or SQLCMD. Connect with the instance name (such as INSTANCE10002 when the container port is 10002). Or you can use the form IPAddressOfWindocksServer,10002 to connect to the SQL container running on port 10002.

Oracle containers are accessed with SQLPlus, RMAN or UI tools for Oracle. You may put in entries in tnsnames.ora for the containers as you would for Oracle instances. With SQLPlus or RMAN, use the form SQLPLUS sys/password@IPAddressOfWindocksLinuxServer:HostPort/orclcdb as sysdba

5. Refresh automatically from production

Images are refreshed with incremental changes from production / primary automatically for both SQL Server and Oracle. After refresh, clones delivered from the image will have the latest production data. See the SQL Server tutorial for a tutorial on refresh for SQL Server using transaction log backups. For a tutorial on Oracle refresh see the sample in the product in windocks\samples\oraclelinux.

 

 

Explore topics

 

 

Let's chat!