Thursday, 23 June 2016

Don't Panic! Recover Your Data from a Crashed Hard Drive In No Time!!!


Do you want to recover your lost data from your crashed hard drive? If yes then you are on the right place. In this article we will discuss about how to recover data from a crashed hard drive. A hard drive can crash with mainly two types of damages namely logical damages and physical damages. So I am going to tell you two best data recovery tools. Here they are:
1) Stellar Phoenix Windows Data Data Recovery
Anyone can use this efficient tool which contains very simple UI. This tool is useful to recover data from any kind of drive in almost every condition. And the more importantly it is free so you no need to pay a penny from your pocket! 
2) Recuva Data Recovery
Recuva is anther free tool to recover data from a crashed hard drive. This is also free tool containing simple features.
Just search in google and you will find the resources. So many other services are available in the market to get your data back from a crashed hard drive. Some of them are PC Inspector File Recovery, Hiren's BootCD, GetDataBack and for mac MiniTool Mac Data Recovery and DiskDrill. 
And finally if none of the above method works then you probably need to send your drive to data recovery service. Grillware is recommended data recovery services.

Whose Fault When You Have Downtime?


OK, time for a reality check. You either have a recovery plan or you don’t.
If you do have a recovery plan, are you sure it will work?
IBM reports 75% of all businesses with recovery plans do not conduct regular recovery testing.
But even if things go as planned, how realistic is the plan? Industry studies document that when downtime strikes, 33% of all recoveries do not go as planned.
Traditional recovery plans generally rely on the availability of a hot site.
  • But even with annual testing, hot site recovery usually takes 1–3 days to get back up and running.
  • 80% of data inaccessibility is due to human error, which can take 2–3 days to recover from traditional backup tapes.
In the meantime…what?

The truth is, you’re probably paying way too much for a plan that won’t deliver.

But the good news is that costs have dropped sharply. Whatever system you have in place now, you may be paying more in annual maintenance than the total cost of a state-of-the-art replacement that offers far greater reliability, regular testing and much faster recovery.
What if you don’t yet have a recovery plan? That means you probably rely on backup tapes. Industry studies show that recovery from tape backup fails 50% of the time. Most multi-server environments rely on a combination of software and a tape library to back up critical data. As these environments grow, the backups become more complicated, which makes recovery even trickier. Rarely do these users ever test a complete backup, and recovery winds up taking 1–3 weeks. The most critical application to recover is usually email. How long can your business tolerate email downtime? Even more significant – studies show that 70% of businesses that suffer major data loss are out of business within 2 years.
Bottom line: Newer recovery technology—which includes fault tolerant clustering, high-availability, virtualized storage and a virtualized tape library—is less expensivethan what businesses currently pay for hot site availability with 1–3 day recoverability. For smaller users, the cost of a virtual tape library is comparable to that of a traditional tape library, yet provides file recovery in a matter of minutes…and can be extended for total disaster recovery.
To learn how much better and more affordable new recovery technology is, I urge you to email me now at blosey@source-data.com or call me at 800-333-2669.

How to get rid of OST file issues?

Outlook is the most popular email client as it offers great reliability and flexibility to perform a professional or personal email communication efficiently. Unlike other email clients, it enables users to work even in offline mode when connection between Outlook and Exchange server gets disrupted due to any possible reason. And, it is possible because of a special kind of file known as offline storage file or OST file. These OST file stores your whole offline work in its database for a short time period. Sooner, when connection gets re-established between Outlook and Exchange server whole OST data get synchronized with Exchange server database.
With this facility, there are few glitches also which arise when OST file undergoes any corruption issues. As, they contains Outlook mailbox items such as emails, notes, journals, calendar, schedules etc. so OST corruption leads to inaccessibility of OST file along with all contained email items. A long duration connection disruption is very harmful for integrity and consistency of OST file. There are several reasons which make OST file inaccessible which are divided into two main categories:
1) Physical or hardware reasons:
  • Corruption of storage media (i.e. bad sectors) leads to inaccessibility of OST file data.
  • Networking fault usually leads to inaccessibility of OST file and thus orphaned OST file created.
  • Sudden or unexpected system shut-down can corrupt OST file.
2) Logical or software reasons:
  • Malicious virus attack causes corruption of OST file.
  • Wrong selection of OST file recovery tool can put your data in even more worst condition.
  • Synchronization interruption due to any reason.
  • Improper shut down of Outlook client can damage Outlook OST file.
  • Hidden viruses of other software files may lead to serious data loss.
