Volume shadow copies
Hi,
My server's hard disk partition (compressed NTFS) is of 1.5 TB and it has shared folders on it and Volume Shadow Copies were configured. for more than a year there has not been any problem with the shadow copies. But suddenly it stopped taking the Shadow
copies. The data size is now half of the total space. I have freed some space by deleting four oldest shadow copies. still there is no solution. Actual space allocated for shadow copies is 120GB.
Every day, it is scheduled to run at 1:00PM. In the Event Viewer, I have these messages
1. At 1:00:55PM, The Volume Shadow Copy service entered the running state.
2. At 1:00:55PM, The Microsoft Software Shadow Copy Provider service entered the running state.
3. At 1:05:45PM, The Volume Shadow Copy service entered the stopped state.
4. At 1:05:45PM, The Microsoft Software Shadow Copy Provider service entered the stopped state.
But if I run the scheduled task, the task is running.
What could be the reason? Please suggest.
But I have not defragmented the drive. also, I have all the shadow copies safe.
Yesterday I have manuall run the task which was automatically created in the Task Scheduler as a result of Shadow copy settings. It run just fine.
But the task is not initiating as per schedule.
Please suggest if any thing else is causing not to run the scheduled task after has VSS Service started.
Thanks,
Ravi Sekhar Modukuru
Similar Messages
-
Configuring Volume Shadow Copies in Windows Server 2012 R2 Core
Hello,
I have a File Server under Windows Server 2012 R2 Core under a Lab Environment, I am trying to configure the Volume Shadow Copy on it, I tried to remote to its Disk Management via Computer Management but couldn't find the configuration for it.
Any Ideas?
For God, and Country.Hi Sheen Lim,
As far as I know we can use cmdlets to manage the volume shadow copy in server core but can not use the server manager remotely. You can refer the following third party article
to enable the VSS.
Configure Shadow Copies on Server Core
http://blogs.msmvps.com/ad/blog/2008/08/12/configure-shadow-copies-on-server-core/
I’m glad to be of help to you!
*** This response contains a reference to a third party World Wide Web site. Microsoft is providing this information as a convenience to you. Microsoft does not control these
sites and has not tested any software or information found on these sites; therefore, Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there. There are inherent dangers in the use
of any software found on the Internet, and Microsoft cautions you to make sure that you completely understand the risk before retrieving any software from the Internet. ***
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected] -
Hi,
New to 2012 and implementing a clustered environment for our File Services role. Have got to a point where I have successfully configured the Shadow copy settings.
Have a large (15tb) disk. S:
Have a VSS drive (volume shadow copy drive) V:
Have successfully configured through Windows Explorer the Shadow copy settings.
Created dependencies in Failcover Cluster Server console whereby S: depends on V:
However, when I failover the resource and browse the Client Access Point share there are no entries under the "Previous Versions" tab.
When I visit the S: drive in windows explorer and open the Shadow copy dialogue box, there are entries showing the times and dates of the shadow copies ran when on the original node. So the disk knows about the shadow copies that were ran on the
original node but the "previous versions" tab has no entries to display.
This is in a 2012 server (NOT R2 version).
Can anyone explain what might be the reason? Do I have an "issue" or is this by design?
All help apprecieated!
Kathy
Kathleen Hayhurst Senior IT Support AnalystHi,
Please first check the requirements in following article:
Using Shadow Copies of Shared Folders in a server cluster
http://technet.microsoft.com/en-us/library/cc779378(v=ws.10).aspx
Cluster-managed shadow copies can only be created in a single quorum device cluster on a disk with a Physical Disk resource. In a single node cluster or majority node set cluster without a shared cluster disk, shadow copies can only be created and managed
locally.
You cannot enable Shadow Copies of Shared Folders for the quorum resource, although you can enable Shadow Copies of Shared Folders for a File Share resource.
The recurring scheduled task that generates volume shadow copies must run on the same node that currently owns the storage volume.
The cluster resource that manages the scheduled task must be able to fail over with the Physical Disk resource that manages the storage volume.
If you have any feedback on our support, please send to [email protected] -
Does deduplication and Volume Shadow Copy work together?
Hi!
I have a fileserver with five 2TB-disks on it on a 2012 R2 server. I want to enable dedup on it that according to DDPEval.exe would save ~40%. I would also like to enable Volume Shadow Copies on the volumes so the the end user easily could restore removed
files and folders.
I have not found anything from microsoft about use both these features on the same volume, is it supported?
I have done some searching and found that for some users the say that dedup would change so much on the snapshots that it have to delete older snapshots, even though not much data have changed, the dedup force VSC to delete old snapshots.
Any experience with these features co-located on the same volume? Do I need to choose just one of them to use on my volumes?
Thanks!Hi,
Based on my research, the Shadow Copy and Deduplication could be used together in a Windows Server 2012 R2. The deletion of the old snapshots could be due to the Volume for which the shadow copy being created is more than 64 TB. Volume Shadow Copy Service supports
a volume size of up to 64 TB.
For more detailed information, you could refer to the article below:
Windows 2012 R2 Data Deduplication Leverages Shadow Copies: “LastOptimizationResultMessage : A volume shadow copy could not be created or was unexpectedly deleted”.
https://workinghardinit.wordpress.com/2014/07/01/windows-2012-r2-data-deduplication-leverages-shadow-copies-lastoptimizationresultmessage-a-volume-shadow-copy-could-not-be-created-or-was-unexpectedly-deleted/
Please Note: Microsoft is providing this information as a convenience to you. The sites are not controlled by Microsoft. Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there. Please
make sure that you completely understand the risk before retrieving any suggestions from the above link.
Best Regards,
Mandy
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected] -
During the restore of data using VSS Snapshots it deleted all the snapshots, this event was written in the system log :
The shadow copies of volume D: were deleted because the shadow copy storage could not grow in time. Consider reducing the IO load on the system or choose a shadow copy storage volume that is not being shadow copied.
It only restored 20 GB of data and there should be plenty of space in the Shadow copy storage
Used Shadow Copy Storage space: 2.692 GB (0%)
Allocated Shadow Copy Storage space: 5.397 GB (0%)
Maximum Shadow Copy Storage space: 694.752 GB (18%)
When there isn't enough space it should start to delete the oldest snapshots to free up additional space, but it deleted
all the snapshots. The problem is the IO but how to prevent this from happening again?Hi,
Since the shadow copy storage space doesn’t run out, the issue could be due to the Volsnap.sys driver has encountered excessive I/O activity.
You could refet to the article below to resolve the issue. This article is for Windows 2003 but it will also help on Windows 2008 R2 system.
Error message when a Windows Server 2003-based computer has a high level of I/O activity: "The shadow copies of volume Volume_Name were aborted because the diff area file could not grow in time"
http://support.microsoft.com/kb/925799
Best Regards,
Mandy
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place. -
2 Cluster Shared Volumes filling up with shadow copies and I can't delete them.
three node Server 2012 R2 cluster
2 CSVs
Veeam Backup software v7
We've been running out of space on our CSVs. I determined that the hidden System Volume Information directory is huge. It is huge because of large VSS files in the directory.
Path to CSVs
c:\ClusterStorage\Volume1
c:\ClusterStorage\Volume2
===========================================================================
List of VSS providers
vssadmin list providers
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2013 Microsoft Corp.
Provider name: 'SmVssProvider'
Provider type: Hardware
Provider Id: {24e4e8a3-69cb-4370-8b7b-c5276cd49765}
Version: 11.10.0001
Provider name: 'Microsoft CSV Shadow Copy Helper Provider'
Provider type: Software
Provider Id: {26d02d81-6aac-4275-8504-b9c6edc5261d}
Version: 1.0.0.1
Provider name: 'Microsoft CSV Shadow Copy Provider'
Provider type: Software
Provider Id: {400a2ff4-5eb1-44b0-8a05-1fcac0bcf9ff}
Version: 1.0.0.1
Provider name: 'Microsoft File Share Shadow Copy provider'
Provider type: Fileshare
Provider Id: {89300202-3cec-4981-9171-19f59559e0f2}
Version: 1.0.0.1
Provider name: 'Microsoft Software Shadow Copy provider 1.0'
Provider type: System
Provider Id: {b5946137-7b9f-4925-af80-51abd60b20d5}
Version: 1.0.0.7
===========================================================================
Vssadmin list shadowstorage doesn't reference the location of my CSVs...
PS C:\Windows\system32> vssadmin list shadowstorage
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2013 Microsoft Corp.
Shadow Copy Storage association
For volume: (C:)\\?\Volume{6bf32257-eccb-11e3-80b5-806e6f6e6963}\
Shadow Copy Storage volume: (C:)\\?\Volume{6bf32257-eccb-11e3-80b5-806e6f6e6963}\
Used Shadow Copy Storage space: 0 bytes (0%)
Allocated Shadow Copy Storage space: 0 bytes (0%)
Maximum Shadow Copy Storage space: 13.6 GB (10%)
============================================================================
PS C:\clusterstorage\volume1> mountvol
Creates, deletes, or lists a volume mount point.
MOUNTVOL [drive:]path VolumeName
MOUNTVOL [drive:]path /D
MOUNTVOL [drive:]path /L
MOUNTVOL [drive:]path /P
MOUNTVOL /R
MOUNTVOL /N
MOUNTVOL /E
path Specifies the existing NTFS directory where the mount
point will reside.
VolumeName Specifies the volume name that is the target of the mount
point.
/D Removes the volume mount point from the specified directory.
/L Lists the mounted volume name for the specified directory.
/P Removes the volume mount point from the specified directory,
dismounts the volume, and makes the volume not mountable.
You can make the volume mountable again by creating a volume
mount point.
/R Removes volume mount point directories and registry settings
for volumes that are no longer in the system.
/N Disables automatic mounting of new volumes.
/E Re-enables automatic mounting of new volumes.
Possible values for VolumeName along with current mount points are:
\\?\Volume{6bf32256-eccb-11e3-80b5-806e6f6e6963}\
*** NO MOUNT POINTS ***
\\?\Volume{6bf32257-eccb-11e3-80b5-806e6f6e6963}\
C:\
\\?\Volume{bd46bae7-015c-4115-88ca-e6e9067fdea1}\
C:\ClusterStorage\Volume2\
\\?\Volume{caf6938a-5faa-4f3b-8e2b-e27d1498dedf}\
C:\ClusterStorage\Volume1\
\\?\Volume{6bf3225c-eccb-11e3-80b5-806e6f6e6963}\
D:\
====================================================================When veeam backup call VSS, it create cache files that at the end of backup should be purged. I suppose that in some case this process don't work properly and leave orphaned cache files.
it's possible that when you move CSV on another node these orphaned files will be purged.
from the disk management, right click on CSV, properties, can you see the shadow copies tab? -
I have this issue and see throughout the Internet that my problem is shared by large numbers of other Windows 7 users, and a few Windows 8 users.
I also see that Microsoft has not addressed the issue.
I've been troubleshooting the problem for 13 months and across 3 separate hard drives on 2 separate computers, with the help of tech escalation from both Carbonite and Dell (whom I wanted to eliminate as causes, and who have been kind enough to assist even
after being eliminated as causes because they evidently care about customer service).
Over 13 months we have run system diagnostics, reinstalls and repairs to no avail. We have been able to reproduce the event in the absence of every attached device, every installed program, every subscribed service, and every hardware type and configuration.
We have visited chat rooms showing that this is a widespread problem (e.g., http://superuser.com/questions/630033/audio-video-glitch-when-shadow-copy-service-starts), and that even professional server administrators simply consign themselves to VSS being "the
bane of backup software" (http://community.spiceworks.com/topic/229743-problem-with-vss-writer-system-writer-timed-out).
Yet regardless of the computer or the configuration, the problem persists. It causes characteristic and alarming disk write error and memory spikes on the Resource Monitor that can be traced to huge numbers on the System 4 and VSSVC.exe processes, occurring
every time the Volume Shadow Copy Service and Application Experience create a restore point during an automatic update of Adobe, antivirus, etc.; and one can even provoke an event simply by manually creating a restore point, which has the bonus of triggering
an 8220 notice that the Volume Shadow Service has run out of time while deleting files. And the only advice I've seen from MS is that this is a "normal condition."
It is not normal to be unable to enjoy audio and video. And it is certainly not normal for one's PC to continually degrade with every update until it becomes unable to update and must be replaced.
I am on my 3rd computer with this problem (different type and configuration each time), and Dell has offered me an upgrade to Windows 8 in the hopes that the problem will not recur there. But I see from Microsoft's tech chat that Windows 8 users are reporting
the problem as well (http://answers.microsoft.com/en-us/windows/forum/windows_8-pictures/after-upgrading-to-windows-8-pro-there-is-an/813432c2-14f1-463f-bba3-ad322ceb6e00).
Please, please post a real answer to this problem. Thank you.Hi,
Above all I understand the frustration as a same issue persists for a very long time.
At first I'm thinking if it is directly related to the application CrashPlan some customers mentioned in one of the threads you provided. However I then noticed that you said it could be also reproduced by creating a System Restore point.
Currently I cannot find a Windows 7 system so I used a Windows 8.1 laptop (also Dell) for testing.
I tried to play an online video and also a local video with creating a restore point in the middle. However I failed to reproduce the same behavior.
The following screenshot was captured in second test (play a local video):
I cannot confirm if it is because we have a large physical memory (8GB), or Windows 8.1 resolved this issue. From the screenshot, memory is not spiked (actually it is almost not changed).
So in current situation you can test to enlarge the size of physical memory (and virtual memory) for test if available. And as Dell provided a Windows 8 system, you can try it before and after installing Windows 8.1.
As a support engineer I also hope to help fix the issue or at least find out the cause. Later I will try to find a Windows 7 system for testing as well.
In addition, please understand that as the issue occurs mostly in Windows 7, though it seems related to VSS, it is still a Windows client system issue. So you can post the question to Windows 7 forum for further information. Here is the link:
http://social.technet.microsoft.com/Forums/en-US/category/w7itpro/
Please remember to mark the replies as answers if they help and un-mark them if they provide no help. If you have feedback for TechNet Support, contact [email protected] -
Shadow Copies on 2012 R2 File Server Cluster
Hello all!
I've inherited a two node physical 2012 R2 file server cluster that contains a few SMB shares on a single clustered disk. I'd like to enable shadow copies for this shared disk but want to store the shadow copy data on its own shared disk
as per shadow copy best practices (at least on non-clustered file servers).
I created a second cluster disk, assigned it to the same resources as the SMB clustered disk.
Now historically I've enabled shadow copies through computer management but I want to ensure the shadow copies are cluster aware so in the Failover Cluster Manager I open Storage | Disks and right click the SMB cluster disk and click the Shadow Copies tab.
From the tab I can Enable shadow copies, this sounds like what I'm looking for, unfortunately it does not give me an option to choose a disk/volume to store my shadow copy data, so this can't be right.
My next step was to connect computer management to the cluster virtual server name (NOCFS4) and through the System Tools | Shared Folders | All Tasks | Configure Shadow Copies it shows me the correct number of shares on the SMB cluster disk plus
I can see the Settings button for configuring the location and size limit for shadow copies, however once I tweak the shadow copy location and size settings, click Ok and click Enable to turn on the shadow copies I get a long pause and an error about
not being able to create a schedule. So it seems connecting to the cluster virtual object is not the answer either.
That leaves using computer management to connect to one of the physical server nodes of the cluster. When I open the shadow copy interface on the physical node I note that it shows a 0 for the number of shares it detects on the SMB clustered disk.
This doesn't surprise me since this interface isn't cluster resource aware.
So I'm stuck. Does anyone know the "Microsoft way" to enable shadow copies on a clustered disk while storing the shadow copy data on a second cluster disk both attached to the same cluster resource?Hi guys
I spotted exactly same problem right now on Windows 2012 R2 with latest updates.
Enabling Shadow Copy via Cluster Manager on disk will enable schedule and snapshots but schedule is not-cluster aware (is created locally on node) and "Previous Versions" are visible only locally but not via shared folders (UNC path accesible by
clients)
When I spotted this behavior I tried different way going via Computer Management and cluster resource name but console always hangs for me when using "Configure Shadow Copies". After many minutes configuration window is opened (Hurray!) but any
action there will hang whole console again. Enabling Shadow Copies will fail with "0x80004005: Unspecified
error" for creating scheduled task but "Next Run Time" column still shows "Disabled". Checking disk resource via Cluster Manager shows it is enabled and ?local? scheduled task is created.
Computer management console still shows DISABLED and any action freezes whole console (only when cluster resource name is used).
This fix I found, unfortunately, is not applicable to 2012 R2 OS: https://support.microsoft.com/en-us/kb/2894464
To sum up there is a major bug in MS implementation in Shadow Copies for Shared Folders when clustering is used or it is still not supported in 2012 R2? Doing it outside cluster works as it should (without freezes and Previous Versions are available via
UNC)
There is no documentation about FileServer Clustering on 2012(R2) unfortunately.
Could someone from MS clarify it?
Many thanks
Filip
EDIT:
Ok, one correction:
Scheduled task is not created in "Failover Clustering" hive of Scheduled tasks as user may expect but failover of fileshare to other node will unregister/reregister it on active node only. -
Server 2012 File Server Cluster Shadow Copies Disappear Some Time After Failover
Hello,
I've seen similar questions posted on here before however I have yet to find a solution that worked for us so I'm adding my process in hopes someone can point out where I went wrong.
The problem: After failover, shadow copies are only available for a short time on the secondary server. Before the task to create new shadow copies happens the shadow copies are deleted. Failing back shows them missing on the primary server as
well when this happens.
We have a 2 node (hereafter server1 and server2) cluster with a quorum disk. There are 8 disk resources which are mapped to the cluster via iScsi. 4 of these disks are setup as storage and the other 4 are currently set up as shadow copy volumes
for their respective storage volume.
Previously we weren't using separate shadow copy volumes and seeing the same issue described in the topic title. I followed two other topics on here that seemed close and then setup the separate shadow copy volumes however it has yet to alleviate the
issue. These are the two other topics :
Topic 1: https://social.technet.microsoft.com/Forums/windowsserver/en-US/ba0d2568-53ac-4523-a49e-4e453d14627f/failover-cluster-server-file-server-role-is-clustered-shadow-copies-do-not-seem-to-travel-to?forum=winserverClustering
Topic 2: https://social.technet.microsoft.com/Forums/windowsserver/en-US/c884c31b-a50e-4c9d-96f3-119e347a61e8/shadow-copies-missing-after-failover-on-2008-r2-cluster
After reading both of those topics I did the following:
1) Add the 4 new volumes to the cluster for shadow copies
2) Made each storage volume dependent on it's shadow copy volume in FCM
3) Went to the currently active node directly and opened up "My Computer", I then went to the properties of each storage volume and set up shadow copies to go to the respective shadow copy volume drive letter with correct size for spacing, etc.
4) I then went back to FCM and right clicked on the corresponding storage volume and choose "Configure Shadow Copy" and set the schedule for 12:00 noon and 5:00 PM.
5) I noticed that on the nodes the task was created and that the task would failover between the nodes and appeared correct.
6) Everything appears to failover correctly, all volumes come up, drive letters are same, shadow copy storage settings are the same, and 4 scheduled tasks for shadow copy appear on the current node after failover.
Thinking everything was setup according to best practice I did some testing by changing file contents throughout the day making sure that previous versions were created as scheduled on server1. I then rebooted Server1 to simulate failure. Server2
picked up the role within about 10 seconds and files were avaiable. I checked and I could still see previous versions for the files after failover that were created on server1. Unfortunately that didn't last as the next day before noon I was going
to make more changes to files to ensure that not only could we see the shadow copies that were created when Server1 owned the file server role but also that the copies created on Server2 would be seen on failback. I was disappointed to discover that
the shadow copies were all gone and failing back didn't produce them either.
Does anyone have any insight into this issue? I must be missing a switch somewhere or perhaps this isn't even possible with our cluster type based on this: http://technet.microsoft.com/en-us/library/cc779378%28v=ws.10%29.aspx
Now here's an interesting part, shadow copies on 1 of our 4 volumes have been retained from both nodes through the testing, but I can't figure out what makes it different though I do suspect that perhaps the "Disk#s" in computer management / disk
management perhaps need to be the same between servers? For example, on server 1 the disk #s for cluster volume 1 might be "Disk4" but on server 2 the same volume might be called "Disk7", however I think that operations like this
and shadow copy are based on the disk GUID and perhaps this shouldn't matter.
Edit, checked on the disk numbers, I see no correlation between what I'm seeing in shadow copy and what is happening to the numbers. All other items, quotas, etc fail and work correctly despite these diffs:
Disk Numbers on Server 1:
Format: "shadow/storerelation volume = Disk Number"
aHome storage1 = 16
aShared storage2 = 09
sHome storage3 = 01
sShared storage4 = 04
aHome shadow1 = 10
aShared shadow2 = 11
sHome shadow3 = 02
sShared shadow4 = 05
Disk numbers on Server 2:
aHome storage1 = 16 (SAME)
aShared storage2 = 04 (DIFF)
sHome storage3 = 05 (DIFF)
sShared storage4 = 08 (DIFF)
aHome shadow1 = 10 (SAME)
aShared shadow2 = 11 (SAME)
sHome shadow3 = 06 (DIFF)
sShared shadow4 = 09 (DIFF)
Thanks in advance for your assistance/guidance on this matter!Hello Alex,
Thank you for your reply. I will go through your questions in order as best I can, though I'm not the backup expert here.
1) "Did you see any event ID when the VSS fail?
please offer us more information about your environment, such as what type backup you are using the soft ware based or hard ware VSS device."
I saw a number of events on inspection. Interestingly enough, the event ID 60 issues did not occur on the drive where shadow copies did remain after the two reboots. I'm putting my event notes in a code block to try to preserve formatting/readability.
I've written down events from both server 1 and 2 in this code block, documenting the first reboot causing the role to move to server 2 and then the second reboot going back to server 1:
JANUARY 2
9:34:20 PM - Server 1 - Event ID: 1074 - INFO - Source: User 32 - Standard reboot request from explorer.exe (Initiated by me)
9:34:21 PM - Server 1 - Event ID: 7036 - INFO - Source: Service Control Manager - "The Volume Shadow Copy service entered the running state."
9:34:21 PM - Server 1 - Event ID: 60 - ERROR - Source: volsnap - "The description for Event ID 60 from source volsnap cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:
\Device\HarddiskVolumeShadowCopy49
F:
T:
The locale specific resource for the desired message is not present"
9:34:21 PM - Server 1 - Event ID 60 - ERROR - Source: volsnap - "The description for Event ID 60 from source volsnap cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:
\Device\HarddiskVolumeShadowCopy1
H:
V:
The locale specific resource for the desired message is not present"
***The above event repeats with only the number changing, drive letters stay same, citing VolumeShadowCopy# numbers 6, 13, 18, 22, 27, 32, 38, 41, 45, 51,
9:34:21 PM - Server 1 - Event ID: 60 - ERROR - Source: volsnap - "The description for Event ID 60 from source volsnap cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:
\Device\HarddiskVolumeShadowCopy4
E:
S:
The locale specific resource for the desired message is not present"
***The above event repeats with only the number changing, drive letters stay same, citing VolumeShadowCopy# numbers 5, 10, 19, 21, 25, 29, 37, 40, 46, 48, 48
9:34:28 PM - Server 1 - Event ID: 7036 - INFO - Source: Service Control Manager - "The NetBackup Legacy Network Service service entered the stopped state."
9:34:28 PM - Server 1 - Event ID: 7036 - INFO - Source: Service Control Manager - "The Volume Shadow Copy service entered the stopped state.""
9:34:29 PM - Server 1 - Event ID: 7036 - INFO - Source: Service Control Manager - "The NetBackup Client Service service entered the stopped state."
9:34:30 PM - Server 1 - Event ID: 7036 - INFO - Source: Service Control Manager - "The NetBackup Discovery Framework service entered the stopped state."
10:44:07 PM - Server 2 - Event ID: 7036 - INFO - Source: Service Control Manager - "The Volume Shadow Copy service entered the running state."
10:44:08 PM - Server 2 - Event ID: 7036 - INFO - Source: Service Control Manager - "The Microsoft Software Shadow Copy Provider service entered the running state."
10:45:01 PM - Server 2 - Event ID: 48 - ERROR - Source: bxois - "Target failed to respond in time to a NOP request."
10:45:01 PM - Server 2 - Event ID: 20 - ERROR - Source: bxois - "Connection to the target was lost. The initiator will attempt to retry the connection."
10:45:01 PM - Server 2 - Event ID: 153 - WARN - Source: disk - "The IO operation at logical block address 0x146d2c580 for Disk 7 was retried."
10:45:03 PM - Server 2 - Event ID: 34 - INFO - Source: bxois - "A connection to the target was lost, but Initiator successfully reconnected to the target. Dump data contains the target name."
JANUARY 3
At around 2:30 I reboot Server 2, seeing that shadow copy was missing after previous failure. Here are the relevant events from the flip back to server 1.
2:30:34 PM - Server 2 - Event ID: 60 - ERROR - Source: volsnap - "The description for Event ID 60 from source volsnap cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:
\Device\HarddiskVolumeShadowCopy24
F:
T:
The locale specific resource for the desired message is not present"
2:30:34 PM - Server 2 - Event ID: 60 - ERROR - Source: volsnap - "The description for Event ID 60 from source volsnap cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:
\Device\HarddiskVolumeShadowCopy23
E:
S:
The locale specific resource for the desired message is not present"
We are using Symantec NetBackup. The client agent is installed on both server1 and 2. We're backing them up based on the complete drive letter for each storage volume (this makes recovery easier). I believe this is what you would call "software
based VSS". We don't have the infrastructure/setup to do hardware based snapshots. The drives reside on a compellent san mapped to the cluster via iScsi.
2) "Confirm the following registry is exist:
- HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\VSS\Settings"
The key is there, however the DWORD value is not, would that mean that the
default value is being used at this point? -
I construct a failover cluster(file server,AP module) for sharing files by WSS 2012,and I want to use the shadow copies to backup my data,but when making a shadow copies on the volume which is added to the cluster(not the CSV,just add
it to the cluster and use it to share files,it plays the role of file server),there are some errors occured, these errors result in the shadow copies failed,error likes the following pictures:
1: the disk F is added to the cluster,first I make the shadow copies by click the right key of mouse on the disk F,and chouse the configeration shadow copies,and click the settings, then click the schedule , and I wait just a few seconds, the error is appeared,like
this picture 1, the wait operation timed out,and then ,
I click the schedule button once again,a different error occured,like the following picture," the object already exists",if i don't set the schedule at first ,use the default shedule,and click the enable button also the same error must
accure
but the only diffrence is that, a shadow copy time point is created, also ,you can make the shadow copies by click " create now", that is creating the shadow copies manually. Although it can succesfully make the shadow copies, but when I select
a time point to revert, error occured, "A volume that contains operating system files or resides on a cluster shared disk cannot be reverted"
In a word,all the errors above make the shadow copies by schedulling failed,except making the shadow copies manually,but what makes me confused is that I have ever maked the shadow copies succesfully by schedul a policy,I don't know what makes it succesful,
it's small probability, most of time ,it's failed.No matter what kind of situation, revert must be failed.
I'm sorry for my pool english , it's the first time for me getting help in forum by english ,I don't know if I descripe my question clearly, also ,other method like the link
http://technet.microsoft.com/en-us/library/cc784118(v=ws.10).aspx I have tried,but the same errors occured.Can anyone tell me How can I make the shadow copies in File Server
cluster（AP module）？And I make a mistake in operating？ Looking forward for your reply.Thanks!Hi,
Please check the following 2 places:
HKEY_LOCAL_MACHINE\Cluster\Tasks
C:\Windows\System32\Tasks
First please compare permission settings of the folder C:\Windows\System32\Tasks with a working computer. Correct permission settings if anything wrong. Specifically, confirm you current account do have permission on this folder.
As it said "object already exists", find the schedules you created before, backup and delete all these schedules in both registry key and folder.
Then test to create a new schedule to see if issue still exists.
Meanwhile what kind of storage device you are using? The issue could occur on specific storage device, so test to enable shadow copy on a local disk to see if that will work.
TechNet Subscriber Support in forum |If you have any feedback on our support, please contact [email protected]
Thank you for you reply.On the local volume,all of these errors will not occur, but the volume in the file server cluser.There is no value in HKEY_LOCAL_MACHINE\Cluster\Tasks. On local volume, everything goes well about the shadow copy, so I do not
think something is wrong about the permission settings of the folder C:\Windows\System32\Tasks.Storage device is a SAN,we use RAID6 and provide the LUNs to the NAS engine, and the make the volume on these LUNs, Is Angthing wrong? Hope for you
reply~~ -
We are using TINA backup solution and windows 2003 backup is failling with VSS error.
For testing purpose we initiate a system state backup (or any file backup) with the help of windows 2003 ntbackup.exe and found it is failing with below error.
Backup error report.
Backup Status
Operation: Backup
Active backup destination: File
Media name: "Backup.bkf created 28/05/2014 at 06:34"
Volume shadow copy creation: Attempt 1.
Error returned while creating the volume shadow copy:0x8004230f.
Error returned while creating the volume shadow copy:8004230f
Aborting Backup.
The operation did not successfully complete.
We check event viewer and found below error event.
Event Type:
Error
Event Source:
VSS
Event Category:
None
Event ID:
12293
Date:
28/05/2014
Time:
05:48:10
User:
N/A
Computer:
CQ329TOS
Description:
Volume Shadow Copy Service error: Error calling a routine on the Shadow Copy Provider {b5946137-7b9f-4925-af80-51abd60b20d5}. Routine details Cannot ask provider {b5946137-7b9f-4925-af80-51abd60b20d5} if
volume is supported. [0x8000ffff] [hr = 0x8000ffff].Resolution:
After getting this error we check Shadow Copy provider and writer health and fond it is fine.
To get shadow copy providers details use below command.
Command: vssadmin list providers
Command output
C:\>vssadmin list providers
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001 Microsoft Corp.
Provider name: 'Microsoft Software Shadow Copy provider 1.0'
Provider type: System
Provider Id: {b5946137-7b9f-4925-af80-51abd60b20d5}
Version: 1.0.0.7
To get shadow copy writers health
Command: vssadmin list writers
Command Output.
C:\>vssadmin list writers
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001 Microsoft Corp.
Writer name: 'System Writer'
Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
Writer Instance Id: {333e02cd-d9ec-43c8-9b45-39691ad1b351}
State: [1] Stable
Last error: No error
Writer name: 'Registry Writer'
Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
Writer Instance Id: {800877a5-e13d-47a3-8f99-ebd4d3b3fd12}
State: [1] Stable
Last error: No error
Writer name: 'MSDEWriter'
Writer Id: {f8544ac1-0611-4fa5-b04b-f7ee00b03277}
Writer Instance Id: {63400aa0-a17f-4121-9483-1cd226f03238}
State: [1] Stable
Last error: No error
Writer name: 'COM+ REGDB Writer'
Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
Writer Instance Id: {e13cb72b-84fa-4c86-86d8-48f523aafc9a}
State: [1] Stable
Last error: No error
Writer name: 'Event Log Writer'
Writer Id: {eee8c692-67ed-4250-8d86-390603070d00}
Writer Instance Id: {ce63b3a0-e038-4e56-9d07-929f256639de}
State: [1] Stable
Last error: No error
Writer name: 'WMI Writer'
Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
Writer Instance Id: {008e8714-ed6d-4288-81ce-4b0b1ec41294}
State: [1] Stable
Last error: No error
Writer name: 'BITS Writer'
Writer Id: {4969d978-be47-48b0-b100-f328f07ac1e0}
Writer Instance Id: {e22a8953-a52c-4a76-bec0-8773122cbff8}
State: [1] Stable
Last error: No error
Next I check Shadow Copies details from volume properties (right click on C or other drive then select properties then click on Shadow Copies Tab) and found it is showing the same error code..
From this error it is clear that the issue is inside the registry hive and due to junk hive shadow copies services not able to working properly.
For me the server have two disk we check disk signature at MBR and found the disk signature was.
Signature disk 0 : 9351912b
Signature disk 0 : FDFBE035
But at registry we found lot of nonexistance signature. Which indicate lot of junk valu inside registry.
Now how can we resolve this issue?
It is very simple just delete the registry key “volume” (registry key “HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\STORAGE\Volume”) and reboot the server it will “Volume” registry hive automatically.
Note:
When you remove registry key it is showing error unable to delete, then please right click on it select permission then take ownership and assign full permission to your login account.
Please be careful when you delete registry key because system can fully crashed if you delete or modify wrong registry key.
Your can take a backup of the registry key by exporting. -
Windows Server 2008 x64: Error on Shadow Copies tab
Pulling up the Shadow Copies tab on any of my drives gives the following error:
Initialization failed. Error 0x80040154: Class not registered.
Any ideas? Per the event log, the VSS service is starting and stopping successfully with no errors. No errors are being recorded in the event log when this error happens.Hi Richard,
This issue may be occur due to some DLL files failure registered on the system.
Troubleshooting steps:
1. Open a command-prompt on the problematic server, and type the following commands to manually Register the following VSS DLL's.
cd %windir%\system32
regsvr32.exe /i eventcls.dll
regsvr32.exe /i swprv.dll
regsvr32.exe vssui.dll
regsvr32.exe vss_ps.dll
regsvr32.exe msxml.dll
regsvr32.exe msxml2.dll
regsvr32.exe msxml3.dll
regsvr32.exe ole32.dll
regsvr32.exe oleaut32.dll
regsvr32.exe es.dll
vssvc /register
2. If the above steps don't resolve the issue. Since the VSS UI also depends on the proper functionality of the "Task Scheduler" service. Please check and verify the "Task Scheduler" service is Started. After a reboot,
please check if the Shadow Copies Tab can function properly.
Hope it helps.
David Shen - MSFT
worked for me on our 2008 R2 SP1 PDC server with file server (and DFS) role.
However I got a bunch of errors on registering most of components, only a few succeeded (vss_ps.dll,
msxml3.dll and command vssvc /register) - that was enough to restore the Shadow Copies tab in volume properties, I was getting access denied before. -
Shadow copies tab is missing from ReFS on Windows Server 2012
We're currently designing a new infrastructure based around Windows Server 2012 so I'm currently investigating all the new technologies, including whether we should format the file server drive in ReFS format - and what problems we might encounter. I'm aware
that it's not a good choice for SQL due to lack of sparse files but for a plain-vanilla file system, it might be a good thing to use.
However, we currently use scheduled Shadow Copies to allow users to recover accidentally deleted/corrupt files during the day before the nightly backup kicks in. In my lab environment, I've just created two drives. One formatted as NFTS and the other formatted
as ReFS.
When I look at the properties of the NTFS drive, Shadow Copies tab is there:
Including the F: drive - the ReFS drive.
However, when I bring up the properties of the F: drive, the Shadow Copies tab is missing:
So to configure shadow copies on ReFS drive, you have to select an NTFS drive and then select the ReFS volume.
A little bizarre?
Cheers, Rob.Hi Rob.
What if you:
start Computer Mangement.
Open System Tools
Right Click Shared Folders
Select All Tasks -> Configure Shadow Copies
Do you see/can configure both disk available there?
Via cmd can you list the volumes that vss knows about using:
vssadmin list volumes
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. Even if you are not the author of a thread you can always help others by voting as Helpful. This can
be beneficial to other community members reading the thread.
Oscar Virot -
"DPM uses the Volume Shadow Copy Service (VSS)"
"DPM uses the Volume Shadow Copy Service (VSS) to create a snapshot of the protected data."
According to MS (http://technet.microsoft.com/en-us/library/bb808827.aspx)
Does that mean I have to set asides space on the protected server (a file server), so it can store shadow copies, and the DPM server taps into those shadow copies to create its recovery points etc?
ThanksHi Joe,
when you are protecting a file server. DPM will implement a change journal to record all the blocks that have been changed.
Then once the sync starts. The journal is interrogated and will tell DPM which file have been changed.
Then the VSS writer makes a copy of these data and send them to DPM.
You don't need additionnal space or to create a new folder on your server. -
I have a Windows 2008 File Server which we have shadow copies running on 1 volume M-F 8-6 which gives us about a 1 weeks worth. This morning I was shocked to see that all my shadow copies were gone except for the ones created this morning. On the event logs,
there are numerous VSS errors:
12294
Volume Shadow Copy Service error: Error calling a routine on the Shadow Copy Provider {b5946137-7b9f-4925-af80-51abd60b20d5}. Routine returned E_INVALIDARG. Routine details GetSnapshot({00000000-0000-0000-0000-000000000000},03526740).
12293
Volume Shadow Copy Service error: Error calling a routine on a Shadow Copy Provider {b5946137-7b9f-4925-af80-51abd60b20d5}. Routine details EndPrepareSnapshots({bef82808-c26c-467d-b470-1898a732c8b4}) [hr = 0x8000ffff].
12289
Volume Shadow Copy Service error: Unexpected error Error calling CreateFile on volume '\\?\Volume{1a2d17d4-007c-11e2-866e-1cc1de21b71e}\'. hr = 0x80070037.
12298
Volume Shadow Copy Service error: The I/O writes cannot be held during the shadow copy creation period on volume \\?\Volume{529c5cfa-e61c-11df-9d22-806e6f6e6963}\. The volume index in the shadow copy set is 0. Error details: Open[0x00000000], Flush[0x00000000],
Release[0x00000000], OnRun[0x80042314].
12310
Volume Shadow Copy Service error: The shadow copy could not be committed - operation timed out. Error context: DeviceIoControl(\\?\Volume{529c5cfa-e61c-11df-9d22-806e6f6e6963} - 0000021C,0x0053c010,00AFF0D8,0,00AF80A0,4096,[0]).
12340
Volume Shadow Copy Error: VSS waited more than 40 seconds for all voumes to be flushed. This caused volume \\?\Volume{529c5cfa-e61c-11df-9d22-806e6f6e6963}\ to timeout while waiting for the release-writes phase of shadow copy creation. Trying
again when disk activity is lower may solve this problem.
20
The shadow copies of volume E: were aborted because of a failed free space computation.
8
The flush and hold writes operation on volume E: timed out while waiting for a release writes command.
The E volume is the one where shadow copies are enabled. There's plenty of free space on the volume dedicated for shadow copies. Running vssadmin list writers reports no errors. We're currently backing up the server with Backup Exec and Crashplan Pro.Hi,
Please run the VSSADMIN LIST WRITERS command and post the result. Then refer to the thread below to see if it helps:
VSS fails to run properly. Event ID 12294.
http://answers.microsoft.com/en-us/windows/forum/windows_vista-system/vss-fails-to-run-properly-event-id-12294/0beee636-01c4-4d0b-9c6c-083e18e6f8e9
Regards,
Mandy
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.
Maybe you are looking for
-
Use eps files in a 2' x 6' banner designed in CS2 Illustrator.
I have two eps files (logos) I'd like to use in a 2' x 6' banner. The rest of the banner will use text. How can I incorporate these eps files? I'm using CS2 Illustrator. Thanks for your help.
-
Mavericks Mail-cannot scroll down to select a group by holding mouse button.
I do not like the new Mavericks mail. When I attempt to hold the left mouse button and scroll down to select a group, the program automatically locks onto the first message I touch and moves it. Prior to Mavericks scrolling was an easy process. This
-
MY 'sent' messages are marked as junk
I am in training mode in Apple mail. Why are all my sent messages marked as junk?
-
IChat screen sharing- shared screen is green/grey pixelated
Have a strange problem trying to share the screen of my parent's MacBook Pro: request accepted, but I can't see their screen. I get a first glimpse and it works, but then it degrades to grey/green pixelated, in general, unreadable. Both computers are
-
Unix command to make list of file name
Hi Gurus, I have seen post how to process multiple file from johngoodwin.blogspot.com. But what is the equlivalent command in unix to list all file names. I want one text file will contain all text file name and another text file will contain all csv