The Storage Team Blog about file services and storage features in Windows and Windows Server.
Beta testers using the file backup application in Windows Vista have complained about being prompted for a user name and password after they try to back up to a network share. It’s especially frustrating for users who know they already have access to the share. Though this behavior might seem like a bug, there’s a good reason why the prompt occurs: the backup application needs to store the user name and password for the share so that when the scheduled backup job runs, under the “LocalSystem” account, the backup application can use those credentials to access the share. If the backup application didn’t gather these credentials ahead of time, you would be prompted to enter them before each backup. (And I should mention that if the password changes at some point, you’ll need to re-enter the credentials in the backup settings or else the next backup will fail, and the resulting error message will then link you to a UI that lets you update the backup configuration.)
Speaking of backing up to network shares, there is another requirement you should be aware of: the credentials you supply must have what is called “Full Control” to the target share, also known as “Co-owner” of the share if you use the setup wizard in Windows Vista. This means that both the file system permissions and share permissions must be set to Full Control for the user name you specify in the backup. To help maintain the security of the backup location, we recommend that you set up a user account to be used only by the backup application, and then set permissions on the share and folder so that only your “backup user” account can access it. That account can be a local account on the computer where you host the network share, or it can be a domain account. It does not have to be the administrator account on that computer.
And finally, we want to call out two specific issues with backing up to a share on a computer running Windows XP:
--Jill (with help from Dan Stevenson and Ivan Pashov)
that's for this info... I have one other queiston about backups and NTFS EFS I have potsed on the newsgroups and other blogs with no answer... I'll post below... Thanks for any info on it
The biggest and most surprising to me is that encrypted files don’t get backed up. And there is no warning of this. So if you encrypt a folder the files just get skipped. This is NOT GOOD. As people will think files are getting backed up when they are not.
With the new “ZIP” type format MS is using although nice is some ways, doesn’t seem like it could keep the EFS files encrypted, which is why they probably skip them. This is a huge flaw! I think vista needs the old ntbackup put back in for power users.
Another thing is you can’t specify the paths you want to backup anymore, you just get these vague file types, our company partitions all our drive to C and D and all user data is on D. There doesn’t seem to be away to point the
new backups at the drives and paths we want. What I would like to see is the NTbackup put back in, for those who know how to use it and already use it in XP. The new system is nice for the very dumb, but not for the power user. And the EFS thing needs to be addressed.
PingBack from http://www.msblog.org/2006/09/29/using-network-shares-as-targets-for-the-file-based-backup-tool-in-windows-vista/
Yes I second that..please allow/add an option to backup encrypted NTFS files... and specify paths too....
[Last updated 1/24/07] The new File Backup is too simple. Why didn’t you add more features, such as location-based
[Last updated 1/30/07] On Windows Vista, how can I restore a .bkf backup made using NTBackup in Windows
Windows Server 2008 brings the successor to ye old NTBackup. The role that can be installed separately
PingBack from http://eknowlogy.com/blogs/andylalaguna/archive/2008/07/08/so-where-will-windows-2008-hyper-v-server-run.aspx