Hi,
I'm trying to rescan an existing repository and every time during reload the process fails. It takes about ten minutes and then fails with the message: "The operation failed, see inner exception. A connection attempt failed because the connected party did not properly respond after a period of time, or the established connection failed because the connected host failed to respond."
I'm able to access the share where the backup data is located and there is another backup on the same repository. I'm also able to map the job to the new repository and calculate storage.
I'm running Backup & Replications 6.0.0.153 (64 bit)
Any help is appreciated.
thanks,
Keith
-
- Lurker
- Posts: 2
- Liked: never
- Joined: Oct 06, 2015 2:05 am
- Full Name: Keith M
- Contact:
-
- Product Manager
- Posts: 20389
- Liked: 2298 times
- Joined: Oct 26, 2012 3:28 pm
- Full Name: Vladimir Eremin
- Contact:
Re: Problem Reloading Repository
Hi, Keith,
It's hard to say what can cause the described situation without seeing actual logs. So, kindly, open a ticket with out support team and let them investigate it directly.
However, before opening a ticket it might be worth updating your installation to the newest product version, as the one you're currently using is no longer supported. Chances are, product upgrade will also solve the existing problem, as a lot of issues have been fixed since version 6.
Thanks.
It's hard to say what can cause the described situation without seeing actual logs. So, kindly, open a ticket with out support team and let them investigate it directly.
However, before opening a ticket it might be worth updating your installation to the newest product version, as the one you're currently using is no longer supported. Chances are, product upgrade will also solve the existing problem, as a lot of issues have been fixed since version 6.
Thanks.
-
- Lurker
- Posts: 2
- Liked: never
- Joined: Oct 06, 2015 2:05 am
- Full Name: Keith M
- Contact:
Re: Problem Reloading Repository
Thanks for the reply and sorry for the delay.
The issue seemed to resolve itself after posting, which leads me to believe that there may be a network issue. Especially since now I am receiving semaphore timeout errors during backup.
I'm going to attempt an upgrade of the software to see if that resolves these issues.
The issue seemed to resolve itself after posting, which leads me to believe that there may be a network issue. Especially since now I am receiving semaphore timeout errors during backup.
I'm going to attempt an upgrade of the software to see if that resolves these issues.
Who is online
Users browsing this forum: Bing [Bot], Kirassant, Majestic-12 [Bot], NightBird, Semrush [Bot] and 167 guests