- Community Home
- >
- Storage
- >
- Midrange and Enterprise Storage
- >
- HPE EVA Storage
- >
- Snapclone/windows issue
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-27-2006 06:43 AM
09-27-2006 06:43 AM
Snapclone/windows issue
This is the process. First, create snapclone of a vdisk from server 'A' and present cloned vdisk to server 'B', no problem. We do this step only once. After this, the cloned disk presented to server B is re-cloned daily. The same LUN address and WWN are added to the re-cloned vdisk as it had originally, and it is again presented to server B. Ideally, server B will not notice that the disk was briefly offline, and the disk will retain the same drive letter, just new data (from a windows perspective).
My problem is that after I re-clone the vdisk and present it to server B, I don't see the new data, just the original data. To see the new data, I have to reboot server B.
Anyone know why this is? Is there a way to get windows to see the re-created clone without a reboot. Any help would be greatly appreciated!
Our SAN is EVA6000, presenting to Windows 2003 server as a basic disk.
Blake
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-27-2006 05:04 PM
09-27-2006 05:04 PM
Re: Snapclone/windows issue
The server did not notice that the underlying disk has changed. No operating system supports such an operation anyway, because the new disk has a (slightly) different structure.
You need to dismount the disk on the operating system before you unpresent the virtual disk. After you have presented the new virtual disk, you need to mount it, so that the server reads a fresh copy of the file system.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-28-2006 02:47 AM
09-28-2006 02:47 AM
Re: Snapclone/windows issue
Note: While I am an HPE Employee, all of my comments (whether noted or not), are my own and are not any official representation of the company
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-28-2006 11:48 PM
09-28-2006 11:48 PM
Re: Snapclone/windows issue
We had a similar issue.
After months of playing around we came up with the following solution that works.
a) Make sure the windows server is not logged in which the change happens.
b) We alternate drive letters. eg one day is N:\ next day it T:\ next day its N:\ and so on.
Shahram
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-29-2006 05:46 AM
09-29-2006 05:46 AM