Unitrends on CloudatCost?

thanksajdotcom

Yeah, it was just a random thought. I doubt in a practical way this would work at this point, but it was a thought.

IRJ

I would not have any type of disaster recovery server on C@C servers at this point. We have seen downtime almost weekly.

thanksajdotcom

@IRJ said:

I would not have any type of disaster recovery server on C@C servers at this point. We have seen downtime almost weekly.

I'm thinking more as a replication source than anything.

thanksajdotcom

@IRJ said:

I would not have any type of disaster recovery server on C@C servers at this point. We have seen downtime almost weekly.

I definitely agree. Not as a primary backup location!

@scottalanmiller said:

Well my first thought is that Unitrends, I believe, only can run on CentOS 5 (hence no Pertino on there yet) and CloudatCost is CentOS 6 and 7 only. So that rules that concept out, I think.

Pretty sure mine is running CentOS 6.5
But yeah it's not really possible

thanksajdotcom

@thecreativeone91 said:

@scottalanmiller said:

Well my first thought is that Unitrends, I believe, only can run on CentOS 5 (hence no Pertino on there yet) and CloudatCost is CentOS 6 and 7 only. So that rules that concept out, I think.

Pretty sure mine is running CentOS 6.5
But yeah it's not really possible

I doubt it. Mine is fully up-to-date and still on CentOS 5.

scottalanmiller

Same here. But it could easily be different generations of installs.

@thanksajdotcom said:

@thecreativeone91 said:

@scottalanmiller said:

Well my first thought is that Unitrends, I believe, only can run on CentOS 5 (hence no Pertino on there yet) and CloudatCost is CentOS 6 and 7 only. So that rules that concept out, I think.

Pretty sure mine is running CentOS 6.5
But yeah it's not really possible

I doubt it. Mine is fully up-to-date and still on CentOS 5.

cat /etc/redhat-release
RecoveryOS release 6.5 (Final)

 uname -a
2.6.32-504.1.3.el6_bp.x86_64 #1 SMP Fri Nov 21 16:41:42 EST 2014 x86_64 x86_64 x86_64      GNU/Linux


cat install.log
Installing glusterfs-libs-3.4.0.57rhs-1.el6_5.x86_64
warning: glusterfs-libs-3.4.0.57rhs-1.el6_5.x86_64: Header V3 RSA/SHA1 Signature, key I     D c105b9de: NOKEY
Installing glusterfs-api-3.4.0.57rhs-1.el6_5.x86_64
Installing libgcc-4.4.7-4.el6.x86_64
Installing setup-2.8.14-20.el6_4.1.noarch
Installing filesystem-2.4.30-3.el6.x86_64
Installing mailcap-2.1.31-2.el6.noarch
Installing basesystem-10.0-4.el6.noarch
Installing ncurses-base-5.7-3.20090208.el6.x86_64

I didn't list all the install.log but it's definetly. CentOS 6. The Packages even have EL6 and EL6_5 in some of them.

thanksajdotcom

@thecreativeone91 said:

@thanksajdotcom said:

@thecreativeone91 said:

@scottalanmiller said:

Well my first thought is that Unitrends, I believe, only can run on CentOS 5 (hence no Pertino on there yet) and CloudatCost is CentOS 6 and 7 only. So that rules that concept out, I think.

Pretty sure mine is running CentOS 6.5
But yeah it's not really possible

I doubt it. Mine is fully up-to-date and still on CentOS 5.
cat /etc/redhat-release
RecoveryOS release 6.5 (Final)

 uname -a
2.6.32-504.1.3.el6_bp.x86_64 #1 SMP Fri Nov 21 16:41:42 EST 2014 x86_64 x86_64 x86_64      GNU/Linux


cat install.log
Installing glusterfs-libs-3.4.0.57rhs-1.el6_5.x86_64
warning: glusterfs-libs-3.4.0.57rhs-1.el6_5.x86_64: Header V3 RSA/SHA1 Signature, key I     D c105b9de: NOKEY
Installing glusterfs-api-3.4.0.57rhs-1.el6_5.x86_64
Installing libgcc-4.4.7-4.el6.x86_64
Installing setup-2.8.14-20.el6_4.1.noarch
Installing filesystem-2.4.30-3.el6.x86_64
Installing mailcap-2.1.31-2.el6.noarch
Installing basesystem-10.0-4.el6.noarch
Installing ncurses-base-5.7-3.20090208.el6.x86_64
I didn't list all the install.log but it's definetly. CentOS 6. The Packages even have EL6 and EL6_5 in some of them.

Hmmm...odd...I'm on the latest release...

scottalanmiller

@thanksajdotcom said:

Hmmm...odd...I'm on the latest release...

Did you miss my point about the age of the install? Even if they moved up to CentOS 6... how would your older install have gotten updated?

thanksajdotcom

@scottalanmiller said:

@thanksajdotcom said:

Hmmm...odd...I'm on the latest release...

Did you miss my point about the age of the install? Even if they moved up to CentOS 6... how would your older install have gotten updated?

I would think they'd push out an update to update the core OS files too, or change the repos or something.

scottalanmiller

@thanksajdotcom said:

@scottalanmiller said:

@thanksajdotcom said:

Hmmm...odd...I'm on the latest release...

Did you miss my point about the age of the install? Even if they moved up to CentOS 6... how would your older install have gotten updated?

I would think they'd push out an update to update the core OS files too, or change the repos or something.

That's not how CentOS works. That would just stop updates. They would have to write a massive OS updating system to handle this. CentOS didn't have that between CentOS 5 and CentOS 6. So what you are asking of them, while not crazy, is extreme. It's not something that they can "just do". They'd have to make this a major focus of development.

thanksajdotcom

@scottalanmiller said:

@thanksajdotcom said:

@scottalanmiller said:

@thanksajdotcom said:

Hmmm...odd...I'm on the latest release...

Did you miss my point about the age of the install? Even if they moved up to CentOS 6... how would your older install have gotten updated?

I would think they'd push out an update to update the core OS files too, or change the repos or something.

That's not how CentOS works. That would just stop updates. They would have to write a massive OS updating system to handle this. CentOS didn't have that between CentOS 5 and CentOS 6. So what you are asking of them, while not crazy, is extreme. It's not something that they can "just do". They'd have to make this a major focus of development.

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?

scottalanmiller

@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.

thanksajdotcom

@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.

@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.

thanksajdotcom

@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.