Hi all, need your kind help, thanks.

Enviroment is Windows Server 2012 R2 Standard  6.3.9600 Build 9600 and Veritas cluster implemented, after online windows update, the windows server backup function cannot work.

Whenever enter the backup UI or using the wbadmin CLI, I got error message as below:

A Volume Shadow Copy Service operation error has occurred: <0x80042401>

"There are too few disks on this computer or one or more of the disks is too small. Add or change disks so they match the disks in the backup, and try the restore again.

Hello,

we using workfolders on over 5000 clients - the problem is, that neither the IT department nor the user has a fast possibility to monitor the last state of a workfolders sync.

we know about the view in the control panel -> workfolders... but tell this to the users (#eyerolling)

we want to determine the state by script (powershell, vbs) or registry query and than show a popup on the screen.

how can we achieve this? we found registry keys under "HKEY_CURRENT_USER\Software\Classes\Local Settings\Software\Microsoft\Windows\CurrentVersion\WorkFolders\Partnership\Microsoft.SyncShare.UserData" called "LastSuccessfulSyncTime" and "LastSyncHResult". we can translate the date/time but the "LastSyncHResult" stays at value "0" even if there are file errors and the sync is red/yellow in the control panel.

any help/ideas are appreciated.

thanks in advance!

Hi,

I'm taking a closer look at 2 seemingly similar commands : VSSADMIN andDISKSHADOW. I'm scratching my head a bit, because most of other commands do different tasks. But if you take a look, what is the difference between those:

vssadmin create shadow and diskshadow create/delete/revert.

Vssadmin create shadow

Vssadmin list shadows

Vssadmin delete shadows

Diskshadow:

list writers list shadows list providers

delete shadows

reverthttps://docs.microsoft.com/en-us/windows-server/administration/windows-commands/vssadmin

https://docs.microsoft.com/en-us/windows-server/administration/windows-commands/diskshadow

They at least seem to do exactly the same thing. Diskshadow has some extra options the other does not have. Can somebody just explain this in plain language?

Thank you

We have a strange issue with a new Server 2019 file server where the Search service stops working properly until restarted. The issue is as follows...

When users search the results all have blank icons and double clicking on them doesn't launch the file/app. This is company wide on all computers (Win10 Pro).



Restarting the Windows Search service resolves the issue and search works for all users...

I noticed that when in a failed state if i go to the Indexing Options on the Server it only shows Internet Explorer History but if i restart the Windows Search service all the other included locations then appear in the list.

So far I have tried installing all Windows updates and rebuilding the Search index but the same issue occurs. Nothing in the even logs seem to relate to this issue. The server does have the MS Filter Pack Installed.

Any ideas or anyone else getting this issue?

Hi,

Some of my users complain that when they have an office file open (excel) and they move to another floor (switching to another wifi AP) they can no longer save the file, it becomes read-only, and they are forced to save-as with another name. The files are on a shared file server. I've found some old threads on the internet, but this is happening on recent Windows 10 client machines with Office 365 Pro+. The file server is in our data center.

Any hints to help me troubleshoot this ?

Stephane

Stephane

Hi There, 

Need some insight.

Users remote login to few computers. From those machines, They are unable to access Share through DFS Namespace. \\domain\dfsroot . They get access denied error.

However through File server UNC \\fileserver\path and with it's IP, They can access. I'm the Domain Admin however I get the same error from those Machines. They have the proper permission to those folders.

From their windows 7 work laptops they can access fine. But when they RDP to few machines They have this problem. Problematic machines have Windows 2012 R2 server.

* Windows server 2012 R2 machine is in AWS Cloud. Users can access from other Windows 2012 R2 server in the same IP range. (These Windows 2012 R2 machines do not run any server services. It was implemented for few users to access some restricted website I guess)

* I remember troubleshooting the same scenario in Windows 7 machines, It had ended up as Offline Sync folder issue.

This could even be a Sync Issue ? as this issue is just for one folder under that DFS Namespace. Rest of the other folders which under the same namespace can be accessible without any problem from the same problematic machine from those users.

For Example: 

\\contoso\Folder1 ----> Inaccessible

\\contoso\Folder2 ----> Accessible

\\contoso\Folder3----> Accessible

\\contoso\Folder4----> Accessible

\\contoso\Folder5----> Accessible

In the DFS service installed Server, Under that DFS namespace. I clicked on the problematic folder.

In the right pane, I have selected the one for which the referral status is "Enabled'--->Then "Open in Explorer". Usually this should open the UNC of file server \\fileserver\Folder1 , However in my case for that particular folder that local windows explorer is getting opened. 

Anybody have any idea ?

Hi all - 

Brand new Windows Server Essentials 2016 VM on Server 2019 Hyper-V, brand new Dell T340 - all SSD storage, very nice.

Windows Search is crapping out. Indexing about 600,000 items on two volumes, it works for a minute, and then searches return an unclickable list of files with white generic icons and no data. Restarting the service works for a while. I've reindexed a bunch.

Any thoughts or ideas? Thanks!

Good day

Im building a dfs setup and have hit a snag. Enduser are able to view folders and files they shouldn't be. I have enabled Access base enumeration on namespace. is there a way to make sure the permissions set on folders are respected?

Thanks

We've had some varied issues with some workstations on 1903 not allowing sync to take place. Some of these workstations came with 1903 out of the box new and some were upgraded from 1809 to 1903. The error I have been seeing is "Sync failed. Work Folders path: ...; Error: (0x80c80314) The Work Folders path has to be encrypted. You might have an application holding the Work Folders folder open or the folder might be compressed. Close File Explorer and any open files or apps, and check the folder Advanced properties to ensure that the folder is not compressed."

I've verified that the folder is not compressed and not opened. At first it seemed to be impacting all of the 1903 workstations we had but then it seemed like some of them had the issue cleared up. Looking at it further, I found that some just needed credentials updated.

I verified on the ones still having an issue, that we can use EFS to encrypt another folder successfully.

My test VM upgrades with Work Folders enabled and is updated to 1903 without issue other than reauth'ing Work Folders.

Hi,

Just wanted to check, if I want to use VSS on a volume -  ReFS or otherwise it has a 64TB max size??

I can't find anywhere that specifically notes the limits for ReFS volumes, so assume this applies.

Would be great if larger volumes are supported.

Thanks

I have recently upgraded a clients servers to Windows Server 2012 & since doing so have lost the ability to scan to folder.

Both servers are domain controllers and previously on a 2008 domain controller I would have had to make the following change to allow scan to folder:
 Administrative Tools
 Server Manager
 Features
 Group Policy Manager
 Forest: ...
 Default Domain Policy
Computer configuration
 Policies
 Windows Settings
 Security Settings
 Local Policies
 Security Options
 Microsoft Network Server: Digitally Sign Communications (Always)
 - Define This Policy
 - Disabled

However I have applied this to the Windows 2012 server but am still unable to scan, possibly due to added layers of security in server 2012. The error on the scanner is Authentication with the destination has failed check settings.
I have also tried the following at the server:
Policies -> Security Policies
Change Network Security: LAN Manager authentication level to: Send LM & NTLM - Use NTLMv2 session security if negotiated.
Network security: Minimum session security for NTLM SSP based (including secure RPC) clients and uncheck the require 128 bit.
Network security: Minimum session security for NTLM SSP based (including secure RPC) servers and uncheck the require 128 bit
I have created a user account on the server for the ricoh and set this in the settiings of the Ricoh and verified everything is correct.

Are there any other things I have missed?

Dear All,

I want to configure block all file types in file screening and allow only custom file types.

please help me.

SUNIL PATEL SYSTEM ADMINISTRATOR

Hi Team,

We create a share folder & mapped as a network drive. Now, we want this mapped drive show in every system when we logged in via "test" domain user. Could someone please advise how this can be possible ?

Hi,

problems with WF encryption was discussed here many times before, but I think that now it's related to Windows 10 1903, because Windows 10 1809 is working fine.

Error message is still the same:

Sync failed. Work Folders path: C:\Users\MYUSER\Work Folders; Error: (0x80c80314) The Work Folders path has to be encrypted. You might have an application holding the Work Folders folder open or the folder might be compressed. Close File Explorer and any open files or apps, and check the folder's Advanced properties to ensure that the folder is not compressed. EventID 2100

I had tried Windows 10 1903 domain joined / not domain joined, followed tips on https://techcommunity.microsoft.com/t5/Storage-at-Microsoft/Troubleshooting-Work-Folders-on-Windows-client/ba-p/425627 but WF encryption is still failing.

Has anyone working WF on Windows 10 1903 with encryption enabled?

Best regards,

Jiri

Problem:

This error is periodically recorded in the System event log:

Event ID: 10000
Source: DistributedCOM
Event Data: Unable to start a DCOM Server: {9C38ED61-D565-4728-AEEE-C80952F0ECDE}. The error: "0" Happened while starting this command: C:\Windows\System32\vdsldr.exe -Embedding

This error appears when DFS-R is installed, when the computer is rebooted, every time the DFS-R service is started, and whenever application aware checkpoint-based backups are taken.

Simple reproduction steps:

1. On a clean computer or VM, boot from the Microsoft-provided Windows Server 2019 media. I used SW_DVD9_Win_Server_STD_CORE_2019_1809.1_64Bit_English_DC_STD_MLF_X22-02970.ISO from the Volume Licensing website.
2. Install Windows Server 2019
3. Install DFS-R using PowerShell: Install-WindowsFeature -Name FS-DFS-Replication
4. Error will now be present in Event Log: Get-EventLog -LogName System -EntryType Error -Source DCOM
5. Restarting the computer, or just restarting the DFS-R service, will cause another error to be added to the event log.

Notes:

• Problem affects Core and Desktop Experience
• Problem affects Standard and Datacenter
• As of 2020-Feb-28, installing Windows Updates doesn't make a difference
• Joining a domain, or not, makes no difference
• Properly configuring DFS Replication does not make a difference

Request:

This issue is related to another TechNet question, but there's no answer there.

I thinkit's ignorable, but I don't really know.  I would like to "fix" whatever is causing this error.  Or, at least get some authoritative comments that it is safe to ignore, and preferably have someone at Microsoft correct the problem that is leading to an ignorable error.

Any and all help would be appreciated.  Thank you.

-Tony

Hello Every one,

I have a File Server (Windows Server 2012 R2) which has 3 Share Folders and these share folders are accessed over 100 users at a time what I want is to turn on delete and delete sub folders and files, whenever a users deletes a folder, sub folder and file.

I have looked at its group policy there is two options for this one isObject Access Policy and Second one is Audit File Share Policy Now which one should I use ???

As my understanding as I am setting this policy only for shares, So I must go with Audit File Share Policy, but still I need your kind suggestions.

Thanks

Hello guys,

I've got a file server running on Windows Server 2019 Standard Core and having quite a troublesome time with it. When a client is writing to the virtual disk via SMB those two issues appear:

Stage 1: Event 1020 SMBServer gets logged. This means the whole connection to the client is just cutting out for about two minutes. The share just becomes unavailable for the client, meaning no reads or writes go through anymore.  This issue happens approx. five times a day.

File system operation has taken longer than expected.

Client Name: \\192.168.179.11
Client Address: 192.168.179.11:58364
User Name: FILE01\Administrator
Session ID: 0xB40014000055
Share Name: \\*\D$
File Name: *filename*
Command: 9
Duration (in milliseconds): 100779
Warning Threshold (in milliseconds): 15000

Guidance:

The underlying file system has taken too long to respond to an operation. This typically indicates a problem with the storage and not SMB.

Stage 2: Sometimes it even gets worse. A couple of Event 312 StorageSpaces-Driver are getting logged. This results into a complete unmount of the virtual disk. As a "workaround" I've written a script that automatically remounts the virtual disk on an Event 312. The share is unavailable for about fifteen minutes and all ongoing writes are lost. This issue is happening 2-3 times a week. I think it's happening when there are too many writes in a row. For example writing a 100 GB to the server with full 1GBit speed will for sure trigger this issue. As another "workaround" I'm limiting the write speed to the share on the client-side.

Virtual disk {7987cc19-b41b-4297-b0ea-4046b7464f74} has failed a write operation to all its copies.                  
You can online the disk by using the following commands in PowerShell:                  
Get-VirtualDisk | ?{ $_.ObjectId -Match "{7987cc19-b41b-4297-b0ea-4046b7464f74}" } | Get-Disk | Set-Disk -IsReadOnly $false                  
Get-VirtualDisk | ?{ $_.ObjectId -Match "{7987cc19-b41b-4297-b0ea-4046b7464f74}" } | Get-Disk | Set-Disk -IsOffline  $false

Specs:

• Windows Server 2019 Standard Core
  
• Supermicro CSE-846 (24 bay with Expander Backplane)
• Supermicro X9DRi-LN4F+
• 2 x Intel Xeon E5-2609
• 64 GB RAM
• Adaptec HBA 1100 1100-4i

I have a single virtual disk configured as parity with four columns. The server is mainly accessed only by two clients. A CentOS 8 sever and a Windows 10 machine. The issue appears with both clients.

PS C:\Users\Administrator> Get-StoragePool | fl


ObjectId                          : {1}\\FILE01\root/Microsoft/Windows/Storage/Providers_v2\SPACES_StoragePool.ObjectId
                                    ="{915a2771-c33c-11e9-8be8-806e6f6e6963}:SP:{0c929b5d-5e78-427c-a3d3-9260c80dad56}"
PassThroughClass                  :
PassThroughIds                    :
PassThroughNamespace              :
PassThroughServer                 :
UniqueId                          : {0c929b5d-5e78-427c-a3d3-9260c80dad56}
AllocatedSize                     : 75909520424960
ClearOnDeallocate                 : False
EnclosureAwareDefault             : False
FaultDomainAwarenessDefault       : PhysicalDisk
FriendlyName                      : Pool01
HealthStatus                      : Healthy
IsClustered                       : False
IsPowerProtected                  : True
IsPrimordial                      : False
IsReadOnly                        : False
LogicalSectorSize                 : 4096
MediaTypeDefault                  : Unspecified
Name                              :
OperationalStatus                 : OK
OtherOperationalStatusDescription :
OtherUsageDescription             :
PhysicalSectorSize                : 4096
ProvisioningTypeDefault           : Fixed
ReadOnlyReason                    : None
RepairPolicy                      : Parallel
ResiliencySettingNameDefault      : Mirror
RetireMissingPhysicalDisks        : Auto
Size                              : 103006267768832
SupportedProvisioningTypes        : {Thin, Fixed}
SupportsDeduplication             : True
ThinProvisioningAlertThresholds   : {70}
Usage                             : Other
Version                           : Windows Server 2019
WriteCacheSizeDefault             : Auto
WriteCacheSizeMax                 : 18446744073709551614
WriteCacheSizeMin                 : 0
PSComputerName                    :

ObjectId                          : {1}\\FILE01\root/Microsoft/Windows/Storage/Providers_v2\SPACES_StoragePool.ObjectId
                                    ="{915a2771-c33c-11e9-8be8-806e6f6e6963}:SP:{915a2770-c33c-11e9-8be8-806e6f6e6963}"
PassThroughClass                  :
PassThroughIds                    :
PassThroughNamespace              :
PassThroughServer                 :
UniqueId                          : {915a2770-c33c-11e9-8be8-806e6f6e6963}
AllocatedSize                     : 103015394574336
ClearOnDeallocate                 : False
EnclosureAwareDefault             : False
FaultDomainAwarenessDefault       : PhysicalDisk
FriendlyName                      : Primordial
HealthStatus                      : Healthy
IsClustered                       : False
IsPowerProtected                  : False
IsPrimordial                      : True
IsReadOnly                        : False
LogicalSectorSize                 :
MediaTypeDefault                  : Unspecified
Name                              :
OperationalStatus                 : OK
OtherOperationalStatusDescription :
OtherUsageDescription             :
PhysicalSectorSize                :
ProvisioningTypeDefault           : Fixed
ReadOnlyReason                    : None
RepairPolicy                      : Parallel
ResiliencySettingNameDefault      : Mirror
RetireMissingPhysicalDisks        : Auto
Size                              : 103135725436928
SupportedProvisioningTypes        : {Thin, Fixed}
SupportsDeduplication             : True
ThinProvisioningAlertThresholds   : {70}
Usage                             : Other
Version                           : Windows Server 2019
WriteCacheSizeDefault             : Auto
WriteCacheSizeMax                 : 18446744073709551614
WriteCacheSizeMin                 : 0
PSComputerName                    :

PS C:\Users\Administrator> Get-VirtualDisk | fl


ObjectId                          : {1}\\FILE01\root/Microsoft/Windows/Storage/Providers_v2\SPACES_VirtualDisk.ObjectId
                                    ="{915a2771-c33c-11e9-8be8-806e6f6e6963}:VD:{0c929b5d-5e78-427c-a3d3-9260c80dad56}{
                                    7987cc19-b41b-4297-b0ea-4046b7464f74}"
