Hello fs.shmidt!
My official answer would be to scrap the old path entirely once the migration is over. It's not possible to "recycle" another server's backup path, as during an External Restore domains/Classes of Service/mailboxes and items are created with new IDs which are different than those in the old server - so the metadata of the old backup is inconsistent with the new server.
BUT
There's something more 
Item BLOBs' contents are not based on any kind of changing ID: this means that you can salvage the vast majority of old BLOBs to speed up the initialization process and avoid disk usage overhead.
In order to do so you need to:
- Delete every file in the backup path used as the migration's import path except for the "items" directory.
- Make sure that the RealTime Scanner is disabled (it should be, I'm just overzealous)
Code:
zxsuite backup getProperty ZxBackup_RealTimeScanner
- Set what's left of the old backup as the Backup Path through the ZeXtras CLI
Code:
zxsuite backup setProperty ZxBackup_DestPath /path/to/your/backup
- Start a SmartScan in order to initialize the Backup Path
Code:
zxsuite backup doSmartScan
- Once the SmartScan is completed, run a Coherency Check with the "fixBackup" option to move broken and unreferenced BLOBs out of the backup
Code:
zxsuite backup doCoherencyCheck /path/to/your/backup fixBackup true
- You can now delete the BLOBs moved out by the Coherency Check (check the path in the "Operation Completed" notification) and enjoy ZeXtras Suite!
Make sure to use the CLI commands I mentioned, the ZeXtras Administration Zimlet has additional safety checks that won't allow you to follow some of the steps.
Have a nice day,
Cine
the ZeXtras Team
Bookmarks