VSR and Changed block tracking

[iforbes]

Hi. I've noticed that VSR doesn't seed exact contents of the source vm folder. It seeds the .vmdk file(s) and creates several VSR specific files. Is this because files on the source like .log, .vmx, .lck, etc are recreated during VSR restore? More specifically I have an Avomar backup solution that uses changed block tracking. I notice the ctk file (changed block tracking file) on the source vm folder, but don't see that file on the target storage folder. Will I have to reseed all of my Avomar backups once the vm is restored via VSR at target site?

[vbrowncoat]

1. yes

2. This is really a question for Avamar. Are you failing over to a different vCenter or the same? I'm not sure how Avamar will react to that. if it's a different vCenter it seems like it will see it as a different VM. On the backend though I would think that it wouldn't need to copy all the data again as I think Avamar has global dedupe.

I recommend checking with someone knowledgable in Avamar on this and/or testing it yourself.

[iforbes]

Thanks. Yes, it's replicating to a different vcenter. I'll check with Avomar.