Algeria AgencyCategory
IT infrastructure articles
Network, backups, security and continuity — what only gets noticed once it fails.
Articles about what has to work every day and only gets noticed when it fails: backups that are actually tested, Wi-Fi that holds up, everyday security.
The common theme is verification. A backup never restored, a UPS never tested, an access never revoked from a former employee: three things that look in place and are not.
These articles are written to be usable without us. Most describe checks you can run yourself this week, and the result is rarely the one expected.
The order of priority is almost always the same, and it is not the expected one: backups first, then power, then access, and hardware last. It is also the reverse of the order in which anyone wants to spend.
Explore
Cloud hosting: what costs is not the storage
The line everybody compares is the cheapest on the invoice. The other three get paid on the day you need them most.The account, not the server: what you actually lose in the cloud
Everything you keep there passes through one login, one mailbox and one card. What breaks that chain, and in what order.Infrastructure: where your data lives, and how long it takes to leave
The only family in this pillar that produces nothing visible. The useful question is not local or cloud: it is the notice period for getting out.The mains before the UPS: earth, circuit and heat
A UPS fixes neither a missing earth, nor a shared circuit, nor the heat that follows an outage. What damages equipment upstream of it, and how to check.Backups and continuity: what actually gets a business running again
A backup that has never been restored is not a backup. It is an assumption.The restore test: the one day you know the backup exists
A backup never restored is a hypothesis. The test is scheduled, timed and recorded — twice a year, onto a machine that is not the original.IT: what actually stops a business, and in what order to deal with it
This pillar is bought after the incident, so in the worst conditions. One hour of questions puts the five families back in order.Moving the business: what to order three months ahead, and the weeks you exist at two addresses
A move tests your whole system at once, on a date a landlord set. The long pole is never the van.Access control: a key cannot be revoked
Everything sits in that sentence. A badge is cancelled in one action; a key is taken back by changing the lock — and nobody ever changes the lock.The badge that never came back: issuing, revoking, counting
A badge can be withdrawn — provided somebody withdraws it. The register, the badge lost on a Friday evening, and the departure handled in a minute.Firewalls and VPNs: what goes out matters more than what comes in
What arrives unrequested is already blocked by any router. The useful half is the other one, and it is the half nobody configures.March’s temporary rule: rereading a firewall six months later
A rule added for a week is never removed. How to reread a rule set in two hours, and how to take one out without breaking anything.Networks: the cheapest layer, and the one that produces half the faults
A network is a chain: it is worth what its worst segment is worth. That is why it gets bought in the order the signal travels.The line is down: establishing which side, and what comes next
Five minutes decide whether the fault is yours or the operator’s. What to record before calling, how to escalate, and what a second line really covers.IT support: the reported fault is not the fault
Nobody rings to describe a defect. People ring to say what they can no longer do, and all the work starts with that translation.The person everybody asks: the internal relay
In every business somebody who is not in IT absorbs half the problems. What the role costs them, what to give them, and its three limits.Telephony: the number is the asset, not the system
Your customers know a number, not a piece of equipment. Everything decided here has to protect that number and what happens when somebody dials it.The call nobody took: counting what no longer rings
A missed call is the only lost customer that leaves a trace. How to count them in fifteen minutes, and what really produces them.Windows Server: what you actually buy when you buy a server
The machine is bought once, the right to use it is paid per person. And it carries a written end date, which is the only certain one in this pillar.Shares: who can open what, and since when
A directory does one thing daily: decide who opens which folder. Groups, inheritance, and the tree you should stop copying from the org chart.Cabling: a hundred metres, and not all of them are yours
The standard grants a copper link a hundred metres. Ninety are in the wall and never change; the other ten get spent after you have gone.The cabling you did not lay: taking over premises already wired
No plan, no certification report, and sockets nobody can trace. What to test, what to reuse, and what the lease decides.Professional or consumer Wi-Fi: what actually changes
The speed printed on the box was never the problem. The problem is how many devices are connected at once.The guest network: what your customers reach, and what they cost you
A guest network exists the moment a waiter gives out the password. What it should reach, what it takes off the line, and what not to collect.IT audit: start by opening the cupboard
An audit is done standing up, on the premises, opening doors. What is found there decides everything else, and it is written down nowhere.The second audit: what moved, and the findings that never will
A first audit describes. The second compares — and comparison says things about a business that no description can.Cameras: the field decides, not the resolution
A camera covering too wide a field recognises nobody, whatever its definition. What decides is the place it covers and the hour it gets judged at.The day you need the footage: extracting, showing, handing over
Recording is easy; producing a usable sequence is not. The order of operations, who may watch, and what gets handed to whom.IT security: four stories, and how long it takes to notice
What costs is almost never the moment of the incident. It is the interval between it happening and somebody noticing.The phone is the workstation: what leaves with it
Orders arrive on a phone the business never bought. The number, the session left open, and what goes on the day somebody leaves.Support and maintenance: what you buy when you buy time
It is the only family in the pillar sold by time. Everything turns on a sentence nobody asks for: the moment the clock starts.The quarterly review: holding a provider to what they signed
Between signing and leaving there are two years nobody writes about. Four numbers measured from your side, and a thirty-minute meeting.Switches and routers: count before comparing
A switch does not make a network faster. It decides how many devices fit, and how many of them can be powered over the cable.The loop, the second DHCP and the switch under the desk
Five years of additions by whoever needed a port. The three faults that produces, and the order you unplug in to find them.Buying IT equipment: what decides is not the spec sheet
Two machines with identical specifications are not worth the same here. What decides is the applicable warranty and the number of different models.Twelve machines bought together grow old together
Buying the same hardware twelve times is the right advice. Nobody says what it costs three years later, or how to stagger it.Repair: the decision is about days, not dinars
The one-third rule settles the easy half. The real question is how many days the machine will be gone, and what the person does meanwhile.The machine you do not repair: wiping, reselling, scrapping
A dead machine leaves the building with its disk. What has to come out first, what it is still worth, and why the cupboard costs more than the skip.Security and surveillance: the order matters more than the product
It is the only family in the pillar bought against a fear rather than a need. And fear buys in the wrong order: what can be seen, first.What the insurer asks for: declaring, proving, being paid
The only third party that will ever examine your security does it once, after the loss. What it will ask for, and what has to exist beforehand.
Frequently asked questions
Do we need an IT team to apply this?
No for the checks, yes for some of the fixes. What needs an intervention is indicated.
Do these subjects apply to small organisations?
Particularly. A small organisation loses proportionally more to an outage, because it has no second system and no second person.
Where should we start?
By restoring a backup. It is the fastest check and the one that most often reveals a problem.
Let us talk about your project
A free audit, no commitment: we look at your online presence and tell you what is holding it back.