If user trying to use an Advanced Format drive (4K sectors) with win7 or Server 2008 R2 Backup and format the drive using Disk Management as normal. Windows will create a partition on the drive that is 4K aligned, When set up a scheduled backup and specify that using this drive for backups only. Windows Backup then re-formats the drive for it's use. However Windows Backup will no t recognize the drive as a valid backup destination.

cause:When Windows Vista and Server 2008 were released, Microsoft turned its back on tape backup. The built-in backup utility only backs up to hard drives. Windows 7 and Server 2008 R2 continue this policy. The recommended strategy for Small Business Server 2008 and 2011, for example, is to have a bunch of external USB drives and to use them in rotation.

Windows Server Backup, and its command-line version wbadmin, work well enough, but users with growing storage requirements have been buying larger external drives. That seems fine: external USB drives with 2TB and 3TB capacities are now commonplace. Except that they often run into problems when used with Windows Server Backup. You might see error 2155348010 or 0x8078002A, or “The request could not be performed because of an I/O device error”, or some other error.

The reason is that most of these large drives have a 4K sector size, rather than the older 512 byte sector size. You can get a patch for Windows 7 and Windows Server 2008 R2 that fixes most problems, but it does not fix the backup issue.

The further reason is that Windows Server Backup uses VHD virtual drives as its file format. The VHD format presumes the use of 512byte sectors, and the drivers that read and write data are optimised for this. You cannot create or mount VHDs on a disk with 4K sectors.

you can use fsutil command to check the hard disk (H disk) sector information

C:\Windows\system32>fsutil fsinfo ntfsinfo H:

Bytes Per Sector  :               4096
Bytes Per Physical Sector :       <Not Supported>
Bytes Per Cluster :               4096
Bytes Per FileRecord Segment    : 4096

Solution For Western digital 4k Drive

Some drives have a firmware option to emulate 512byte sectors. These drives work, but with a performance penalty. Western Digital is one such, and you have a WD drive you may be in lucky, it is still possible to use a 2.5 TB drive or larger with Windows 7 or server 2008 Backup and Restore, as long as you don't need to use the drive with Windows XP. Using the WD Quick Formatter tool (See attachment), select the "Most Compatible (Vista or later required)" configuration to reformat the drive.

after format, now you can use fsutil command to check the hard disk (H disk) sector information

C:\Windows\system32>fsutil fsinfo ntfsinfo H:

Bytes Per Sector  :               512
Bytes Per Physical Sector :       <Not Supported>
Bytes Per Cluster :               4096
Bytes Per FileRecord Segment    : 1024

Solution For Seagate 4k Drive

No solution currently

Solution For Win8 or Windows server 2012

Windows Server 8 introduces the .VHDX format which both supports larger drives, and also fixes the issues with 4K sector sizes. 

The reason of backup to a network share command fails because we have the SQL Server service running as Local System account, it cannot access any network resources.

In order to allow SQL to backup directly to a network share, we have to run the SQL Server service as a domain network account which does have access to network resources.

Edit the properties of the SQL Server service and on the Log On tab, configure the service to run as an alternate account which has network access rights.

When you click OK, you will get a prompt that the settings will not take effect until the service is restarted.

Restart the service.

The services list should now show the SQL Server service is running as the account you configured.

Now you can backup MSSQL Database to the network share.

If you want to log the progress of the file copy or got error message (insufficient memory)from xcopy command, you should explore the use of "ROBOCOPY"

