OK, Here is my issue. I am wanting to do Hyper V full backups on two of my bare metal servers but I am not able to get to the share on the unitrends device. I have a total of 4 bare metal servers. 2 of them can see the share and the other 2 can’t. The two that cannot see the share are able to ping the unitrends device and can also successfully do an nslookup via IP address or name successfully.
Unitrends device has been upgraded to 9.0 as well as the agents on the servers.
What do I need to check on the two servers that cannot see the share?
2 Spice ups
Todd - I’m sorry to hear that you’re having these issues. It sounds like you’re protecting these clients as physical servers, with an agent. Is that correct?
Yes, I am. The two I am having problems with are used exactly like the other two servers we have here and they do not have any issues getting to that share on the Unitrends device.
Todd - Just to confirm, all 4 clients are Hyper-V, but your’e protecting all with an agent, and only two are not connecting to your Unitrends installation?
they are connecting to the device and stanard backups are running fine. I am just having issues running HyperV backups on these two and I am thinking that since they cannot see the share then that might be one of the issues. To get the agent updated on the two servers I am having problems with I have to copy the install to the server from anohter server that has access and then run the install.
That should not be the case.
So you’re trying to protect these clients both as a physical client with an agent, and as a VM, in an agentless architecture? Is that accurate?
yes that is correct, I believe
That’s what is most likely causing the issue. Is there something specific that you’re trying to achieve that is prompting you to try to setup both an agentless backup and an agented backup?
I want to be able to do HyperV backups and standard backups on the same server. agent verses agentless should not matter on whether or not I can see a share on the unitrends device.
Todd - When you say Hyper-V backups and standard backups, do you mean file level and OS level backups/restores?
Yes that is what I am talking about when I say standard backups.
Todd - It sounds like you’re wanting to backup just the OS & the files separately so that you can do BareMetal restores and file level restores as needed. If this is the case, you can achieve this same goal by using an agent (ie a traditional backup) or by taking a snapshot from the hypervisor level, which is done without an agent. Both are not required. Since it sounds like you’re more comfortable using an agent, I would remove these clients from the host level backup schedule for Hyper-V, and proceed with an agented BareMetal backup, and a file level backup. Once you’ve removed these clients from the Hyper-V host schedule, you should be able to proceed without issue. If you need assistance making these changes, please let me know so that I can have support contact you.
Please have a tech call me on this issue. I am not at my office at the momen . Can you have them call my cell phone at 765-891-8415. Thanks
Todd - I’m not sure why I didn’t get the alert that you had posted these details until today, so my apologies for my delayed response. I’m happy to have someone call you. I would recommend that you edit or delete your post above since it has your personal telephone number in it.
