Leaked source code of windows server 2003
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

92 lines
3.4 KiB

  1. ---------------------------------------------
  2. Microsoft Volume Snapshot API Readme File
  3. February 2000
  4. ---------------------------------------------
  5. (c) Microsoft Corporation, 2000. All rights reserved.
  6. This document provides late-breaking or other information that
  7. supplements the Microsoft Volume Snapshot API documentation.
  8. -------------------------
  9. How to Use This Document
  10. -------------------------
  11. To view the Readme file on-screen in Windows Notepad,
  12. maximize the Notepad window. On the Format menu, click Word
  13. Wrap. To print the Readme file, open it in Notepad or
  14. another word processor, and then use the Print command on
  15. the File menu.
  16. ---------
  17. CONTENTS
  18. ---------
  19. Creating a snapshot using the command-line utility
  20. You can create a snapshot on a certain set of volumes by
  21. running vss_demo.exe. You should choose the default values
  22. for vss_demo prompts excepting maybe for the Volume Name
  23. prompt where you must put the mount point path (terminated
  24. with backslash) for that volume, for example "F:\". Beware
  25. that the created snapshots are lost after a reboot.
  26. Before creating the snapshot on a FAT volume you must first
  27. configure the diff area for that volume. See the "Moving a
  28. Diff Area... " section below for details. You do not need
  29. to configure the diff area for an NTFS volume before
  30. creating a snapshot.
  31. Example:
  32. Z:\nt\drivers\storage\volsnap\vss\bin\i386>vss_demo
  33. Snapshot Set creation succeeded.
  34. GUID = {932ae8c4-1b97-4032-8062-0ab93fce92fc}
  35. Add a volume to the snapshot set? [Y/n]
  36. Attributes [0]:
  37. Initial allocated size (Mb): [20]:
  38. Volume name: ["G:\"]: F:\
  39. Snapshot details: [""]:
  40. A Volume Snapshot was succesfully added to the snapshot set.
  41. The Volume Snapshot was succesfully configured.
  42. Add a volume to the snapshot set? [Y/n] n
  43. Commiting the snapshot(s)..
  44. Allow partial commit? [Y/n]
  45. Allow writers cancel? [y/N]
  46. Ignore writer vetoes? [Y/n]
  47. The snapshot(s) were succesfully created.
  48. The properties of the snapshot #0 :
  49. Id = {00000000-0000-0000-0000-000000000000},
  50. SnapshotSetId = {00000000-0000-0000-0000-000000000000}
  51. Volume = (null), DevObj = (null)
  52. OriginalVolumeId = {00000000-0000-0000-0000-000000000000}
  53. OriginalVolumeName = (null)
  54. ProviderId = {00000000-0000-0000-0000-000000000000}
  55. Details = NULL
  56. Attributes = 0x00000000
  57. Timestamp = 0x0000000000000000
  58. Status = 0,0,0, Inc. No = 0x0000000000000000
  59. Data Length = 0x00000000, Opaque Data = NULL
  60. The name of snapshot #0 : \Device\HarddiskVolumeSnapshot3
  61. Moving a Diff Area from the Default Location
  62. To move a diff area from the default location to another
  63. drive, execute the following commands from the command
  64. line after each boot. Note that "F:" is the name of the
  65. target drive for the snapshot and "G:" is the name of the
  66. drive the diff area will be moved to. Also, the "F:" drive
  67. must be FAT and the "G:" drive must be NTFS. Beware that
  68. the diff area settings are lost after a reboot.
  69. Example:
  70. vsclrda F:
  71. vsda F: G:
  72. Using the sample writers
  73. A writer is by definition an ordinary application that
  74. can listen for snapshot-related events. For running the
  75. command-line sample writer in this SDK you need only
  76. to run tsub.exe in a command window. Then, in a separate
  77. command window you must create a snapshot using vss_demo.
  78. You will notice that the running tsub.exe gets notified
  79. before and after a snapshot gets created.