Search
- Filter results by:
- View attachments
- https://kb.netapp.com/Cloud/BlueXP/Cloud_Data_Sense/BlueXP_Classification_-_How_to_do_a_hard_reset_on_Podman_and_Docker_InstallationsApplies to BlueXP Classification (Data Sense or Cloud Compliance) Hard reset on Podman and Docker Installations Description Procedure to hard reset on BlueXP Classification Podman and Docker Installat...Applies to BlueXP Classification (Data Sense or Cloud Compliance) Hard reset on Podman and Docker Installations Description Procedure to hard reset on BlueXP Classification Podman and Docker Installations as for issues in network etc., hard reset is quicker than uninstall and re-install.
- https://kb.netapp.com/Cloud/BlueXP/Cloud_Data_Sense/BlueXP_Classification_-_How_to_find_if_share_path_is_mounted_on_data_sense_instanceApplies to BlueXP Classification (Data Sense or Cloud Compliance) Mount verification for NFS mount or CIFS shares Description Procedure to find if share path or export is mounted on data sense instanc...Applies to BlueXP Classification (Data Sense or Cloud Compliance) Mount verification for NFS mount or CIFS shares Description Procedure to find if share path or export is mounted on data sense instance
- https://kb.netapp.com/on-prem/ontap/DP/SnapLock/SnapLock-KBs/Is_it_possible_to_convert_SnapLock_mode_of_a_volumeIt is not possible to convert an existing SnapLock Enterprise volume to a SnapLock Compliance volume It is not possible to convert an existing SnapLock Compliance volume to a SnapLock Enterprise volum...It is not possible to convert an existing SnapLock Enterprise volume to a SnapLock Compliance volume It is not possible to convert an existing SnapLock Compliance volume to a SnapLock Enterprise volume When creating a FlexClone volume of a SnapLock volume, Compliance, Enterprise, or non-SnapLock can be specified as the new, cloned volume type. The SnapLock types of a new FlexClone volume do not need to match the SnapLock type of the parent volume.
- https://kb.netapp.com/Cloud/BlueXP/Cloud_Data_Sense/BlueXP_Classification_How_to_check_troubleshoot_and_fix_a_Data_Sense_upgradeApplies to BlueXP Classification (Data Sense or Cloud Compliance) DataSense version upgrade Description Procedure to check, troubleshoot and fix a Data Sense upgrade that has a failure or has been in ...Applies to BlueXP Classification (Data Sense or Cloud Compliance) DataSense version upgrade Description Procedure to check, troubleshoot and fix a Data Sense upgrade that has a failure or has been in the "Upgrading" state for awhile.
- https://kb.netapp.com/hybrid/StorageGRID/Object_Mgmt/How_to_manage_legacy_Compliant_buckets_in_StorageGRID_11.5Because the S3 Object Lock feature conforms to Amazon S3 requirements, it deprecates the proprietary StorageGRID Compliance feature, which is now referred to as the “legacy Compliance feature.” Compli...Because the S3 Object Lock feature conforms to Amazon S3 requirements, it deprecates the proprietary StorageGRID Compliance feature, which is now referred to as the “legacy Compliance feature.” Compliant ILM rules and ILM policies function the same for objects in legacy Compliant buckets as they do for S3 Object Lock objects in buckets with S3 Object Lock enabled.
- https://kb.netapp.com/Cloud/BlueXP/Cloud_Data_Sense/How_to_troubleshoot_BlueXP_Classification_previously_Data_Sense_or_Cloud_ComplianceApplies to BlueXP Classification (Data Sense or Cloud Compliance) Description Guide to assist in BlueXP Classification Troubleshooting
- https://kb.netapp.com/on-prem/ontap/OHW/OHW-KBs/How_to_remove_SnapLock_Compliance_volume_to_unjoin_nodes_from_FAS_AFF_systemApplies to ONTAP 9 FAS/AFF SnapLock Compliance Volumes Description Unable to unjoin nodes from cluster due to the existence of unused SnapLock Compliance volumes that have not reached the expiration d...Applies to ONTAP 9 FAS/AFF SnapLock Compliance Volumes Description Unable to unjoin nodes from cluster due to the existence of unused SnapLock Compliance volumes that have not reached the expiration date
- https://kb.netapp.com/Cloud/BlueXP/Cloud_Data_Sense/How_to_manually_collect_Data_Sense_Compliance_Classification_logsApplies to BlueXP Classification Description There is a built in script on the Classification VM that will manually zip up the Classification logs. This script takes all the logs and zips them into a ...Applies to BlueXP Classification Description There is a built in script on the Classification VM that will manually zip up the Classification logs. This script takes all the logs and zips them into a single file in the /tmp directory with filename datasense_logs_<date>.zip
- https://kb.netapp.com/Cloud/BlueXP/Cloud_Data_Sense/BlueXP_Classification_Where_to_find_install_logsApplies to BlueXP Classification (Data Sense or Cloud Compliance) Install Log Location Description Install log location for BlueXP Classification (Data Sense or Cloud Compliance)
- https://kb.netapp.com/Cloud/BlueXP/Cloud_Data_SenseOther Resources Recently Created Recently Updated Is it possible to automate Data Sense report generation?Tue, 25 Mar 2025 Classification : Upgrade was not successfulMon, 24 Mar 2025 BlueXP Classifica...Other Resources Recently Created Recently Updated Is it possible to automate Data Sense report generation?Tue, 25 Mar 2025 Classification : Upgrade was not successfulMon, 24 Mar 2025 BlueXP Classification Darksite v1.39 installation fails with connection refusedMon, 24 Mar 2025 Classification : Unbale to upgrade to latest version due to docker swarm errorSun, 23 Mar 2025 Classification : Upgrade stuck from 1.38 to 1.41Fri, 21 Mar 2025 Classification : CIFS file share keeps failing with retryFri…
- https://kb.netapp.com/Cloud/BlueXP/Cloud_Data_Sense/BlueXP_Classification_Do_containers_restart_automatically_after_stop_and_removeBlueXP Classification (Data Sense or Cloud Compliance) Container removal Container Autorestart All other containers except ds_mount_server start automatically even when removed. ds_mount_server has to...BlueXP Classification (Data Sense or Cloud Compliance) Container removal Container Autorestart All other containers except ds_mount_server start automatically even when removed. ds_mount_server has to be manually restarted. For Docker Installations: For Podman Installations: All other containers except ds_mount_servercontainer - example here datasense_celery_dirlist_worker - automatic restart on stop and remove container: ds_mount_server container - manual restart on stop and remove container: