Version Rollback

During application updates or new deployments, there may be cases where you need to revert to a previous working version of your application. This document explains two rollback methods, their procedures, and important limitations to consider.

Rollback Methods

Option 1. Re-upload Previous Build (Recommended for All Plans)

1. Download the previous working build from:

   • Your S3 storage (Only for Enterprise Plan user)

   • OR the Old Control Panel (For All Plans)
     https://controlpanel-old.eagle3dstreaming.com/

2. Upload the previous build as a new version.

3. This method ensures a clean deployment without directly modifying shared infrastructure.

Pros:

• Safe and supported on all plans

• Minimal risk of deployment issues

Cons:

• Time-consuming

Option 2. Manual Shared-Drive Rollback (Only for Enterprise Plan)

Enterprise users can manually manage versions directly via the shared drive. This allows rolling back quickly without uploading the old build.

Steps:

1. Disable the “delete old version” feature on the shared drive.

2. Access the shared drive on your VM.

3. Delete the latest problematic version (e.g., v10).

4. Rename the previous version (e.g., v9) to the latest version name (v10).

Example:

• Version 10 is uploaded and has issues

• Version 9 is the last working build

• Delete v10 and rename v9 → v10

• Application now runs v9 as the active version

Important Limitations:

• Manual Handling: Any mistake during renaming or deletion can break the deployment.

• Shared Drive Rebuilds: If the shared-drive machine is deleted or rebuilt, it will automatically pull the latest uploaded version. Older versions may be lost.

• Storage Management: Disabling the delete-old-version feature keeps all previous builds on the shared drive. Over time, this can fill the drive and cause operational issues. Customers are responsible for cleaning up old versions.

Pros:

• Fast rollback without re-uploading builds

• Immediate effect for all running instances

Cons:

• Requires careful manual handling

• Risk of data mismatch or deployment failure

Summary

Manual rollback via shared drive is a powerful tool for Enterprise users who require fast recovery, but it comes with operational risks. All users should consider their plan level, storage capacity, and team capability before using this feature.

💬 Ask questions and help your peers Community Forum

📄 Need help? Contact Support

Facebook | Github | Linkedin | Youtube