https://www.urbackup.org/administration_manual.html#x1-50002.1.1
- The volume should be persistently online while the UrBackup Server instance is running. UrBackup does not support different backup volumes/drives
Can this possibly be made into a feature?
An easy example, I am comparing Dell’s AppAssure (what we were using before) to UrBackup:
- Can set each client to backup to a specific location vs. all clients backup to one.
- Can have a central backup machine that manages all clients vs. multiple backup servers that house certain clients.
The main reason for this request is not compression or storage, but the centralization of hardware; relying solely on a massive spanned or striped drive to hold everything in your organization. The people I work with are skeptics about it, and have a preference for keeping things separate in the case of a massive failure - that way we do not lose all of our data.
So, I would like to request a feature added in to be able to backup specified clients to a specified directory; this way I can have:
- H:\urbackup
- John-PC
- Kelly-PC
- Amanda-PC
- G:\urbackup
- Tiffany-PC
- Arnold-PC
- Austin-PC
- F:\urbackup
- FileServer2
- I:\urbackup
- FileServer1
- Server3
- K:\urbackup
- Server1
- Server2
Instead of having all of my clients under H:\urbackup, they would reside under a repository that I dictated; possibly as a setting under each individual client on the server. This way, if I wanted to have certain computer reside under certain repository, I would not have to:
- Use resources (virtual or physical) to make another server - (i.e. taking up a rack slot; using up virtual resources on a Hyper-V server).
- Use up an IP Address to make another server.
- Spend hours to build another server - whether importing a saved OS or working up from bare-metal.
All this just to add an additional backup location.
At the same time, I would feel like this would also simplify upgrades (and possibly downgrades for testing):
- Moving saved backups from a 1.X server to a 2.X server, via a USB Hard Disk of a 1.X client - vice versa.
Even if there was no “hot-swap” support like stated above, but something to where multiple drives can be used; where you can have more than just one backup repository.