We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Description: Networker VM Backups are currently not listed within the Backup Tools section, as described in Issue #6.
Request: Is there any option to add Dell Networker backups to the backup section?
Details: We observe backup information in the custom attributes of the VM, formatted as follows:
Last EMC vProxy Backup Backup Server=backup01.local, Policy=RZ, Workflow=vm_day_backup, Action=backup, JobId=71687619, StartTime=2024-06-10T19:59:13Z, EndTime=2024-06-10T19:59:38Z
Expected Behavior: The Backup Tools section should list the Networker VM Backups based on the custom attribute information provided.
Environment:
Steps to Reproduce:
Additional Information: Any guidance or updates on adding support for Dell Networker backups would be greatly appreciated.
Thank you for your attention to this issue.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Issue: Networker VM Backups Not Listed in Backup Tools Section
Description:
Networker VM Backups are currently not listed within the Backup Tools section, as described in Issue #6.
Request:
Is there any option to add Dell Networker backups to the backup section?
Details:
We observe backup information in the custom attributes of the VM, formatted as follows:
Expected Behavior:
The Backup Tools section should list the Networker VM Backups based on the custom attribute information provided.
Environment:
Steps to Reproduce:
Additional Information:
Any guidance or updates on adding support for Dell Networker backups would be greatly appreciated.
Thank you for your attention to this issue.
The text was updated successfully, but these errors were encountered: