Type your search keyword, and press enter

Differentiating Between an Active and a Passive DisplayPort Converter

The existing differences existing between an active and a passive DisplayPort converter should properly be considered when converting a video from any source that makes use of mini DisplayPort to DVI. For instance, a computer to another monitor. If a dual-mode DisplayPort or a DP++ is supported by the source, then a passive adapter should be used, in as much as the source can do the conversion.  But where dual-mode DisplayPort or DP++ is not being supported by the source, then the active converter is recommended because it includes additional conversion chips. Thunderbolt ports support DP++ in some sort of way (natively).

Passive Adapters

The fact that this type of adapters does not include any additional conversion chip tends to make it less expensive. If you intend finding out if the passive adapter can work for you, then check if the DP++ symbol is above the mini DisplayPort source. This symbol is shown as a D and a P inside it with double + signs to the left, with one above the other.

Active Adapters

This type of adapter makes use of an additional chip for making conversion within the adapter, whether DP++ is supported by the source or not. This type of adapters is more expensive than the passive adapter types. If you have plans of using different monitors but with one particular computer then the active adapter is best for you, this is because most video cards are incapable of running the maximum monitors number when DP++ is in use. This can be attested to when the computer possesses two or more mini DisplayPort active connection. You can also find out from your video card supplier to make sure you know the adapter type needed for the setup you desire to run.

For more information click here.

Don’t Let Your Files Be Held For Ransom

An International Issue

Ransomware is pervasive and fired at e-mail accounts like a digital shotgun blast. It’s a kind of net on the web, if you will. Basically, those who program ransomware applications shoot out their viruses as far and wide as they can, then wait for a bite.

It’s usually not about a specific target with ransomware (though this isn’t always the case), it’s usually about taking advantage of whoever is unfortunate enough to download the software.

Ransomware hides itself in emails that may look legitimate. There are cases where a hacker using a ransomware virus has sent out an email that looks as though it comes from a top-tier online website like Facebook or Google. Usually the email will make up some reason that sounds slightly legitimate why you should send your login and password information in reply.

Don’t fall for it; this sends the hacker(s) a “ding!” which notifies them that they can break into your system one way or another. Don’t feel bad if you get “phished” like this; you’re far from alone. In the fourth quarter of 2016, San Francisco’s transit system was subject to a ransomware attack. That’s a transit system in one of the most technologically advanced cities in the nation.

If anyone should have been able to avoid a ransomware attack, it should have been a public services provider in San Francisco. That they were victim to attack demonstrates just how pervasive these attacks have become, and how potentially dangerous they can ultimately be.

Finding An Agency

According to SentinelOne.com, a purveyor of ransomware protection software, “It’s time for security companies to back their technology and provide users with the financial assurance they deserve against ransomware attacks.” The fact is, if you have ransomware protection that you’ve paid for, and it doesn’t work, you should be remunerated.

Companies that guarantee such financial assurance are a safe bet when it comes to sourcing proper protection against scams that hold your files for ransom against payment of a fee. The thing is, some ransomware programs are so good that if you don’t pay the fee, not only do you not get your files back; they may be destroyed. This can be a critical blow to small and large businesses alike. See more.

How to boot virtual machine in the Recovery Mode?

How to Boot Virtual Machine in the Recovery Mode

Many are the ways through which you can boot a virtual machine in the recovery mode. Here, we are going to focus on of the most effective ways of achieving the same. We will inform you of a method that geeks and other computer experts use to go around the task. Every step below is critical therefore; there is need for you to pay close attention to each one of them.

What are the steps to take?

In this method, the buttons from F1, F2… etc. are very important so there is need to ensure that all of them are functional before beginning the process. Below are the steps to take:

  1. 1. Opening of the OS X System preferences

The first step involves opening of the OS X system preferences using your keyboard. Enable all the keys that will serve as standard functional keys.

  1. 2. Open the configuration pane

The next step involves opening of the virtual machine configuration pane. You should follow the steps from hardware to boot order where you will get various options. Click on the “select boot device on startup” option. You should then start your virtual machine and make its window active be clicking on it.

  1. 3. Press F8

Depending on the type of operating system that you are using, press the F8 button before anything appears on the screen your computer. For some types of OSs like Windows 8.1, you will have to press Shift and F8 to achieve the same effect as the other types.

It is important to note that this stage requires patience. We recommend that after booting your virtual machine; continue pressing on F8 multiple times until the advanced boot option appears on your screen. If you do not achieve this on the first attempt, shut down the computer and redo the procedure.

  1. 4. Choose repair your computer option

When the advanced boot option appears on your screen, use the arrow keys to select the “repair your computer option”. Windows will then ask you to choose your language and from here, you can enter your credentials and continue. If you are using Windows 8.1, choose the troubleshoot option.

  1. 5. Select boot device on startup option

After the repair or the troubleshooting process is over, the next step is to select the boot device on startup option.It is important to note that you might not be able to boot your machine into recovery mode if you do not have a system recovery partition. However, you can go about that by booting the virtual machine from the installation media. Booting a virtual machine in the recovery mode is not as hard a task. All you need to do is follow the steps above.

VMFS partitions stored on corrupted RAID arrays with or without RAID controller

VMFS Partitions Stored on Corrupted RAID Controller

Corrupted RAID arrays are one of the two main things that can lead to a Virtual Machine File System, (VMFS) failure, the second being damaged blocks. These are not all there are to a VMFS failure but they are the two most common reasons why VMFS failures happen. However, restoring lost data is not an impossibility. This is where VMFS recovery comes in; a tool designed for anyone who uses virtual machines whether VirtualPC, VirtualBox, VMware, Parallels EnCase or any other. This tool additionally comes with vSphere 6 as well as ESX server support.

