Most companies consider downtime any time that some or all of its employees are not doing their jobs due to circumstances beyond their control or when their online customers can't access their systems.
Where computers and data usage is concerned, this is more often caused by a technological malfunction, such as a computer server going down, than a power outage.
Downtime also comes in the form of database inaccessibility from software incompatibility, data loss, hardware or software upgrades and new system installation.
One goal of most remote database consulting services is to prevent their clients from having downtime.
From the perspective of a remote database administrator (DBA), downtime due to data loss is always preventable.
Data Loss Data can be lost in a number of ways, such as being corrupted by a virus, destroyed in a fire or flood or put into a data storage unit that fails.
Having a database backup ensures that files, facts, figures and other information can be retrieved if the primary source becomes compromised.
Adatabase backup is critical to the preservation of a company's data, especially if the company's office is damaged.
The backup process should be checked and tested regularly.
One way to prevent data loss is to make sure that everything is backed up at least twice.
Corrupt Files From time to time, files become corrupted.
The corruption may be due to a virus, a power surge, application error or some sort of physical damage to the storage device.
Files can be restored from another source using a remote database backup.
The transfer of information can only prevent downtime if it is done quickly and the information replaces that which was lost.
If the backup is also corrupt or no one is available to retrieve the information, the downtime will be significant.
Inaccessibility Some companies set up database storage and file transfer on their own through their information technology department, but once the system is in place it is often never touched or tested.
If a power outage knocks the system offline, the data may stop backing up until someone needs it and notices its absence.
If the device where the storage is kept becomes obsolete, the information will likely be inaccessible over time.
Similarly, if the information must be retrieved through outdated software or communications devices, the company will have significant downtime.
Offline A database is typically taken offline for hardware and software installation or upgrades.
One way to prevent downtime during this transitional period is for the upgrade and installation work to be done while no one is using the system.
This is becoming more and more difficult to do in a world that never sleeps, where there is always someone working or accessing the data.
One way to prevent this problem is to run two or three sets of backups and a standby system, then perform the upgrade on a device not in use while a second unit is in place.
The second unit is then upgraded while the first unit is in place.
This prevents the data's loss and company downtime.
Where computers and data usage is concerned, this is more often caused by a technological malfunction, such as a computer server going down, than a power outage.
Downtime also comes in the form of database inaccessibility from software incompatibility, data loss, hardware or software upgrades and new system installation.
One goal of most remote database consulting services is to prevent their clients from having downtime.
From the perspective of a remote database administrator (DBA), downtime due to data loss is always preventable.
Data Loss Data can be lost in a number of ways, such as being corrupted by a virus, destroyed in a fire or flood or put into a data storage unit that fails.
Having a database backup ensures that files, facts, figures and other information can be retrieved if the primary source becomes compromised.
Adatabase backup is critical to the preservation of a company's data, especially if the company's office is damaged.
The backup process should be checked and tested regularly.
One way to prevent data loss is to make sure that everything is backed up at least twice.
Corrupt Files From time to time, files become corrupted.
The corruption may be due to a virus, a power surge, application error or some sort of physical damage to the storage device.
Files can be restored from another source using a remote database backup.
The transfer of information can only prevent downtime if it is done quickly and the information replaces that which was lost.
If the backup is also corrupt or no one is available to retrieve the information, the downtime will be significant.
Inaccessibility Some companies set up database storage and file transfer on their own through their information technology department, but once the system is in place it is often never touched or tested.
If a power outage knocks the system offline, the data may stop backing up until someone needs it and notices its absence.
If the device where the storage is kept becomes obsolete, the information will likely be inaccessible over time.
Similarly, if the information must be retrieved through outdated software or communications devices, the company will have significant downtime.
Offline A database is typically taken offline for hardware and software installation or upgrades.
One way to prevent downtime during this transitional period is for the upgrade and installation work to be done while no one is using the system.
This is becoming more and more difficult to do in a world that never sleeps, where there is always someone working or accessing the data.
One way to prevent this problem is to run two or three sets of backups and a standby system, then perform the upgrade on a device not in use while a second unit is in place.
The second unit is then upgraded while the first unit is in place.
This prevents the data's loss and company downtime.
SHARE
