Clean map of RDM files

I just want to get clarification.  I removed some RDM tonight a virtual machine, but instead of removing and deleting, I just went with the removal of the RDM.  I now find myself with some of the mapping files and was curious to know if its ok just to remove @ this point?

http://monosnap.com/image/Hc4AzgXHXET9PBy79UYUZmaRn.png

Hello

The withdrawal of RDM mapping files will not cause any problem. When you add RDM back it will create again. It's so safe.

Concerning

Mohammed

Tags: VMware

Similar Questions

  • Simple mapping of RDM vs file several mapping of RDM files?

    Hello

    When you configure Microsoft Cluster nodes in a scenario of cluster-across-boxes (stream clustering) (two ESXi hosts, two-node cluster MSCS, with a bow on each ESXi host), I realize that using physical RDM Mode (pass-through RDM) is the way to go.  I also usually have to locate the C: drive (zero eager thick) for each cluster node on another volume VMFS to ensure two distinct areas of failure.  So, for example the C: drive of node of Cluster 1 (VM1) could be the Datastore1 and the C: drive of Cluster 2 node (VM2) might be on Datastore2.  Similarly, I always created RDM mapping files for each virtual computer as well, pointing to the same raw LUN.  For example, I would put the mapping of RDM for the quorum shared LUN on Datastore1 for VM1 and file a new mapping file RDM pointing to the same conditions of quorum LUN on Datastore2 for VM2.  In this way, the failure of Datastore1 will affect only VM1 and VM2affect only the failure of Datastore2 .  I did this for years (probably since ESX 2.5) and MSCS works very well in this configuration.

    However, I was re-reading of the official documentation of "configuration of Failover Clustering and the Microsoft Cluster Service" VMware and noticed that specific VMware at several locations as "a map file of RDM single and shared for each clustered disk is necessary."  In other words, they call for me to select 'existing hard drive' VM2, and then tap the RDM mapping file that I created on VM1, rather than creating a new fresh RDM for VM2 mapping file.  This seems to be "less safe" because the failure of Datastore1, or RDM 1 mapping file corruption, would result in the failure of VM2.  A separate mapping RDM for VM2, on a separate data store file would provide two distinct areas fault to two virtual machines.

    Does anyone know why VMware requires a shared single RDM mapping file?  Are there specific problems, caused by the presence of two separate files RDM mapping?

    Thank you

    Bill

    It seems that VMware has posted a KB that explicitly indicates that a pointer/mapping "single" RDM file must be used on all nodes of the cluster.  So I guess this settles my question!

    Several files of RDM pointer after the migration of storage (2131011)

    http://KB.VMware.com/kb/2131011

    Bill

  • New hard disc RDM - selection of the mapping of rdm file creation

    Hi all

    I am trying to automate the creation of new RDM disks for virtual machines.

    Watch us row map separately files on a data store named, here is the sequence of orders.

    1. because I can't find the PoweCLI method to create the mapping of RDM file, I use vmkfs as below:

    vmkfstools - z/vfms/devices/disks/naa. XXXX01 /vmfs/volumes/clustername/SharedDisk/hostname/disk1.vmdk

    2. now, we have the mapping of rdm file, I would like to create a new physical disk RDM.

    New-harddisk - Contorller $controller DiskType - RawPhysical - DeviceName ' / vfms, devices, disks, naa.» XXXX01"- vm $vm

    However, this creates a new mapping file. I don't see how I can use the one I created above.

    Am I missing something? The operation of fixing using the existing mapping of RDM file is insignificant in the GUI.

    No, not missing anything.

    This scenario is not possible with the cmdlet New-hard drive I'm afraid.

    You can use a script that uses the ReconfigVM method.

    Through the Device.Backing property, you can specify the location of the VMDK file

  • RDM to delete and recreate the mapping of RDM file and fix

    Hello

    I wrote the following script, but it works fine except it does not create the mapping of RDM file.

    If I comment out the following lines, it works fine.

    $fileMgr.DeleteDatastoreFile_Task ($name, $datacenter)

    $spec.deviceChange [0] .fileOperation = "crΘer".

    Here is the code below

    Replace-VM-RDM function {}

    Param ($scsiid, $rdmname, $vmname, $filename)

    < #.

    Convert SCSI address in Vmware format

    # >

    $scsicontroller = $null

    $scsiid_split = $null

    $scsiid_split = $scsiid.split(":")

    $scsicontroller =($scsiid_split[0])

    # SCSI VMware in the GUI controller ID is a number greater than the real controller id

    $scsicontroller = [int] $scsicontroller + 1

    # Vmware waiting conntroller with 4-character id

    $scsicontroller =($scsicontroller.) (ToString()) + "000".

    $scsicontroller

    # SCSI LOGICAL UNIT NUMBER

    $scsilun = $null

    # VMware SCSI LUN ID in the GUI is a higher number than the id real lun

    $scsilun = [int]($scsiid_split[1]) #+ 1

    ###

    $vm = get-VM-name '$vmname ' | Get-View

    IF (!) (($filename))) {}

    $RDMFile = $rdmname.split("") [0] + "_RDM.vmdk"

    $filename = (($vm.)) (Config.Files.VmPathName). Replace("$vmname.vmx","$RDMFile"))

    }

    $esx is get-view $vm. Runtime.Host

    < #.

    Download CanonicalName RDM Lun

    # >

    $rdmCanonicalName = $null

    $rdmCanonicalName = (($esx.)) Config.StorageDevice.ScsiLun | where {$_.} DisplayName - eq $rdmname}). CanonicalName)

    $rdmDevicePath = (($esx.)) Config.StorageDevice.ScsiLun | where {$_.} DisplayName - eq $rdmname}). DevicePath)

    foreach ($dev in $vm. Config.Hardware.Device) {}

    If (($dev.)) GetType()). {Name - eq "VirtualDisk")}

    If (($dev.Backing.CompatibilityMode-eq "physicalMode") - or)

    ($dev.Backing.CompatibilityMode-eq "virtualMode")) {}

    If (($dev.)) ControllerKey - eq "$scsicontroller") - and ($dev. UnitNumber - eq "$scsilun")) {}

    # Remove the hard drive

    $hd = get-disk hard $vm.name | where {$_.} Filename - eq $dev. Backing.FileName}

    $hd | Remove-hard drive - confirm: $false

    Write-Host "file name:" $dev.backing.fileName "

    Write-Host "Disk Mode:" $dev.backing.diskMode

    $dev.backing.deviceName

    $dev.backing.lunUuid

    $DevKey = $dev.key

    $CapacityInKB = $ dev. CapacityInKB

    $fileMgr = get-View (view Get ServiceInstance). Content.fileManager

    $datacenter = (get-View (Get - VM $VMname |)) Get-Datacenter) USER.USER) .get_MoRef)

    foreach ($disk in $vm. LayoutEx.Disk) {}

    if($Disk.) Key - eq $dev. Key) {}

    foreach ($chain in $disk. {String)

    foreach ($file in $chain.) FileKey) {}

    $name = $vm. LayoutEx.File [$file]. Name

    $fileMgr.DeleteDatastoreFile_Task ($name, $datacenter)

    }

    }

    continue

    }

    }

    }

    }

    Else if (($dev.)) ControllerKey - eq "$scsicontroller") - and ($dev. UnitNumber - eq "$scsilun")) {Write-Host "Selected SCSI address [$scsiid] is not a RDM"}

    }

    }

    #$hd1 = New-disk hard - VM $vmname - DeviceName $rdmDevicePath - DiskType RawPhysical # this line works

    $spec = $null

    $spec = new-Object VMware.Vim.VirtualMachineConfigSpec

    $spec.deviceChange = @)

    $spec.deviceChange += new-Object VMware.Vim.VirtualDeviceConfigSpec

    $spec.deviceChange [0] = new-Object VMware.Vim.VirtualDisk .device

    $spec.devicechange [0].device.capacityInKB = $CapacityInKB

    $spec.deviceChange [0].device.backing = new-Object VMware.Vim.VirtualDiskRawDiskMappingVer1BackingInfo

    $spec.deviceChange [0].device.backing.fileName = $filename

    $spec.deviceChange [0].device.backing.compatibilityMode = "physicalMode".

    $spec.deviceChange [0].device.backing.diskMode = «»

    $spec.deviceChange [0].device.backing.lunUuid = (($esx.)) Config.StorageDevice.ScsiLun | where {$_.} DisplayName - eq $rdmname}). UUID)

    $spec.deviceChange [0].device.connectable = new-Object VMware.Vim.VirtualDeviceConnectInfo

    $spec.deviceChange [0].device.connectable.startConnected = $true

    $spec.deviceChange [0].device.connectable.allowGuestControl = $false

    $spec.deviceChange [0].device.connectable.connected = $true

    # Take the next unused volume for HD key

    $spec.deviceChange [0].device.key = $DevKey + 1

    # 7 SCSIID UnitNUmber is reserved for the controller - then go to 8.

    If ($scsilun - eq 6) {$scsilun = $scsilun + 1}

    # Take the next unit for the HD number

    $spec.deviceChange [0].device.unitnumber = $scsilun

    # Key device for the SCSI controller

    $spec.deviceChange [0].device.controllerKey = $scsicontroller

    # Create vmdk file

    $spec.deviceChange [0] .fileOperation = "crΘer".

    $spec.deviceChange [0] .operation = 'Add '.

    $vm = get - View (Get - VM $VMname) USER.USER

    $vm. ReconfigVM_Task ($spec)

    }

    Replace-VM-RDM $vmname $scsiid $rdmname $filename

    I am working, it just need to reorganization and then the Devicename was wrong.

    Here's the script working.

    Replace-VM-RDM function {}

    Param ($scsiid, $rdmname, $vmname, $filename)

    <>

    Convert SCSI address in Vmware format

    #>

    $scsicontroller = $null

    $scsiid_split = $null

    $scsiid_split = $scsiid.split(":")

    $scsicontroller =($scsiid_split[0])

    # SCSI VMware in the GUI controller ID is a number greater than the real controller id

    $scsicontroller = [int] $scsicontroller + 1

    # Vmware waiting conntroller with 4-character id

    $scsicontroller =($scsicontroller.) (ToString()) + "000".

    $scsicontroller

    # SCSI LOGICAL UNIT NUMBER

    $scsilun = $null

    # VMware SCSI LUN ID in the GUI is a higher number than the id real lun

    $scsilun = [int]($scsiid_split[1]) #+ 1

    ###

    $vm = get-VM-name '$vmname ' | Get-View

    IF (!) (($filename))) {}

    $RDMFile = $rdmname.split("") [0] + "_RDM.vmdk"

    $filename = (($vm.)) (Config.Files.VmPathName). Replace("$vmname.vmx","$RDMFile"))

    }

    $esx is get-view $vm. Runtime.Host

    <>

    Download CanonicalName RDM Lun

    #>

    $rdmCanonicalName = $null

    $rdmCanonicalName = (($esx.)) Config.StorageDevice.ScsiLun | where {$_.} DisplayName - eq $rdmname}). CanonicalName)

    $rdmDevicePath = (($esx.)) Config.StorageDevice.ScsiLun | where {$_.} DisplayName - eq $rdmname}). DevicePath)

    foreach ($dev in $vm. Config.Hardware.Device) {}

    If (($dev.)) GetType()). {Name - eq "VirtualDisk")}

    If (($dev.Backing.CompatibilityMode-eq "physicalMode") - or)

    ($dev.Backing.CompatibilityMode-eq "virtualMode")) {}

    If (($dev.)) ControllerKey - eq "$scsicontroller") - and ($dev. UnitNumber - eq "$scsilun")) {}

    # Remove the hard drive

    $hd = get-disk hard $vm.name | where {$_.} Filename - eq $dev. Backing.FileName}

    $hd | Remove-hard drive - confirm: $false - DeletePermanently

    Write-Host "file name:" $dev.backing.fileName "

    Write-Host "Disk Mode:" $dev.backing.diskMode

    $dev.backing.deviceName

    $dev.backing.lunUuid

    $DevKey = $dev.key

    $CapacityInKB = $ dev. CapacityInKB

    <#$fileMgr =="" get-view="" (get-view="">

    $datacenter = (get-View (Get - VM $VMname |)) Get-Datacenter) USER.USER) .get_MoRef)

    foreach ($disk in $vm. LayoutEx.Disk) {}

    if($Disk.) Key - eq $dev. Key) {}

    foreach ($chain in $disk. {String)

    foreach ($file in $chain.) FileKey) {}

    $name = $vm. LayoutEx.File [$file]. Name

    $fileMgr.DeleteDatastoreFile_Task ($name, $datacenter)

    }

    }

    continue

    }

    }#>

    }

    }

    Else if (($dev.)) ControllerKey - eq "$scsicontroller") - and ($dev. UnitNumber - eq "$scsilun")) {Write-Host "Selected SCSI address [$scsiid] is not a RDM"}

    }

    }

    #$hd1 = New-disk hard - VM $vmname - DeviceName $rdmDevicePath - DiskType RawPhysical # this line works

    $spec = $null

    $spec = new-Object VMware.Vim.VirtualMachineConfigSpec

    $spec.deviceChange = new-Object VMware.Vim.VirtualDeviceConfigSpec [] (1)

    $spec.deviceChange [0] = new-Object VMware.Vim.VirtualDeviceConfigSpec

    # Create vmdk file

    $spec.deviceChange [0] .fileOperation = "crΘer".

    $spec.deviceChange [0] .operation = 'Add '.

    $spec.deviceChange = new-Object VMware.Vim.VirtualDeviceConfigSpec [] (1)

    $spec.deviceChange [0] = new-Object VMware.Vim.VirtualDeviceConfigSpec

    $spec.deviceChange [0] .operation = 'Add '.

    $spec.deviceChange [0] .fileOperation = "crΘer".

    $spec.deviceChange [0] = new-Object VMware.Vim.VirtualDisk .device

    $spec.deviceChange [0].device.key = - 100

    $spec.deviceChange [0].device.backing = new-Object VMware.Vim.VirtualDiskRawDiskMappingVer1BackingInfo

    $spec.deviceChange [0].device.backing.fileName = "$filename".

    $spec.deviceChange [0].device.backing.deviceName = (($esx.)) Config.StorageDevice.ScsiLun | where {$_.} DisplayName - eq $rdmname}). DevicePath)

    $spec.deviceChange [0].device.backing.compatibilityMode = "physicalMode".

    $spec.deviceChange [0].device.backing.diskMode = «»

    $spec.deviceChange [0].device.connectable = new-Object VMware.Vim.VirtualDeviceConnectInfo

    $spec.deviceChange [0].device.connectable.startConnected = $true

    $spec.deviceChange [0].device.connectable.allowGuestControl = $false

    $spec.deviceChange [0].device.connectable.connected = $true

    # Key device for the SCSI controller

    $spec.deviceChange [0].device.controllerKey = [int] $scsicontroller

    # 7 SCSIID UnitNUmber is reserved for the controller - then go to 8.

    If ($scsilun - eq 6) {$scsilun = $scsilun + 1}

    # Take the next unit for the HD number

    $spec.deviceChange [0].device.unitnumber = [int] $scsilun

    $spec.deviceChange [0].device.capacityInKB = [int] $CapacityInKB

    $vm = get - View (Get - VM $VMname) USER.USER

    $vm. ReconfigVM ($spec)

    }

    Replace-VM-RDM $vmname $scsiid $rdmname $filename

  • Map of RDM file size?

    So I I've attached some LUN to a virtual machine that is in a 180 GB data store.

    LUNS was 558 GB in size... and it has created a map file and stored with the virtual machine on the data store.

    When I browse the data store, he says he is a size 558 GB... vmdk file that is larger than the actual data store?

    What a mistake... or not the actual vmdk file mapping size?

    Probably it is just a file that indicates the size of the lun it points to...?   which makes sense because I do not understand any delete what space released if a vmdk file mapping in the data store.

    How much space the actual mapping files themselves take in the data store?

    Advice appreciated.

    Using RDM with a virtual machine, you will see a just big VMDK file such as size of the LUN on the VMFS datastore (in the vSphere client), but it is not allocated to the VMFS data bank.

    Logging to the console, you will see two files when mounted with RDM;

    VirtualDisk - rdmp.vmdk size 0 bytes
    VirtualDisk.vmdk size 64 bytes

  • OK to remove the mapping of RDM?

    I need to cold migrate some virtual machines with virtual RDM mode on new servers. I'll introduce the RDM with different numbers of LUNS on the target hosts. My co worker suggests that when you remove the ROW before the migration of the cold, you can not delete the mapping file, otherwise this will cause data corruption, so it selects the removal of the option of vm (not remove and delete).

    My understanding is the file ROW is just a mapping file and is safe to delete. My thought is that delete saves space and accelerates the migration time.

    RDM files can simply be removed without data corruption?, most vmware articles suggest they can and they're just mapping files.

    When the virtual machine allows you new hosts, a new virtual RDM will be added when the lun is presented to the new hosts.

    Yes, you can delete the ROW with removal of the VM disk option before the migration of the cold.

    It won't cause any data corruption that all data is on LUN storage.

    RDM file contain only for the LUN mapping information.

    Once you have completed the migration of VM, you can add RDM LUN to VM, just make sure that you attach Correct RDM LUN to VM.

    See this KB for more information-

    VMware KB: Switching between physical and virtual compatibility modes in ESX/ESXi, a mapping of raw data

  • How do I restore the hard ESXi RDM file?

    Hi all, I have created a file hard RDM using vmkfstools - z and boarded one of the virtual machines. However, I have deleted the virtual machine of the drive and re - create a new virtual machine in esxi.

    When I tried to recreate RDM hard, it shows an error:

    vmkfstools - z/vmfs/devices/disks/t10. ATA___TOSHIBA_DT01ACA200______1234ABCD "/ vmfs/volumes/HARDDISK/VM/1234ABCD.vmdk"

    Unable to create the virtual disk: the system cannot find the specified file (25).

    I noticed there are additional files (: 1,: 2 and: 3) who were not exist when I created first the hard

    T10. ATA___TOSHIBA_DT01ACA200___1234ABCD

    T10. 1234ABCDATA___TOSHIBA_DT01ACA200___: 1

    T10. ATA___TOSHIBA_DT01ACA200___1234ABCD: 2

    T10. ATA___TOSHIBA_DT01ACA200___1234ABCD: 3

    So, does anyone know how to recreate for RDM hard to mount on my new virtual machine without losing any data?

    Thank you.

    Welcome to the community,

    Take a look at e.g. RDMs SATA drives create how to create the RDM. Also make sure that the destination folder (in which you create the map file) already exists.

    The additional "files" that you see in the output of the command ls are partitions on this disk, which were probably created while the ROW was mounted on the virtual machine.

    André

  • Configure a mapping with txt file in LabVIEW

    Hello world

    I would like to connect my I/O with labVIEW and my .txt file (as in VeriStand) but I can't find any block or VI to do.

    Is there a trick or something like that? My txt file is approximately 300 lines...

    Thank you!

    Nico

    This VI is correct.

    Your problem is related to the names of agencies and models.

    Once you correct this (in the Homeless or TXT), it works fine.

    Check the attached file. Only the LED switches to green when each channel is added to the Homeless, if you have a single channel with the wrong name, he is unable to map all other channels.

  • Mapped DFS network file causes windows Explorer to hang

    Hello

    I have an environment running windows xp service Pack 3 and distributed file system (DFS) mapped network.
    The domain level is windows 2003 service pack 2 and server dfs are running in windows 2008 service pack 2.

    whenever a client machine connects open Windows Explorer / my computer on a slow network or vpn, Windows Explorer / my computer freezes for ever. The computer can operate correctly, except for this problem. The only way is to cut my cable network or perform a restart.
    I suspect it's due to the unavailable to the dfs file server SMB 445 port.

    I have found no solution or the hotfix of google or microsoft knowledge base.
    I also tried to find ways to change any dfs registry to reduce the interval or prevent as much as possible.
    For the moment, I am naïve, thank you for any help or experience to solve this problem.

    Hi Patrick.star,

    The issue of Windows XP, you have posted is related to Windows XP in a domain environment. It is better suited for the IT Pro TechNet public. Please ask your question in the TechNet forums for assistance.

    Hope the helps of information.

  • 'clean boot' will delete files saved... documents, photos etc?

    Our HP laptop gets slower of the day.  The blue little spinning circle won't go away.  After reading the other posts, looks like I need to "clean boot" it.   My question is will erase saved documents and photos that I have on the computer?  Thanks for any advice.

    A clean boot is just a way to start your computer with a minimum of programs and drivers for you to solve the problems which programs and driver (s) can cause a problem. It does not remove your personal files such as documents and images.

    Having said that, I strongly recommend that you regularly back up all personal files are important to you in a separate drive - such as an external hard drive or DVD. This is particularly important if you do something important on your computer (such as the level) or other difficulties. In addition, while hard disks are usually reliable enough these days, they can and fail without warning - if you have not backed up then its probably goodbye to your files.

    With respect to the slower your computer, I'd take a glance on the advice of this article:

    http://www.microsoft.com/atwork/maintenance/speed.aspx#fbid=mNHXB9JZ1SD .

  • When you attempt to install error Street travels and maps is the file is corrupted

    I can't fully extract free street maps and Microsoft travel 2010 evaluation edition. I get to the end and when almost done it says that the file is corrupted. I can't ask microsoft do anything without having to pay. It's sad, especially in this time of recession, we can report a problem without having to pay. Shame on Microsoft. I want to give my email but they do not like and delete so I'll try this way. Please help me, anyone, anytime by going to the hotmail Web site and typing in busmanonthego first.

    Thank you and God bless.

    Try to download another copy and save it to your desktop (do not use Run to proceed with the installation).  Then try to install it from there.  The original downloaded file was perhaps actually corrupted.  BTW, happens to mention the name of the corrupted file?

    I hope this helps.

    Good luck!

    Lorien - MCSA/MCSE/network + / has + - if this post solves your problem, please click the 'Mark as answer' or 'Useful' button at the top of this message. Marking a post as answer, or relatively useful, you help others find the answer more quickly.

  • Clean system lack button files

    I installed Win 7 home and ultimate on 2 computers. Files system clean button is missing from the disc clean the box after completing the drive clean program, only the view folders botton is, what happened to the clean system files button? Is there an adjustment somwhere that has changed?
    Thank you
    Mark

    It's already there?  My ultimate laptop, it shows to me (it has the security shield in the button).  You may have turned off UAC?  If UAC is disabled, this button is not necessary because it can already access system files.

    If it was useful, you can vote by clicking on the green triangle. If it solves the problem, click on propose as answer. Thank you!

  • How to find all the controller ID: target used for the mapping of RDM on virtual machine

    I want to get a list of all the target ID used for ROW mapping on each controller.  Then next time, I can use the remaining ID of the target for RDM disk mapping using the perl script.

    I checked findVMsWithRDMs.pl but it shows an ID used target for each disc RDM. I use 5.5 ESXi servers and SDK for perl.

    Thank you

    Celine

    You will have to list all config.hardware.device devices, and then find the raw disk support type (to select the ROW).  Then look at the number of drive.  Then use it's value of controllerKey to get the controllers in config.hardware.device with the corresponding key and then get its value busNumber.  So it's busNumber:UnitNumber for the SCSI ID.

    You'll probably want to get all used SCSI identification numbers (use a hash such as BusNumber:UnitNumber-1 online).  Then you can quickly search number the first available bus.  That's what I generally find a free SCSI ID to add a new disk (including the ROW).

  • Mapping of RDM slow powercli

    We have a process where we input a list of devices to drive about 15 in a foreach loop to add them to a virtual machine (see the code snippet).  The process works well, however there is a delay about 1 minute between each map to real device as when we look at the "recent tasks" view in the client...  Any ideas on what could be causing this delay between maps and/or ways to speed it up?... thx...

    # Add RDM disks
    {foreach ($rdmID to $rdmIDs)
    Write-host "Mapping" $rdmID.DeviceId "as a replay of the ' $vmName
    $deviceName = (get-ScsiLun - vmhost $esxhost - LunType disc | where {$_.}) ({CanonicalName-match $rdmID.DeviceID}). ConsoleDeviceName
    New-disk-hard - VM $vmName - DiskType RawPhysical - $deviceName DeviceName | Out-Null
    } # End addition of RDM disks

    If you use a column header try something like this

    Import-Csv C:\names.csv - UseCulture | % {« naa ». + $_. DeviceId}

  • Importing and organizing photo files lightroom 5 for the first time. Clean photo hard drive files

    I have a trial version of lightroom 5 and would like one once and forall to restore order to my two drives hard and lightroom 5 collection. Some photos in lightroom 5 seem to have lost their way. Some are in folders of Windows 7 and others are 9 elements. I made backup copies of some records and would like to have a more systematic approach to save them in the future. I have a NAS (network access storage) device and an additional hard drive, I thought that it would be better to use my cell phone as main for my photo files working memory such that it would be faster to work with the NAS or external and then again everything down to the NAS and external. I consider that the main challenge group all files and as much as possible to preserve the sides I gave photos; I would like to eliminate duplicats. on both the hard drive and in lightroom. I watched one of the vidios of initial training on the 'library' of the adobe help section and the presenter talked about two ways to import photos. the first and I think that I will use in the future is to open lightroom and import from the SD directly rather than having the Windows 7 import, and then ask to lightroom to find them. If anyone Kow of an exhaustive enumeration of the instructions on how to clean up my hard drives that would be extremely useful? Peter

    I doubt that it is a list of instructions to wipe a hard drive, because each starting situation is different and your 'own' is probably very different than my "clean".

    But let's clear up a few things first. From your writings, it seems that you think that you have stored pictures in post-secondary education and photos stored in LR. This is not correct. None of these programs to store your photos. All your pictures are on your hard drive, in folders, somewhere.

    Regarding the missing photos in Lightroom, when you move or rename your photos and folders outside of the Lightroom, Lightroom doesn't know where they are and bring back them as being absent. To fix it, see: http://www.computer-darkroom.com/lr2_find_folder/find-folder.htm related to that, you don't want to 'clean up' things in Windows and also "clean things" upward in Lightroom. Instead, once you import photos into Lightroom, you must do all the managing photos in Lightroom, not Windows, otherwise you'll just create several missing files.

    Regarding duplicates, Lightroom has some tools to detect duplicates. He will try to prevent duplicates during the import, and if you are unable to import duplicates, you can use the "auto stack by Capture time" to try to find additional duplicates. But if those who do not work, then're it pretty much on your own.

    With regard to put photos on your laptop to work on them rather than on your external hard drive, I think you will find that this gives a fraction of a second speed improvement that you may even not notice, which will be offset by the time you spend moving somewhere else photos when finished. So just put the photos in their final destination on your external HD or a NAS file and don't bother moving them to the internal HD.

    Which leads to another point. Once you have done this 'cleaning', your workflow should be to put the photos in a place and then do not transfer! (Exception: not enough space on the disk or moving to another drive/computer) Make your life easier as possible.

    One last point: seriously consider using keywords and other metadata for the Organization, rather than move photos/files from here to there, to reach the organization. These tools in Lightroom will give you the possibility of organizing in a much more powerful and flexible organization and what you can do by moving the photos/files from here to there. (Note: If you want all the photos in a sort of centralized location because it meets your storage needs, can do that because it meets your storage needs.) In this collection of photos in a centralized location, using keywords and other metadata to achieve organization and research)

Maybe you are looking for