PassThroughClass                  :
PassThroughIds                    :
PassThroughNamespace              :
PassThroughServer                 :
UniqueId                          : 19CC87791BB49742B0EA4046B7464F74
Access                            : Read/Write
AllocatedSize                     : 56927107153920
AllocationUnitSize                : 268435456
ColumnIsolation                   : PhysicalDisk
DetachedReason                    : None
FaultDomainAwareness              : PhysicalDisk
FootprintOnPool                   : 75904957022208
FriendlyName                      : vDisk01
HealthStatus                      : Healthy
Interleave                        : 262144
IsDeduplicationEnabled            : False
IsEnclosureAware                  : False
IsManualAttach                    : False
IsSnapshot                        : False
IsTiered                          : False
LogicalSectorSize                 : 4096
MediaType                         : Unspecified
Name                              :
NameFormat                        :
NumberOfAvailableCopies           :
NumberOfColumns                   : 4
NumberOfDataCopies                : 1
NumberOfGroups                    : 1
OperationalStatus                 : OK
OtherOperationalStatusDescription :
OtherUsageDescription             :
ParityLayout                      : Rotated Parity
PhysicalDiskRedundancy            : 1
PhysicalSectorSize                : 4096
ProvisioningType                  : Thin
ReadCacheSize                     : 0
RequestNoSinglePointOfFailure     : False
ResiliencySettingName             : Parity
Size                              : 65970697666560
UniqueIdFormat                    : Vendor Specific
UniqueIdFormatDescription         :
Usage                             : Data
WriteCacheSize                    : 33554432
PSComputerName                    :

