Data Recovery Services: What To Do When Your Hard Drive Fails
According to most people, there are two types of hard drives: those that have failed and those that will fail. But for folks who use Data Recovery Services, there is a third type of hard drive: one that does not fail.
A hard drive is the most vulnerable part of a computer; it has moving gears and is hence prone to wear and tear. So when you need hard disk data recovery, you must deeply consider the service and practice of the various repair companies in your area. A company that has been around the block more than a few times is ideal.
But more importantly, experts that ask questions and appreciate your situation are a necessity; companies that approach your needs in an impersonal way simply cannot diagnose your computer problems properly. For example, an expert who is on hand to ask specific questions about your hard disk will know whether or not to go about repair with mere software or through more professional means.
There are a variety of problems that lead to hard drive failure. If the hard drive is part of a mirror set, mirrored stripe set, or stripe set with uniformity, then all you will need to do is replace the drive – any lost data will mechanically regenerate.
A local service company can handle all your concerns though. Fixing a hard drive yourself is a tedious process, requiring lots of time and even research. Your next-door neighbor might be a computer geek, but that doesn’t mean his or her advice is remotely accurate. After all, a computer can fail for many different reasons and they are not always easy to pinpoint.
The ideal solution is usually to replace a failed drive and re-establish your backup. This does not always work though, as many people find the necessary backup is outdated or sometimes, non-existent.
If a hard drive is beyond repair, data recovery is obviously not an option. So prepare for unexpected charges; you might have to buy a whole new drive. In this case, just be careful when replacing it, as you don’t want to lose your data.
الاثنين، 16 نوفمبر 2009
الجمعة، 2 أكتوبر 2009
How to Configure your server to permit Server Side Includes SSI
Configuring your server to permit Server Side Includes SSI
To permit SSI on your server, you must have the following directive either in your httpd.conf file, or in a .htaccess file:
This tells Apache that you want to permit files to be parsed for SSI directives. Note that most configurations contain multiple Options directives that can override each other. You will probably need to apply the Options to the specific directory where you want SSI enabled in order to assure that it gets evaluated last.
Not just any file is parsed for SSI directives. You have to tell Apache which files should be parsed. There are two ways to do this. You can tell Apache to parse any file with a particular file extension, such as .shtml, with the following directives:
One disadvantage to this approach is that if you wanted to add SSI directives to an existing page, you would have to change the name of that page, and all links to that page, in order to give it a .shtml extension, so that those directives would be executed.
The other method is to use the XBitHack directive:
XBitHack on
XBitHack tells Apache to parse files for SSI directives if they have the execute bit set. So, to add SSI directives to an existing page, rather than having to change the file name, you would just need to make the file executable using chmod.
A brief comment about what not to do. You'll occasionally see people recommending that you just tell Apache to parse all .html files for SSI, so that you don't have to mess with .shtml file names. These folks have perhaps not heard about XBitHack. The thing to keep in mind is that, by doing this, you're requiring that Apache read through every single file that it sends out to clients, even if they don't contain any SSI directives. This can slow things down quite a bit, and is not a good idea.
Of course, on Windows, there is no such thing as an execute bit to set, so that limits your options a little.
In its default configuration, Apache does not send the last modified date or content length HTTP headers on SSI pages, because these values are difficult to calculate for dynamic content. This can prevent your document from being cached, and result in slower perceived client performance. There are two ways to solve this:
Basic SSI directives
SSI directives have the following syntax:
It is formatted like an HTML comment, so if you don't have SSI correctly enabled, the browser will ignore it, but it will still be visible in the HTML source. If you have SSI correctly configured, the directive will be replaced with its results.
The element can be one of a number of things, and we'll talk some more about most of these in the next installment of this series. For now, here are some examples of what you can do with SSI
Today's date
The echo element just spits out the value of a variable. There are a number of standard variables, which include the whole set of environment variables that are available to CGI programs. Also, you can define your own variables with the set element.
If you don't like the format in which the date gets printed, you can use the config element, with a timefmt attribute, to modify that formatting.
Modification date of the file
This element is also subject to timefmt format configurations.
Including the results of a CGI program
This is one of the more common uses of SSI - to output the results of a CGI program, such as everybody's favorite, a ``hit counter.''
What else can I config?
In addition to being able to config the time format, you can also config two other things.
Usually, when something goes wrong with your SSI directive, you get the message
[an error occurred while processing this directive]
If you want to change that message to something else, you can do so with the errmsg attribute to the config element:
Hopefully, end users will never see this message, because you will have resolved all the problems with your SSI directives before your site goes live. (Right?)
And you can config the format in which file sizes are returned with the sizefmt attribute. You can specify bytes for a full count in bytes, or abbrev for an abbreviated number in Kb or Mb, as appropriate.
To permit SSI on your server, you must have the following directive either in your httpd.conf file, or in a .htaccess file:
code HTML:
Options +Includes
Not just any file is parsed for SSI directives. You have to tell Apache which files should be parsed. There are two ways to do this. You can tell Apache to parse any file with a particular file extension, such as .shtml, with the following directives:
code HTML:
AddType text/html .shtml
AddOutputFilter INCLUDES .shtml
One disadvantage to this approach is that if you wanted to add SSI directives to an existing page, you would have to change the name of that page, and all links to that page, in order to give it a .shtml extension, so that those directives would be executed.
The other method is to use the XBitHack directive:
XBitHack on
XBitHack tells Apache to parse files for SSI directives if they have the execute bit set. So, to add SSI directives to an existing page, rather than having to change the file name, you would just need to make the file executable using chmod.
code HTML:
chmod +x pagename.html
Of course, on Windows, there is no such thing as an execute bit to set, so that limits your options a little.
In its default configuration, Apache does not send the last modified date or content length HTTP headers on SSI pages, because these values are difficult to calculate for dynamic content. This can prevent your document from being cached, and result in slower perceived client performance. There are two ways to solve this:
- Use the XBitHack Full configuration. This tells Apache to determine the last modified date by looking only at the date of the originally requested file, ignoring the modification date of any included files.
- Use the directives provided by mod_expires to set an explicit expiration time on your files, thereby letting browsers and proxies know that it is acceptable to cache them.
Basic SSI directives
SSI directives have the following syntax:
code HTML:
The element can be one of a number of things, and we'll talk some more about most of these in the next installment of this series. For now, here are some examples of what you can do with SSI
Today's date
code HTML:
If you don't like the format in which the date gets printed, you can use the config element, with a timefmt attribute, to modify that formatting.
code HTML:
Today is
code HTML:
This document last modified
Including the results of a CGI program
This is one of the more common uses of SSI - to output the results of a CGI program, such as everybody's favorite, a ``hit counter.''
code HTML:
What else can I config?
In addition to being able to config the time format, you can also config two other things.
Usually, when something goes wrong with your SSI directive, you get the message
[an error occurred while processing this directive]
If you want to change that message to something else, you can do so with the errmsg attribute to the config element:
code HTML:
And you can config the format in which file sizes are returned with the sizefmt attribute. You can specify bytes for a full count in bytes, or abbrev for an abbreviated number in Kb or Mb, as appropriate.
الاشتراك في:
الرسائل (Atom)