Hey all - have an environment running 9.5 U4 and VCSA 6.7 U2. Noticed recently I cannot create a backup job using tags. There is simply no tag option in the "add VMs" window. I made sure that the VCSA is set for FQDN and all, but alas no go.
Any thoughts?
Thanks!
-
- Influencer
- Posts: 18
- Liked: 3 times
- Joined: Aug 03, 2016 8:20 pm
- Full Name: None
- Contact:
-
- Product Manager
- Posts: 14837
- Liked: 3083 times
- Joined: Sep 01, 2014 11:46 am
- Full Name: Hannes Kasparick
- Location: Austria
- Contact:
Re: Veeam 9.5 Update 4 w/ VCSA 6.7 U2 -- no tag option for jobs
Hello,
must be an issue in your environment. I have the same setup and it works.
Please open a support case and post the case number here for reference.
Best regards,
Hannes
must be an issue in your environment. I have the same setup and it works.
Please open a support case and post the case number here for reference.
Best regards,
Hannes
-
- Service Provider
- Posts: 29
- Liked: 8 times
- Joined: Nov 20, 2015 12:37 pm
- Full Name: Andy
- Contact:
Re: Veeam 9.5 Update 4 w/ VCSA 6.7 U2 -- no tag option for jobs
Hi,
this is a problem with your screen resolution and scaling settings.
Try a different resolution or tryx setting your scaling setting to 100%.
This helped me:
veeam-backup-replication-f2/b-r-replica ... 32324.html
this is a problem with your screen resolution and scaling settings.
Try a different resolution or tryx setting your scaling setting to 100%.
This helped me:
veeam-backup-replication-f2/b-r-replica ... 32324.html
-
- Influencer
- Posts: 18
- Liked: 3 times
- Joined: Aug 03, 2016 8:20 pm
- Full Name: None
- Contact:
Re: Veeam 9.5 Update 4 w/ VCSA 6.7 U2 -- no tag option for jobs
Hey guys - not a prob w/ screen scaling/resolution. Turns out, this VCSA had been rebuilt after an "oops" a few months ago. Backups had been recreated using VMs but apparently the VCSA was the same FQDN as the original and Veeam was not rebuilt/reconfigured, so it must have been unhappy inventorying VM tags. Granted, I would have expected more to not work, but after reinstalling Veeam and setting up a new config database everything is working as expected! Was probably throwing ID and MOB errors in logs some place but I didn't get that far in searching. Thanks all.
Who is online
Users browsing this forum: Google [Bot], Spex and 65 guests