-
- Service Provider
- Posts: 16
- Liked: never
- Joined: Nov 17, 2013 10:02 pm
- Full Name: Nathan Work
- Contact:
There is an folder item with the specified name and another
Hello all,
On more than one occasion, various copy jobs have begun to fail with the error:
"There is an folder item with the specified name and another type."
A Google search for this phrase returns just one hit with no solution in it: http://forums.veeam.com/veeam-backup-re ... 24673.html
The case manager has told me that the only solution may be to create a new backup chain which would have the effect of sending the entire copy over the WAN again.
Even if creating a new backup chain isn't the only solution - that Veeam technical support can edit the VBM file to correct the issue - it still doesn't make Veeam B&R an acceptable solution in a vendor-customer relationship where we - the vendor - don't have the ability (proximity) or relationship (the right to be on-prem) with the customer to grab a seed, and it surely doesn't adhere to Veeam's "It just works" philosophy.
I anxiously await a solution to the reoccurring problem - not just a fix to this acute issue - as we fall further out of our SLA.
Nathan
Case # 00918817
On more than one occasion, various copy jobs have begun to fail with the error:
"There is an folder item with the specified name and another type."
A Google search for this phrase returns just one hit with no solution in it: http://forums.veeam.com/veeam-backup-re ... 24673.html
The case manager has told me that the only solution may be to create a new backup chain which would have the effect of sending the entire copy over the WAN again.
Even if creating a new backup chain isn't the only solution - that Veeam technical support can edit the VBM file to correct the issue - it still doesn't make Veeam B&R an acceptable solution in a vendor-customer relationship where we - the vendor - don't have the ability (proximity) or relationship (the right to be on-prem) with the customer to grab a seed, and it surely doesn't adhere to Veeam's "It just works" philosophy.
I anxiously await a solution to the reoccurring problem - not just a fix to this acute issue - as we fall further out of our SLA.
Nathan
Case # 00918817
-
- Product Manager
- Posts: 20405
- Liked: 2298 times
- Joined: Oct 26, 2012 3:28 pm
- Full Name: Vladimir Eremin
- Contact:
Re: There is an folder item with the specified name and anot
Have you been provided with the explanation in regards to the root cause of the said problem and it's under the investigation? Thanks.
-
- Service Provider
- Posts: 16
- Liked: never
- Joined: Nov 17, 2013 10:02 pm
- Full Name: Nathan Work
- Contact:
Re: There is an folder item with the specified name and anot
No, I have not.
-
- Veteran
- Posts: 387
- Liked: 97 times
- Joined: Mar 24, 2010 5:47 pm
- Full Name: Larry Walker
- Contact:
Re: There is an folder item with the specified name and anot
I had this happen in v7 when I created a folder in the VC and moved all the replica's there , some ended up in two locations, some reported your error, of course some were just fine.
-
- Service Provider
- Posts: 16
- Liked: never
- Joined: Nov 17, 2013 10:02 pm
- Full Name: Nathan Work
- Contact:
Re: There is an folder item with the specified name and anot
@ v.Eremin: Can you provide an explanation as to a common root cause for this issue?
-
- Product Manager
- Posts: 20405
- Liked: 2298 times
- Joined: Oct 26, 2012 3:28 pm
- Full Name: Vladimir Eremin
- Contact:
Re: There is an folder item with the specified name and anot
Before Update 2 there has been additional check incorporated inside backup copy job. Under certain circumstances the said check might render backup copy chain unusable.
We're really sorry to hear that you've come across that. Chain re-creation seems to be the only available solution, thus, recommendation from support engineer.
In Update 2 we've addressed that, so, the given problem is no longer present.
Thanks.
We're really sorry to hear that you've come across that. Chain re-creation seems to be the only available solution, thus, recommendation from support engineer.
In Update 2 we've addressed that, so, the given problem is no longer present.
Thanks.
Who is online
Users browsing this forum: Bing [Bot], EskBackupGuy23, Paul.Loewenkamp and 293 guests