@thecreativeone91 said:

How did you add this disk? Is is a second VMDK/VHDX or a Pass through?

a second vhdx

@dafyre said:

My thinking was more along @scottalanmiller's this time... But like everything "it depends" on what the server does. For a File Server, or an application server (Exchange, et al) that we previously mentioned, to me an agent would make more sense.

However, I thought that restoring to different hardware was actually a function of the restore process, and not necessarily part of the backup process. (I guess it depends on what backup software we are talking about).

Your first, and thus main, backup should always be the entire VM for anything.

If you then need some of the features a backup from inside the OS gives you, then make secondary backups there.

Veeam can be made application aware and issue commands inside the guest to ensure the specified application is in a state for a valid recovery. I would assume that Unitrends has similar functionality, but no idea.

@thecreativeone91 said:

@scottalanmiller said:

Yes, Pertino can go directly on the "new" installs of UEB. Not if you have an old CentOS 5 one. You can always reinstall now.

I guess the new beta's are likely CentOS 7?

Pretty sure it's CentOS6

@thecreativeone91 said:

@thanksajdotcom said:

@scottalanmiller said:

@thanksajdotcom said:

Ok, I'd think it'd be a simple thing to add the CentOS 6 repos, run a yum update, and allow the packages to update. What makes it not that simple?

That it does nothing. A CentOS 5 system, pointed to CentOS 6 repos will simply see the as not applying. You can't change your OS version using YUM.

Oh, I was not aware of that.

Maybe you are thinking of Minor release updates, not major release.

Yeah, must be.

Yup, pretty normal. Postgres is the database. Hashing never stops, baby.

Unitrends is constantly preparing itself for need to do an autosynth, and is working on the dedup and inline hashing and everything else all the time. It's pretty normal for postsgres to be pegged.