Skip to main content
NetApp Knowledge Base

Search

  • Filter results by:
    • View attachments
    Searching in
    About 9 results
    • Adding or editing an SVM in SC fails with "API invoke failed"
      https://kb.netapp.com/data-mgmt/SnapCenter/SC_KBs/Adding_storage_system_to_SC_fails_with_API_invoke_failed
      Applies to SnapCenter Server (SC) SnapCenter Plug-in for VMware vSphere (SCV) Adding or editing an SVM Issue Adding or editing an SVM in SC or SCV fails with error: Netapp Error. Failed to connect to ...Applies to SnapCenter Server (SC) SnapCenter Plug-in for VMware vSphere (SCV) Adding or editing an SVM Issue Adding or editing an SVM in SC or SCV fails with error: Netapp Error. Failed to connect to storage system <FQDN> API Invoke failed
    • Failed to create snapshot with Data ONTAP VSS Hardware Provider
      https://kb.netapp.com/data-mgmt/SnapCenter/SC_KBs/Failed_to_create_snapshot_with_Data_ONTAP_VSS_Hardware_Provider
      Applies to SnapCenter Plug-in for Windows (SCW) Veeam Backup Issue Veeam Backups fail Error message: Failed to add volume [\\?\Volume{<voume_id>}\] to the VSS snapshot set
    • How to find the path of SnapCenter Server database repository backups
      https://kb.netapp.com/data-mgmt/SnapCenter/SC_KBs/How_to_find_the_path_of_SnapCenter_Server_database_repository_backups
      Applies to SnapCenter Server 4.1 Description This article describes how to find the path of SnapCenter Server database repository backups.
    • SnapCenter SCV:  Unable to quiesce on SCV: Exception occurred when quiescing virtual machines: VM_NAME
      https://kb.netapp.com/data-mgmt/SnapCenter/SC_KBs/SnapCenter_SCV__Unable_to_quiesce_on_SCV__Exception_occurred_when_quiescing_virtual_machines__VM_name
      Applies to SnapCenter plugin for VMware vSphere (SCV) 4.3 Issue SCV 4.3 Unable to quiesce virtual machines during backup
    • How to enable the feature "Enable Teams Backup" for backup of MS Teams Chat
      https://kb.netapp.com/Legacy/SaaS_Backup/How_to_enable_the_feature_Enable_Teams_Backup_for_backup_of_MS_Teams_Chat
      Applies to SaaS Backup for Microsoft Office 365 (SaaS) Microsoft Teams Description How to enable the feature Enable Teams Backup for backup of Microsoft Teams Chat
    • Is there a way to restore all mail for an O365 user from March 2018 to March 2019 without opening each restore point created over the 12 month period and completing individual restores?
      https://kb.netapp.com/Legacy/SaaS_Backup/Is_there_a_way_to_restore_all_mail_for_an_O365_user_without_opening_each_restore_point_created_over_the_12
      Applies to SaaS Backup for Microsoft Office 365 (SaaS) Answer This SaaS feature has not been implemented at this moment. Additional Information
    • SaaS backup or synchronization jobs fail with "Access token could not be refreshed for service"
      https://kb.netapp.com/Legacy/SaaS_Backup/SaaS_backup_or_synchronization_jobs_fail_with_Access_token_could_not_be_refreshed_for_service
      Applies to SaaS Backup for Microsoft Office 365 Issue SaaS backup or synchronization jobs fail with error: Access token could not be refreshed for service
    • After restoring a database to another location and migrating databases back to its source, backups are failing
      https://kb.netapp.com/Legacy/SnapManager/After_restoring_a_database_to_another_location_and_migrating_databases_back_to_its_source_backups_are_failing
      Applies to SnapManager for Microsoft SQL (SMSQL) 7.2.3 SnapDrive for Windows (SDW) 7.1.5 Issue After restoring a database to another location and migrating databases back to its source, backups are fa...Applies to SnapManager for Microsoft SQL (SMSQL) 7.2.3 SnapDrive for Windows (SDW) 7.1.5 Issue After restoring a database to another location and migrating databases back to its source, backups are failing. Error: Unable to create a Snapshot copy This operaton can not be preformed by NEtApp Tec
    • Trident v20.01 fails to update backend with Error: "Unable to find key"
      https://kb.netapp.com/Cloud/Astra/Trident/Trident_v20_01_fails_to_update_backend_with_Error__Unable_to_find_key
      Applies to Trident v20.01 and higher Kubernetes Issue Customer not able to update the Trident v20.01 backend.json config using the 'tridentctl update backend' command Error: problem persisting renamed...Applies to Trident v20.01 and higher Kubernetes Issue Customer not able to update the Trident v20.01 backend.json config using the 'tridentctl update backend' command Error: problem persisting renamed backend error: Unable to find key"