Document toolboxDocument toolbox

Managing Sandboxes

If your business requires a separate test environment for the Infoblox Platform, you can purchase a sandbox and set it up for testing purposes. You can use the sandbox to test new security policies, updates to a NIOS-X server, and other changes before deploying them to production. You can also use the sandbox for training users on the product or exploring new features before activating them in production.

About the Infoblox Platform Sandbox

  • An Infoblox sandbox is a temporary, non-production account that contains and operates the same features and capabilities as those of its parent account.

  • Each sandbox SKU allows you to create one sandbox per Infoblox account.

  • Each sandbox has a maximum consumption rate. As per the terms of service, the sandbox is considered a production instance if the rate exceeds the maximum, and that is a violation of the terms of service.

  • The consumption rate and usage in the sandbox account do not affect the subscription guardrails of the parent account.

  • Infoblox Platform does not create sandboxes automatically, even when you have the sandbox SKUs. You must create sandbox accounts and enable them before you can use them. For details, see Creating Sandboxes.

  • Only admin users have the permission to create sandboxes. After creating a sandbox, an admin user can add users to the sandbox and set up applicable configurations, just as the admin user would do in production. An admin user in the parent account can delete a sandbox. Admin privileges are not transferable between the parent and sandbox accounts.

  • All newly created sandboxes are enabled by default. When enabled, your sandboxes support all Infoblox Platform features and capabilities of the parent account.

  • You must renew your sandbox’s SKU before it expires. Failure to renew the SKU will terminate access to the sandbox account, even if the parent subscription is still valid.

Sandboxes and NIOS-X Servers

  • You can deploy NIOS-X servers and connect them to your sandboxes, but you cannot reassign servers from one sandbox to another. You must create new servers for each sandbox.

  • A sandbox is not a virtual machine. Therefore, you cannot install and test malware on it.

  • For information about deploying a server, see Deploying NIOS-X Servers.

Sandbox Data

  • In the Infoblox Portal, all sandboxes are separate accounts associated with the parent account. There is no data synchronization between a sandbox account and the production account, and you can use the sandbox environment for non-production purposes only.

  • Data remains in the parent account and is not automatically copied to a sandbox. If you have multiple sandboxes, each of them works independently of the others, based on its individual configurations.

  • Data related to policies, configurations, and Infoblox Platform operations cannot be copied between the sandbox accounts.

  • All newly created sandboxes are enabled by default. You can disable a sandbox if you no longer need it.

  • To retain the data of a sandbox you are about to delete, you must export the data as a CSV file and save the file for future importing purposes. For information about the import/export feature, see Importing and Exporting Data.

For more information, see the following:

 

 

 

Â