Robocopy (Robust File Copy) is a command-line file copy utility in Windows Vista. Until Vista, Robocopy was a part of Windows Resource Kit Tools as a free download (http://www.microsoft.com/downloads/details.aspx?FamilyID=9D467A69-57FF-4AE7-96EE-B18C4790CFFD&displaylang=en. Unlike normal copy commands, Robocopy is designed for reliable copy or mirroring while maintaining the permissions, attributes, owner information, timestamps and properties of the objects copied. 

Syntax:

ROBOCOPY <source> <destination> [file…] [options]

Examples:
1. To copy contents of C:\UserFolder to C:\FolderBackup: 
     Robocopy C:\UserFolder C:\FolderBackup 
    This is the simplest usage for Robocopy 

2. To copy all contents including empty directories of SourceFolder to DestinationFolder: 
    Robocopy C:\SourceDir C:\DestDir /E 

3. Copy files from one computer to another, skipping files already in the destination. 
     ROBOCOPY \\Computer1\reports \\Computer2\backup *.doc /S 

4. List only files larger than 32 MBytes(33553332 bytes) in size. 
    Robocopy.exe c:\sourceFolder d:\targetfolder /min:33553332 /l 
    List only files less than 32 MBytes(33553332 bytes) in size. 
    Robocopy.exe c:\sourceFolder d:\targetfolder /max:33553332 /l 

Note: /l - will list files matching the criteria. if /l is omitted, files matching the criteria will be copied to the taget location 

5. Move files over 14 days old (note the MOVE option will fail if any files are open and locked). 
    ROBOCOPY C:\SourceFoldern D:\DestinationFolder /move /minage:14 
    Similarly you could use the below switches
     /maxage: <N> Specifies the maximum file age (to exclude files older than N days or date).
     /minage: <N> Specifies the minimum file age (exclude files newer than N days or date).
     /maxlad: <N> Specifies the maximum last access date (excludes files unused since N).
     /minlad: <N> Specifies the minimum last access date (excludes files used since N) If N is less than 1900, N specifies the number of days. Otherwise, N specifies a date in the format YYYYMMDD 

6. /MIR is an option to ROBOCOPY where you mirror a directory tree with all the subfolders including the empty directories and you purge files and folders on the destination server that no longer exists in source. 
    ROBOCOPY \\sourceserver\share \\destinationserver\share /MIR 
    Or 
    ROBOCOPY source-drive:\DIR destination-drive:\DIR /MIR 

7. The following command will mirror the directories using Robocopy: 
    Robocopy \\SourceServer\Share \\DestinationServer\Share /MIR /FFT /Z /XA:H /W:5 
    /MIR specifies that Robocopy should mirror the source directory and the destination directory. Note that this will delete files at the destination if they were deleted at the source.
     /FFT uses fat file timing instead of NTFS. This means the granularity is a bit less precise. For across-network share operations this seems to be much more reliable - just don't rely on the file timings to be completely precise to the second.
     /Z ensures Robocopy can resume the transfer of a large file in mid-file instead of restarting.
     /XA:H makes Robocopy ignore hidden files, usually these will be system files that we're not interested in.
     /W:5 reduces the wait time between failures to 5 seconds instead of the 30 second default. 

8. Use Robocopy to copy all changes to files in a directory called c:\data to a directory that contains the date, like data_20091124. Create a batch file as follows. 
    @echo off 
    set day=%date:~0,2% 
    set month=%date:~3,2% 
    set year=%date:~6,4% 
    Robocopy "c:\data" "c:\backup\data\%day%-%month%-%year%\" /MAXAGE:1 
     
9. To mirror the directory "C:\directory" to "\\server2\directory" excluding \\server2\directory\dir2" from being deleted (since it isn't present in C:\directory) use the following command: 
    Robocopy "C:\Folder" "\\Machine2\Folder" /MIR /XD \\server2\ directory\dir2" 
    Robocopy can be setup as a simply Scheduled Task that runs daily, hourly, weekly etc. Note that Robocopy also contains a switch that will make Robocopy monitor the source for changes and invoke synchronization each time a configurable number of changes has been made. This may work in your scenario, but be aware that Robocopy will not just copy the changes, it will scan the complete directory structure just like a normal mirroring procedure. If there are a lot of files & directories, this may hamper performance. 

10. You have copied the contents from source to destination but now you made changes to the Security permissions at source. You wanted to copy only the permission changes and not data. 
     ROBOCOPY <Source> <Target> /E /Copy:S /IS /IT 

Copy option have the following flags to use:
     D Data 
     A Attributes 
     T Time stamps
     S NTFS access control list (ACL)
     O Owner information
     U Auditing information
     The default value for CopyFlags is DAT (data, attributes, and time stamps). 
    /IS - Includes the same files.
     /IT - Includes "tweaked" files.

11. To copy a directory tree along with the source timestamps for folders 
    Robocopy C:\Folder1 C:\Folder2 /MIR /dcopy:T 

12. To copy a directory name contains space to my NASdrive using quotes,excluding the folder name contains "backup" and "download",excluding the file name contains "*.bak",newer than 2015-01-06

    Robocopy "\\server\my files"  "\\NAS\My Document" /E /XD backup download /XF *.bak /MAXAGE:20150106

Taking ownership of system files or folders in Windows is not a simple task. Whether you use the GUI or the command line, it takes far too many steps. This method works in Windows Vista, 7, 8, and 8.1, and it maybe works in XP, though you won’t need it there.

Thankfully somebody created a registry hack that will give you a menu item for “Take Ownership” that will handle all the steps for you. We found this many years ago, and since then it’s been hosted here for everybody to use.

Here’s what the new right-click menu will look like after installing this registry hack. If you are in Windows 8 or 8.1, the little shield won’t show up, but it’ll work just fine.

Install

Download Take Ownership.zip and unzip the files contained in the zipfile. Double-click the InstallTakeOwnership.reg file and click through the prompts. No reboot necessary.

Uninstall

Double-click the RemoveTakeOwnership.reg file and click through the prompts. No reboot necessary.

see attachment!

1.     Install windows normally or windows has been installed.

2.     Log in to windows, write down the system drive letter and the target drive letter (if your system has more than 1 physic drive, the drive letter could be difference when you boot with optical drive), eg,system drive letter is c and target drive letter is d.

3.     Boot from Windows installation disk.

4.     Get into the command prompt by clicking "repair".

5.     Use robocopy to copy c:\users to d:\users (make sure the system drive letter is not changed and target driver letter is not changed). The command line should be: 
robocopy c:\users d:\users /mir /xj /copyall
if system letter is changed from c to d and target letter is changed from d to e then 
robocopy d:\users e:\users /mir /xj /copyall

6.     Verify all files copied successfully.

7.     Delete c:\users. Command line should be: 
rmdir /s /q c:\users
if system letter is changed from c to d: and target letter is changed from d to e: then 
rmdir /s /q d:\users
mkdir d:\users (make a user folder at d disk)

8.     Create junction to new Users directory. Command line should be:(no matter what driver letter is you must link the system drive letter to the target drive letter)
mklink /j c:\users d:\users

9.     Restart computer.

To load the firmware, you can use only the top port usb back of the cabinet. Other inactive (this is important).

1 Insert usb stick with the firmware restoration in the upper port usb. Enable power button NAS device

2 Wait for the download to the error that there is no disk (if the error was originally)

3 Press the power button and wait for it to NAS device is turned off.

4 Press a thin tool (eg toothpick) reset button and hold it down, press the power button once the device NAS.

5 Expect activity signal indicator usb stick after start flashing Remove "toothpick" from the reset button.

6 Wait for the end of the firmware restoration

(!!!!!Warning!!!!!NAS auto OFF).

WARNING !!! Potential problems can be if usb stick not found in bios NAS. So there is NOT REMOVE out usb stick, several times to enable, disable, enable NAS

Ref Link: http://forum.nas-central.org/viewtopic.php?f=285&t=15911           Download the USB Boot Recovery Tools 

To resolve the problem, I did these three commands from PE or boot from windows disc enter the command line,

which resolved my problem: 

c:\windows\system32\bcdedit /set {default} device partition=c:
c:\windows\system32\bcdedit /set {default} osdevice partition=c:
c:\windows\system32\bcdedit /set {bootmgr} device partition=c:  //not applied for windows server 2008

the fault reason cause by the system booted with another new hard drive or USB disk that is formatted as HDD mode

diagnostic disc should use floppy,zip or CD, DVD media,when use USB dongle, it must be formatted as FDD,ZIP not hdd mode to avoide this fault.