I have a Buffalo (Melco) NTFS formatted hard drive attached to my home
network and mapped to L:/.

For some reason it's not displayed on the list of drives I can back up to
and I can't use the L:/ as the location.

Any ideas?

Thanks,

Andrew Shuttleworth

---
I tried \\DEVICE-NAME\share but was prompted for a password that I don't
believe I have set. Perhaps something to do with the way the device was
configured during the automatic setup ???

You cannot backup to a mapped drive.

Your logged in users mapped the drive and the backup software is a service,
so it won’t see YOUR mapped drivers.

Also, some network file stores do not implement windows file sharing
correctly so they wont work.

They may be a work around that I don’t know about, but I just bought a USB
external hard disk and it works a treat.

ta

Steve


"Andrew Shuttleworth" <(E-Mail Removed)> wrote
in message news:46503519-1861-4E6A-BBFD-(E-Mail Removed)...
>I have a Buffalo (Melco) NTFS formatted hard drive attached to my home
> network and mapped to L:/.
>
> For some reason it's not displayed on the list of drives I can back up to
> and I can't use the L:/ as the location.
>
> Any ideas?
>
> Thanks,
>
> Andrew Shuttleworth
>
> ---
> I tried \\DEVICE-NAME\share but was prompted for a password that I don't
> believe I have set. Perhaps something to do with the way the device was
> configured during the automatic setup ???
>

I have tried getting a Buffalo to work, we have one at work.

I did not get anywhere with using \\NETWORKNAME\SHARE

I tried creating a share that had a login and password, still not luck.

Without doing any R&D, I recon Buffalo use Samba type implementation and its
does not support the way that the backup service is trying to authenticate.

If anyone has done some R&D I would be interested here any outcome.

Steve





"Andrew Shuttleworth" <(E-Mail Removed)> wrote
in message news:16CAA7A1-F56F-456D-A42C-(E-Mail Removed)...
> Thanks for the explanation. If anyone from MS is reading perhaps this
> should
> be added to the help file. Below is the most relevant answer I could find
> which didn't cover this scenario.
>
> I do have a USB drive, but my PC is a laptop and even when I'm at home I'm
> moving around from place to place and having a connected drive is a drag
> and
> not really practical for regular backups.
>
> Will have to find out if there is someway I can use the full path to the
> drive.
>
> Thanks again,
>
> Andrew
>
> ===
> Quote from the Windows Help File:
>
> When I'm using the Back Up Files wizard, why don't I see the location that
> I
> want to back up to when I'm choosing where to save my backup?
> When you choose a location to save your backup to, the wizard searches
> your
> computer and displays a list of all locations that you can use. If the
> location that you want to use doesn't appear in the list, it could be due
> to
> one of the following problems:
>
> The location is a tape drive. You can't save backups to tapes.
>
> The location is a disk that you are trying to back up. You can't back up a
> disk to the same disk. For example, you can't back up the contents of a
> disc
> on drive D to that same disc.
>
> The location is a CD-ROM drive. You can't use a CD-ROM drive to make a
> backup; you must use a CD burner, also known as a CD-R or CD-RW drive.
>
> The location is a USB flash drive. You can't save backups to a flash
> drive.
>
> The location is not formatted as NTFS, FAT, or Universal Disk Format (UDF)
> (also called Live File System). Backups can only be saved to disks that
> are
> formatted using the NTFS, FAT, or UDF file systems. For more information,
> see
> Comparing NTFS and FAT file systems.
>
> The location is either the system disk (the disk that Windows is installed
> on—also called the C drive) or the boot disk (the disk that Windows uses
> to
> start your computer—also called the startup disk).
>
>
> "Steve Drake" wrote:
>
>> You cannot backup to a mapped drive.
>>
>> Your logged in users mapped the drive and the backup software is a
>> service,
>> so it won’t see YOUR mapped drivers.
>>
>> Also, some network file stores do not implement windows file sharing
>> correctly so they wont work.
>>
>> They may be a work around that I don’t know about, but I just bought a
>> USB
>> external hard disk and it works a treat.
>>
>> ta
>>
>> Steve
>>
>>
>> "Andrew Shuttleworth" <(E-Mail Removed)>
>> wrote
>> in message news:46503519-1861-4E6A-BBFD-(E-Mail Removed)...
>> >I have a Buffalo (Melco) NTFS formatted hard drive attached to my home
>> > network and mapped to L:/.
>> >
>> > For some reason it's not displayed on the list of drives I can back up
>> > to
>> > and I can't use the L:/ as the location.
>> >
>> > Any ideas?
>> >
>> > Thanks,
>> >
>> > Andrew Shuttleworth
>> >
>> > ---
>> > I tried \\DEVICE-NAME\share but was prompted for a password that I
>> > don't
>> > believe I have set. Perhaps something to do with the way the device was
>> > configured during the automatic setup ???
>> >
>>

