This article applies to version 6.
This tutorial explains how to set up a test Code42 environment that simulates a multi-server production Code42 environment. You can use the test environment to test upgrades and features without affecting your production environment.
If your production environment includes...
- One Code42 authority server and no storage servers, see Setting Up A Single-Server Test Environment.
- Multiple Code42 authority servers, contact your Customer Success Manager (CSM) at firstname.lastname@example.org to engage the Code42 Professional Services team. Or, post your question to the Code42 community to get advice from fellow Code42 administrators.
- Code42 environment
A broad term for all parts of a Code42 for Enterprise installation, which might include an authority server, storage servers, the administration console, organizations, users, and devices.
Example: "Go to Settings > Security > LDAP to enable LDAP integration for your Code42 environment."
- host server
- A physical or virtual machine that hosts a Code42 server.
- production environment
- The environment that supports the day-to-day operations of your business.
- test environment
- An environment dedicated to testing and separated from your production environment.
Your test environment should contain one authority server and at least one storage server. You do not need to set up the same number of storage servers in your test environment as in your production environment.
Before you begin
- Contact your Customer Success Manager (CSM). Ask for a master license key (MLK) for a test environment.
- Allocate two physical or virtual machines to host the test authority server and storage server. The machines need to match the system requirements for a Code42 server.
- Allocate a physical or virtual machine—separate from the test server hosts—to host a test Code42 app. The machine needs to match the system requirements for a Code42 app.
- Disconnect your test machines from your production network in order to avoid unintended interaction during testing.
- The test machines do need to communicate with one another.
Set up the test Code42 servers
Perform these steps for all your test Code42 servers: authority server and storage server:
- Assign IP addresses to the test servers.
Do not use IP addresses assigned to your production Code42 servers.
- If your test environment has a dedicated DNS server, configure DNS records for the test machines.
If there is no DNS server, assign host names on the test server machines:
- Open the hosts file with a text editor:
- Add or modify a line to say:
Do not use the host name of your production server.
- Open the hosts file with a text editor:
- In the test environment, install an authority server and at least one storage server, both using same version as your production servers. During the install, provide your new MLK for testing.
Code42 strongly recommends creating your test environment at the same Code42 version as your production environment. If you want to test a newer version, you can then upgrade the test environment. That way, any testing of new features comes after you have tested and affirmed that the upgrade works.
Verify Code42 server communication
Verify that the test Code42 servers communicate with each other.
- Sign in to the authority server's administration console.
- Navigate to Storage > Server.
- Click the name of the test storage server.
- Find the online indicator located at the top left of the server details.
A solid circle indicates that the storage server is online.
Production resources to never duplicate in your test environment
In your test environment, do not duplicate the following parts of your production environment:
Master license key
For your test Code42 servers, ask your Customer Success Manager (CSM) for a new master license key (MLK).
Storage provider key
If your production environment uses data storage in the Code42 cloud, do not use your production provider key in your test environment. Ask your CSM about Code42 cloud options, or use only local storage in your test environment.
The production and test authority servers must have different addresses. For test machines, assign IP addresses and host names different from the production machines. After installing the test authority server, go to Settings > Server, and set the addresses on the:
- Website protocol, host and port
- Primary network address
- Secondary network address
Do not import your production database into your test authority server. Doing so may cause your production environment to report incorrect licensing information and may interfere with the provider sync process.
Configure your test environment
Exactly which production details you need to duplicate in your test environment depends on what you intend to test. The following describes some typical suggestions:
Back up and protect your test environment's database as you do your production database. Backing up the database means you can recover your test authority server in the event of trouble or a test that goes bad.
Authentication and authorization
Administrators, users, and Code42 apps in test environments can use accounts defined within the test authority server. Add users in the administration console at Users > Add a new user.
Every Code42 server has a built-in email server that is sufficient for most test purposes. You may, however, configure your Code42 server to send mail through some other email server. That is particularly advisable if your test environment has a large number of users. Define the email server in the Code42 administration console, at Settings > Server > Email.
Backup settings—at system-wide and organization scales—govern backup frequency, retention, file selection, storage destinations, among other details. To make test and production environments match, you need to manually reproduce some backup settings at the test authority server. In the administration console:
- For settings that apply system-wide, see Settings > Device Backup
- For settings that apply to individual organizations:
- Go to Organizations.
- Select an organization by name.
- From the action menu, select Device Backup Defaults...
Some global backup settings you can export from production and import to test. See Export and Import at:
- Settings > Device Backup > Backup > Filename Exclusions
- Settings > Device Backup > General > Hidden Filenames
- Settings > Device Backup > General > Global Exclusions
- Settings > Device Backup > General > Cloud Exclusions
You may create additional store points in your test environment, beyond the default store point.
If your test and production environments used shared storage, be careful to create separate paths for test and production store points. That will make clear which archives belong to which environment.
Set up test Code42 devices
- Add Code42 app installer files to your test authority server.
- At the administration console, select App Downloads.
- Download Code42 app installer files for your test devices.
- Install the Code42 app on your test app machines.
Customized installers should not be used for upgrade testing.
- At Code42 app sign in to the test server.
- Register the Code42 apps under new user accounts.
- Use the Code42 apps to back up a small amount of data to the test Code42 server.