I have a remote workstation that connects over a VPN to Veeam, I had to change several things and it ended up with a different hostname and IP address, and on a different VPN segment where it saw the Veeam server with a different ip. I couldn't figure out how to get the Windows Agent to change which IP it was looking at, so I added a new computer in inventory and switched the job to use that instead. That ended up giving me all sorts of cryptic errors that seemed to be caused by it being on a new job.
Anyhow, I figured I could just delete the job and re-map the backups, so I did, but when select the backup repository I'm never given the option to map the backup, even after following the instructions to remove from configuration/rescan repository.
-
- Influencer
- Posts: 14
- Liked: never
- Joined: Oct 11, 2021 8:28 pm
- Full Name: Micah Leier
- Contact:
-
- Product Manager
- Posts: 2578
- Liked: 707 times
- Joined: Jun 14, 2013 9:30 am
- Full Name: Egor Yakovlev
- Location: Prague, Czech Republic
- Contact:
Re: Unable to map backups from VRB Workstation client
Hi Micah,
Too many changes to guess of the root to solve the issue.
It will be best to work it out with support team - feel free to open a ticket at my.veeam.com - I'm sure of successful resolution.
/Thanks!
Too many changes to guess of the root to solve the issue.
It will be best to work it out with support team - feel free to open a ticket at my.veeam.com - I'm sure of successful resolution.
/Thanks!
-
- Product Manager
- Posts: 14716
- Liked: 1703 times
- Joined: Feb 04, 2013 2:07 pm
- Full Name: Dmitry Popov
- Location: Prague
- Contact:
Re: Unable to map backups from VRB Workstation client
Hi,
Mapping for managed by agent job is performed automagically, please follow the steps from the KB article to make it work: Veeam Agent Managed by Agent jobs mapping. Thanks!
Try to flush DNS on a Veeam B&R server and perform a rescan. IP addresses received during name resolution are stored in the Veeam B&R DNS cache, so if the change was performed - it's good to clear the local machines cache first.it ended up with a different hostname and IP address, and on a different VPN segment where it saw the Veeam server with a different ip
Mapping for managed by agent job is performed automagically, please follow the steps from the KB article to make it work: Veeam Agent Managed by Agent jobs mapping. Thanks!
Who is online
Users browsing this forum: No registered users and 6 guests