Jo-Anne
Wed Jun 25 23:10:58 PDT 2008
Hi, Dave,
I'm just a newbie trying to get everything right. Here's where I was told to
"identify your drives via unique disk volume names assigned by you as
detailed in Link 1 below. Relying on just drive letters will cause confusion
as these will differ when using TI [Acronis True Image] in Rescue mode."
http://www.wilderssecurity.com/supportfiles/gh-acronis-backup1.pdf
The link referred to is at
http://www.wilderssecurity.com/supportfiles/unique-drive-naming.pdf
Jo-Anne
"Lil' Dave" <spamyourself@virus.net> wrote in message
news:u2$CXl01IHA.5048@TK2MSFTNGP06.phx.gbl...
> So, I'm confused here reading the thread. The volume name, from what I
> can determine is the same as the label name for a partition, not a
> physical hard drive. Why would one rename a windows backup boot
> partition? Its rather obvious if the backup partition is on another
> physical hard drive. And, can't be visible to the original XP if booting
> is desired on the alternate physical hard drive.
>
> --
> Dave
> "JS" <@> wrote in message news:u1ccpiz1IHA.6096@TK2MSFTNGP06.phx.gbl...
>>I though about it after I sent the post and then realized it could also
>>mean "Partition 1" as it does in your case.
>>
>> JS
>>
>> "Jo-Anne" <naples@tbcnet.com> wrote in message
>> news:OyC4gCz1IHA.2188@TK2MSFTNGP04.phx.gbl...
>>> Actually, to the guy who did it, I think it means SATA drive, partition
>>> 1, C drive letter (he kept the drive letter that way because the backup
>>> program changes drive letters in the restore, and he wanted to be sure
>>> he knew which real drive was being referenced). Anyway, I do understand
>>> that the name should be simple and something that will make sense to me
>>> down the line.
>>>
>>> Jo-Anne
>>>
>>> "JS" <@> wrote in message
>>> news:%233EAV9y1IHA.2208@TK2MSFTNGP04.phx.gbl...
>>>> If the names you have chosen make sense to you now and if you parked
>>>> and never used your PC for the next 5 years and then booted it up and
>>>> the names make sense to you five years from now then your choice of
>>>> names is what important and meaningful to you, that and only that is
>>>> what counts.
>>>>
>>>> In short 'SATA-P1_C' tells me that it's a SATA drive, Cable #1, C
>>>> partition.
>>>>
>>>> JS
>>>>
>>>> "Jo-Anne" <naples@tbcnet.com> wrote in message
>>>> news:eif4Xwy1IHA.3860@TK2MSFTNGP05.phx.gbl...
>>>>> Sorry! What I meant was that the example showed the original drive
>>>>> names as Local Disk (C:), Local Disk (D:), etc. After renaming (or
>>>>> naming, actually), they became SATA-P1_C (C:), SATA-P2_D (D:). Does
>>>>> that make sense? I'm sure I didn't express it well. A lot of what I'm
>>>>> trying to do is new to me, so I may get the phrasing wrong.
>>>>>
>>>>> Jo-Anne
>>>>>
>>>>> "JS" <@> wrote in message
>>>>> news:ugZXRzx1IHA.2384@TK2MSFTNGP04.phx.gbl...
>>>>>> "From the example I saw, I'd guess that's why the new name
>>>>>> included the original drive letter."
>>>>>>
>>>>>> Not certain exactly what you meant by "new name", could you clarify.
>>>>>>
>>>>>> JS
>>>>>>
>>>>>>
>>>>>> "Jo-Anne" <naples@tbcnet.com> wrote in message
>>>>>> news:us0rajx1IHA.4004@TK2MSFTNGP03.phx.gbl...
>>>>>>> Thank you, JS! That's exactly the kind of information I need. I have
>>>>>>> the impression from what I've read so far that Acronis will use the
>>>>>>> name you choose but may well change the drive letter in restoring.
>>>>>>> Hence the need to name the drive. From the example I saw, I'd guess
>>>>>>> that's why the new name included the original drive letter.
>>>>>>>
>>>>>>> Jo-Anne
>>>>>>>
>>>>>>> "JS" <@> wrote in message
>>>>>>> news:u5Uu2Zx1IHA.2068@TK2MSFTNGP05.phx.gbl...
>>>>>>>> Yep, Big Al's USB_BACKUP is a better choice.
>>>>>>>> Changing a drives Volume name is not an issue.
>>>>>>>> However it is possible that changing the Drive Letter
>>>>>>>> could be an issue depending on what installed or located on the USB
>>>>>>>> drive.
>>>>>>>>
>>>>>>>> Applications installed on the USB drive would hiccup with a
>>>>>>>> drive letter change, but data files should not be a problem.
>>>>>>>>
>>>>>>>> Image backup files may or may not be an issue (see below)
>>>>>>>> depending on how the image backup application locates
>>>>>>>> where the image files are stored.
>>>>>>>>
>>>>>>>> I understand you are using Acronis,
>>>>>>>> I use Ghost and one file and it's contents that
>>>>>>>> Ghost creates and uses contains the following entries:
>>>>>>>>
>>>>>>>> [RecoveryPointStorageLocation]
>>>>>>>> J:\Ghost 052208=.
>>>>>>>> J:\Ghost 053008=.
>>>>>>>> J:\Ghost 053008D=.
>>>>>>>> J:\Ghost 060708=.
>>>>>>>> J:\Ghost 060808=.
>>>>>>>> J:\Ghost 060808D=.
>>>>>>>> J:\Ghost 062308=.
>>>>>>>> [TimeZoneInformation]
>>>>>>>> Bias=300
>>>>>>>> TimeZoneName=Eastern Standard Time
>>>>>>>>
>>>>>>>> As you can see it has no reference to the drive's Volume name
>>>>>>>> (Which is named 'Backup' on my PC)
>>>>>>>> but it does reference the drive letter where my image backups
>>>>>>>> are stored.
>>>>>>>>
>>>>>>>> J: is the drive letter and 'Ghost 052208' is the folder name
>>>>>>>> I created and is where the actual image file is created and stored.
>>>>>>>> The 052208 as part of the folder name represents
>>>>>>>> the date the image was created, this makes it easy for me
>>>>>>>> to see when backup were created without actually loading Ghost.
>>>>>>>>
>>>>>>>> In addition I also create a 'readme.txt' file in each folder
>>>>>>>> using Notepad that tells me why the backup was made.
>>>>>>>>
>>>>>>>> Example of readme.txt file I created:
>>>>>>>> "Prior to Verizon ActionTec Router replacement - 5/30/08
>>>>>>>> and new Intel PWLA8391GT PRO/1000 NIC card install".
>>>>>>>>
>>>>>>>> JS
>>>>>>>>
>>>>>>>>
>>>>>>>> "Jo-Anne" <naples@tbcnet.com> wrote in message
>>>>>>>> news:O$t8U$w1IHA.4572@TK2MSFTNGP03.phx.gbl...
>>>>>>>>> Than