Upgraded Veeam with Update 3.
Build Version is 9.5.0.1536
Centralized physical agent backups is awesome and all my agents are upgraded.
Below are my current challenges to get it working - Any suggestion is highly appreciated
-- Unable to read previous agent backup files. Is it by design?
-- Any additional port requirement - I see error "Connecting to VAW, ips: '_._._._ ', port: '6184'"
-- Any possibility to Map backups from earlier Agent backups?
-- Any known cross domain issues - " Cannot send backup job configuration to <server fqdn name > Error: Cannot connect to <server fqdn name>
-
- Influencer
- Posts: 13
- Liked: 4 times
- Joined: Dec 12, 2017 10:55 am
- Full Name: Sreejith Soman
- Contact:
-
- Product Manager
- Posts: 14725
- Liked: 1705 times
- Joined: Feb 04, 2013 2:07 pm
- Full Name: Dmitry Popov
- Location: Prague
- Contact:
Re: Upgraded to Veeam 9.5 Update 3
Hello and welcome to the community Sreejith.
Music to my ears, thank you!sreejiths wrote:Centralized physical agent backups is awesome and all my agents are upgraded.
No, backup files created by standalone agents should be fully operational.sreejiths wrote:Unable to read previous agent backup files. Is it by design?
Yes, additional ports are used for agent deployment. Take a look at this Help Center article.sreejiths wrote:Any additional port requirement - I see error "Connecting to VAW, ips: '_._._._ ', port: '6184'"
Unfortunately, this is not possible. You have to start a new backup chain after Veeam B&R starts to manage agent jobs (for both managed by VBR and managed by Agent types)sreejiths wrote:Any possibility to Map backups from earlier Agent backups?
Veeam B&R server host name should be resolved correctly from the agent side.sreejiths wrote:Any known cross domain issues - " Cannot send backup job configuration to <server fqdn name > Error: Cannot connect to <server fqdn name>
-
- Influencer
- Posts: 13
- Liked: 4 times
- Joined: Dec 12, 2017 10:55 am
- Full Name: Sreejith Soman
- Contact:
Re: Upgraded to Veeam 9.5 Update 3
Thank you for the response.
It was the port issue. My bookmarked port link dint had them covered.
its good now
It was the port issue. My bookmarked port link dint had them covered.
its good now
Who is online
Users browsing this forum: No registered users and 6 guests