Use the following procedure when creating
For a process overview of the snapshot virtual disk creation process, refer to Create Snapshot Virtual Disk Wizard: Process Overview - Windows 2000 and Windows Server 2003.
Snapshot virtual disks might be reused (for frequent or nightly backups) or may be created for one-time usage (speculative change or upgrade testing). For instructions on how to reuse a disabled snapshot virtual disk, see Reusing Snapshot Virtual Disks.
Use the following procedure to create a snapshot virtual disk.
Caution: Risk of application errors -- Windows operating systems traditionally support a Master Boot Record (MBR) disk partition format. 64-bit Windows Server 2003 supports the new GUID Partition Table (GPT) disk partition format. The 32-bit Windows Server 2003 and Windows 2000 operating systems do not have support for this new partition format and do not know how to properly access a GPT disk. When a source virtual disk mapped to a 64-bit Windows Server 2003 host is
with the GPT disk partition format, you must map any snapshot virtual disks created of this source virtual disk to a 64-bit Windows Server 2003 host. If you map the snapshot virtual disk to a 32-bit Windows Server 2003 or Windows 2000 host, the operating system does not recognize the partition format of the snapshot virtual disk. Alternatively, you can initialize the source virtual disk on the 64-bit Windows Server 2003 host with the older MBR disk partition format, and any snapshots of that source virtual disk are accessible by other 32-bit Windows hosts.
|
1 |
Start the storage management software. The Enterprise Management Window is displayed. |
|
2 |
Launch an The Array Management Window is opened in a separate window. |
|
3 |
Within the Logical View of the Array Management Window, select a
|
|
4 |
Disable the snapshot virtual disk. Disable snapshot virtual disks by using one of the following methods:
|
|
5 |
Assign a
|
|
|
Important: Stop all I/O activity to the source virtual disk (or data transfer suspended) before starting this procedure. Stopping all I/O activity ensures that an accurate point-in-time image of the source virtual disk is captured. Close all applications (including Windows Explorer) to ensure all I/O activity has been stopped. |
|
6 |
Run the At a host prompt, type the following command, and press Enter: SMrepassist -f <filesystem-identifier> where <filesystem-identifier> is the physical disk letter assigned to the source virtual disk. Example: If the new disk physical disk (for the source virtual disk) was assigned physical disk letter "E" using the Create Partition Wizard , you would enter the following command, and press Enter: SMrepassist -f e: The write buffers for the disk physical disk are flushed. |
|
7 |
In the storage management software, re-create the snapshot virtual disk by using one of the following methods:
|
|
|
Important: If I/O activity to the source virtual disk was stopped or data transfer was suspended, resume I/O activity to the source virtual disk at this time (or reenable data transfer). |
|
8 |
Run the After virtual disks have been created and virtual disk-to-LUN mappings have been defined, run the hot_add utility to ensure that the operating system is aware of the newly created virtual disks, without having to reboot the host. For information on which operating systems support the hot_add utility, refer to your
|
|
9 |
Run the After the virtual disks have been created and virtual disk-to-LUN mappings have been defined, the SMdevices utility is run to ensure that the virtual disk name and the operating system storage array name (assigned by the operating system) correlate. |
|
10 |
Open the
The Disk Management dialog is displayed with a graphical representation of all the physical disks connected to the host and their associated partitions. |
|
11 |
In the Disk Management dialog, locate the disk and virtual disk definition that represents the snapshot virtual disk you re-created, and ensure that a new physical disk letter has automatically been assigned. |
|
12 |
Use the snapshot virtual disk with your backup application (reusing a snapshot virtual disk), or for speculative change and upgrade testing (one-time usage). For information on how to reuse a disabled snapshot virtual disk, see Reusing Snapshot Virtual Disks. |
|
13 |
After the snapshot virtual disk is no longer required, disable or delete the snapshot virtual disk. If you disable the snapshot virtual disk instead of deleting it, you can retain the snapshot virtual disk and its associated For more information, see Disabling a Snapshot Virtual Disk or Deleting a Virtual Disk. For command reference information on disabling or deleting a snapshot virtual disk, refer to the Enterprise Management Window online help. |
Caution: Risk of application errors -- Windows operating systems traditionally support a Master Boot Record (MBR) disk partition format. 64-bit Windows Server 2003 supports the new GUID Partition Table (GPT) disk partition format. The 32-bit Windows Server 2003 and Windows 2000 operating systems do not support this new partition format and do not know how to properly access a GPT disk. When a source virtual disk mapped to a 64 bit Windows Server 2003 host is initialized with the GPT disk partition format, any snapshot virtual disks created of this source virtual disk must also be mapped to a 64-bit Windows Server 2003 host. If you map the snapshot virtual disk to a 32-bit Windows Server 2003 or Windows 2000 host, the operating system does not recognize the partition format of the snapshot virtual disk. Alternatively, you can initialize the source virtual disk on the 64-bit Windows Server 2003 host with the older MBR disk partition format, and any snapshots of that source virtual disk will be accessible by other 32-bit Windows hosts.
Typically, when a snapshot virtual disk has been created it is disabled until a new point-in-time image of the same source virtual disk is required. Use the following procedure to create a new point-in-time image of the same source virtual disk.
|
|
Important: Stop all I/O activity to the source virtual disk (or data transfer suspended) before starting this procedure. Stopping all I/O activity ensures that an accurate point-in-time image of the source virtual disk is captured. Close all applications (including Windows Explorer) to ensure all I/O activity has been stopped. |
|
1 |
To flush all the write buffers from the new disk physical disk, run the SMrepassist utility on the host where the snapshot virtual disk is mounted. At the host prompt, type the following command, and press Enter: SMrepassist -f <filesystem-identifier> where <filesystem-identifier> is the physical disk letter assigned to the snapshot virtual disk. The write buffers for the disk physical disk are flushed. |
|
2
|
List all of the mounted virtual disks, and locate the disk representing the snapshot virtual disk. At the command prompt, type the following command, and press Enter: mountvol [physical disk:]path /l where [physical disk:]path is the NTFS folder where the mount point resides. All of the mount virtual disks are listed. For more information on using mountvol, refer to your operating system documentation. |
|
3
|
Unmount the disk representing the snapshot virtual disk. At the command prompt, type the following command, and press Enter: mountvol [physical disk:]path /d where [physical disk:]path is the NTFS folder where the mount point resides. The disk is unmounted. For more information on using the mountvol utility, refer to your operating system documentation. |
|
4
|
Remove any virtual disk-to-LUN mappings for the snapshot virtual disk by using one of the following methods:
where ["virtual disk name"] is the snapshot virtual disk name. For command reference-specific information on disabling a snapshot virtual disk, refer to the Enterprise Management Window online help. |
|
5 |
Disable the snapshot virtual disk by using one of the following methods:
|
|
6 |
Run the SMrepassist utility on the host where the source virtual disk is mounted to flush all the write buffers from the new disk physical disk. At the host prompt, type the following command, and press Enter: SMrepassist -f <filesystem-identifier> where <filesystem-identifier> is the physical disk letter assigned to the source virtual disk. The write buffers for the disk physical disk are flushed. |
|
7 |
In the storage management software, re-create the snapshot virtual disk by using one of the following methods:
|
|
|
Important: If I/O activity to the source virtual disk was stopped or data transfer was suspended, resume I/O activity to the source virtual disk at this time (or reenable data transfer). |
|
8
|
Assign a virtual disk-to-LUN mapping between the snapshot virtual disk and the host that will access the snapshot virtual disk.
Define virtual disk-to-LUN mappings by using one of the following methods:
For command reference-specific information on creating a virtual disk-to-LUN mapping, refer to the Enterprise Management Window online help. |
|
9
|
Run the After virtual disks have been created and virtual disk-to-LUN mappings have been defined, run the hot_add utility to ensure that the operating system is aware of the newly created virtual disks, without having to reboot the host. For information on which operating systems support the hot_add utility, refer to your
|
|
10
|
Mount the disk representing the snapshot virtual disk. At the command prompt, type the following command, and press Enter: mountvol [physical disk:]path Virtual Disk{GUID} where [physical disk:]path is the NTFS folder where the mount point will reside, and Virtual Disk{GUID} is the name of the virtual disk that is the target of the mount point in VolumeGUID format. The disk representing the snapshot virtual disk is mounted. For more information on using mountvol, refer to your operating system documentation. |
|
11
|
Note: This step is optional. If you are configuring your storage array using auto scripting operations, it is recommend that you complete this step. Assign the original virtual disk label to the disk representing the snapshot virtual disk. At the command prompt, type the following command, and press Enter: label [physical disk:][label] where [physical disk:] is the location of the disk you want to name, and [label]is the new virtual disk label. The disk representing the snapshot virtual disk is renamed. For more information on using the label command, refer to your operating system documentation. |
|
12
|
Note: This step is optional. If you are configuring your storage array using auto scripting operations, it is recommended that you complete this step.
Run the chkdsk command on the snapshot virtual disk to create and display a status report for the disk. At the command prompt, type the following command, and press Enter: chkdsk [physical disk:] where [physical disk:] is the physical disk that contains the disk that you want to check. A status report for the snapshot virtual disk is displayed. For more information on using the chkdsk command, refer to your operating system documentation. |
|
13 |
Use the snapshot virtual disk with your backup application (or with another application). |
|
14 |
When the snapshot virtual disk is no longer required, disable the snapshot virtual disk. If you disable the snapshot virtual disk instead of deleting it, you can retain the snapshot virtual disk and its associated snapshot repository virtual disk. When you must create a different snapshot of the same source virtual disk, you can re-create the disabled snapshot virtual disk. This takes less time than creating a new snapshot virtual disk and stops any reduction in performance that might occur if the snapshot virtual disk remains available. For more information, see Disabling a Snapshot Virtual Disk and Recreating a Snapshot Virtual Disk. For command reference information on disabling and recreating a snapshot virtual disk, refer to the Enterprise Management Window online help. |
Create Snapshot Virtual Disk Wizard: Additional Instructions