As it is now, it didn't work with any NAS system I have tested with. Not
from Netgear on the SC101 not on the TEAC HD350 and as have been tested by
colleague's not on the Buffalo's either.

So backing op to NAS doesn't work at the moment we have to wait for updated
firmware that support the networking from Vista to be able to do so.

Contact the Supplier from Buffalo NAS regarding this problem as we have
done to the others, the only way to get this cured. I am lucky my own
backup software does work with the NAS.

Ko.

"Steve Drake" <steve@NOSPAM_SS_Drakey.co.uk> schreef in bericht
news:6D94C523-584A-4C88-A79D-(E-Mail Removed)...
>I have tried getting a Buffalo to work, we have one at work.
>
> I did not get anywhere with using \\NETWORKNAME\SHARE
>
> I tried creating a share that had a login and password, still not luck.
>
> Without doing any R&D, I recon Buffalo use Samba type implementation and
> its does not support the way that the backup service is trying to
> authenticate.
>
> If anyone has done some R&D I would be interested here any outcome.
>
> Steve
>
>
>
>
>
> "Andrew Shuttleworth" <(E-Mail Removed)> wrote
> in message news:16CAA7A1-F56F-456D-A42C-(E-Mail Removed)...
>> Thanks for the explanation. If anyone from MS is reading perhaps this
>> should
>> be added to the help file. Below is the most relevant answer I could find
>> which didn't cover this scenario.
>>
>> I do have a USB drive, but my PC is a laptop and even when I'm at home
>> I'm
>> moving around from place to place and having a connected drive is a drag
>> and
>> not really practical for regular backups.
>>
>> Will have to find out if there is someway I can use the full path to the
>> drive.
>>
>> Thanks again,
>>
>> Andrew
>>
>> ===
>> Quote from the Windows Help File:
>>
>> When I'm using the Back Up Files wizard, why don't I see the location
>> that I
>> want to back up to when I'm choosing where to save my backup?
>> When you choose a location to save your backup to, the wizard searches
>> your
>> computer and displays a list of all locations that you can use. If the
>> location that you want to use doesn't appear in the list, it could be due
>> to
>> one of the following problems:
>>
>> The location is a tape drive. You can't save backups to tapes.
>>
>> The location is a disk that you are trying to back up. You can't back up
>> a
>> disk to the same disk. For example, you can't back up the contents of a
>> disc
>> on drive D to that same disc.
>>
>> The location is a CD-ROM drive. You can't use a CD-ROM drive to make a
>> backup; you must use a CD burner, also known as a CD-R or CD-RW drive.
>>
>> The location is a USB flash drive. You can't save backups to a flash
>> drive.
>>
>> The location is not formatted as NTFS, FAT, or Universal Disk Format
>> (UDF)
>> (also called Live File System). Backups can only be saved to disks that
>> are
>> formatted using the NTFS, FAT, or UDF file systems. For more information,
>> see
>> Comparing NTFS and FAT file systems.
>>
>> The location is either the system disk (the disk that Windows is
>> installed
>> on-also called the C drive) or the boot disk (the disk that Windows uses
>> to
>> start your computer-also called the startup disk).
>>
>>
>> "Steve Drake" wrote:
>>
>>> You cannot backup to a mapped drive.
>>>
>>> Your logged in users mapped the drive and the backup software is a
>>> service,
>>> so it won't see YOUR mapped drivers.
>>>
>>> Also, some network file stores do not implement windows file sharing
>>> correctly so they wont work.
>>>
>>> They may be a work around that I don't know about, but I just bought a
>>> USB
>>> external hard disk and it works a treat.
>>>
>>> ta
>>>
>>> Steve
>>>
>>>
>>> "Andrew Shuttleworth" <(E-Mail Removed)>
>>> wrote
>>> in message news:46503519-1861-4E6A-BBFD-(E-Mail Removed)...
>>> >I have a Buffalo (Melco) NTFS formatted hard drive attached to my home
>>> > network and mapped to L:/.
>>> >
>>> > For some reason it's not displayed on the list of drives I can back up
>>> > to
>>> > and I can't use the L:/ as the location.
>>> >
>>> > Any ideas?
>>> >
>>> > Thanks,
>>> >
>>> > Andrew Shuttleworth
>>> >
>>> > ---
>>> > I tried \\DEVICE-NAME\share but was prompted for a password that I
>>> > don't
>>> > believe I have set. Perhaps something to do with the way the device
>>> > was
>>> > configured during the automatic setup ???
>>> >
>>>
>

