Chatee ahora con Soporte
Chat con el soporte

StoragePoint 6.4 - Known Issues

Known Issues
Introduction Installer May Not Always Rollback on Cancel Installer May Fail if Critical Updates Are Missing Uninstalling other Metalogix Products Applying CU or Updates Large File Support Large File Content Type FIPS Compliance Incorrect Endpoint Size and BLOB Count on Dashboard Using the Previous Version of SharePoint for the Look and Feel SharePoint 2013 Eval Sites Loading Files Outside of the UI Bulk Recall and Unused BLOB Cleanup Selecting Scope for a Profile goes to Central Admin Scheduling the Process Existing Jobs Customized or Unghosted Files Move-SPSite Upgrade Support from Previous Versions of StoragePoint Deprecated Data Types Modern UI for SharePoint 2019/SharePoint SE BLOBS Not Being Removed by UBC Upgrade from 5.9.0.74 to 6.1 is failing with a timeout error When Metadata Change Rule Condition is Content Property=Folder, blobs are not archived Masterkey error after migration (SharePoint 2013/SharePoint 2016) Not all missing blobs are repopulated when the option “Restore Missing blobs” in BLOB Health Analyzer is checked Unused BLOB Cleanup job counts unused BLOBs as backup BLOBs Number of BLOBs to migrate and size of migrated BLOBs are always 0 in BLOB Migrate Analyze and Estimate After completing the StoragePoint upgrade process from 5.x, the old logos are maintained. Analyze and Estimate for BLOB recall/externalize is not accurate if large file(s) exist(s) "TypeLoadException: Could not load file or assembly 'Bluethread.SharePoint.StoragePoint.Utilities" ULS error Free space is marked as N/A for endpoints BLOB Migrate displays free space as 0B There is an error “This page has encountered a critical error. Contact your system administrator if this problem persists.” when cataloging librarian from the Web Application or Content Database
About Us

Masterkey error after migration (SharePoint 2013/SharePoint 2016)

If a user has moved CDB on to another SQL instance with a different SMK (service master key), the connection between the SMK and DMK will be broken. To work correctly (e.g. a STP upgrade) with those CDBs, StoragePoint needs to regenerate the DMK with the following SQL query:

OPEN MASTER KEY DECRYPTION BY PASSWORD = '<DMK password>'; -- password used to protect DMK on previous/source SQL instance

ALTER MASTER KEY REGENERATE WITH ENCRYPTION BY PASSWORD = '<new or the same DMK password>'; -- could be used the same password but this one will be "secured" by target SQL instance SMK

CLOSE MASTER KEY;

 

You do not need to regenerate DMK if CDB does not have DMK or if the existing DMK is working correctly.

 

Not all missing blobs are repopulated when the option “Restore Missing blobs” in BLOB Health Analyzer is checked

info

NOTE: SharePoint 2019 and above only.

 

When the option “Restore missing blobs” is checked, and some BLOBs are missing from the endpoint, not all the missing BLOBs are repopulated.

BLOB Health Analyzer restores only BLOBs associated with a SharePoint file/attachment. In SharePoint 2019 and above, there are some BLOBs that are externalized and do not belong to any files, so even if they are backed up, they are not repopulated when the option “Restore Missing blobs” in BLOB Health Analyzer is checked.

Unused BLOB Cleanup job counts unused BLOBs as backup BLOBs

If a storage profile has a backup endpoint configured and a SharePoint file (contained within the scope of the storage profile) is deleted, its residual BLOBs will be counted twice. They will appear both in the "Unused BLOB files marked for future deletion" field and in the "Unused backup BLOB files marked for future deletion" field, without necessarily having backup BLOBs of the SharePoint file.

If the storage profile does not have a backup endpoint configured, this behavior will not occur.

Number of BLOBs to migrate and size of migrated BLOBs are always 0 in BLOB Migrate Analyze and Estimate

 

In the case of synchronized profiles, the number of BLOBs to migrate and the size of migrated BLOBs in the Migration Analyze and Estimate feature is inaccurate unless a BLOB Health Analyzer job has been run first.

Documentos relacionados

The document was helpful.

Seleccionar calificación

I easily found the information I needed.

Seleccionar calificación