-
- Veeam Vanguard
- Posts: 395
- Liked: 169 times
- Joined: Nov 17, 2010 11:42 am
- Full Name: Eric Machabert
- Location: France
- Contact:
Volume Label is too long/short, limit is 1 to 42
Hi everyone,
I'am installing Veeam B&R 6 patch3 and I have an issue when attempting a resore since Veeam can't mount the NFS datastore because VMWare vSphere 5 does not accept a volume name that is larger than 42 characters.
I can't reduce my domain name length (server name + TLB = 35 characters), so how can I tell veeam to use it's IP adress instead of it's dns name for the vPowerNFS mount ?
Thank you.
I'am installing Veeam B&R 6 patch3 and I have an issue when attempting a resore since Veeam can't mount the NFS datastore because VMWare vSphere 5 does not accept a volume name that is larger than 42 characters.
I can't reduce my domain name length (server name + TLB = 35 characters), so how can I tell veeam to use it's IP adress instead of it's dns name for the vPowerNFS mount ?
Thank you.
Veeamizing your IT since 2009/ Veeam Vanguard 2015 - 2023
-
- Veeam Vanguard
- Posts: 395
- Liked: 169 times
- Joined: Nov 17, 2010 11:42 am
- Full Name: Eric Machabert
- Location: France
- Contact:
Re: Volume Label is too long/short, limit is 1 to 42
Answered to myself, I removed the server that had been added with the FQDN and then I re-added it with it's short name.
Now able to restore.
Now able to restore.
Veeamizing your IT since 2009/ Veeam Vanguard 2015 - 2023
-
- Veteran
- Posts: 295
- Liked: 59 times
- Joined: Sep 06, 2011 8:45 am
- Full Name: Haris Cokovic
- Contact:
Re: Volume Label is too long/short, limit is 1 to 42
Great forum with self healing effects
-
- Veeam Vanguard
- Posts: 395
- Liked: 169 times
- Joined: Nov 17, 2010 11:42 am
- Full Name: Eric Machabert
- Location: France
- Contact:
Re: Volume Label is too long/short, limit is 1 to 42
Yeah, that's why I love Veeam, problems
By the way, this limitation is not clearly mentionned and should be stated in the FAQ, as it could save time to many users
Don't you think ?
By the way, this limitation is not clearly mentionned and should be stated in the FAQ, as it could save time to many users
Don't you think ?
Veeamizing your IT since 2009/ Veeam Vanguard 2015 - 2023
-
- Chief Product Officer
- Posts: 31790
- Liked: 7294 times
- Joined: Jan 01, 2006 1:01 am
- Location: Baar, Switzerland
- Contact:
Re: Volume Label is too long/short, limit is 1 to 42
FAQ stands for frequently asked questions... this one only came up once in 5 years
-
- Veeam Vanguard
- Posts: 395
- Liked: 169 times
- Joined: Nov 17, 2010 11:42 am
- Full Name: Eric Machabert
- Location: France
- Contact:
Re: Volume Label is too long/short, limit is 1 to 42
So I suggest you open the RAQ (Rarely Asked Questions)
Veeamizing your IT since 2009/ Veeam Vanguard 2015 - 2023
-
- Enthusiast
- Posts: 27
- Liked: 5 times
- Joined: May 21, 2012 2:28 pm
- Full Name: Andrew Carpenter
- Contact:
Re: Volume Label is too long/short, limit is 1 to 42
Sorry to dig up an old thread, but I'm having the same issue. Trying to restore guest O/S files from a Linux server and it's failing because of this too short / too long problem.
Veeam says:
Can anyone help please? Not sure how I can fix this.
Thank you.
Andrew
Veeam says:
vCenter says:01/08/2013 09:46:26 Multi-OS File Level Restore started
01/08/2013 09:47:04 Fail Failed to mount vPower NFS datastore to host "ccesx05.cirencester.local" Error: Unable to mount vPower NFS volume (CCBACKUPPROX01.cirencester.local:/VeeamBackup_CCBACKUPPROX01.cirencester.local). CCBACKUPPROX01.cirencester.local: An error occurred during host configuration.
10.10.242.15: An error occurred during host configuration.
01/08/2013 09:47:04 Fail Unknown failure Error: Unable to mount vPower NFS volume (CCBACKUPPROX01.cirencester.local:/VeeamBackup_CCBACKUPPROX01.cirencester.local). CCBACKUPPROX01.cirencester.local: An error occurred during host configuration.
10.10.242.15: An error occurred during host configuration.
I guess it's choking on the name "CCBACKUPPROX01.cirencester.local:/VeeamBackup_CCBACKUPPROX01.cirencester.local". CCBACKUPPROX01 is our Veeam Backup Proxy server that talks to the repository.Operation failed, diagnostics report: Volume Label is too long/short, limit is 1 to 42 characters
Can anyone help please? Not sure how I can fix this.
Thank you.
Andrew
-
- Veeam Software
- Posts: 21138
- Liked: 2141 times
- Joined: Jul 11, 2011 10:22 am
- Full Name: Alexander Fogelson
- Contact:
Re: Volume Label is too long/short, limit is 1 to 42
Andrew, have you tried to add that server to Veeam B&R console using its short DNS name or IP address? In this case the vPowerNFS datastore name will be like VeeamBackup_CCBACKUPPROX01, without domain and suffix, which is much shorter.
-
- Veeam Software
- Posts: 21138
- Liked: 2141 times
- Joined: Jul 11, 2011 10:22 am
- Full Name: Alexander Fogelson
- Contact:
Re: Volume Label is too long/short, limit is 1 to 42
Another option is to change the server's display name directly in the SQL database using the following script:
This is what our support usually advises to do in such cases.
Code: Select all
$server = Get-VBRServer | ?{$_.name -eq "name of proxy"}
$server.SetName("Newname of proxy")
-
- Enthusiast
- Posts: 27
- Liked: 5 times
- Joined: May 21, 2012 2:28 pm
- Full Name: Andrew Carpenter
- Contact:
Re: Volume Label is too long/short, limit is 1 to 42
Hi foggy, thanks for responding.
Using your clues I was able to resolve the problem. For anyone coming to this thread in search of the solution, here's a summary what I did:
I added a new backup proxy using the short name of the backup proxy server (ccbackupprox01 instead of ccbackupprox01.cirencester.local). I then removed the other backup proxy from the list. Next I edited the backup repository. Go to the vPower NFS section, and ensure the correct backup proxy (with the short name) is selected from the drop-down list.
After making those changes I verified backups could still run successfully. I then tested whether the Guest Files (Other OS) restore would now work, which it did.
If your backup jobs are set to use a specific backup proxy, you'll need to edit those. Mine were all set to automatic, so I didn't need to change them.
Thanks again.
Andrew
Using your clues I was able to resolve the problem. For anyone coming to this thread in search of the solution, here's a summary what I did:
I added a new backup proxy using the short name of the backup proxy server (ccbackupprox01 instead of ccbackupprox01.cirencester.local). I then removed the other backup proxy from the list. Next I edited the backup repository. Go to the vPower NFS section, and ensure the correct backup proxy (with the short name) is selected from the drop-down list.
After making those changes I verified backups could still run successfully. I then tested whether the Guest Files (Other OS) restore would now work, which it did.
If your backup jobs are set to use a specific backup proxy, you'll need to edit those. Mine were all set to automatic, so I didn't need to change them.
Thanks again.
Andrew
-
- Veeam Software
- Posts: 21138
- Liked: 2141 times
- Joined: Jul 11, 2011 10:22 am
- Full Name: Alexander Fogelson
- Contact:
Re: Volume Label is too long/short, limit is 1 to 42
Andrew, thanks for updating the thread. Glad you've resolved the issue successfully.
-
- Veeam ProPartner
- Posts: 28
- Liked: 7 times
- Joined: Mar 16, 2011 8:36 am
- Full Name: Leonhard Kurz
- Contact:
[MERGED] fqdn instead of netbios name in NFS mount
Hi,
when I trigger instant recovery, the fqdn is used in the name/folder of the NFS mount. As the fqdn is pretty long, it's even truncaded with an "_". It works all right but I'd preffer the "official" naming. Any idea where to configure/change this or what went wrong?
Cheers
__Leo
when I trigger instant recovery, the fqdn is used in the name/folder of the NFS mount. As the fqdn is pretty long, it's even truncaded with an "_". It works all right but I'd preffer the "official" naming. Any idea where to configure/change this or what went wrong?
Cheers
__Leo
-
- Veeam Software
- Posts: 21138
- Liked: 2141 times
- Joined: Jul 11, 2011 10:22 am
- Full Name: Alexander Fogelson
- Contact:
Re: Volume Label is too long/short, limit is 1 to 42
Leo, you can re-add the corresponding server using its short name to Veeam B&R console.
Who is online
Users browsing this forum: Google [Bot] and 80 guests