You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Disaster Recovery Linux Manager (DRLM) Issue Template
Quick response time is not guaranteed with free support, if you are using DRLM in a production environment and enterprise grade level support services are required, please see: http://www.brainupdaters.net/en/drlm-services.
Please fill in the following items before submitting a new issue:
For a better ReaR-DRLM management the RESTful API needs to be improved to have a good error handling between DRLM and ReaR clients with standard HTTP response codes.
Also needs to be prepared to be extended easily to support more features.
DRLM Server information:
DRLM version (/usr/sbin/drlm -V): Future DRLM version 2.2.0
DRLM Client information:
ReaR version (/usr/sbin/rear -V): Future ReaR version 2.1
The text was updated successfully, but these errors were encountered:
From ReaR 2.1 (current snapshot) and DRLM 2.2.0 (current develop branch) there is a better error handling from client side (ReaR), also new/clients/ID/log resource has been added (see issue #58) and is prepared to support ReaR multiple configurations rear -C confname.
This change is backwards compatible for previous ReaR versions (since 1.17).
Disaster Recovery Linux Manager (DRLM) Issue Template
Quick response time is not guaranteed with free support, if you are using DRLM in a production environment and enterprise grade level support services are required, please see: http://www.brainupdaters.net/en/drlm-services.
Please fill in the following items before submitting a new issue:
Issue details:
For a better ReaR-DRLM management the RESTful API needs to be improved to have a good error handling between DRLM and ReaR clients with standard HTTP response codes.
Also needs to be prepared to be extended easily to support more features.
DRLM Server information:
DRLM Client information:
The text was updated successfully, but these errors were encountered: