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
The time variable should be in %H:%M %p or be equal to latest using cluster local time and the export will be executed using the snapshot at that time.
Current Behavior
The time variable finds the correct existing snapshot but then translates the time zone to client local time when running the POST command for the export, causing an export failure.
Failure Information (for bugs)
Using time='latest' or an exact time, the API finds the correct snapshot but then changes the time zone for the POST command, this example is running from client in PST on a cluster in UTC using 02:00 AM as the timestamp (on March 26th):
Traceback (most recent call last): sql_db_export = rubrik.sql_db_export(db_name, File "/Library/Frameworks/Python.framework/Versions/3.9/lib/python3.9/site-packages/rubrik_cdm/data_management.py", line 2561, in sql_db_export return self.post('v1', '/mssql/db/{}/export'.format(mssql_id), config, timeout) File "/Library/Frameworks/Python.framework/Versions/3.9/lib/python3.9/site-packages/rubrik_cdm/api.py", line 249, in post return self._common_api( File "/Library/Frameworks/Python.framework/Versions/3.9/lib/python3.9/site-packages/rubrik_cdm/api.py", line 168, in _common_api raise APICallException(error_message) rubrik_cdm.exceptions.APICallException: Cannot recover database to time Mar 26, 2021 09:00:00 GMT.
This function should be modified to either not translate the time zone or to only translate it if they're on different time zones. Right now it does it regardless, so if you adjust to your local time it will still fail.
Steps to Reproduce
Use sql_db_export on a Rubrik cluster that has a different time zone then the client.
This is remediated if you set an environmental variable before running Python (i.e. TZ="Europe/London" python3 script.py)
Context
Running CDM 5.3.0-p3-18540
The text was updated successfully, but these errors were encountered:
Expected Behavior
When running:
rubrik.sql_db_export(db_name, date, time, sql_instance, sql_host, target_instance_name, target_hostname, target_database_name, target_data_file_path, target_log_file_path, allow_overwrite=True)
The time variable should be in
%H:%M %p
or be equal tolatest
using cluster local time and the export will be executed using the snapshot at that time.Current Behavior
The time variable finds the correct existing snapshot but then translates the time zone to client local time when running the POST command for the export, causing an export failure.
Failure Information (for bugs)
Using time='latest' or an exact time, the API finds the correct snapshot but then changes the time zone for the POST command, this example is running from client in PST on a cluster in UTC using 02:00 AM as the timestamp (on March 26th):
Traceback (most recent call last): sql_db_export = rubrik.sql_db_export(db_name, File "/Library/Frameworks/Python.framework/Versions/3.9/lib/python3.9/site-packages/rubrik_cdm/data_management.py", line 2561, in sql_db_export return self.post('v1', '/mssql/db/{}/export'.format(mssql_id), config, timeout) File "/Library/Frameworks/Python.framework/Versions/3.9/lib/python3.9/site-packages/rubrik_cdm/api.py", line 249, in post return self._common_api( File "/Library/Frameworks/Python.framework/Versions/3.9/lib/python3.9/site-packages/rubrik_cdm/api.py", line 168, in _common_api raise APICallException(error_message) rubrik_cdm.exceptions.APICallException: Cannot recover database to time Mar 26, 2021 09:00:00 GMT.
This function should be modified to either not translate the time zone or to only translate it if they're on different time zones. Right now it does it regardless, so if you adjust to your local time it will still fail.
Steps to Reproduce
Use sql_db_export on a Rubrik cluster that has a different time zone then the client.
This is remediated if you set an environmental variable before running Python (i.e. TZ="Europe/London" python3 script.py)
Context
Running CDM 5.3.0-p3-18540
The text was updated successfully, but these errors were encountered: