Standalone backup agent for Microsoft Windows servers and workstations (formerly Veeam Endpoint Backup FREE)
Post Reply
MVanek
Influencer
Posts: 12
Liked: 5 times
Joined: May 20, 2019 4:12 pm
Full Name: Martin Vanek
Contact:

Continue existing backup chain with new HW

Post by MVanek »

Hi,
I wonder if there is a possibility to let veeam to continue existing backup chain, when I move HDD from failed machine to new one (same HW).
Everything looks fine, rescan is successful and veeam can "see" the agent computer. But when I try to map it to new job (old one reported nothing to process), veeam performs new full.
Maybe I just missing something. I know with VMs there are MOREF IDs....I suppose agent backup works with similiar fashion.
Thanks for help
Martin
Egor Yakovlev
Veeam Software
Posts: 2536
Liked: 680 times
Joined: Jun 14, 2013 9:30 am
Full Name: Egor Yakovlev
Location: Prague, Czech Republic
Contact:

Re: Continue existing backup chain with new HW

Post by Egor Yakovlev »

Hi Martin,
Yes it is expected behavior. MoRefID in Virtual world and BIOS UUID in physical behave similar - new motherboard has different UUID(even if HDD is still the same), thus agent is treated as 100% new. You can double-proof that with cmd -> wmic -> csproduct.
/Thanks!
MVanek
Influencer
Posts: 12
Liked: 5 times
Joined: May 20, 2019 4:12 pm
Full Name: Martin Vanek
Contact:

Re: Continue existing backup chain with new HW

Post by MVanek »

Hi, yes, so its BIOS UID, I should have asked straight :D
Thank you!
Post Reply

Who is online

Users browsing this forum: Bing [Bot] and 40 guests