For convenience, email your suggestion to (E-Mail Removed).

"Andrew Shuttleworth" <(E-Mail Removed)> wrote
in message news:16CAA7A1-F56F-456D-A42C-(E-Mail Removed)...
> Thanks for the explanation. If anyone from MS is reading perhaps this
> should
> be added to the help file. Below is the most relevant answer I could find
> which didn't cover this scenario.

I think you can backup to a networked drive, but only from the command line.
I have done this myself, so this info could be incorrect.

-iceeagle


"Colin Barnhorst" <(E-Mail Removed)> wrote in message
news:%(E-Mail Removed)...
> For convenience, email your suggestion to (E-Mail Removed).
>
> "Andrew Shuttleworth" <(E-Mail Removed)> wrote
> in message news:16CAA7A1-F56F-456D-A42C-(E-Mail Removed)...
>> Thanks for the explanation. If anyone from MS is reading perhaps this
>> should
>> be added to the help file. Below is the most relevant answer I could find
>> which didn't cover this scenario.
>

This is indeed the reason why backing up to mapped drives isn't supported.
Thanks Steve for pointing this out.

According to our backup team, to use a NAS device as a backup target, you
need to create the share with "Full Control" privileges for the user whose
credentials they want to connect with. There is some information in the help
on this. (Though, I don't see this after a quick scan.)

If this doesn't work, we recommend contacting your NAS manufacturer to ask
them for upgraded firmware based on 3.x version of Samba.


--
This posting is provided "AS IS" with no warranties, and confers no rights.

Want to learn more about Windows Server file and storage technologies? Visit
our team blog at http://blogs.technet.com/filecab/default.aspx.


"Steve Drake" <steve@NOSPAM_SS_Drakey.co.uk> wrote in message
news:9BE07670-D32D-465A-BF05-(E-Mail Removed)...
> You cannot backup to a mapped drive.
>
> Your logged in users mapped the drive and the backup software is a
> service, so it won't see YOUR mapped drivers.
>
> Also, some network file stores do not implement windows file sharing
> correctly so they wont work.
>
> They may be a work around that I don't know about, but I just bought a USB
> external hard disk and it works a treat.
>
> ta
>
> Steve
>
>
> "Andrew Shuttleworth" <(E-Mail Removed)> wrote
> in message news:46503519-1861-4E6A-BBFD-(E-Mail Removed)...
>>I have a Buffalo (Melco) NTFS formatted hard drive attached to my home
>> network and mapped to L:/.
>>
>> For some reason it's not displayed on the list of drives I can back up to
>> and I can't use the L:/ as the location.
>>
>> Any ideas?
>>
>> Thanks,
>>
>> Andrew Shuttleworth
>>
>> ---
>> I tried \\DEVICE-NAME\share but was prompted for a password that I don't
>> believe I have set. Perhaps something to do with the way the device was
>> configured during the automatic setup ???
>>
>

Hi Jill,

Not to get picky but why doesn't Vista Backup work with compressed drives?

And why can we not select what we want to backup, instead of MS deciding for
us?

Third, why limit the destinations where a backup can be placed, if the main
reason for reworking backup was to get more people to *USE* Vista backup?

In all the years of IT, this is the worst application *ever* to come out of
Redmond.

Ok, besides MS Bob. (with apologies to Melinda.)

Just my 2 centimes, since you popped up.

--
Mark-Allen Perry
160825 / 1112165
Windows Vista X64 Ultimate
RTM Build 6000.16386
ALPHA Systems
Marly, Switzerland
mark-allen @ mvps . org



"Jill Zoeller [MSFT]" <(E-Mail Removed)> wrote in message
news:%(E-Mail Removed)...
> This is indeed the reason why backing up to mapped drives isn't supported.
> Thanks Steve for pointing this out.
>
> According to our backup team, to use a NAS device as a backup target, you
> need to create the share with "Full Control" privileges for the user whose
> credentials they want to connect with. There is some information in the
> help on this. (Though, I don't see this after a quick scan.)
>
> If this doesn't work, we recommend contacting your NAS manufacturer to ask
> them for upgraded firmware based on 3.x version of Samba.
>
>
> --
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>
> Want to learn more about Windows Server file and storage technologies?
> Visit our team blog at http://blogs.technet.com/filecab/default.aspx.
>
>
> "Steve Drake" <steve@NOSPAM_SS_Drakey.co.uk> wrote in message
> news:9BE07670-D32D-465A-BF05-(E-Mail Removed)...
>> You cannot backup to a mapped drive.
>>
>> Your logged in users mapped the drive and the backup software is a
>> service, so it won't see YOUR mapped drivers.
>>
>> Also, some network file stores do not implement windows file sharing
>> correctly so they wont work.
>>
>> They may be a work around that I don't know about, but I just bought a
>> USB external hard disk and it works a treat.
>>
>> ta
>>
>> Steve
>>
>>
>> "Andrew Shuttleworth" <(E-Mail Removed)>
>> wrote in message
>> news:46503519-1861-4E6A-BBFD-(E-Mail Removed)...
>>>I have a Buffalo (Melco) NTFS formatted hard drive attached to my home
>>> network and mapped to L:/.
>>>
>>> For some reason it's not displayed on the list of drives I can back up
>>> to
>>> and I can't use the L:/ as the location.
>>>
>>> Any ideas?
>>>
>>> Thanks,
>>>
>>> Andrew Shuttleworth
>>>
>>> ---
>>> I tried \\DEVICE-NAME\share but was prompted for a password that I don't
>>> believe I have set. Perhaps something to do with the way the device was
>>> configured during the automatic setup ???
>>>
>>
>
>

File Backup *does* work with compressed drives. The CompletePC backup engine
does not allow the target to be compressed, but the source can be
compressed. The reason behind this decision is because copy-on-write doesn't
work well when the .vhd is compressed. We are looking to allow compressed
target volumes in the future.

We talk more about the Backup changes in our FAQ at
http://blogs.technet.com/filecab/pag...vista-faq.aspx.
We were targeting core consumers for this release, and we are working to
address the feedback we've received from the newsgroup community...I can't
give more specific details...yet.

--
This posting is provided "AS IS" with no warranties, and confers no rights.

Want to learn more about Windows file and storage technologies? Visit our
team blog at http://blogs.technet.com/filecab/default.aspx.


"Mark-Allen [160825]" <mark-(E-Mail Removed)> wrote in message
news:uMVNv$(E-Mail Removed)...
> Hi Jill,
>
> Not to get picky but why doesn't Vista Backup work with compressed drives?
>
> And why can we not select what we want to backup, instead of MS deciding
> for us?
>
> Third, why limit the destinations where a backup can be placed, if the
> main reason for reworking backup was to get more people to *USE* Vista
> backup?
>
> In all the years of IT, this is the worst application *ever* to come out
> of Redmond.
>
> Ok, besides MS Bob. (with apologies to Melinda.)
>
> Just my 2 centimes, since you popped up.
>
> --
> Mark-Allen Perry
> 160825 / 1112165
> Windows Vista X64 Ultimate
> RTM Build 6000.16386
> ALPHA Systems
> Marly, Switzerland
> mark-allen @ mvps . org
>
>
>
> "Jill Zoeller [MSFT]" <(E-Mail Removed)> wrote in message
> news:%(E-Mail Removed)...
>> This is indeed the reason why backing up to mapped drives isn't
>> supported. Thanks Steve for pointing this out.
>>
>> According to our backup team, to use a NAS device as a backup target, you
>> need to create the share with "Full Control" privileges for the user
>> whose credentials they want to connect with. There is some information in
>> the help on this. (Though, I don't see this after a quick scan.)
>>
>> If this doesn't work, we recommend contacting your NAS manufacturer to
>> ask them for upgraded firmware based on 3.x version of Samba.
>>
>>
>> --
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>>
>> Want to learn more about Windows Server file and storage technologies?
>> Visit our team blog at http://blogs.technet.com/filecab/default.aspx.
>>
>>
>> "Steve Drake" <steve@NOSPAM_SS_Drakey.co.uk> wrote in message
>> news:9BE07670-D32D-465A-BF05-(E-Mail Removed)...
>>> You cannot backup to a mapped drive.
>>>
>>> Your logged in users mapped the drive and the backup software is a
>>> service, so it won't see YOUR mapped drivers.
>>>
>>> Also, some network file stores do not implement windows file sharing
>>> correctly so they wont work.
>>>
>>> They may be a work around that I don't know about, but I just bought a
>>> USB external hard disk and it works a treat.
>>>
>>> ta
>>>
>>> Steve
>>>
>>>
>>> "Andrew Shuttleworth" <(E-Mail Removed)>
>>> wrote in message
>>> news:46503519-1861-4E6A-BBFD-(E-Mail Removed)...
>>>>I have a Buffalo (Melco) NTFS formatted hard drive attached to my home
>>>> network and mapped to L:/.
>>>>
>>>> For some reason it's not displayed on the list of drives I can back up
>>>> to
>>>> and I can't use the L:/ as the location.
>>>>
>>>> Any ideas?
>>>>
>>>> Thanks,
>>>>
>>>> Andrew Shuttleworth
>>>>
>>>> ---
>>>> I tried \\DEVICE-NAME\share but was prompted for a password that I
>>>> don't
>>>> believe I have set. Perhaps something to do with the way the device was
>>>> configured during the automatic setup ???
>>>>
>>>
>>
>>
>

Is this true of the backup program as well?

"Jill Zoeller [MSFT]" <(E-Mail Removed)> wrote in message
news:%(E-Mail Removed)...
> File Backup *does* work with compressed drives. The CompletePC backup
> engine does not allow the target to be compressed, but the source can be
> compressed. The reason behind this decision is because copy-on-write
> doesn't work well when the .vhd is compressed. We are looking to allow
> compressed target volumes in the future.
>
> We talk more about the Backup changes in our FAQ at
> http://blogs.technet.com/filecab/pag...vista-faq.aspx.
> We were targeting core consumers for this release, and we are working to
> address the feedback we've received from the newsgroup community...I can't
> give more specific details...yet.
>
> --
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>
> Want to learn more about Windows file and storage technologies? Visit our
> team blog at http://blogs.technet.com/filecab/default.aspx.
>
>
> "Mark-Allen [160825]" <mark-(E-Mail Removed)> wrote in message
> news:uMVNv$(E-Mail Removed)...
>> Hi Jill,
>>
>> Not to get picky but why doesn't Vista Backup work with compressed
>> drives?
>>
>> And why can we not select what we want to backup, instead of MS deciding
>> for us?
>>
>> Third, why limit the destinations where a backup can be placed, if the
>> main reason for reworking backup was to get more people to *USE* Vista
>> backup?
>>
>> In all the years of IT, this is the worst application *ever* to come out
>> of Redmond.
>>
>> Ok, besides MS Bob. (with apologies to Melinda.)
>>
>> Just my 2 centimes, since you popped up.
>>
>> --
>> Mark-Allen Perry
>> 160825 / 1112165
>> Windows Vista X64 Ultimate
>> RTM Build 6000.16386
>> ALPHA Systems
>> Marly, Switzerland
>> mark-allen @ mvps . org
>>
>>
>>
>> "Jill Zoeller [MSFT]" <(E-Mail Removed)> wrote in message
>> news:%(E-Mail Removed)...
>>> This is indeed the reason why backing up to mapped drives isn't
>>> supported. Thanks Steve for pointing this out.
>>>
>>> According to our backup team, to use a NAS device as a backup target,
>>> you need to create the share with "Full Control" privileges for the user
>>> whose credentials they want to connect with. There is some information
>>> in the help on this. (Though, I don't see this after a quick scan.)
>>>
>>> If this doesn't work, we recommend contacting your NAS manufacturer to
>>> ask them for upgraded firmware based on 3.x version of Samba.
>>>
>>>
>>> --
>>> This posting is provided "AS IS" with no warranties, and confers no
>>> rights.
>>>
>>> Want to learn more about Windows Server file and storage technologies?
>>> Visit our team blog at http://blogs.technet.com/filecab/default.aspx.
>>>
>>>
>>> "Steve Drake" <steve@NOSPAM_SS_Drakey.co.uk> wrote in message
>>> news:9BE07670-D32D-465A-BF05-(E-Mail Removed)...
>>>> You cannot backup to a mapped drive.
>>>>
>>>> Your logged in users mapped the drive and the backup software is a
>>>> service, so it won't see YOUR mapped drivers.
>>>>
>>>> Also, some network file stores do not implement windows file sharing
>>>> correctly so they wont work.
>>>>
>>>> They may be a work around that I don't know about, but I just bought a
>>>> USB external hard disk and it works a treat.
>>>>
>>>> ta
>>>>
>>>> Steve
>>>>
>>>>
>>>> "Andrew Shuttleworth" <(E-Mail Removed)>
>>>> wrote in message
>>>> news:46503519-1861-4E6A-BBFD-(E-Mail Removed)...
>>>>>I have a Buffalo (Melco) NTFS formatted hard drive attached to my home
>>>>> network and mapped to L:/.
>>>>>
>>>>> For some reason it's not displayed on the list of drives I can back up
>>>>> to
>>>>> and I can't use the L:/ as the location.
>>>>>
>>>>> Any ideas?
>>>>>
>>>>> Thanks,
>>>>>
>>>>> Andrew Shuttleworth
>>>>>
>>>>> ---
>>>>> I tried \\DEVICE-NAME\share but was prompted for a password that I
>>>>> don't
>>>>> believe I have set. Perhaps something to do with the way the device
>>>>> was
>>>>> configured during the automatic setup ???
>>>>>
>>>>
>>>
>>>
>>
>
>