Resolution 1:
Inaccessibility of OST file may results a great data disaster situation for Outlook users. You find yourself unable to access your mailbox data and other email items from orphaned OST file. In such cases, consistency and integrity of OST to PST file gets interrupted. To get rid of integrity issues, you can create a new OST file by following given steps:
Create a New OST file:
  • Close Microsoft Outlook.
  • Click Start, and then click Control Panel.
  • Click Switch to Classic View if you are using Windows XP or higher versions.
  • Double-click Mail.
  • In the Mail Setup dialog box, click Show Profiles.
  • Select one of the incorrect profile in the list and click Remove to remove it.
  • Repeat 6.6 until all incorrect profiles have been removed.
  • Click Add to create a new profile and add email accounts according to their settings on the Exchange server.
  • Start Outlook and re-synchronize your Exchange mailbox, your problem will get resolved.
Resolution 2:
Other possible solution of OST file corruption is use of OST integrity check tool (Scanost.exe). It is very popular utility for resolving issues related to OST file integrity and consistency. To use the OST Integrity Check tool, your Outlook must be connected to your Exchange account. The tool can scan your mailbox folders and items. Before running this tool, you need to change your Outlook startup settings temporarily. It scans your infected, corrupt or orphaned OST file and tries to repair OST file. The OST Integrity Check tool (Scanost.exe) is installed when you install MS Outlook and it is located at: drive:\Program Files\Microsoft Office\OFFICE12. However, it can fix only few minor errors of your corrupt OST file.
In case of severely corrupted OST file, you have to choose a third party tool like Kernel for OST to PST conversion. It is a much powerful and popular tool for repairing and recovering OST file data. It converts OST file into easily accessible PST file. For More Information... www.osttopst.kerneldatarecovery.com
Summary:
Inaccessibility of OST file is now a common problem among Outlook users. Try inbuilt utilities and eliminate OST issues. If they are not useful then look for a professional third party tool and get desired result.

Modern Backup Infrastructure


I still remember 10 years ago when I was in backup software salesman. We were at this semi-conductor factory somewhere in the Philippines. The partner team and me worked through the night to get the backup software in place for their POC by 6am. The partner team worked with the IT group to put in place one of the first backup to disk solution we ever sold in Asia Pacific. Still remember Cris and Daisy... We completed the first set of backup and the IT manager sat down beside me beside his terminal. He was a skeptic and did not believe in disk backup. I think he was very tired as he looked dazed. Then I started to see beads of perspiration starting to form on his forehead. I knew something was wrong. He accidentally deleted the SAP database file and recovery from tape was not a option as it would take too long. I suggested to him to use the backup set we created and he did.. the rest was history. That was one of the fastest deal we closed...
This is a great story and there are a few important things I learn...
A. You never know when a backup is needed. Most of the time the problem is not a hardware failure but human errors.
B. Recovery always happen at the worst time. When you are minutes from production hours... Somehow Murphy is always part of the team. Recovery is 80% to 90% of the time required from the latest production set and it is needed fast.
C. There is usually no time for recovery. With systems operating 24x7 the amount of time for recovery is very small. With all the modern technologies of snapshots are replication these are often reserved only for the mission critical applications. When IT managers fall back to recover from backups, deduplication technologies which help speed up backup will actually slow down recovery as there is a need to rehydrate backups before they can be recovered.
D. Speed of backup is crucial. Backup needs to be completed within the backup window every night. There is no time for tape stuck or robotic failures from the traditional approach of backing up to tape.
E. You need high compression and deduplication rate so that as much data can be kept on disk as possible. Today every software or hardware backup technology company will claim to offer the highest deduplication rate. As a technologist it is apparent to me that dedicated CPU hardware will push the highest compression rates but arguably some software can do a pretty good job.
F. Replication is a new requirement for backup. Backup is usually part of a DR strategy. Replication or tape-out is usually needed to move data offsite. In some cases branch offices may not have the maturity to administer their own backup, it is important to be replicated to a central primary site.
G. Backup capacity must grow in tandem  with your storage. Most IT department fail to put enough considerations into scaling of backup. The factor of storage growth due to introduction of new services often outstrip that of backup growth capacity. This often cause backup to extend beyond the backup window. Scale-Out and Scale-Up is a interesting trend that storage is adopting to meet unpredictable storage consumption trends. Backup should also be able to match the ability to Scale-Up and Scale-Out to be relevant for the long term.
The backup strategy and recovery strategy is equally important. Choose your strategy carefully and put your requirements in perspective and balance that against your business trends will be a good starting point.
DCIG is a independent evaluator for hardware technologies. A set of free reviews on Deduplicating guide is available on the following site for your review http://www.exagrid.com/why-exagrid/industry-analyst-perspectives/
Tan Lee Ann
Area Sales Director, APAC
ExaGrid 

