Multiple Roles Walkthrough 

Overview 

This guide walks you through setting up multiple Comet Servers with separate roles.

Step 1 - Auth Server Role 

Ready to get started? The first server you need to configure is a Comet server in Auth role. This performs the following actions:

  • Management of users & customers
  • SSL Management
  • Remote configuration management of Comet Backup
  • Create branded Comet Backup installers
  • Handling of direct-to-cloud data storage model

Once you have downloaded and installed the Comet server you will be presented with the Comet Server Service Manager and the setup wizard.

The setup wizard will now guide you through the following steps. You can manually access the setup wizard at any time from the Configuration drop down.

1. Serial number 

You can generate serials from the 'My Account' section of cometbackup.com.

2. Branding 

From here you can set the product names and color scheme of the server.

3. Network 

This is the address on your network that you wish the Comet Server interface to be accessible from. This is also where you can enter the details to configure your Let's Encrypt SSL.

4. Admin accounts 

Configure admin and user accounts to the Comet server.

5. Authentication Role 

This is required if the server is being used for Authentication role.

6. Authentication Role – Request Storage Vault 

The Comet clients can request a pre-configured backup destination instead of entering one manually. From here you can configure the storage locations for the client and rebrand them. If you have a cloud storage destination, enter it here otherwise come back to this section once you have completed setting up your Storage Role server.

7. Authentication Role – Replication 

Come back to this section once you have completed setting up your Replication role server.

8. Authentication Role – Properties 

From here configure the rules for job logs and generating missed backup entries.

9. Storage Role 

This step confirms if this server will be used as a Storage Role server. As we are setting up our Auth server we do not need to check this box.

10. Software Build Role 

Select that this server will generate branded clients.

11. Software Build Role - Branding 

From here you can customize the appearance of the generated client.

12. Constellation Role 

As we are setting up an Auth server we do not need to check this. Constellation Role is covered further in this guide.

13. Start server 

Once you have finished the wizard, start your server

Your Comet server interface should now be accessible from the address you configured in step 3. You can run the setup wizard again at any time to configure your server. For advanced users you can also modify this via 'Configuration – Edit configuration file'.

For troubleshooting select SERVICE – Diagnostic Tools – Run in a popup.

If you need any further support please open a ticket from inside the My Account section of cometbackup.com

Step 2 - Storage Role 

This is required if you're not storing backup data on cloud storage. This performs the following actions:

  • Efficiently span data across multiple vaults, local and Cloud-based vaults simultaneously
  • Supports multiple storage types and operable on all common version of Windows and Linux

Steps:

  1. Install Comet server on the destination that you will be using for storage
  2. Complete steps 1 – 4 of the setup wizard
  3. Authentication Role – De-select this box
  4. Storage Role – Select this box
  5. Store Role – Locations. Configure the locations of where you wish data stored.
  6. Storage Role – Replication. This is where you can enter the details of another Storage Role server to replicate to.
  7. Software Build Role. As you are configuring this server for Storage Role only you do not need to check this box.
  8. Constellation Role. You do not need to check this box.
  9. Complete wizard
  10. Well done, you've just setup a storage destination for your clients.
  11. Repeat as many times as you like to setup further storage destinations.

Step 3 - Replication Role 

Replicating your data protects your data further by adding redundancy. This performs the following actions:

  • Highly efficient, automated, multi-threaded replication that you can rely on.
  • Supports one-to-one, one-to many, many-to-many replication.
  • Full replication of user configuration as well as storage data.

Steps:

  1. Install Comet server on the destination that you will be using for replication
  2. Complete steps 1 – 4 of the setup wizard
  3. Authentication Role – De-select this box
  4. Storage Role – Select this box
  5. Store Role – Locations. Configure the locations of where you wish data stored.
  6. Storage Role – Replication. Enter the details of the Comet Storage role server(s) that you wish to replicate with.
  7. Software Build Role. As you are configuring this server for Replication Role only you do not need to check this box.
  8. Constellation Role. You do not need to check this box.
  9. Complete wizard
  10. Well done, you've just setup replication for your clients.
  11. Repeat as many times as you like to expand your replication environment.

Step 4 - Constellation Role 

We highly recommend deploying a Constellation Role server if you are using replication as it provides the following benefits:

  • Ensures that redundant data is correctly handled across multiple storage locations.
  • Oversees all Comet Storage server and automatically purges unused storage buckets and performs general storage maintenance tasks.

Steps:

  1. Install Comet server on the destination that you will use to host your Constellation Role Server.
  2. Complete steps 1 – 4 of the setup wizard
  3. Authentication Role – do not select
  4. Storage Role – do not select
  5. Software Build Role – do not select
  6. Constellation Role – select
  7. Constellation Role – Targets. Enter the details of all of your Comet servers regardless of role.
  8. Constellation Role – Properties. Delete (Please carefully read the following first for enabling)

The 'Delete Data' option is the clean-up process of your Constellation server. It will look for orphaned data that isn't being used (for example, if a customer cancel but the data remains) across all your destinations and buckets and will prune it. This is why it is critical that all of your servers are in the Constellation server so that it can verify data across all of the locations if you select this option.

Each time you deploy a new server regardless of the role, as soon as you finish setting it up you must add it to your Constellation server before use.