New Backup Solution In My New Virtualized Environment
-
@garak0410 said:
I assume I should also have a solution for my Host right? But the free Unitrends won't take care of that...correct?
No. Don't back up the host. There should be nothing there to protect.
-
Question about backup drives in Unitrends. Does the drive have to be an attached VDISK or can backups go to a network location? I am trying to create a VDISK on our NAS to attach to the Unitrends VM and it drive creation is just CREEPING...terrible slow. I've checked the storage options and they all appear to have to be VDISKS unless I am missing something.
Thanks...
-
You can create a CIFS or NFS share on your NAS to attach storage that way. Here's how...
http://support.unitrends.com/ikm/questions.php?questionid=936
-
This post is deleted! -
@garak0410 said:
@art_of_shred said:
You can create a CIFS or NFS share on your NAS to attach storage that way. Here's how...
http://support.unitrends.com/ikm/questions.php?questionid=936
This helps...now if I can get past this point, I'll be good:
The login info is correct but I am sure there is something missing...
It wanted CIFS...working now...moving on...
-
When trying to run some test backups, now getting this:
"[System] file-level backups not supported in Free Edition License."
Getting confused now in this free license...I've looked at this but it doesn't help: http://support.unitrends.com/ikm/questions.php?questionid=809
-
My understanding is that you can only do VM backups with that license.
-
Right, @scottalanmiller : the free UEB does not support physical clients. File-level backups denotes physical.
-
You can still restore individual files. It's just the backup type that isn't supported.
-
@scottalanmiller said:
My understanding is that you can only do VM backups with that license.
This is a VM I am trying to connect to...
-
@garak0410 said:
@scottalanmiller said:
My understanding is that you can only do VM backups with that license.
This is a VM I am trying to connect to...
Are you connecting to the platform or trying to connect to the VM itself? If the latter, you are treating like it is physical and that is what you can't do.
What you do is attach to VMware and backup that way, you don't attach to an individual VM.
-
@scottalanmiller said:
@garak0410 said:
@scottalanmiller said:
My understanding is that you can only do VM backups with that license.
This is a VM I am trying to connect to...
Are you connecting to the platform or trying to connect to the VM itself? If the latter, you are treating like it is physical and that is what you can't do.
What you do is attach to VMware and backup that way, you don't attach to an individual VM.
He's on Hyper-V
-
Ah yes. But does that change anything?
-
-
Shouldn't. Behavior is the same between the two.
-
If you protect at the hypervisor level, that's virtual and included in the free version. If you try to go the agent-route (which is protecting the vm itself, as @scottalanmiller suggested), that is a "physical" type of backup approach and not supported on the free version. When you protect at the hypervisor level, the hypervisor pushes out to the guest vm's, agent-less. If you put the agent on a single vm and want to register it to Unitrends as a stand-alone client, that's the "physical" approach. Typically, that would be better protection for machines with application level servers (exchange, SQL, sharepoint).
-
Let me ingest these recent posts and see what I can do...I did try Veeam this weekend since I've not gotten Unitrends setup yet. Over the weekend, I just tried a file copy of our two most important directories to our NAS. One of them I started at 9:49PM on the 12th...came in today and it is still running at 83% and 549 KB/s. This is going on 36 hours...This directory contains:\
47GB of Data
1,142,899 filesMind you it isn't going to an enterprise level NAS and it is the first FULL backup but I still expect better throughput. So, saying this, my current backup solution may not be doing so bad...there is a bottleneck somewhere.
-
Are you telling Unitrends to only look at the VMware host? You should only be adding one thing to back up. Not doing anything with the servers that run in top of it.
Or pointing at the HyperV host, rather.