Why clean Excel VBA macros?


Visual Basic for Applications (VBA) is a programming language built into most Microsoft Office applications. It first appeared in 1993. Although new VBA properties and methods are constantly being added to support innovations in Office, the Visual Basic Editor (VBE) and VBA's inner workings haven't changed much over the last 2 decades in order to ensure consistency and compatibility in the programming model across releases. 
Hardware in the mid-90s was pretty slow compared to computers nowadays, so VBA had to rely on an internal performance cache in order to deliver an acceptable user experience. 
Unfortunately, VBA code doesn't properly clean-up after itself, so lots of junk gets left behind in performance caches during extensive editing of VBA projects. Not only does this increase the file size, but it may lead to odd behaviour of your program at runtime or slow loading.

If Add-ins or workbook macros are run across several versions of Office, stability issues are likely to be experienced with any uncleaned VBA project. The problems are triggered by compiled macro code stored in version dependent performance caches.

These redundant code caches can even provide a peak at earlier versions of your code. A forensic investigator can travel back in time and read bits and pieces from code you compiled during VBA code revisions. So, if you really want to delete any sensitive code from your macro-enabled workbooks, you should distribute only cleaned VBA files.
If you plan to share a copy of a macro-enabled Office file or template (workbook, document, presentation etc) you should be aware that the username used by the macro author may be stored inside the redundant compiled code caches of the VBA project.

Depending on how private you want your coding work to be, you may want to remove this hidden information by cleaning the VBA project in macro-enabled files, as it can reveal sensitive details about your company or yourself to the public.

THE WORKAROUND
Ribbon Commander offers the .CleanVBAProject method, which can remove all code garbage from any macro-enabled or binary workbook and Add-ins instantly. 
The Ribbon Commander VBA cleaner removes all redundant caches from closed files, so VBE doesn't get a chance to replace the information. 
Cleaned files are smaller in size. Nowadays files are moved between desktops and the cloud more frequently than ever before. On an enterprise level, smaller files translate into decreased costs for online storage / bandwidth and faster backups or downloads. 
For years the 'golden' standard for Excel VBA code cleaning has been module export - import.  Ribbon Commander aims to raise the bar by offering several productivity advantages for VBA developers. 
  • Ribbon Commander's VBA Project code cleaner supports both 32 & 64 bit versions of Office/Excel.
  • The CleanVBAProject method does NOT open files in Excel. This translates to significant time savings, as massive workbooks may require even minutes to open and save.
  • Multiple closed files can be cleaned very fast by Ribbon Commander. Check if your files are already clean using the .isVBAProjectClean property.
  • Traditional cleaning involves exporting all VBA components to text files on disc. This a loophole for the security minded, as these text files can be undeleted easily by file recovery software.
  • Ribbon Commander's Code Cleaner can read and clean both unlocked & locked VBA projects. 
  • End users can clean 3rd party protected Add-ins, when stability issues are experienced during loading or running code. Locked VBA projects are not unprotected under any circumstances.
  • Ribbon Commander's Code Cleaner can clean closed macro-enabled (.xlsm), binary (.xlsb) workbooks, templates (.xltm) & Add-ins (.xlam) or any macro-enabled Office file (PowerPoint presentations & Word documents).
  • Ribbon Commander's Code Cleaner can remove the full path to MSForms.exd from the VBA performance cache, which contains the developer's username in the format shown below:
    C:\Users\james07\AppData\Local\Temp\VBE\MSForms.exd
Reclaim existing storage space on desktop PCs and servers by replacing large macro-enabled Microsoft Office files with smaller versions. Slow storage growth as new files are added. Test for yourself: files shown are available at Bruce's Mcpherson blog:Desktop Liberation

Apple's Responsibility to Law Enforcement as a Licensor of "Way Cool" Technology


Tim Cook's responsibility is to his company and his philosophy around "privacy" is primarily shaped by his mandate to protect the company’s perception, dominant market position and value of its stock. This is as it should be and he has done a wonderful job at it. An obvious and key component of that winning philosophy and strategy is the degree to which Apple will go to the mat in order protect sanctity of its customer’s data fromunwarranted disclosures to 3rd parties, namely the government. Way Cool companies, and there is no other Way Cooler tech juggernaut than Apple, spend hundreds of millions of dollars cultivating and tuning every aspect of their public image. Every time I think of Apple, images of Way Cool young people wearing skinny jeans comes to mind. They're bouncing around, brimming with hipness, sheikness and a carefree freedom that makes me wonder if they have student loans. The problem for Apple is that Farook Sayed and Tafsheen Malik, are not Way Cool. They are terrorists and any form of association with them is from a corporate perspective, a marketing and PR nightmare. The issues raised in the in FBI’s motion to compel assistance in data recovery drags Apple into a realm of political and legal debate that it would do well to avoid. In my humble opinion and for reasons which I will explain, the FBI's sought after assistance in cracking the password to facilitate the disclosure of Apple licensee and ISIS devotee Farook Sayed's data, is fully warranted. Mr. Cook has to understand that you can't go wrong helping G-Men get to a terrorist's data that is stored on one of Apple’s devices. He has muddled the issues of general data privacy with a legal duty as established by a court to assist in an investigation where the discovery boundaries are specified and narrow in scope.  He should be focusing on the unenviable challenge of spinning how Way Cool Apple is helping to insulate America from terrorists hell bent on killing innocent American civilians.
The government is now the custodian of a specific iPhone, to be specific it's an phone iPhone 5C with the following unique characteristics, Model: A1532, PIN:21 MGFG2LL/A, SIN: FFMNQ3MTG2DJ, IMEI: 358820052301412. The phone belonged to one individual, a Farook Sayed, who in conjunction with his paramour and wife, one Tafsheen Malik, committed specific acts of terrorism on American soil. There is an obvious reason for belaboring specificity and one of them is that the FBI is not requesting blanket access to all iPhones owned by law abiding Americans. Right now, Apple is taking the lead in spinning up the Snowden NSA “data hoovering” angst that gripped the nation a few years ago, and they are doing so by virtue of turning a limited and legitimate criminal investigation into one implicating the privacy rights of all Americans. While it is true that the methods employed to bypass the iPhone security model to allow access to the data in fact potentially allow access to others phones, Apple is not being asked to do so.  The order compelling Apple stipulates that the government, the FBI specifically, obtain the following from them:
Apple's reasonable technical assistance shall accomplish the following three important functions: (1) it will bypass or disable the auto-erase function whether or not it has been enabled; (2) it will enable the FBI to submit passcodes to the SUBJECT DEVICE for testing electronically via the physical device port, Bluetooth, Wi-Fi, or other protocol available on the SUBJECT DEVICE and (3) it will ensure that when the FBI submits passcodes to the SUBJECT DEVICE, software running on the device will not purposefully introduce any additional delay between passcode attempts beyond what is incurred by Apple hardware.
Apple's reasonable technical assistance may include, but is not limited to: providing the FBI with a signed iPhone Software file, recovery bundle, or other Software Image File ("SIF") that can be loaded onto the SUBJECT DEVICE. The SIF will load and run from Random Access Memory and will not modify the iOS on the actual phone, the user data partition or system partition on the device's flash memory. The SIF will be coded by Apple with a unique identifier of the phone so that the SIF would only load and execute on the SUBJECT DEVICE. The SIF will be loaded via Device Firmware Upgrade ("DFU") mode, recovery mode, or other applicable mode available to the FBI. Once active on the SUBJECT DEVICE, the SIF will accomplish the three functions specified in paragraph 2. The SIF will be loaded on the SUBJECT DEVICE at either a government facility, or alternatively, at an Apple facility; if the latter, Apple shall provide the government with remote access to the SUBJECT DEVICE through a computer allowing the government to conduct passcode recovery analysis.
Case No. ED 15 - 0451M’s motion and order are pretty specific and tailored to obtain discovery pursuant to a criminal investigation. It's not the job of the FBI to pontificate and postulate about why their actions do not constitute government overreach at this stage. Further, the issue of data privacy, while legitimately introduced by Mr. Cook, is a red herring here. Based on what I've read to date, it occurs to me that the real issue is one of a corporate organization's responsibility and legal obligation to aid a legally sanctioned law enforcement agency with their investigation when ordered by a court to do so. More specifically, the government's position is that when one of its investigative agencies has posited facts before a court to support their belief that a licensee of a corporation's proprietary technology may have used that technology in furtherance of a crime or that potential evidentiary material may be secreted within the device only accessible with the assistance of said corporation, they want help. Frankly, this position is not unreasonable.
A password protected iPhone with information on it is analogous to a sophisticated safe with documents written in Wingdings in it. If the documents in the safe were subject to a subpoena or discovery request and the combination was irretrievably lost, it would not be unreasonable for a court to enlist the help of the manufacturer, which is typically done under the guidance and oversight of a qualified special master to open it. It would then up to the investigative agency to find a certified Wingding translator to decode the Wingding encoded document. In this case what Apple is being asked to do is suspend the function of certain IOS9 proprietary security models to expose the data - in other words open the safe. The FBI will then use brute force password decryption methods, if needed, on the iPhone data. Does this scare me? Not in the slightest. My household is fully Apple enabled. I have a primary and backup Macbook Pro and my wife and kids all have the latest Macbook Airs and iPhones. I am of the opinion that Apple’s primary concern should be related to safeguarding their proprietary technology, algorithms and methods related to their encryption/decryption technology. If Apple could have assurances that their IP would be protected from release to the public domain, then Apple could have their pie and eat it too. If my team was on the Apple crisis management and incident response team, we would shield Mr. Cook by minimizing Apple’s contribution to the public debate about data privacy by downplaying the significance of Apple's role in this matter – less is more in this instance. To do so we would use the very language in the order compelling Apple to support the FBI. We’d also make sure that there were easily implementable protective caveats in Apple's favor in the form of an iron clad protective order governing confidentiality around processes and methods used to facilitate the government's request. 
If a related terrorist attack were to occur and it turns out that it could have been thwarted with help from Apple in the instant case, Mr. Cook's plate spinning act to manage the hot button issues of the market’s desire for consumer data privacy, with law enforcement needs while maintaining a Way Cool corporate culture that is above the political fray could end with a lot of shattered porcelain. The fallout from such a potential attack could cause reverberations not just in Apple's board room but create a chilling atmosphere on Capitol Hill as an already skittish America would clamor for something more to be done...and that usually means more hawkish legislation which statutorily chips away at the very thing Mr. Cook is trying to protect, privacy.
The bottom line is it's easier to quantify the knowns which include the perceptual fallout from working with the government than it is to calculate the probability that there isn't information on the iPhones in question that could lead to preventing a terrorist attack. Ultimately from a business perspective the decision Mr. Cook will make really boils down to Apple’s risk tolerance in relation to the company’s corporate goodwill. If he does accede to the court ordered directive, Apple could reassure their customers that this was a special case of Apple working to protect America; the order to compel Apple was very specific as it relates to the government's access needs for ONE device. Surely Apple's vaunted PR and marketing machine people could spin this story and surely a Judge can ensure that a protective order could be crafted to ameliorate concerns about protecting encryption/decryption IP.
Rest assured Mr. Cook, most of us won't see you as colluding with Big Brother, as consumers we're pretty fickle but not that fickle. A decision one way or the other won't change buying patterns as I love my Macs and iPhones....but know this, we live in different times and I remember the smell that lingered for years in lower Manhattan after the towers came down. A lot of us who lived and worked in NYC before and after that day do. I think you know where this licensee of Apple technology is coming from.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
The motion and order have been OCR'd and can be download from the links below should you like to have a read.  
@msn @aiim @wsj @arma @yahoo @google @bbc @reuters @nytimes @huffingtonpost @bloomberg
About the author: My passion is gardening (buds are sprouting) and my favorite role is that of Enterprise Discovery Solutions Architect. My group develops Information Governance Strategies and conducts e-Discovery and Litigation Readiness Gap Analyses for companies in the Energy, Pharmaceuticals/Financial Services/Insurance and High Tech verticals. On occasion we'll work with communications groups to help with messaging. We’ve got lots of experience testifying as a technical experts as well as doing data conversion from disparate complex systems to normalized formats. I am a fan of anything technical, namely the most complex e-Discovery challenges out there. Feel free to ping me from my LinkedIn profile or @ redavis@verisolutions.com with any confidential questions or comments, or if you'd prefer to call, you can ping me at Mobile 1.646.306.3833 - Office: 1.646.205.3208.
Cheers...Rich