Kasyea K2 Acronis issues with Windows 2008

Thread needs solution
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Beginner
Posts: 1
Comments: 1

I'm finding that various Windows 2008 servers stop backing up to NAS devices. They claim they are no accessible. Yet you can PING via IP or DNS name. You can get the backup to run again if you do one of two things:

Reboot the Server 2008 and it will find the storage and do a backup

OR

Change the targer host from a DNS to IP \\192.168.....\Share and it will work for a couple of daya, then fail. But if you switch the target back to DNS backups will resume.

Fri, 08/06/2010 - 04:36
0 Users found this helpful
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Forum Star
Posts: 24
Comments: 3268

Hello John!

Welcome to our Forum, it's nice to have you with us! I entirely understand your concern and will be glad to assist you.

Unfortunately due to the lack of diagnostic information it's hard to identify why the target machines are are no accessible, so this situation requires investigation.

Since you're using Kaseya distribution, there may be some differences in the program code, so I'd advise you to contact Kasya support first. I'm sure it will speed up the process of solving the issue.

Should you have any additional questions or concern - please let us know, we will be glad to help you!

Thank you!

Fri, 08/06/2010 - 17:33
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Beginner
Posts: 0
Comments: 7

forums are useless if the answers are never posted. Might as well call support from the beginning instead of reading that others have the same issues with no resolution given.

Mon, 12/13/2010 - 19:56
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Forum Star
Posts: 24
Comments: 3268

Hello Netlogic DC,

Thank you for your comment, and for sharing your concerns with us. I understand your frustration, and will be glad to shed the light to the situation.

Forum is not a support channel, but a community, as you can see from the Forum Terms of Use. We're aiming to provide Forum members with the answers on their questions. In case one opens a thread regarding a known issue with the common solution, we immediately post it. In case one opens a thread regarding the new issue, we monitor his support case till the end, and in case it also has a common solution - we post it. Every addressed thread contains the latest information regarding the problem. Unfortunately most of the time the issue's caused by the individual reasons, and each case should be investigated separately.  So in case you check the thread, and see that the last suggestion was to contact support - it means that the issue has no common solution, and should be investigated with support.

You can always contact us directly with any questions as well as submit feedback directly.

In this case, as described earlier, since you're using Kaseya distribution, there may be some differences in the program code, so we'd advise you to contact Kasya support first.

Should you need anything else or have any further questions - feel free to contact us at your earliest convenience, we will be happy to help you!

Thank you!

Tue, 12/14/2010 - 12:12