data recovery 1.2 only supports 2 destinations at once

Similar Questions

• Data Recovery Advisor does not work

  In our environment of RAC DB 12 c Data Recovery Advisor does not work? Why?

  The Data Recovery Advisor is only supported by ORACLE DB Single Instance!

  https://docs.Oracle.com/CD/E60665_01/db121/BRADV/rcmrepai.htm#BRADV246

• Attached data recovery problem size Raw LUN

  
  We have a problem with our unit of recovery to Date.

  We have a matrix of about 12 TB discs intended to save our VMs.

  So, I try to join VM recovery given as a raw LUN.

  I saw 10.9 TB plug in recovery. try to format... it seemed to me that it works.
  But when I ride it, it was presented as a 2 TB drive.

  Umount - 10.9 Tb
  Mont - 2 TB

  The next step... I have connected to the computer of data recovery (I mean it's just a CentOS behind). And try to make a hand partion using parted and mkfs.

  parted worked well (with TPG as the label).
  So I launched
  mkfs.ext3/dev/sdb1

  It took a lot of time, went up to
  "Writing Superblocks and filesystem accounting information.
  and it seems that it crashes.

  mkfs still present in the process, but it seems that it do nothing.

  It's probably a problem with the ext3 file system.
  But
  (a) it seems I might have an ext3 file system larger than 2 TB.
  (b) ext4 is not available on CentOS of data recovery... so what could I do?

  So... maybe someone has a tip for this problem?

  Thank you very much.

  P.S.: Just for the record, we have 3 ESXi5 host with vCenter 5.

  I'm not 100% sure why you see the wrong size RDM, but make sure you read the Administrators Guide.

  of http://pubs.vmware.com/vsphere-50/topic/com.vmware.ICbase/PDF/vmware-data-recovery-administrators-guide-20.pdf

  Data recovery is designed to support deduplication stores that are up to one terabyte of size and each appliance backup is limited to the use of two stores of deduplication. Data recovery imposes no limits on the size of the stores of deduplication, but if the size of a store exceeds a terabyte, performance may be affected. While data recovery imposes no limits on deduplication store size, other factors limit the actions of deduplication. So, the stores of deduplication are limited to:
  -500 GB on CIFS network shares
  -1 to VMDK and RDM

  André

• What type of destination data recovery?

  Hello

  What types of destinations are supported for new data recovery backups in vSphere 4? Is it only save existing data warehouse? Or you can save to NFS or SMB shares?

  Thank you

  Pascale

  Here is a link to a FAQ which answers these questions actually:

  http://www.VMware.com/files/PDF/VMware_Data_Recovery_FAQ_4.21.09.PDF

  Duncan

  VMware communities user moderator

  -

• Types of backup destination VMware Data Recovery

  IM test VMware Data Recovery and reading it can save to different destinations. Here's a sentence from of the Administrator's guide.

  You can store backups on network, VMDK shares, or RDM.

  The only option I see is the network share and make a folder called VMwareDataRecovery with other files and folders in it. If I backup more 1 VM to this nextwork share looks like it mixes everything together. I was under the impression that you can save in a file single vdmk.

  The only options I have under VMware Data Recovery for Destinations are Refresh, add a share of Nework, Format, Mount, Unmount, Extend and integrity check

  Remove you it from the virtual computer by means of the settings?  If so, have you selected the option to remove the virtual machine and remove the disc?  If you have them removed from the virtual computer through the settings, then you can delete browser data store.  It will come to your space.  Also, see IO errors is because you took the disk to the virtual machine without removing firstly by vDR Console's Configuration.

  That said, I would do the following:

  1. Ensure that the VM vDR does not any VMDK attached other than the VMDK root which is 5 GB in size.

  2. Open the browser of data store and make sure that the former VMDK you created have disappeared.  If not, select them and click on delete.

  3. Go to the Configuration Console for vDR and look at Destinations of backup to make sure there is nothing there.  There should be nothing in the list of destinations, if there are, remove them.

  4. After checking the above, create a new size 15GB VMDK.

  5. Restart your virtual machine of vDR

  6. Go into the Console to Setup vDR and select the disk that you created in the backup Destinations, do a right click and select format.

  7. The size should report something similar to what my screenshot of previous shows.

  I would like to know if that works for you!

  If you have found this helpful at all prices please points using the correct or useful!  Thank you!

• Error starting data recovery - "your CPU does not support long mode.

  Hello

  When I turn on the VM data recovery, and after that he begins the boot process, it displays a message "your CPU does not support long mode. Use a 32-bit distribution"

  Data recovery is installed on an ESX 4.0 update1 then the ESX is installed on a VMware Workstation 6.5.2 as a virtual machine in my home test environment.

  My processor is a 64 bit CPU (AMD Phenom 9950 Quad-Core).

  I wonder if this message is because the ESX is running in a virtual machine on the workstation may be that it not only Duke that the processor is a 64-bit?

  Someone at - he of the idea?

  Thank you

  Marcos

  You can run the 64-bit if clients your ESX is a virtual machine. VMware Workstation does not pass through the VT extensions that are necessary for the performance of a 64-bit as VDR host.

• Data recovery device storage supported

  Where can I find a list of storage devices supported by the device of data recovery?

  How can I detect if a given storage device can be used by the device of data recovery?

  Concerning

  Marius

  All storage devices located in VMware HCL + network CIFS shares are supported as target

  pelase see http://www.vmware.com/files/pdf/VMware_Data_Recovery_FAQ_4.21.09.pdf

• your processor does not support long mode. use a 32-bit Vmware Data Recovery distribution

  Hi all

  When I tried to start VM in Vmware Data recovery, her gives me error as

  "your cpu does not support long mode. use a 32-bit distribution"

  I tried searching for the 32-bit version of data recovery, but not able to find out.

  Help, please

  Kind regards

  Selim Desai

  You can add a 64-bit host to a virtualized session of ESXi. The ability of VT is not transmitted to a guest operating system.

• VMWARE data recovery deduplicate Disk Cleanup

  I'm testing data 1.2.1 recovery before you install it in production. Everything looks ok, except that I could not find how to delete a backup job data from the backup store itself to make space if I do not need this working at all. Thanks in advance

  not that I know a lot of things about it, but the practice of cleaning up a data de-dup store can be difficult.

  as the data in a data de-dup store are really just a bit pattern that arose then make a backup of this data block is referenced at least a backup task, it can be referenced by multiple backup jobs in order to clean the store de-dup means understanding if the block is referenced by any other backup jobs or not If not so empty on the block and the restructuring/re-pre-order the disk of destination, would not be an easy task.

  You should keep in mind that the backup task is not a traditional backup, it's really a collection of blocks of data with different models that were found at least once, after which it's just a known entity that can be mentioned in the backup jobs later.

  the backup task has become so do the not too well more than a bunch of links to blocks known.  so when you delete a job or expiry date the only clean thing is the entity that has defined the work and blocks associated (and the directory Info? for file-level recovery).

  Since each DR unit supports 2 destination volumes I took bike destination volumes when it fills up, and it becomes so great that the consistency check takes almost all day, I create a new destination, move jobs and keep the old as archive until the jobs have expired , or are considered too old to be useful, then unmount the destination disk and get rid of (or move it to a location of storage just in case).

  I was originally of traditional thinking that remove old backup jobs should reduce the destination disk, but when it turns out there no, even when all the backup jobs have been deleted, then it starts to make me think about how it really works.

  There is a cleanup job casual that tracks that may be releasing part of the datablock storage but since it really does not report how many of the destination disk is actually used, other than the size of the backup report which is still way less than the physical size of the destination, it is not really so or the amount of free space that may exist in the destination disk.

  Wayne

• Satellite L850: Drive HARD Firmware problem prevent data recovery

  Am a little confused and need a simple explanation
  My HDD L850 died under warranty and was sent to the people of data recovery to recover the data before entering new drive under warranty.

  I am told that my hard drive has a fairly unique combination of firmware and the drive that prevents the recovery until they get this firmware. Now 6 weeks after it happened I stll wait.

  Someone in support could explain to me in simple terms, why this firmware is the problem cause and so far can only be obtained by your partner data recovery company?

  Hello

  I think that you will here get a correct answer, why the people of data recovery needs of these packages since it is a user forum.

  But to my knowledge all the 2.5 hard drives and SSD drive supports various firmware.
  These firmware tells the hardware how to interact with the operating system.

  It seems that people in data recovery needs these packages in order to get access to the HARD drive, and I presume, without the compatible firmware, it is not possible to recover the data.

• Data Recovery HP once recovery

  I moved my 'once' HP on a USB key and on an external HARD drive data recovery. Is there a way to make these bootable data again?

  Thank you

  Hi there @Brotocol,

  Thank you for joining the Forums HP's Support and welcome! It is a great place to ask questions, find solutions and get help from others in the community! I read your post on the Forums of HP Support. I wanted to join you and help! I understand that you had the recovery of data on a USB key, put it on another hard drive and you want to know if you can take on this hard drive again.

  Due to software licenses, only a set of recovery disks can be created. This means that you could have done a copy USB or CD/DVD of it only. There is no way for you to get off the other hard drive to use it now.

  You will need toget a USB HP recovery disc or HP recovery disks. Please follow the provided document and follow the steps to order recovery media if you need.

  Please let me know if I answered your question by clicking the "Thumbs up" if the troubleshooting in this post steps solves the problem for you please click on the button "Accept as Solution" . This will allow to the others is that present the same problem a solution also. If you need assistance, please let me know to publish again. Could you please include your model number (How can I find my model number or product number?) also?

  Thank you!

  Have a great day!

• Data Recovery Advisor work RAC?

  Grid infrastructure: 11.2.0.4

  DB version: 11.2.0.4

  OS: Oracle Linux 6.5

  Data recovery Advisor will work with the CCR in 11.2.0.4? How does 12.1?

  http://docs.Oracle.com/CD/E11882_01/backup.112/e10643/rcmsynta003.htm#RCMRF166

  In the current version, Data Recovery Advisor only supports specific databases. Oracle Real Application Clusters (Oracle RAC) databases are not supported.

  https://docs.Oracle.com/database/121/RCMRF/rcmsynta003.htm#RCMRF166

  In the current version, Data Recovery Advisor only supports specific databases. Oracle Real Application Clusters (Oracle RAC) databases are not supported.

  
  

  So the answer is no.

• Seagate Barracuda 7200.11 failed drive and data recovery

  I own a HP Pavilion Media Center m8350f PC witch came with a 750 GB Seagate Barracuda 7200.11 internal hard drive model #ST3750630AS.  After about 3 months, the system didn't recognize the hard drive.  Having initially contacted HP tech support in December, they told me to send the PC to them for hard drive replacement.  They were unable to diagnose anything other that the drive had failed.  Yet I have to send it, because I know that the drive works, it's just that it is not recognized by my system.  I need a car access.  No replacement drive.

  I discovered recently, Seagate press release that they shipped a defective lot of readers with firmware.  In their initial press release, they stated:

  "We believe that the vast majority of customers are no disruption related to this issue, and that concerned readers can be used as is. But as part of our commitment to the satisfaction of the customer, Seagate offers a free upgrade of the firmware to respond proactively products likely to be affected. This new update fixes compatibility problems that have occurred with the download of the firmware provided on our Web site on 16 January. We regret any inconvenience that firmware problems have caused to our customers... " In the unlikely case where your drive is affected and you can not access your data, the data still resides on the disk and there is no data loss associated with this issue."

  Now that the real problem has been identified, what alternative support is available from HP at this topic?  HP will push their provider, Seagate, to extend this offer to the customers of HP?  Can HP unlock these discs?  The average consumer cannot ' of the Nations United-brick ' these readers with the new firmware and I guess, it's relatively easy for Seagate (i365) data recovery company to manage.

  Bottom line: based on my understanding of the problem, readers have not suffered loss of data, they are stuck in a 'busy' State and must be unlocked.  This is a critical point, because I believe that no one really cares to know if they get a new drive.  They want to only be able to access their data and awaken the drive is all it takes.

  My previous post was the original incorrect announcement of Seagate Barracuda chess.  The message I pasted was monitoring them upward.  The correct statement is below:

  "We offer free data recovery, because the drive information is not deleted. He's just made inaccessible by this suspect firmware,"spokesman of Seagate Michael Hall.

  Seagate said it has reissued the firmware originally proposed last Friday, saying: he has isolated the bug in the firmware in a "limited number of Barracuda 7200.11 hard drives with the SATA drives based on this platform of products, manufactured until December 2008. "In some circumstances, data on hard drives can become inaccessible to the user when the host system is powered on," Hall said.

  "Although we believe that the vast majority of customers are no disruption related to this issue, as part of our commitment to the satisfaction of the customer, Seagate offers a free upgrade of the firmware to respond proactively products likely to be affected", he added.

• Full VM data recovery or just snapshots?

  Hi people,

  I'm really in doubt on this subject.

  I started a job to backup with approximately 20 virtual machines, and after a while, when it finished I checked the ocupied backup size. Then I surprised because the size of the entire backup was only 64GB, and the storage space total occupied by all virtual machines is about 1 TB.

  
  So, how can I do a full backup vm?

  Example/Question: If I lost the entire data store where my vm running (one really disaster), I can restore my vm with data recovery (with backups stored in the other data store)?

  Kind regards

  sm4rtins.

  I don't know what help I can be, because my main experience with VDR is full of episodes of frustration. It could have been a reasonable product, but it seems to be deliberately crippled, and although version 2 is much more stable than the 1.x version (we meet only a few points of restore damaged about once a month or more, and not twice a week), it's always make us nervous.

  The only thing I would say is that we use fast SAN storage for destinations. VDR doesn't seem to be sensitive to the speed of disk I/O, and my assumption is that we get a restore point damaged when the disk i/o on the SAN is high (the SAN is shared with about 40 virtual machines and several physical servers that use for cluster storage databases). We do not have the data to back up this hypothesis (still trying to get a handle on how I'd get I/O stats to prove), but I don't see what it might be (other than the product being simply bugged, which might be the case).

  Could you move your store of destination from NFS to a fast SAN, just to see if the error rate?

• How many vmware data recovery machines possible?

  Hello

  is it possible to use more than one computer of vmware data recovery? I need because the vmdr is limited to two destinations and I need one more backup on a USB key.

  Greetings

  Gregor

  According to VMware Data Recovery requirements

  Ten aircraft of backup data recovery for each instance of vCenter Server

  However. I don't think that storage device USB is supported as a store of deduplication.

  André