CORBA Architecture in Development of Distributed Backup Applications

What is CORBA? Missplelled "COBRA"? A code name for the Secret World Gorenment run by Doctor Evil (Confident Organization of Bankers and Raging Architectures)? And, what is more important, why would anyone care? There are two ways to learn the answers:

• Actually trying things out
• Reading the wordy explanation below

To go for the first one, use the download button below to test Handy Backup software with the CORBA backup magic inside.

Download for Free

Version 8.5.3 , built on March 5, 2024. 116 MB
30-day full-featured trial period

Common Object Request Broker Architecture

Let’s start with that formal step of expanding the abbreviation.

Common Object Request Broker Architecture is the specification for creating, distributing, and managing program objects via network. The CORBA architecture was developed by a consortium of the Object Management Group (that one is probably the geekiest phrase to be the full version of OMG). To make an impression, we are speaking about more than 500 member companies here.

Ok. So, what is CORBA? That CORBA thing allows programs at different locations in a network to communicate and arrange data transfers. The magic phrase here is "interface broker". That last one provides a client program (which may itself be an object) in a network with request services from a server program or an object (and vice versa).

It can be done without having to understand where the backup server is in a distributed network and what the interface is. Sounds as dull as a dog’s snore, but damn it, I’ll pay the hero who will be able to explain the concept clearer.

CORBA Protocols

Can we already get to discussing cool CORBA software? Well, we still got a bit of alphabet letters to name. So, can we make something useful of I, O, R, B, and P?

To make requests or return replies between those brokers (or ORB like in Object Request Broker), programs use the General Inter-ORB Protocol (GIOP) and Internet Inter-ORB Protocol (IIOP) for the Internet. IIOP maps GIOP requests and replies to the Internet’s Transmission Control Protocol (TCP) layer in each computer.

CORBA Case Study: Client-Server Network Backup Software

Here come examples at last. Take Handy Backup Server Network, the client-server based network workstation backup software with the CORBA architecture implemented. Handy Backup’s client part (client-server architecture, remember?) invokes operations on distributed objects with no concern to object locations in the network, OS platform, communication protocols and interconnects, and hardware.

This approach on the one hand allows hiding (in some sense) the interaction between client and server, and on the other hand increasing the productivity of the CORBA software.

You can see it in work, when, for example, you hide the workstation backup proceeding, starting it as a Windows service. So, you get an opportunity to make network backup from, for example, an Android mobile device (as if it were a workstation) to your desktop.

As a result, you potentially get the chance

• manipulate your work PC data from your phone;
• delete your Galaxy Tab docs from your home desktop (forget the cables, you just have everything turned on and online);
• back the whole bunch of computers (say, running under Linux, Windows, and Android) to the cloud from a single control point.

Not bad, huh?

CORBA architecture boosts the performance of distributed backup via networks. Use it now!

Download for Free

Version 8.5.3 , built on March 5, 2024. 116 MB
30-day full-featured trial period

See after the CORBA Backup page:

LAN Backup: managing backup data over a local network: what you should know (the best practices)

Data Synchronization Solutions: what the difference between syncing, mirroring, and cloning is, and why anyone would care

VSS Backup and Resotre: Volume Shadow Copy service for copying processed data, pros and cons

Backup to FTP: get use of one of the most popular storage options