I am Technical guy I am totally unaware of trademark related things.
But you must be thinking in admin Linux blog I am talking about trademark what happen to this guy. Believe me I am not crazy.
One day I got this comment:
"
Dear Mr. Kumar,Your "Open Hearts" header presents a bit of a problem for us as we hold the international trademark for "Open hearts. Open minds. Open doors." We ask you, kindly, to please remove this statement from your blog. If you have any questions, please contact us at im@umcom.org. --The United Methodist Church.
"
"Open Hearts, Open Minds, Open Doors... Open Source" yes this Title Description is trademark to someone.
Now just I reshuffled this and made it to “Open Minds, Open Hearts, Open Doors... Open Source"
Hope this will not create any problem.
Saturday, September 15, 2007
Thursday, September 13, 2007
Backup strategy
Backup strategy:
In computer world most important thing is DATA. No system can 100% secure or fault tolerance, so we always worry & care about data.
Various organization follows different back strategy. Like daily, weekly, monthly or yearly and at different levels.
Once my CEO asked me to design the backup system, and then I study various backup system, algorithms and architectures.
Then I come up with this backup architecture
Level 0 - Hard disk backup using RAID -1 mirroring, its purpose is to use in the case of hardware failure.
Level 1 – OS backup using rsnapshot. It is a file system backup utility based on rsyn, using rsnapshot; it is possible to take snapshots of your file systems at different points in time. Its purpose is to use in the case of OS failure.
Level 2 – Application data backup on same data center using Rsync. Its purpose is to use in the case of application failure.
Level 3 – Application data backup at remote location. Its purpose is to use in the case of data center failure.
As you move from level – 0 to level -3, you have to take more revisions like hours 1, day 1, week 1, and year.
I think this is quit good backup strategy.
In computer world most important thing is DATA. No system can 100% secure or fault tolerance, so we always worry & care about data.
Various organization follows different back strategy. Like daily, weekly, monthly or yearly and at different levels.
Once my CEO asked me to design the backup system, and then I study various backup system, algorithms and architectures.
Then I come up with this backup architecture
Level 0 - Hard disk backup using RAID -1 mirroring, its purpose is to use in the case of hardware failure.
Level 1 – OS backup using rsnapshot. It is a file system backup utility based on rsyn, using rsnapshot; it is possible to take snapshots of your file systems at different points in time. Its purpose is to use in the case of OS failure.
Level 2 – Application data backup on same data center using Rsync. Its purpose is to use in the case of application failure.
Level 3 – Application data backup at remote location. Its purpose is to use in the case of data center failure.
As you move from level – 0 to level -3, you have to take more revisions like hours 1, day 1, week 1, and year.
I think this is quit good backup strategy.
Subscribe to:
Posts (Atom)
-
Change Views DEFINER without ALTER VIEW: UPDATE `mysql`.`proc` p SET definer = ‘root@localhost’ WHERE definer=’root@foobar’ AND db=’w...
-
The Unix top command is designed to help users determine which processes are running and which applications are using more memory or process...
-
MySQL's InnoDB storage engine data refresh every situation. This post from InnoDB down, look at the data from the memory to the InnoDB ...