PS C:\Users\Administrator> Get-PhysicalDisk

DeviceId FriendlyName              SerialNumber    MediaType CanPool OperationalStatus HealthStatus Usage          Size
-------- ------------              ------------    --------- ------- ----------------- ------------ -----          ----
10       ATA TOSHIBA DT01ACA3      535T1SYYS       HDD       False   OK                Healthy      Hot Spare   2.73 TB
9        ATA WDC WD100EMAZ-00      JEK2JYYZ        HDD       False   OK                Healthy      Auto-Select  9.1 TB
16       ATA WDC WD60EZRZ-00G      WD-WXN1H844JV54 HDD       False   OK                Healthy      Auto-Select 5.46 TB
5        ATA WDC WD100EMAZ-00      JEHLDU2X        HDD       False   OK                Healthy      Auto-Select  9.1 TB
14       ATA TOSHIBA DT01ACA3      69KAV9MAS       HDD       False   OK                Healthy      Auto-Select 2.73 TB
1        ATA TOSHIBA DT01ACA3      18F94WVAS       HDD       False   OK                Healthy      Auto-Select 2.73 TB
15       ATA WDC WD60EZRZ-00G      WD-WX21DA5FNJ2J HDD       False   OK                Healthy      Auto-Select 5.46 TB
11       ATA WDC WD60EZRZ-00R      WD-WX21DB509FD4 HDD       False   OK                Healthy      Auto-Select 5.46 TB
0        Samsung SSD 840 EVO 120GB S1D5NSAF203917B SSD       False   OK                Healthy      Auto-Select ...9 GB
6        ATA TOSHIBA DT01ACA3      X384UVNGS       HDD       False   OK                Healthy      Auto-Select 2.73 TB
7        ATA WDC WD60EZRZ-00G      WD-WXB1HB4U9486 HDD       False   OK                Healthy      Auto-Select 5.46 TB
4        ATA WDC WD60EZRZ-00G      WD-WX11DC57SHUK HDD       False   OK                Healthy      Auto-Select 5.46 TB
3        ATA WDC WD60EZRZ-00G      WD-WX11DC57S2ZE HDD       False   OK                Healthy      Auto-Select 5.46 TB
2        ATA TOSHIBA DT01ACA3      18F93URAS       HDD       False   OK                Healthy      Auto-Select 2.73 TB
17       ATA WDC WD100EMAZ-00      JEHR7YZZ        HDD       False   OK                Healthy      Auto-Select  9.1 TB
13       ATA WDC WD100EMAZ-00      JEK15YAZ        HDD       False   OK                Healthy      Auto-Select  9.1 TB
8        ATA WDC WD60EZRZ-00G      WD-WXN1H8494ELD HDD       False   OK                Healthy      Auto-Select 5.46 TB
12       ATA WDC WD60EZRZ-00G      WD-WX81D65D9803 HDD       False   OK                Healthy      Auto-Select 5.46 TB

