Author Topic: Tip: Manage Volume Shadow Copy Service from the Vssadmin Command-Line  (Read 2881 times)

0 Members and 1 Guest are viewing this topic.

Offline Webmaster

  • Nick Computer Services
  • Administrator
  • Full Member
  • *
  • Posts: 168
  • Karma: +999/-0
  • Gender: Male
  • Love Me Love My Services
    • Computer Service

You can manage the Volume Shadow Copy service using the Vssadmin command-line tool from an elevated command prompt. You can use this tool to run the following commands:
Vssadmin List Providers Lists registered Volume Shadow Copy providers. Windows Vista includes Software Shadow Copy Provider 1.0.

Vssadmin List Shadows Lists existing volume shadow copies, the time the shadow copy was created, and its location.

Vssadmin List ShadowStorage Lists the volume shadow storage space currently in use, the space that is reserved for future use (labeled as allocated), and the maximum space that might be dedicated. This space is used to store changes while a shadow copy is active. The following sample output was generated using a computer that currently had about 3GB of files stored in a shadow copy, but that might allocate as much as 6.4GB.

Vssadmin List Volumes Lists volumes that are eligible for shadow copies.
Vssadmin List Writers Lists shadow copy writers, which support communicating with the Volume Shadow Copy service to ensure that files are captured in a consistent state. By default, subscribed writers include an operating system writer, a registry writer, a WMI writer, and a search service writer, among others. SQL Server also provides a Volume Shadow Copy writer.

Vssadmin Resize ShadowStorage Resizes Volume Shadow Copy storage. You can use this command to increase the maximum space that might be used by Volume Shadow Copy. Typically, this is unnecessary. However, if you discover that backups are failing on a computer because of an extremely high volume of changes during a backup, and Vssadmin List ShadowStorage reveals that the used Shadow Copy Storage space is at the maximum, you might be able to resolve the problem by manually increasing the maximum size.


 
Share this topic...
In a forum
(BBCode)
In a site/blog
(HTML)


Related Topics

  Subject / Started by Replies Last post
0 Replies
3240 Views
Last post February 16, 2009, 06:37:12 PM
by Webmaster
0 Replies
3184 Views
Last post June 11, 2010, 06:31:21 PM
by Nick
0 Replies
3449 Views
Last post June 11, 2010, 07:07:10 PM
by Nick
0 Replies
7338 Views
Last post June 16, 2010, 01:47:32 PM
by Nick
0 Replies
3517 Views
Last post June 16, 2010, 02:10:11 PM
by Nick
0 Replies
2449 Views
Last post June 16, 2010, 06:01:54 PM
by Nick
0 Replies
2813 Views
Last post June 16, 2010, 07:14:52 PM
by Nick
0 Replies
2368 Views
Last post June 16, 2010, 09:19:44 PM
by Nick
0 Replies
2323 Views
Last post June 16, 2010, 09:45:08 PM
by Nick
0 Replies
12391 Views
Last post July 03, 2010, 02:57:44 PM
by Nick