-
- Enthusiast
- Posts: 30
- Liked: 2 times
- Joined: Feb 13, 2013 12:20 pm
- Full Name: Bob Baird
- Contact:
Can't Access Respoitory Since 01/01/2018
Hello,
Since the turn of the year, any backup I take to the default backup repository completes successfully, but I am unable to view the backup via Exchange Explorer - the only backups available for me to "explore" are those that were take before 01/01/2018.
I have a case open and this is currently being investigated, but I just wonder if anyone else has happened upon this issue?
My case number is 02455531
Thanks,
Bob
Since the turn of the year, any backup I take to the default backup repository completes successfully, but I am unable to view the backup via Exchange Explorer - the only backups available for me to "explore" are those that were take before 01/01/2018.
I have a case open and this is currently being investigated, but I just wonder if anyone else has happened upon this issue?
My case number is 02455531
Thanks,
Bob
-
- Product Manager
- Posts: 8191
- Liked: 1322 times
- Joined: Feb 08, 2013 3:08 pm
- Full Name: Mike Resseler
- Location: Belgium
- Contact:
Re: Can't Access Respoitory Since 01/01/2018
Bob,
Are you at the latest version (1.5)? Did you look at this KB? https://www.veeam.com/kb2412
Please keep working with our engineers and keep us informed about the progress
Thanks
Mike
Are you at the latest version (1.5)? Did you look at this KB? https://www.veeam.com/kb2412
Please keep working with our engineers and keep us informed about the progress
Thanks
Mike
-
- Enthusiast
- Posts: 30
- Liked: 2 times
- Joined: Feb 13, 2013 12:20 pm
- Full Name: Bob Baird
- Contact:
Re: Can't Access Respoitory Since 01/01/2018
Hi Mike,
Thanks for your reply.
I already installed that hotfix and I am using 1.5.0.1309 of Veeam Backup for O365 as well as 1.0.0.1309/1308 of Explorer for Exchange.
Further to my last email, it would appear that everything works as you would expect for any new repository that is created - it just seems to be an issue with the repositories that were in place prior to 01/01/2018.
Regards,
Bob
Thanks for your reply.
I already installed that hotfix and I am using 1.5.0.1309 of Veeam Backup for O365 as well as 1.0.0.1309/1308 of Explorer for Exchange.
Further to my last email, it would appear that everything works as you would expect for any new repository that is created - it just seems to be an issue with the repositories that were in place prior to 01/01/2018.
Regards,
Bob
-
- Product Manager
- Posts: 8191
- Liked: 1322 times
- Joined: Feb 08, 2013 3:08 pm
- Full Name: Mike Resseler
- Location: Belgium
- Contact:
Re: Can't Access Respoitory Since 01/01/2018
Thanks Bob,
Please let me know when you know more from our support team.
Mike
Please let me know when you know more from our support team.
Mike
-
- Enthusiast
- Posts: 30
- Liked: 2 times
- Joined: Feb 13, 2013 12:20 pm
- Full Name: Bob Baird
- Contact:
Re: Can't Access Respoitory Since 01/01/2018
Hi Mike,
I will indeed keep you updated once I hear back from your engineer, although sadly (and very unusually), the response to my support request has been far from satisfactory on this occasion I have to say.
Hopefully I'll get work back before the end of the day.
Regards,
Bob
I will indeed keep you updated once I hear back from your engineer, although sadly (and very unusually), the response to my support request has been far from satisfactory on this occasion I have to say.
Hopefully I'll get work back before the end of the day.
Regards,
Bob
-
- Lurker
- Posts: 2
- Liked: never
- Joined: Jan 10, 2018 2:24 am
- Full Name: jdk
- Contact:
Re: Can't Access Respoitory Since 01/01/2018
Ive had a similar issue since new year, im using v1.5 too and i use a rotated repo. Every time we rotate the drive i get a failure to find the storage path and a jet io error, the only workaround is to recreate the repo.
I did create a ticket but i closed it as i thought the issue was resolved by recreating the repo, but didnt realise it would happen again on the 2nd drive.
Has there been a solution to this issue of storage errors since new years day?
JK
I did create a ticket but i closed it as i thought the issue was resolved by recreating the repo, but didnt realise it would happen again on the 2nd drive.
Has there been a solution to this issue of storage errors since new years day?
JK
-
- Product Manager
- Posts: 8191
- Liked: 1322 times
- Joined: Feb 08, 2013 3:08 pm
- Full Name: Mike Resseler
- Location: Belgium
- Contact:
Re: Can't Access Respoitory Since 01/01/2018
Hi JK,
The case is still open and is being investigated further. I would advise you to create also a case again, point to the previous one and say it didn't solve. The thing what scares me though is a rotated repository? That is not a supported repository under VBO as it is not the same as a VBR repository. A VBO repository is a running database so I have no idea how you got that running in the first place to be honest.
The case is still open and is being investigated further. I would advise you to create also a case again, point to the previous one and say it didn't solve. The thing what scares me though is a rotated repository? That is not a supported repository under VBO as it is not the same as a VBR repository. A VBO repository is a running database so I have no idea how you got that running in the first place to be honest.
-
- Lurker
- Posts: 2
- Liked: never
- Joined: Jan 10, 2018 2:24 am
- Full Name: jdk
- Contact:
Re: Can't Access Respoitory Since 01/01/2018
It worked all the time in v1.
-
- Product Manager
- Posts: 8191
- Liked: 1322 times
- Joined: Feb 08, 2013 3:08 pm
- Full Name: Mike Resseler
- Location: Belgium
- Contact:
Re: Can't Access Respoitory Since 01/01/2018
Did you already create a support case?
-
- Enthusiast
- Posts: 30
- Liked: 2 times
- Joined: Feb 13, 2013 12:20 pm
- Full Name: Bob Baird
- Contact:
Re: Can't Access Respoitory Since 01/01/2018
Hello Everyone,
I have received word back from the engineer that this is a "known" issue (https://www.veeam.com/kb2412) however this is not exactly the same issue I'm having.
If I create a new backup job today and successfully save to the default repository (c:\veeamrepository), I cannot browse this backup. However, I have created a new repository (c:\temp\veeamrespoitory) and upon successful completion of the very same backup job, I can browse the backup.
Most strange.
I have received word back from the engineer that this is a "known" issue (https://www.veeam.com/kb2412) however this is not exactly the same issue I'm having.
If I create a new backup job today and successfully save to the default repository (c:\veeamrepository), I cannot browse this backup. However, I have created a new repository (c:\temp\veeamrespoitory) and upon successful completion of the very same backup job, I can browse the backup.
Most strange.
-
- Product Manager
- Posts: 8191
- Liked: 1322 times
- Joined: Feb 08, 2013 3:08 pm
- Full Name: Mike Resseler
- Location: Belgium
- Contact:
Re: Can't Access Respoitory Since 01/01/2018
Did you tell the engineer that you already installed the hotfix?
-
- Enthusiast
- Posts: 30
- Liked: 2 times
- Joined: Feb 13, 2013 12:20 pm
- Full Name: Bob Baird
- Contact:
Re: Can't Access Respoitory Since 01/01/2018
Yes. In fact, just checking back on my email communication with him, he pointed me in the direction of that hotfix and I told him I had already installed it. I believe my issue is completely different.
My workaround is as folllows:
After all my backup jobs have completed, I run a small mailbox backup that is being saved to the new repository I have created i.e. c:\temp\veeamrepository.
I cannot browse the individual backup jobs as last backup date in Explorer is showing as 31/12/2017, but I can select the top level organization, which allows me to open the mailboxes based on the last successful backup date/time of my test backup.
My workaround is as folllows:
After all my backup jobs have completed, I run a small mailbox backup that is being saved to the new repository I have created i.e. c:\temp\veeamrepository.
I cannot browse the individual backup jobs as last backup date in Explorer is showing as 31/12/2017, but I can select the top level organization, which allows me to open the mailboxes based on the last successful backup date/time of my test backup.
-
- Product Manager
- Posts: 8191
- Liked: 1322 times
- Joined: Feb 08, 2013 3:08 pm
- Full Name: Mike Resseler
- Location: Belgium
- Contact:
Re: Can't Access Respoitory Since 01/01/2018
Please keep this case open and escalate if necessary. The workaround can help you today but should remain a workaround.
-
- Enthusiast
- Posts: 30
- Liked: 2 times
- Joined: Feb 13, 2013 12:20 pm
- Full Name: Bob Baird
- Contact:
Who is online
Users browsing this forum: No registered users and 15 guests