VMFS cloning

Similar Questions

• Backup errors with backup of thin provisioned disks on ESXi 5.1

  Hello

  I try to set up a backup solution for two servers in ESXi 5.1. (free version).

  I have installed and configured the ghettoVCB successfully and everything seems to be ok.

  However, when I start to create a backup, the process would end with an error :-(

  It didn't matter if the server is enabled or disabled, I get the same result.

  All data warehouses are local, 2 x free WD500GB with plenty of space.

  There is no snapshot, anything that could (in my eyes) prevent a good backup.

  The server works perfectly, when turned on.

  I'd appreciate any useful comment. Thanks in advance! The log is attached.

  / vmfs/volumes/519fceb8-3d39150e-2D0F-001999eeb339/ghettoVCB-Master #./ghettoVCB.sh f vms_to_backup
  Recording output to ' / tmp/ghettoVCB-2013-05-25_20-56-28-324192.log '...
  2013-05-25 20:56:29 - info: = ghettoVCB NEWSPAPER BEGIN =.

  2013-05-25 20:56:29 - info: CONFIG - VERSION = 2013_01_11_0
  2013-05-25 20:56:29 - info: CONFIG - GHETTOVCB_PID = 324192
  2013-05-25 20:56:29 - info: CONFIG - VM_BACKUP_VOLUME/vmfs/volumes/backup/ghettoBackups =
  2013-05-25 20:56:29 - info: CONFIG - VM_BACKUP_ROTATION_COUNT = 3
  2013-05-25 20:56:29 - info: CONFIG - VM_BACKUP_DIR_NAMING_CONVENTION = 2013-05-25_20-56-28
  2013-05-25 20:56:29 - info: CONFIG - DISK_BACKUP_FORMAT = thin
  2013-05-25 20:56:29 - info: CONFIG - POWER_VM_DOWN_BEFORE_BACKUP = 0
  2013-05-25 20:56:29 - info: CONFIG - ENABLE_HARD_POWER_OFF = 0
  2013-05-25 20:56:29 - info: CONFIG - ITER_TO_WAIT_SHUTDOWN = 3
  2013-05-25 20:56:29 - info: CONFIG - POWER_DOWN_TIMEOUT = 5
  2013-05-25 20:56:29 - info: CONFIG - SNAPSHOT_TIMEOUT = 15
  2013-05-25 20:56:29 - info: CONFIG - LOG_LEVEL = info
  2013-05-25 20:56:29 - info: CONFIG - BACKUP_LOG_OUTPUT = /tmp/ghettoVCB-2013-05-25_20-56-28-324192.log
  2013-05-25 20:56:29 - info: CONFIG - ENABLE_COMPRESSION = 0
  2013-05-25 20:56:29 - info: CONFIG - VM_SNAPSHOT_MEMORY = 0
  2013-05-25 20:56:29 - info: CONFIG - VM_SNAPSHOT_QUIESCE = 0
  2013-05-25 20:56:29 - info: CONFIG - ALLOW_VMS_WITH_SNAPSHOTS_TO_BE_BACKEDUP = 0
  2013-05-25 20:56:29 - info: CONFIG - VMDK_FILES_TO_BACKUP = all
  2013-05-25 20:56:29 - info: CONFIG - VM_SHUTDOWN_ORDER =
  2013-05-25 20:56:29 - info: CONFIG - VM_STARTUP_ORDER =
  2013-05-25 20:56:29 - info: CONFIG - EMAIL_LOG = 0
  2013-05-25 20:56:29 - info:
  2013-05-25 20:56:35 - info: start the backup for server W2003
  Destination disk format: thin provisioned VMFS
  Cloning disk ' / vmfs/volumes/519fceb8-3d39150e-2d0f-001999eeb339/w2003-server (2) 2/w2003 Server _1.vmdk'...
  Clone: 36% of fact.
  2013-05-25 20:59:34 - info: ERROR: error in the backup of "/ vmfs/volumes/519fceb8-3d39150e-2d0f-001999eeb339/w2003-server (2) 2/w2003 Server _1.vmdk ' to W2003 Server
  Destination disk format: thin provisioned VMFS
  Cloning disk ' / vmfs/volumes/WD500GB-1/W2003-Doma¤ne/w2003-server (2) hard '...
  Clone: 66% of fact.
  2013-05-25 21:08:59 - info: ERROR: error in the backup of "/ vmfs/volumes/WD500GB-1/W2003-Doma¤ne/w2003-server (2) hard" to W2003 Server
  2013-05-25 21:08:59 - Info: backup time: 12,40 Minutes
  2013-05-25 21:08:59 - info: ERROR: impossible to W2003 server from backup because of the error in VMDK backup!

  2013-05-25 21:09 - info: # final status: ERROR: No. VMs saved! ######

  2013-05-25 21:09 - info: = ghettoVCB JOURNAL END =.

  / vmfs/volumes/519fceb8-3d39150e-2D0F-001999eeb339/ghettoVCB-Master #.

  > However, when I start to create a backup, the process would end with an error :-(

  This is not correct.  Depending on your position, you've got to 66%, until he ended with an error.

  I have the same problem. In my case, I make a virtual disk full and mount it with Server 2003 for project a NFS volume.  I use GhettoVCB, as you do.  It uses the standard vkmfstools in the script to make the clone/backup.  I have proven that the problem also occurs when you use the command line vkmfstools.  GhettoVCB has the bad habit of you cache the error code.  The error code is he ran out of disk space, which we both did not happen.  Once the problem occurs, the only way I could fix is to delete the virtual disk and start over, however, the problem will come back.  The problem didn't surface until what I moved to ESXi 4.0 5.1 on the servers.  Through this process, the hardware off the VMS version did not change, nor dare, because I may need to take 5.1 and back to 4.x.

• Incorrect error message

  Hello

  I have a virtual machine with a disc indepdenent, I did for this virtual computer to a configuration only file to non-independent backup discs. The file is loaded, but then the backup process the script says ' final status: ERROR: no stored virtual machines. " That s not correct, because the VMDK I declared in the configuration file has been saved.

  Look at the output:

  2011-04-13 07:49:32 - info: = ghettoVCB NEWSPAPER BEGIN =.

  2011-04-13 07:49:32 - info: CONFIG - CONFIGURATION FILE with the HELP of = / vmfs/volumes/datastore1/backup_config/serverxyz
  2011-04-13 07:49:32 - info: CONFIG - VERSION = 2011_03_14_1
  2011-04-13 07:49:32 - info: CONFIG - GHETTOVCB_PID = 109181
  2011-04-13 07:49:32 - info: CONFIG - VM_BACKUP_VOLUME = / vmfs/volumes/Backup
  2011-04-13 07:49:32 - info: CONFIG - VM_BACKUP_ROTATION_COUNT = 1
  2011-04-13 07:49:32 - info: CONFIG - VM_BACKUP_DIR_NAMING_CONVENTION = 2011-04-13_07-49-32
  2011-04-13 07:49:32 - info: CONFIG - DISK_BACKUP_FORMAT = zeroedthick
  2011-04-13 07:49:32 - info: CONFIG - ADAPTER_FORMAT = free
  2011-04-13 07:49:32 - info: CONFIG - POWER_VM_DOWN_BEFORE_BACKUP = 0
  2011-04-13 07:49:32 - info: CONFIG - ENABLE_HARD_POWER_OFF = 0
  2011-04-13 07:49:32 - info: CONFIG - ITER_TO_WAIT_SHUTDOWN = 4
  2011-04-13 07:49:32 - info: CONFIG - POWER_DOWN_TIMEOUT = 5
  2011-04-13 07:49:32 - info: CONFIG - SNAPSHOT_TIMEOUT = 15
  2011-04-13 07:49:32 - info: CONFIG - LOG_LEVEL = info
  2011-04-13 07:49:32 - info: CONFIG - BACKUP_LOG_OUTPUT = /vmfs/volumes/Backup/Backup_Log_ESX2.log
  2011-04-13 07:49:32 - info: CONFIG - VM_SNAPSHOT_MEMORY = 0
  2011-04-13 07:49:32 - info: CONFIG - VM_SNAPSHOT_QUIESCE = 0
  2011-04-13 07:49:32 - info: CONFIG - VMDK_FILES_TO_BACKUP = serverxyz.vmdk
  2011-04-13 07:49:32 - info: CONFIG - EMAIL_LOG = 1
  2011-04-13 07:49:32 - info: CONFIG - EMAIL_DEBUG = 0
  2011-04-13 07:49:32 - info: CONFIG - EMAIL_SERVER = 192.168.101.8
  2011-04-13 07:49:32 - info: CONFIG - EMAIL_SERVER_PORT = 25
  2011-04-13 07:49:32 - info: CONFIG - EMAIL_FROM = [email protected]
  2011-04-13 07:49:32 - info: CONFIG - EMAIL_TO = [email protected]
  2011-04-13 07:49:32 - info:
  Cat: can't open ' / vmfs/volumes/datastore1/serverxyz//vmfs/volumes/4da47275-895fcfb7-82ed-001ec9eb39c2/serverxyz/Partition_T.vmdk ': no such file or directory
  2011-04-13 07:49:34 - info: start backup for serverxyz
  2011-04-13 07:49:34 - info: creation of snapshot 'ghettoVCB-snapshot-2011-04-13' for serverxyz
  Destination disk format: zeroedthick VMFS
  Cloning disk ' / vmfs/volumes/datastore1/serverxyz/serverxyz.vmdk'...
  Clone: 99% in fact.
  2011-04-13 07:56:44 - info: Instant withdrawal of serverxyz...
  2011-04-13 07:56:44 - Info: backup duration: 7.17 Minutes
  2011-04-13 07:56:44 - info: WARN: serverxyz has some independent VMDK which cannot be saved!

  2011-04-13 07:56:44 - info: # final status: ERROR: No. VMs saved! ######

  2011-04-13 07:56:44 - info: = ghettoVCB JOURNAL END =.

  Why the script tries to open the independent disk?

  My config file is:

  VM_BACKUP_VOLUME = / vmfs/volumes/Backup
  DISK_BACKUP_FORMAT = zeroedthick
  VM_BACKUP_ROTATION_COUNT = 1
  POWER_VM_DOWN_BEFORE_BACKUP = 0
  ENABLE_HARD_POWER_OFF = 0
  ITER_TO_WAIT_SHUTDOWN = 4
  POWER_DOWN_TIMEOUT = 5
  SNAPSHOT_TIMEOUT = 15
  ENABLE_COMPRESSION = 0
  ADAPTER_FORMAT = free
  VM_SNAPSHOT_MEMORY = 0
  VM_SNAPSHOT_QUIESCE = 0
  VMDK_FILES_TO_BACKUP = "serverxyz.vmdk"

  Will he do a dryrun I get "final status: OK, only a dryrun.» ... but I would also have a positive message if I do the actual backup! Is there a way to do this?

  Best regards

  Tom

  Hi Tom,

  Can you give the version found on github a try - https://github.com/lamw/ghettoVCB I believe that this may have to do with a bug with multi-VMDK (s).

  Let me know if you're still having problems

• Questions and answers backing up/cloning a VM NFS

  Situation :

  1. I use vsphere 5.1 with thin VM.
  2. I will only use virtual machines for backup targets.
  3. I am currently using Windows 2003 Server VM, projecting an NFS volume, to back up to.  A big advantage of this is NTFS compression.  The problem is from 2003 and 2008 cannot manage virtual machines without running frequently in file size problems.  Example: I have a 1 TB NTFS compressed volume I export as a NFS volume.  It has 667 GB of free space.  If I clone a virtual machine that has a declared 80 GB size and a slim waist 42 GB, is the command and the result:
  

  # vmkfstools-i d inh.vmdk thin /vmfs/volumes/nas-2/backups/server1/inh/inh-2014-03-19_05-22-41/inh.vmdk

  Destination disk format: thin provisioned VMFS

  Cloning disk "inh.vmdk"...

  Clone: 78% of fact. Impossible to clone the drive: there is not enough space on the file system for the selected operation (13)
  A few days later, after a few copy and delete could start working again, or I can run chkdsk on it, and he will back up again.  You can run the chkdsk command 10 times in a row and getting errors every time.  Microsoft knows the problem, did not fix, it has not been set, and if they have not fixed now, I doubt they will ever be, because those aren't their current products.  At the time virtualization and files of several gigabytes were not a market reality.
  4. I read that ESXi is default for thin then copy to NFS, and I specify in vmkfstools when you are copying anyway.
  5. to correct my backup file of the size matters, I thought I'd use a? NIX to replace 2003 as the VM NFS for backup.  It seems? NIX is no good compression options.  ZFS looks like its as good as it gets, and from what I've read, it's great to manage a large number of data and records, but slow and a resource hog for this type of work.
  6. I decided just thin backup would be good enough, and I could go out without compression.  However, when I tested the backups on the NFS volumes, they used their full size declared.  Here are the results of these measures.

  As backed up to a volume of Windows Server 2003 NFS
  # ls - l fstop - flat hard
  -rw - 1 root 42949672 85899345920 Mar 14 06:53 fstop - flat hard

  # stat fstop - flat hard
  File: fstop - flat hard
  Size: 85899345920 blocks: block IO 167772160: 131072 regular file
  
  Calculation:
  167772160 * 512 = 85,899,345,920
  85,899,345,920/1024/1024/1024 = 80 GB (full size, not thin)

  
  Same virtual machine running on VMFS Volume:
  # ls-l fstop - flat hard
  -rw - 1 root root 85899345920 15 March 23:11 fstop - flat hard
  
  # stat fstop - flat hard
  File: fstop - flat hard
  Size: 85899345920 blocks: 124723200 IO block: 131072 regular file
  
  Calculation:
  124723200 * 512 = 63,858,278,400
  63,858,278,400/1024/1024/1024 = 59.47265625 (thin) GB

  
  Another VM saved on a compressed volume of NFS for Windows Server 2003
  -inh - flat hard has a declared 80 GB size
  -As thin on VMFS, it has a size of 38,72 GB
  -Also supported up to a window thin hard, with NTFS compression, projected as an NFS share is 19.26 GB
  
  Analysis/thoughts:
  1. the VMware docs state that, by default, VMDK made on an NFS volume are slim.  In fact, when I backup my thin VMs to an NFS share and restore to a file system vmfs, the hard just thin back, so there is no doubt that it is stored as thin.

  
  2. even if a hard backed up on an NFS share is thin, unlike under vmfs, a thin hard residing on a NFS volume consumes all of the blocks required by its size declared.  FOR EXAMPLE we have a VM said thin with a size of 80 GB, which uses 59,47 Go on a vmfs volume, but when saved on a store NFS, there are 80 GB of disk space each time.  On a 250 GB NFS volume, so there room for not more than 3 backups.
  
  3. the only way to effectively store backups on a volume of NFS is whether this volume supports compression.  The only solid choices in this area seem to be NTFS and ZFS. ZFS is to consume a lot of resources because of all the other things, it was designed to do.  If I was going to ZFS, I would probably just add to an existing FreeBSD VM. I don't need all the stuff done FreeNAS.  Windows through 2008 have problems with large files.  I have not tried Windows 2012.
  
  Question:
  At this point, I think to try a Windows VM to 2012 to take the place of VM Windows 2003 to see if 2012 has beaten the problems of file size of volume.  In 2012, virtualization was hot, and so I guess that he could not have the problem with large files.  Everyone using one? NIX VM for this assignment which is effective, reliable and supports compression?
  
  Thank you!
  
  

  Forward:
  I installed a Server Microsoft 2012 64 VM today to serve as the target of compressed backup NFS to determine if they have fixed the problem with large files which is rampant in the 2 K - 2008 R2 and learned by doing more tests and more.

  2012 compressed Server NFS volume tests:

  Backup on compressed NTFS volume projected as NFS
  * The VM has here a test size declared 80 GB.  The NFS VHD said to 150 GB

  -vmkfstools-i d dstop.vmdk thin /vmfs/volumes/nas-4/backups/server1/dstop/1/dstop.vmdk

  -When you have finished, stat reports he uses 40.23 GB

  -VCLI engages with the Go 40,23 and shows that I have 109,53 GB remaining in free space

  -Windows shows Go 40.2 used on the disk and 109 GB free

  Second backup
  -Size of the vhd is 80 GB, so there should be more than enough space to make a second backup if vmkfstools considers that the first backup is 40.2 GB and not his declared 80 GB size.

  -vmkfstools-i d dstop.vmdk thin /vmfs/volumes/nas-4/backups/server1/dstop/2/dstop.vmdk

  -When you have finished, stat says it requires 40.23 GB

  -VCLI agrees with the 80.66 and shows that I have 69,21 GB remaining in free space

  -Windows shows also 80.4 GB used on the disk and 69.2 GB free

  -Because the backup is complete, it turned vmkfstools saw all the remaining space on the compressed volume.  If such were not the case, there is not room for the second copy as we would have been short 10 GB.  (80 GB * 2 = 160 GB on a 150 GB NFS volume)

  -Doing a stat on virtual hard drive storage shows its size to be 121,93 GB, not the expected 40,23 GB X 2 = 80.46 GB.  Which indicates that, during the thin vhd for volume cloning compressed NFS, the VHD used initially full value declared of the 80 GB (40.23 + 80 GB + ~1.5GB) vhd.

  Third backup

  -From the second backup, we learned that cloning for the volume compressed all of the 80 GB declared value plus a few initially used NFS.  After the second copy, we have only 69GB of free space, the third backup to fail if our hypothesis is that a compressed volume Windows initially requires at least the size of the free space to successfully carry out the correct copy.  The 69GB remaining should be too small for the initial 80 GB size required.

  -vmkfstools-i d dstop.vmdk thin /vmfs/volumes/nas-4/backups/server1/dstop/3/dstop.vmdk

  -Command instantly failed with the following error message:

  «Impossible to clone the drive: there is not enough space on the file system for the selected operation (13).»

  Tests of corruption:

  GUI test
  -Windows scanned the disc and found no errors

  -Then, I did a stat on the VHD and seen that it has not changed because of the analysis.

  CHKDSK command prompt:

  -Then, I ran v: chkdsk /R from the command prompt and restart.  It took a long time to complete because it checks the sectors and trying to recover and re-map information.  I thought that it would increase the hard.  He did not.  This seems to indicate that vSphere extend and access the unused space of the disc even for chkdsk/r.

  Recover the thin space experience:

  -Deleted the first backup and subsequently checked with stat.  The size of the vhd has not changed of the original 121,93 Go as planned.

  -Downloaded and run sdelete on the volume. (Documentation, it is said, run it with? nix dd if = / dev/zero of = / [PATH] / zero bs = 4096 & rm f / [PATH] / zeros (I don't understand nor have I tried this command to see if it is correct or even work.))

  -Check the VHD with stat, and as expected, it now has the declared size of 150 GB

  -Ran vmkfstools - punchzero nas - 2_1.vmdk who went much faster than sdelete

  -Run stats on it.  I expect to be the same size, and I have to do a-i thin d vmkfstools to reach the smaller hard, but it was only 42 GB down 150 GB.  I got all but 2 GB back.  Curiously, the free space is exactly the same as before, 109 GB.

  -Decided to try to start the virtual machine, without cloning the hard to see if it would work.  It worked perfectly.  These two steps are the steps only recover space on a thin hard.

  -When he was in disbelief that it was that easy, I decided to do the-i thin d vmkfstools to see what would happen. It worked well, and it is still thin and still the same size.

  Analysis:
  -When you clone one - thin vhd to an NFS volume, it will use the declared size in disk space, not the - thin space as seen with vmfs volumes.
  -When you clone a volume compressed Windows, it uses initially declared the virtual hard disk size in space before it is compressed.
  -2012 server do not have problems with large files than 2008 R2 and earlier.  I do not buy, but the price is mitigated when you consider that you get two licenses VM for that price.
  -Recovering a previously too inflated thin virtual hard drive space is a simple two-step process.  (At least with Windows that is)

  Closed:

  The issue of corruption with versions of Windows server before 2012 and the mystery of why backups were not complete when there was apparently a lot of disk space, has been something that has plagued me for a long time.  Person here and other forums have been able to help.  I hope that my tests have clarified the issues, so that others can enjoy.

• Error VMFS, ESX 3.5 update to vSphere 4.0

  After an upgrade to ESX Server 4.0, two VMFS volumes were is most recognized as valid data store. ESX Server 3.5 has not yet updated, the VMFS appears but only as virtual machines read-only, can not be cloned, disconnected or migrated because the VMFS does not allow this operation.

  How can I find this data store for normal operation?

  Thank you

  Hello

  Moved to vSphere upgrade and install Forum.

  After an upgrade to ESX Server 4.0, two VMFS volumes were is most recognized as valid data store. ESX Server 3.5 has not yet updated, the VMFS appears but only as virtual machines read-only, can not be cloned, disconnected or migrated because the VMFS does not allow this operation.

  Looks like the VMFS 2 for ESX v2.x not 3.x 2.x VMFS are R/O in ESX v3.

  The best thing to do is to unload your virtual machines to the VMFS using ESX v3.5 and then recreate the VMFS on ESX v4, then transfers her back the VMs. You can also recreate on v3.x, but I'm not sure it's necessary.

  Best regards
  Edward L. Haletky VMware communities user moderator, VMware vExpert 2009, 2010

  Now available: url = http://www.astroarch.com/wiki/index.php/VMware_Virtual_Infrastructure_Security'VMware vSphere (TM) and Virtual Infrastructure Security' [/ URL]

  Also available url = http://www.astroarch.com/wiki/index.php/VMWare_ESX_Server_in_the_Enterprise"VMWare ESX Server in the enterprise" [url]

  Blogs: url = http://www.virtualizationpractice.comvirtualization practice [/ URL] | URL = http://www.astroarch.com/blog Blue Gears [url] | URL = http://itknowledgeexchange.techtarget.com/virtualization-pro/ TechTarget [url] | URL = http://www.networkworld.com/community/haletky Global network [url]

  Podcast: url = http://www.astroarch.com/wiki/index.php/Virtualization_Security_Round_Table_Podcastvirtualization security Table round Podcast [url] | Twitter: url = http://www.twitter.com/TexiwillTexiwll [/ URL]

• People are leaning more towards VMFS or RDM these days? What YOU're running and why?

  Hello world

  I know there is a wealth of information on the subject and the standard response is to use both... whether you want array or snapshot level vm, etc..

  However, my environment is staged, I did some torture tests, tests of backup and restore. I'm almost ready to go wild p2v, but I'm still on the fence about the places where use RDM vs. VMFS. I'm running a cx500 and I was bitten by a flare code bug earlier that caused corruption unnoticed in my clone BCV we were using for backups - what was going on FOR the MONTH up to what we found out after we met weird with a cloned Oracle instance anomalies. From there I never did trust snaps or clones on the side of the table. On the other hand, I like the features of sleep to a vmdk.

  Looks like there are great benefits to go especially with VDR VMFS and similar tools push up. BUT... There is always this weird feeling relying on these vmdk files. Just curious to know what percentage of vs. VMFS, RDM people are running and why you personally and absolutely chosen RDM vs. vmfs.

  Thanks in advance.

  As we are ISCSI worldwide 3.5 we directly glued to the MSISCSI on virtual methods, it was for reasons of performance 3.5 with no MPIO

  4.0 worldwide we are leaning toward VMFS functionality set and the behavior of an interruption of SAN are advantageous for us and now with MPIO, we see large absolute performance of VMFS

  Jered Rassier

  * Professional technical EqualLogic certified

  * Dell Enterprise foundations certified professional v.2

  ##If you found my post answered your question or helpful please mark it as such.

• Question of cloning for SSD upgrade on 12 Macbook Pro

  Previously, I did an upgrade to SSD on my Macbook Air to 2012 according to the instructions of JetDrive transcend. Basically connection via USB 3 and using Mac OS X to clear (and format) disc utilities new SSD, then restore again SSD and then remove the original 128 GB SSD and insert the new 480 GB SSD.  For about a month and so far without problem.

  Now I'm trying to 2012 Macbook upgrade my Pro partner (on 10.11.6).  I got a Crucial SSD MX300 to replace his HARD drive.  Crucial comes with (or recommend) Acronis software.  And a lot of the messages of the forum recommend Carbon Copy Clone.

  My question is if I can use the same method for the cloning of the HD as my Macbook Air (just restore disk of Mac OS X utilities)?  This time, I'm upgrading HARD drive and I don't know if something is different.  At the same time, if I got lucky the first time, I don't not ruin Macbook Pro my spouse this time.

  Thank you.

  Yes, you can use disk utility to clone your MBP wives, but unlike CCC, it will not clone the recovery and Partition.

• Cloning of SSD HD via active with Filevault disk utility

  Hi all

  I want to improve my HD to SSD.

  I intend on using disk utility for recovery mode to clone my HD to a Virgin SSD I bought.

  I must, however, Filevault enabled on my HD.

  It will be a problem when it comes to cloning the drive?

  Thank you

  Adam

  No, it shouldn't be a problem. It may be necessary first turn on FileVault and encrypt the SSD. But if there is no problem just turn off FileVault on the HARD drive.

• Is cloning with disk utility (10.11), reliable? Can you do trust sound check?

  I cloned a 4 to with bad sectors (according to DriveDx) and a new 4 to. The drive is successfully verified. Can I trust the contents of the new drive? If the player has verified that means that bad sectors were readable, or just that copied by the damaged disk data utility "with success."

  Another thing, when I started the computer, Time Machine does not recognize that the new disc is a clone of the previous and delete all backups of the previous player (nice one Time Machine)... so now, only two copies of my entire life are these two 4TBs...

  Check it to learn how to move your Time Machine backup on another drive:

  Time Machine: How to transfer backups from a current backup disk to a new backup drive - Apple Support

• Is it safe to delete the original score after successful cloning?

  I have a Mac mini mid2010. I swapped his optical drive to an SSD. Then I cloned the operating system partition and everything works perfectly. My question is whether it is safe to delete the original "Macintosh HD" that I cloned, or if there is a way to keep its files being accessible if I don't get them mixed up.

  Thank you

  Delete the old folder on the internal drive home page only. I should leave everything alone in case you need to boot from this drive. However, in general, it is safe to reformat the hard drive. But it depends on what you plan to do with it.

• After the backup hard drive cloning ARD launch

  OS: 10.11.6 (issue which happened on 10.11.5; update today to see if this helped)

  Recently, I reformatted my hard drive to correct some wacky partitioning I played with and cloned my rear disc of a direct clone of CCC.  Also, I recreated my restoration, installation of Boot Camp and installed Windows partition.

  Then, I went to launch the Office remotely and received the following error:

  

  As a logical person, I uninstalled the application by following the steps here, reinstalled and restarted... to get the same error.

  At this point, I have Google would be a bit and found mention of a permissions issue which was that other people having the same problem.  I checked my diary and here, I got the same errors:

  

  The strict solution seems to be to delete this folder and recreate it.  First of all, I did this by connecting to the recovery partition and deleting the folder 'C' via the Terminal I didn't so not disable controls system integrity.  This resulting no change on a restart, even after do it again, uninstalling Remote Desktop, and then reinstall.

  Then I disabled the system integrity (csrutil disable) in recovery and started to remove it when it is started.  I ran across the same as hoops above because it does not work all the time.

  I even went away so crazy just now as to delete the folder of higher level instead of just the subfolder 'C '.  That no longer works.  I changed the permissions on the folder to 777.  No change.  Changed the owner to my user account because he invites him for an administrator account.  No change.

  I went to the ARD support page and tried to present a real ticket, but it turns out that the ARD is not in the list of software that you can file a ticket on.

  I'm out of ideas.  No luck, can anyone provide some guidance?

  Hi, I have exactly the same problem the first time, I don't have the link with a CCC clone, but this morning (after a clean install because of this problem), I cloned my boot on a new SSD drive and this issue comes up with the clone. I reboot the original disc and ARD works on original, CCC is causing the problem, I made several clones with previous systems without problems, so it's probably a mixture of Capitan/CCC/ARD pure problem.

  I left a message of support to the CCC with a reference to your thread.

  hope for solution too... for the first time in my life of Apple that a problem needs a new facility...

• The wrongly cloned HARD drive recovery

  Hello everyone,

  Instead of using a third-party cloning software, I tried to clone my drive with disk utility. After restart my laptop, I went into recovery by using the command-R and used disk utility menu in this menu. However, I accidentally chose the empty as the source disk Hd and the Macintosh Hd as the destination. I started the process, but in 10 seconds my laptop over cloning. Now I have two empty disks. I tried to restart my system but my whole data were missing. I stopped using it and immediately deleted. Is it possible to restore my drive? I tried 3 data rescue, but my whole files in over 26 thousand records without name. It is very difficult to sort and on top of that, I have really no idea about the collection again correctly my archives 'Photos '. Is there anyone who had this experience? What should I do? Not all recovery software of this kind of recovery with thousands of anonymous records?

  Now, I run my middle 2012 non-retine Macbook Pro 15 "with a new Hd I use El Capitan 10.11.5, if that's important. And also the other drive that I deleted in a box for external drive.

  There is also a thing. It's really very easy to delete our internal drives. Just restart your computer, then press command-r to start the recovery mode. You can clone an empty drive to your home without any problem. Utility disk never asked me my password before cloning. Attackers can erase your data all in 10 seconds. It's really disappointing. I admit it's my mistake, but it does not that much easy to delete my entire drive.

  Thanks in advance and I hope that Apple can solve the problem and may make it difficult to erase drive in recovery mode.

  Apple not to specialize in data recovery, they will probably refer you to someone else.

  If you want to send comments about how easy it was for you to mess up your system, you can use the Web page of apple.com/feedback for do.

• Cloning of mbp ssd

  Hi guys, I just need to know is it cloning software that allows you to clone your hard drive to another ssd or hdd or ssd which includes the recovery ios and partation any window you created via bootcamp. I know that carbon copy allows you to clone the recovery partatiton, but I want to know if he can clone partation of the window too. And one more thing like atm, I am using a mbp 2010 way snack environment in the future if I update my mbp and put my current ssd for the new mbp, is going to be problems with the operating system and that I be able to run to the window, I had in my ssd or not. Ta

  I think you need to use Windows software for cloning to successfully clone the Windows partition.  WinClone?

• Cloning of a Mac mini with application Server

  We bought a condo in Florida and I want to my server it doubles. I use Mac mini (2 different models) with 2 drives external (one for Time Machine backups) and one for data.

  What is the best way to install the Apple Server on Florida related to the Mac mini so I don't have to install it from scratch?

  Yesterday I tried (in vain) to use the Migration Wizard to move all of my Mac mini to the Florida-bound one. Can I use 3rd party app "Carbon Copy Cloner" instead?

  Any recommendations on how to configure the 2nd server would be appreciated.

  The replication server is a relatively trivial process and can be accomplished by using disk utility.  However, the source drive and the destination drive should not be active at the time of cloning.  For example, you have Master Mini and you want to be replicated on Mini replica.  The best way to do it with the included tools must start Master Mini from another disk that contains an operating system to start.  Then start the Mini replica in target disk mode and connect it to the Mini Master (already started from another drive).  Disk utility to clone the Master disk on the drive of replica.

  Ah, but cloning is the easy part.  The question I have for you is that you really want an exact replica?  The reason why I ask, is that your current server should have a name and a fully qualified domain name.  It's server.pauljohnson.com and it has a 10.0.0.10 IP address.  If you clone the device to another Mac, there will also be a name of server.pauljohnson.com and it has a 10.0.0.10 IP.  If two of your networks are configured on the 10.0.0.0/24 subnet then you won't be able to connect to each other.  Similarly, if you depend on external access to devices and must comply with DNS, then you can only point to one of the servers, unless you have a form of installation program to distribute the load between the two locations of load balancing.

  What services run you on the servers other than the Server Time Machine?  Do you intend to have a VPN tunnel between the two institutions?  If you use Open Directory, and DNS, you can configure master and replicas of the two services.  Of course, this should only be done with a tunnel VPN in place I would not recommend exposing these services to the internet.

  Then await you replicate data also?

  Start with a list of services and a list of expectations about how you want client machines work when moving from one place to another.

  Reid

  Apple Consultants Network

  Author - "El Capitan Server - Foundation Services.

  Author - "El Capitan Server - Collaboration & control»

  Author - "El Capitan Server - Advanced Services '.

  : IBooks exclusively available in Apple store

• Qosmio G30 (PQG31) - problem with cloned hard drives

  Hi all!

  * Qosmio G30-154 * (* PQG31 *).

  Demo of the Qosmio has 2 hard drives with XP MCE (32 bit) installed on the primary.
  The RAID parameters are JBOD.
  BIOS is "newer" 3.90

  I would try to upgrade the drives (without installing any OS) and... have a problem!
  BSOD "Stop 0x0000007B" after 'clone with resizing' for the main HARD disk.

  I read on [drivers Toshiba RAID | http://forums.computers.toshiba-europe.com/forums/thread.jspa?threadID=48489] also [how to integrate the AHCI driver when installing Windows XP | http://aps2.toshiba-tro.de/kb0/HTD9401AN0000R01.htm] and (or)
  [SATA and AHCI Intel Matrix Storage Management Software: "the installation program found no hard disk units installed in your computer" Error Message during Manual Installations | http://aps2.toshiba-tro.de/kb0/TSB7B020R0000R01.htm], but I don't want to install OS, I want to keep intact my OS work.
  F6 (for all usb drivers) is not available to boot OS, sorry.

  "cloned" drive is in line with the correct name of made in the BIOS. "Cloned" secondary drive works (with old primary school). How to get access to the new primary OS and loading cloned? Please, any ideas?

  Thank you.

  Hello

  I think that the system cannot boot to the new HARD disk as the partition where the system is installed, was not marked as bootable system partition.

  I recommend to insert the previous HARD drive and to start the laptop.
  HARD drive new, cloned could be connected as an external HARD drive to a USB port.

  Then you should go to disk management (right click my computer - manage-> management-> disk management computer)
  Here you can see the HARD internal disk and the 2nd HARD drive connected to the USB port
  Right-click on the partition (2nd HARD drive) where the Win XP has been installed and choose the partition as the system partition and mark it as active.

  Then you could change the HARD drive again and could power the device in place. Usually, the system should boot to the top of the new marked system partition.