DRB Server Best Practices for Rinsed Implementation

This documentation provides some best practices around the physical DRB server(s) where your Rinsed API connection will live. It is highly recommended that most/all of the below items be implemented. These recommendations will help mitigate potential server downtime as well as make troubleshooting more efficient.

Hardware Labeling

Physically identifying/labeling the DRB server appliance where the Rinsed API connection will live is vital. Labeling the server can speed up future troubleshooting efforts, especially if the server is in the same area as other computers and appliances. If you have multiple replication groups throughout your organization, labeling each server where the Rinsed API connection will live is important. Labeling examples:

• "Rinsed API Connection"
• "Rinsed API Server"
• "DRB/Rinsed Server"

Redundant Power

Power surges/outages are common occurrences at wash sites. To help mitigate downtime due to short-term power loss and surges, keeping the physical server behind a battery backup (UPS) is recommended. A generic, 1500-watt UPS is sufficient.

Public IP Address

Rinsed does not manage customer networks. For additional guidance on this topic, please consult with an internal/external IT contact.

To avoid additional port-forwarding within your internet provider's modem/router, a public static IP should be assigned to the customer SonicWall firewall. This is a small, additional monthly expense from your internet provider. DRB support or an internal/external IT contact can assist with assigning a procured public IP to the SonicWall firewall.

Backup Internet Connection

Rinsed does not manage customer networks. For additional guidance on this topic, please consult with an internal/external IT contact.

In the event your primary internet service fails, a backup connectivity solution is good practice in keeping the API connection up. A cellular backup service is a great option to fulfill this avenue.