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
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
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
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
"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
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
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
Thank you, JS, but the reference is to the actual drive name for
the internal hard drive and its partitions, so Backup would be a
little strange, wouldn't it?
Jo-Anne
I named it: Backups
Keeps it simple and straight forward.
JS
I'm slowly working my way through the manual for a new
backup/imaging program to be used on my Windows XP SP3
computer. One recommendation is to change the disk volume names
to unique descriptive names because restoring from backups
might otherwise be confusing. In one example, Local Disk
partitions were changed to SATA P1_C (C
, SATA P2_D (D
, etc.
Since I'm nervous about making changes, I just want to make
sure I won't be causing a problem by doing it. So...is this an
OK thing to do? If so, should I also name my external drives?
Thank you!
Jo-Anne
