Post

Acronis issues with backups

So with a client, I was hit with an error in Acronis Backup & Recovery 11 that caused these errors:

ProtectCommand: Failed to execute the command.
Additional info:
——————–
Error code: 41
Module: 307
LineInfo: e6792a5ee190dd9e
Fields: $module : agent_protection_addon_glx_pic
Message: ProtectCommand: Failed to execute the command.
——————–
Error code: 53
Module: 309
LineInfo: 2e7e9e174f1fb746
Fields: $module : agent_protection_addon_glx_pic
Message: TOL cumulative completion result.

The issue with Acronis is that, well, it’s just a bad product now… I used to be a big Acronis fan, but when products break on their own, literally 7 times, on 3 clients without any changes to the server nor backup routine, it’s a bad product.  What happens is the XML files and lock files become corrupt, it won’t talk to that folder anymore because IT BROKE ITSELF!!!!  The best solution is to abandon the backup folder and create a new one, then it doesn’t have to work with the old XML and lock files, then it fires right up and works.

I have never been able to fix Acronis backup jobs that roll over and die, nor has the tech support from Acronis that has logged over 10 man hours in these client machines, they really have no answer why and they just rebuild the backup job from scratch and put it in a new folder, that’s the support for their software… It’s like the PC repair guys at the local town shop that believe in this formula

Customer + computer that has an error that isn’t related to a simple setting = reformat and charge for a system setup

I fully believe that Acronis has a similar banner hanging in the tech support office… /rant

Updating ports through SVN (subversion) instead of csup

So working on a customer’s FreeBSD server this month and being a good admin, I made sure I checked the /usr/ports/UPDATING message for anything of interest.  Lo and behold, the following message:

<snippit start>

20120716:
AFFECTS: Nobody
AUTHOR: [email protected]

The FreeBSD ports tree switched from CVS to Subversion. A Subversion
to CVS exporter is in place to continue the support of CVSup.

</snippit>

Sure enough, I started researching the change and found that there wasn’t a great guide out there (yet), so I have this for all of you:

Changing over to SVN for updating your ports:

1. You’ll want to get SVN installed as root….

cd /usr/ports/devel/subversion && make install clean && rehash

(you can run with the defaults in the config screen)

2. Now I find that deleting the old ports tree that I built over time using csup cleans up any garbage that can be in there (old distfiles you forgot to clean, INDEX-*, and more).  Then I do the following….

rm -rf /usr/ports/ && mkdir /usr/ports && rehash

Keep in mind with root permissions already with you, that the ports directory will automatically be built with the correct permissions.  I through in a rehash because the system hated me twice, on two different servers, for killing the /usr/ports directory and recreating it… the rehash wakes up the system to the change.

3. From here, and this is where I found the instructions distracting… If you are reading this, you probably aren’t a developer, in fact, you just want a fresh copy of the ports tree so you can run portupgrade or whatever method you like to use.  The directions that I found out there require logins and more, but that’s because “you are a developer” from the perspective of the authors…. Our lives our easier than those instructions by using….

svn co svn://svn.freebsd.org/ports/head /usr/ports

The co is just “copy”  and from there, I would do a portupgrade -ar , which will rebuild that INDEX-* file in /usr/ports and correctly continue from where it should as if you did a csup.

4.  So how do you update for new ports????  Simple…

svn update

that’s it…

 

Now, what about updating the /usr/src… I normally don’t do that, I leave that to freebsd-update fetch and freebsd-update install , but if you HAD To rebuild it, it would be:

rm -rf /usr/src/ && mkdir /usr/ports

svn co svn://svn.freebsd.org/base/release/8.2.0 /usr/src   (or whatever release you wanted)

freebsd-update fetch

freebsd-update install

 

Though there isn’t a huge reason for us end users to change, IMO, it is way easier for the developers to make changes and slip in updates, plus, on our end we do enjoy a faster process than csup does for updates.