VMFS recovery is capable of providing repair for a corrupted RAID array whether or not a RAID controller is available or accessible. That is, even if the RAID controller is inaccessible, recovery is still possible. With the help of JBOD, VMFS, RAID 0 Recovery can restore virtual machine disks from any hard drives whether they are corrupted or safe. It will by this, give the hard drive access to the corrupt data and thereby recovering it as though it were from a Virtual Machine File System disk that had no issues.

This recovery tool supports VMFS partitions of up to 64 terabytes, files up to 2 terabytes as well as even VMFS5 drives that have over one million files stored in them.

There are two modes available for you to choose from in carrying out the recovery process; the fast mode which you can use for the recovery of existing or deleted files or the full mode which you can use to enable the recovery of your data in more difficult situations.

Virtual PC images can be recovered from ESX servers. First, an ESX / ESXi storage which has been previously damaged is recovered. After this has been done, VMFS recovery will get access to separate virtual machines as well as their VDMK disks. And then the recovery procedure will be carried out.

In order to be able to run the VMFS recovery, you will need at least a standard PC that comes with Windows XP or something higher. It is best, however, to use Windows 8 or 7 with a 4GB RAM and above. This is because the software would build in RAM, a complete VMFS structure before the recovery process takes place. You will also need more RAM if you have bigger VMFS disks or ESX server. In other words, the bigger the ESX server or VMFS disks you have, the more RAM you will need for a successful recovery process.

In addition, you should have it in mind that Virtual Machine File System recoveries would also require up to 16 megabyte space to enable installation. It will also need quite an amount of usable space on the disk where the recovered data can be saved. Basically, however, so much of this would depend on the size of the data you need to recover.

Recover VMware Partitions from Damaged Hard Drives and Faulty RAID Arrays

What is a RAID array?

When we talk of a raid array, what we mean is a system of hard drives that are interconnected in such a way that they act as one storage space. There are many ways of connecting the hard drives to form raids. One thing is that when they are connected to form a raid, the data stored is in stripe from and that the stripe is spread evenly across all drives that are in array. Because of this, there comes a time when the array becomes faulty, either because of damaged hard drives or arrays.

What is virtualization?

This is a process whereby the image of the whole data storage device or array, is made and have it in a single file.

Hard disks can be virtualized and then be contained in files of hard disk drive images. Actually, the virtual hard drives will function just like the real computer that has an operating system. It is sometimes known as virtual machines.

In order to attain a virtual machine to run just like a real physical machine or computer, you first need to create it and run it on the host computer, using a hypervisor.

How to Recover VMware Partitions from Damaged Hard Drives and Faulty RAID Arrays

The first process in recovery is to access the condition of the damaged hard drives. After the repair, a binary read is tried on the drives.

First you need to figure out the geometry of the raid array in question. This is done through combing of the metadata that is contained in each and every drive for one to know where the parity data lies for the arrangement of stripes to be complete. To reorganize and reconstruct the failed arrays, there is need to have all drive that has ever been in connection in the array for the data recovery process to happen.

After arranging the array, what follows is to do data recovery from the virtual machine of the user, which may be in different partitions. Remember that data can only be recovered after flattening delta files and fitting them into the VMDK disk images of the user, afterwards putting the images to the faulty hard drives. This is only possible after taking the reconstructed raid array and referencing them with the VMDK files. This process is basically done to highlight which parts of the virtual machines remained unread because of failure of hard disk in the array, or because of damage.

Then, it’s now the time to run data recovery software on the virtual machine. You can use HOMBRE or any other of your wish. This will definitely grant you back your data into the RAID array.

Mounting ESX Server Disks for data recovery files

Mounting ESX Server Disks for data recovery files

When you want to access files on ESX server disk and use recovery tools, you will have to connect the server disk, you then have to mount its vmdk files, disks and partitions. How do you do this exactly? This is a step by step tutorial of mounting ESX server disks for data recovery files.

Start

You have to ensure that you enable the SSH connectivity on the ESX server that you have. Manually configure the settings of the connection. You do this by entering password and login information, plus the server’s IP address. There are two simple methods you could use to access your files once the ESX server is connected.

First Method

Mounting hard drive containing ESX server

In this method you actually mount the hard drive, you will get access to both the partitioned and un-partitioned areas. You will be getting actual physical access as though the server is connected directly to your computer. This is a pretty easy method and is clearly cut out. You can therefore recover the files from the hard drive and in so doing recover the files of the ESX server.

Second Method

Mounting a vmdk disk

You need to select the folder containing the virtual machine. Once you open the folder you need to select and mount a vmdk file. You could use a VMFS Recovery to mount it and use it to restore the files in the ESX server.

Third Method

This is a method that combines both the first and second method. Its advantage is the fact that you could mount any file you want on the ESX server. You need to open vmfs folder then click on volumes and search for datastore. You will be able to find the hard drives in a folder dev then click on disks. Once you select the drive image or file to mount, just click mount. You will add to the main window a newly mounted disk.

Conclusion

You need to ensure you have a backup for your ESX server in case of any malfunctions or loss of data. It is true that you could recover the data but it is a little bit expensive and there is no guarantee. The above methods are quite simple and you could do in depth research to really understand them. They will help you recover your data in case of any problems with your ESX server. Data recovery is not always a 100% guarantee, sometimes you could loss critical information and not be able to retrieve it. You should have at least have a backup for your important information, and if you can afford it, why not have several.