The 2015 hurricane season is here, are you and your business prepared?

HurricaneThe 2015 hurricane season is here, are you and your business prepared? Hurricanes are a fact of life for us in the southeast.  Take your head out of the sand and let us review your backup and disaster recovery plans.  We can perform a review of your current infrastructure and make recommendations on procedures and technology solutions that match your needs.

Hurricane Tips

  1. Watch the weather and listen to the authorities for evacuation notices and other warnings.
  2. Keep important documents and information together in one place and store in a waterproof bag or container.
  3. Inform your friends and family  during the storm and where you are going to be after. Check in with them to let them know that you are safe.
  4. Document your house and business. Take photos and/or video of your belongings and keep an inventory of all your belongings.
  5. Check and secure all openings to the house (windows, doors, etc.)
  6. Listen to evacuation notices.  Authorities will not be able to help you during a storm.

Hurricane Preparedness Checklist

  • Bottled water (enough for a week)
  • Canned and dry food; Non-perishable
  • Manual can opener
  • Paper products, plates, cups, utensils
  • Gas/charcoal grill
  • Lighter or matches (be careful of open flames)
  • Plenty of Batteries
  • Flashlights
  • Battery powered radio
  • Fill your vehicles with gas
  • Charge Your Cell Phone

Want to know more about protecting your businesses critical data?  Contact us today.

File and Folder Name Best Practices and File Name Limitations

Good file names are essential to accessibility. Many offices utilize a network server to store files so that they are accessible from multiple locations by various people. This requires that file names (as well as folder structures) make sense to more than just the creator. A file name should be clear to everyone in the department or agency in which the file was created. A record should be distinguishable from files with similar subjects as well as different versions of the same file. When other individuals access a record, they may be using different operating systems (Microsoft Windows, Mac OSX), different versions of the system (e.g. Windows Vista, Windows XP), or different software (e.g. Microsoft Word, OpenOffice.org Writer, Notepad); therefore, it is important to follow rules that will allow a file to be recognized in as many different environments as possible.

Rule #1: Avoid using special characters in a file name. \ / : * ? “ < > | [ ] & $ , . The characters listed above are frequently used for specific tasks in an electronic environment. For example, a forward slash is used to identify folder levels in Microsoft products, while Mac operating systems use the colon. Periods are used in front of file-name extensions to denote file formats such as .jpg and .doc; using them in a file name could result in lost files or errors.

Rule #2: Use underscores instead of periods or spaces. As mentioned above, periods already have a specific function in a file name, which is to tell the computer program where the file-name extension begins. Spaces are frequently translated in a Web environment to be read as “%20”. For example, TMD Technology.doc would appear as TMD%20Technology.doc if it were available online. This alteration can cause confusion in identifying the actual file name. Spaces in file names can also cause broken links, because word processing tools like Microsoft Word, and e-mail clients like Microsoft Outlook, recognize spaces as an opportunity to move to another line. Another difference that is found among operating systems and software is the acceptable length of file names. Some systems allow up to 256 characters, while others allow far fewer.

Rule #3: Generally about 20-25 characters is a sufficient length to capture enough descriptive information for naming a record.

Rule #4: Limit The number of sub folders you use in your tree structure.  Each folder and character adds to your file name limit.  Folder names should be descriptive but short.

TMDTechnology.com