nl There is also a DUTCH VERSION of this site

Google

More articles

01 Feb - 28 Feb 2010
01 Jan - 31 Jan 2010
01 Dec - 31 Dec 2009
01 Oct - 31 Oct 2009
01 Sep - 30 Sep 2009
01 Aug - 31 Aug 2009
01 Jun - 30 Jun 2009
01 Apr - 30 Apr 2009
01 Mar - 31 Mar 2009
01 Jan - 31 Jan 2009
01 Dec - 31 Dec 2008
01 Oct - 31 Oct 2008
01 Sep - 30 Sep 2008
01 Aug - 31 Aug 2008
01 Jul - 31 Jul 2008
01 Jun - 30 Jun 2008
01 May - 31 May 2008
01 Apr - 30 Apr 2008
01 Mar - 31 Mar 2008
01 Feb - 28 Feb 2008
01 Jan - 31 Jan 2008
01 Dec - 31 Dec 2007
01 Nov - 30 Nov 2007
01 Oct - 31 Oct 2007
01 Sep - 30 Sep 2007
01 Aug - 31 Aug 2007
01 Jul - 31 Jul 2007
01 Jun - 30 Jun 2007
01 May - 31 May 2007
01 Apr - 30 Apr 2007
01 Mar - 31 Mar 2007
01 Feb - 28 Feb 2007
01 Jan - 31 Jan 2007
01 Dec - 31 Dec 2006
01 Nov - 30 Nov 2006
01 Oct - 31 Oct 2006
01 Sep - 30 Sep 2006
01 Aug - 31 Aug 2006


Links

Deze site wordt gehost bij
ATN-Networks

Aanbevolen
Genootschap voor Informatie Architecten
Rene Hamberg
Bas Varkevisser
Ruth Malan
l-rs.org
Informatiekundig bekeken
Bredemeyer Consulting
Gaudi site
Hans Bot ArchITectuur Bedrijven
Security.nl

Nick Malik
Leo de Sousa



Misc

Powered by Pivot - 1.40.1: 'Dreadwind' 
XML: RSS Feed 
XML: Atom Feed 

Technorati Profile

Who needs a consistent backup?

21 February 10 - 14:18
Area: default - Link to this article

In general much attention is paid to the creation of consistent backups. Specific backup tools and backup agents are configured to ensure databases are flushed to disk to provide a consistent backup.

Of course this is very important. Inconsistent databases can lead to incorrect startup of a database after a restore. An example is the index of the database that is out of sync with the underlying tables.

Database transactions must be handled correctly as well before making a backup to prevent a failing application after a restore. An example is a purchase order that states a product can in, where a change in the financial administration is missing.

The question is weather is it useful to force consistencies in backups on a higher level. I think this is a very expensive exercise (if possible at all) with little benefit. Nowadays systems hardly ever work in isolation. Usually they are part of a chain of internal and external systems. Purchase orders come in via order intake in a SAP system, but can also come in through resellers’ web services or via an Internet site. These systems are connected and it seems to make sense to backup them in an integral way.

However, this is hardly possible. To create an integral backup all systems must be in a consistent state. Not only internally, but also between each system. This is only possible when all connected systems are stopped. Not only is this most of the time not feasible (an Internet page cannot be taken offline to create a backup) , it is also very time consuming. If one of the systems in the chain cannot be stopped due to a long running transaction all other systems have to wait for it in order to get back-upped.

I am not even mentioning chains running over several companies. When transactions run between companies all companies must stop working to create chain-consistent backup.

Let’s first find out why a backup is made at all in large systems (I am not talking about restoring a lost user file). A backup can be used to restore systems that cannot be repaired any other way. This means that the choice to perform a restore has great business impact. A restore must therefore be handled with great care.

It is important to have backups that are consistent within one application to prevent the problems stated above. Usually backups are one or more days old. When after a restore the system would be started without measures, some unwanted side effects could occur. For instance: when just before making the backup a message from a business partner was received and the acknowledgement was not sent yet, the acknowledgement would be sent again to the business partner after the restore of the system a day later. You can probably come up with more examples.

These examples show that restoring a system from backup is always a delicate process that must be taken care of with great caution, especially in a chain of multiple applications or even companies. Therefore it is of no use to have a consistent backup over a set of applications: problems will arise anyway when a restore is performed without additional measures.

A consistent database backup and consistence within applications is therefore enough.

TED talks

07 February 10 - 20:02
Area: default - Link to this article

Something a bit off-topic this time. Do you know TED talks? TED stands for Technology, Entertainment, Design. It is a small non-profit organisation that started in 1984 organising yearly conferences around the globe.

On their website TED.com, they publish videos of the best talks and performances from TED and partners for free. More than 450 TEDTalks are now available, with more added each week. The videos can be viewed on the website, but also downloaded as podcast.

Since more than a year I download the videos on my iPod and view them when I have some time to spare. Most talks are about 15 minutes in length. The talks are always inspiring, brought by inspiring people, mostly unknown, but occasionally well known people like Bill Gates, Al Gore and Bill Clinton perform as well.

Highly recommended, not only for your own education and awareness, but also to learn how to give a good talk to an audience! Some of the most inspiring videos are this and definately this. Just to get you started...


More articles: See left pane.

About Sjaak Laan

Sjaak Laan

I am 45 years old and married with Angelina. We have 3 children of 11, 6 and 4 years old. We live in The Netherlands, in a place called Drachten

I work for Logica as Principal IT Architect. I have 20 years IT experience.

I own the following certificates:

itac_l Master Certified IT Architect



CISSP_logo CISSP (Certified Information Systems Security Professional)



TOGAF8_Certified_web TOGAF Certified Architect


I am a member of the:


I manage my business contacts using Linkedin.


I can be reached through sjaak.laan@gmail.com.

This site states my opinion only, and not nessecarily the opinion of my employer or of the clients I work for.