What I've tried:

• Swapped the HBA
• Swapped all the RAM
• Removed and added physical disks
• Set IsPowerProtected to $true
• Set AdditionalCriticalWorkerThreads to 64
• and much more I can't remember...

Any help is very much appreciated :)

Recently, maybe within the last week, my Server 2016 installation has had extremely slow write speeds. I have two drives in my system. A SSD (C:) and an HDD (D:) and both have been generating Storage errors in the event log. Specifically StorDiag EventID 504, whenever a large files are being written (I've copied an example below). When observing the speeds of a large write, I can see that initially it's fine, but after a few seconds a major slow down takes place, and from then on the speed is very inconsistent. Such a write can generate 30 or more 504 errors. There are also associated errors in the NTFS log, such as Event ID 149 which says that IO failures have taken place (also copied below).

Because this is suddenly happening to both my drives simultaneously, I doubt its a driver issue or a hardware failure issue. My initial Google searches have only related the 504 errors to Card Readers and other removable media, but not disk drives. The 504 and 149 errors implies that write operations are failing, but I just can't see why. My system is fully upgraded, and the Windows reports that drives have the latest drivers. I'll include my system configuration below.

If anyone has an idea as to what my problem is or how to troubleshoot, I would really appreciate the help. Thank you.

--------

System Configuration:

OS Name            Microsoft Windows Server 2016 Datacenter
Version            10.0.14393 Build 14393
System Type        x64-based PC
Processor          Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz, 
                   3401 Mhz, 4 Core(s),8 Logical Processor(s)
BIOS Version/Date  American Megatrends Inc. 0301, 9/16/2011
SMBIOS Version     2.6
BIOS Mode          Legacy
Motherboard        ASUSTeK Computer INC.

Platform Role            Workstation
Secure Boot State        Unsupported
Installed Physical       Memory (RAM)   16.0 GB DDR3
Total Virtual Memory     18.3 GB
Available Virtual Memory 12.5 GB
Page File Space          2.38 GB

C Drive:                 Boot Drive
Model                    INTEL SSDSA2CW120G3 (SATA SSD)
Bytes/Sector             512
Size                     111.79 GB (120,031,511,040 bytes)
Free Space               44.94 GB (48,249,929,728 bytes)

D Drive:
Model                    ST2000DL003-9VT166 (SATA HDD)
Bytes/Sector             512
Size                     1.82 TB (2,000,396,321,280 bytes)
Free Space               746.33 GB (801,364,180,992 bytes)

-------------

StorDiag Event ID 504

Log Name:      Microsoft-Windows-Storage-ClassPnP/Operational
Source:        Microsoft-Windows-StorDiag
Date:          6/12/2019 00:53:30
Event ID:      504
Task Category: Class
Level:         Error
Keywords:      Device I/O control request
User:          computer\Administrator
Computer:      my.computer.net
Description:
Completing a failed IOCTL request.
Event Xml:<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"><System><Provider Name="Microsoft-Windows-StorDiag" Guid="{F5D05B38-80A6-4653-825D-C414E4AB3C68}" /><EventID>504</EventID><Version>1</Version><Level>2</Level><Task>200</Task><Opcode>101</Opcode><Keywords>0x800000040000000</Keywords><TimeCreated SystemTime="2019-06-12T04:53:30.284022800Z" /><EventRecordID>997253</EventRecordID><Correlation /><Execution ProcessID="1784" ThreadID="2336" /><Channel>Microsoft-Windows-Storage-ClassPnP/Operational</Channel><Computer>my.computer.net</Computer><Security UserID="S-1-5-21-4150441485-2800377868-2508223801-500" /></System><EventData><Data Name="DeviceGUID">{D393DD4A-6271-DA94-0AA1-DD1DE3F36251}</Data><Data Name="DeviceNumber">0</Data><Data Name="Vendor">NULL</Data><Data Name="Model">ST2000DL003-9VT166</Data><Data Name="FirmwareVersion">CC32</Data><Data Name="SerialNumber">            6YD0GE9Q</Data><Data Name="IrpStatus">0x80000011</Data><Data Name="IoctlControlCode">0x7c088</Data></EventData></Event> 

--------------

NTFS Event ID 149

In the past 3603 seconds we had IO failures.
This may indicate a failing disk.

           High latency IO count: 7
           Failed writes: 0
           Failed reads: 0
           Bad clusters relocated: 0

           Volume Id: {139daef3-0000-0000-0000-100000000000}
           Volume name: C:
           Is boot volume: true

I've been searching the web and have not been able to find a solid answer. Here is what I need to do

We have a file server that has 3 drives (E,F,G). I have been getting High IO alerts when backups have been running lately. I found the best practices article that states moving the copies to another volume can resolve these problems. So now my question:

If I created an H drive on the server with sufficient space, could I move the storage for the VSS on E,F, and G to the H drive? If so, how would access and aging be handled? would there be any issues restoring files via VSS using this method?