Just sharing in case someone is having the same issue. You are not alone! Lol
Symptom: NetApp backups stuck in "SCAN" phase after upgrade to 11.40
Thousands of Logs on proxy:
Reparse point added to folder list, ReparsePoint=[\\CYR-A001\c$\CYRA001_E]
Reparse point added to folder list, ReparsePoint=[\\CYR-A001\c$\CYRA001_E]
Reparse point added to folder list, ReparsePoint=[\\CYR-A001\c$\CYRA001_E]
Reparse point added to folder list, ReparsePoint=[\\CYR-A001\c$\CYRA001_E]
Yes, I know C$ is not recommended, but it worked fine for 10 years before this upgrade.
Took me multiple weeks to even acknowledge there is an issue! Still no resolution from support but meh.
Workaround: Recreating the subclient (162 subclients, fun times!)
Root cause as per support:
Top-level content processing was enabled by default in SP38 to prevent synthetic full job failures due to empty backups. However, this change introduced an issue during upgrades when the Subclient content path itself is mount point.
Newly created NetApp subclients are designed to use shared scan, where top-level folder processing is not enabled by default. As a result, you not encounter this issue on newly created subclients.
As a workaround, you could disable the "Follow mount points" option at the subclient level to avoid the issue.
However, since the you already replaced 70% of the old, problematic subclients with new ones, you preferred to continue with the same approach for the remaining subclients to maintain consistency across the environment.T
Not looking for answers, just sharing in case it happens to you too, you are not alone, you are not crazy. It was a struggle to even have support admit this was an issue.
