Adding a Multi-String Value named
IgnoreNTFS with data \$Extend\* /s
Restart the server.
Use Alt+F10 to launch another console window
Enter “List Disk”,
If there is any disk which status is offline, customer can select this by “Select disk X”, X is the number shown by “List Disk”
Enter “ONLINE DISK”.
Enter “List Volume”
If there is any volume which status is “failed”, customer can select this by “Select volume X”, X is the number shown by “List Volume”
Enter “Detail Volume” to know the volume’s disk number Y.
Enter “Select Disk Y”
Enter “CLEAN” to clean the disk.
Use the command in step 3 and step 4 again to make sure there is no unhealthy status.
Enter “Exit” to exit diskpart.
Continue with the server factory reset process.
1. Generic workaround of server backup failure is to reconfigure server backup policy. It can solve some issues caused by environment change such as volume GUID change.
For the backup performance, please note:
Block level backup has better performance than file level backup. Block level backup means you select to back up the whole volume during creating the backup policy.
If a backup failed, the subsequent backup will cost more time. The subsequent backup will be a full backup and it will also try to prune the existing backup. So, it will cost much more time for a backup subsequent to a failed backup.
For the backup space management, Server backup will reclaim a small portion of existing backups when it needs new space. Usually, on the dashboard, you will get an alert notifying that backup disk has less than 10% free space. Server backup will
delete the existing backups automatically for space. You can ignore the alert and rely on the server to delete these backups if you don’t want to keep all. We have also updated the alert UI in UR3 to be clearer on the message. If you want to manually manage
the space, you can refer to this blog for further background and details: