Discussions specific to the Microsoft Hyper-V hypervisor
Post Reply
engit
Novice
Posts: 3
Liked: 1 time
Joined: Apr 23, 2020 1:51 pm
Contact:

Renaming Rotated Drives Backup Job & Related Backup Directory

Post by engit » Apr 23, 2020 2:07 pm

Support Case: 04137440

We've followed the article here: https://www.veeam.com/kb2174

But this does not seem to apply/work for jobs that use Rotated drives.

So far we've:
- Renamed the backup Job
- Removed backup disk from configuration
- Renamed backup directory
- Tried to re-add/discover backup directory using 'Rescan'

The last step doesn't find the renamed directory and the "Rescan" option when right clicking on the Backup Repository isn't available like it is for other backup repositories.

Is there a way to get Veeam to re-discover the renamed backup directory or to manually enter the path to a backup location?

Dima P.
Product Manager
Posts: 11404
Liked: 983 times
Joined: Feb 04, 2013 2:07 pm
Full Name: Dmitry Popov
Location: Prague
Contact:

Re: Renaming Rotated Drives Backup Job & Related Backup Directory

Post by Dima P. » Apr 23, 2020 7:53 pm

Hello engit,

What is you Veeam B&R version? How many rotated drives you have? Can you import previously created backup to Veeam B&R console via import functionality? Cheer!

engit
Novice
Posts: 3
Liked: 1 time
Joined: Apr 23, 2020 1:51 pm
Contact:

Re: Renaming Rotated Drives Backup Job & Related Backup Directory

Post by engit » Apr 30, 2020 3:35 pm

Hi Dima,

Sorry for the slow response.

Our Veeam B&R version is: 10.0.0.4461 P1
We have 8 rotated drives (All 4TB Seagate)

I believe we can import but the issue we are having is backing up to new drives. The drive shows up in the HyperV host and is set to the same drive letter. We actually use these same rotated drives with another VM backup job which works fine. The job that fails is a 'File Share' job.

foggy
Veeam Software
Posts: 19048
Liked: 1693 times
Joined: Jul 11, 2011 10:22 am
Full Name: Alexander Fogelson
Contact:

Re: Renaming Rotated Drives Backup Job & Related Backup Directory

Post by foggy » May 08, 2020 4:40 pm

Not sure I understand the setup as repositories with rotated drives are not supported for NAS backup (File Share jobs).

engit
Novice
Posts: 3
Liked: 1 time
Joined: Apr 23, 2020 1:51 pm
Contact:

Re: Renaming Rotated Drives Backup Job & Related Backup Directory

Post by engit » May 11, 2020 11:40 am 1 person likes this post

Thanks foggy, that was our issue. We've switched to a non-rotated repository now and things are working as expected.

selva
Influencer
Posts: 14
Liked: 1 time
Joined: Apr 07, 2017 5:30 pm
Contact:

Re: Renaming Rotated Drives Backup Job & Related Backup Directory

Post by selva » May 16, 2020 6:44 pm

I see that veeam (B&R 10) errors the first time after a drive letter change (its still looking at the old drive letter) but then succeeds on stopping and restarting the job. For me this happens also with copy backup jobs of VMs, not just file share jobs: logs show drive letter changed to K: (was E:) but then it errors saying could not create E:\veeam-repo which was the original target directory name. On the next run it succeeds.

The difference between the failing and succeeding runs is that the first one started and went idle before the drive letter change (waiting for usage period). But it still notices the drive letter change but not fully, it seems.

Has anyone else seen this?

foggy
Veeam Software
Posts: 19048
Liked: 1693 times
Joined: Jul 11, 2011 10:22 am
Full Name: Alexander Fogelson
Contact:

Re: Renaming Rotated Drives Backup Job & Related Backup Directory

Post by foggy » May 17, 2020 10:11 pm

I recommend asking our support engineers to review this closer to see if it is expected or not.

selva
Influencer
Posts: 14
Liked: 1 time
Joined: Apr 07, 2017 5:30 pm
Contact:

Re: Renaming Rotated Drives Backup Job & Related Backup Directory

Post by selva » May 19, 2020 1:39 am 1 person likes this post

Okay, thatnks: case #04182841

selva
Influencer
Posts: 14
Liked: 1 time
Joined: Apr 07, 2017 5:30 pm
Contact:

Re: Renaming Rotated Drives Backup Job & Related Backup Directory

Post by selva » May 23, 2020 3:22 am

I got the following response to my case:

"With backup to rotated drives , the idea is that the device can change without the drive letter changing. If multiple devices are used, they all have to be represented by the same drive."

Go figure!

foggy
Veeam Software
Posts: 19048
Liked: 1693 times
Joined: Jul 11, 2011 10:22 am
Full Name: Alexander Fogelson
Contact:

Re: Renaming Rotated Drives Backup Job & Related Backup Directory

Post by foggy » May 23, 2020 11:15 pm

That doesn't sound right - after being introduced for the first time, a device can change the letter, Veeam B&R will 'follow' the known device. I've seen your comment to the engineer along the same lines, please continue working with him.

selva
Influencer
Posts: 14
Liked: 1 time
Joined: Apr 07, 2017 5:30 pm
Contact:

Re: Renaming Rotated Drives Backup Job & Related Backup Directory

Post by selva » May 28, 2020 3:53 am

Still working with support, but here is a follow up as I had to switch the disk yesterday.

Changed to a new disk keeping the drive letter same as required in this case. When triggered on reaching allowed time-frame the job failed -- it was looking for old backups on the disk. During the next run the job succeeded.

In summary this is what I see: when the copy job is in "Idle" state waiting for restore points or allowed time frame, if the disk is swapped in a rotated disk repo, the change is not fully recognized and jobs fails when triggered. As the job restarts for the next cycle it does recognize a new disk on same drive letter or old disk on any drive letter, and works as expected.

I am unable to avoid one failure and associated error notification. My copy jobs are "periodic copy" type, not "immediate copy" and are not allowed to run at all times, so the job stays in "Idle" state most of the time waiting for either restore points or time-frame to run.

foggy
Veeam Software
Posts: 19048
Liked: 1693 times
Joined: Jul 11, 2011 10:22 am
Full Name: Alexander Fogelson
Contact:

Re: Renaming Rotated Drives Backup Job & Related Backup Directory

Post by foggy » May 28, 2020 9:15 pm

Just to check - are you using the ForceCreateMissingVBK registry value by any chance (found an old issue with similar behavior when this value was used)?

Post Reply

Who is online

Users browsing this forum: No registered users and 6 guests