HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Legacy
- >
- Windows Server 2003
- >
- Re: migrating windows veritas cluster to standalon...
Windows Server 2003
1826364
Members
4729
Online
109692
Solutions
Forums
Categories
Company
Local Language
back
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
back
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
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- 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
06-21-2009 03:46 AM
06-21-2009 03:46 AM
migrating windows veritas cluster to standalone server
hi, ihave the following issue
i am trying to migrate veritas disk group (part of verotas cluster resource) to a standalone server using san migration tools.
after migrating the disk group , i can from the standalone server import the disk group and i can see the violume with their size but i can't explore the volume.
is there any special setting that should i do to be able to see the data from the standalone server?
i am trying to migrate veritas disk group (part of verotas cluster resource) to a standalone server using san migration tools.
after migrating the disk group , i can from the standalone server import the disk group and i can see the violume with their size but i can't explore the volume.
is there any special setting that should i do to be able to see the data from the standalone server?
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-21-2009 12:23 PM
06-21-2009 12:23 PM
Re: migrating windows veritas cluster to standalone server
What windows version are you using?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-21-2009 06:21 PM
06-21-2009 06:21 PM
Re: migrating windows veritas cluster to standalone server
win 2003,
veritas 4.3
veritas 4.3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-30-2009 11:19 PM
06-30-2009 11:19 PM
Re: migrating windows veritas cluster to standalone server
AFAIK, this is not going to work. There is a special driver that VCS uses for the disks that will make it not readable unless you install VCS.
Depending on the data on the drive, your best bet is to simply ROBOCOPY the data off to the new machine.
You need something that will read at the file level and not the block level basically. SAN type tools only usually run at the block level.
PS: My company had this same problem 8 months ago and we ended up just doing a Robocopy. It was a SQL2000 Cluster. Source was 2003 32 Ent with VCS and Destination was a 2003 32 Ent with no VCS.
Depending on the data on the drive, your best bet is to simply ROBOCOPY the data off to the new machine.
You need something that will read at the file level and not the block level basically. SAN type tools only usually run at the block level.
PS: My company had this same problem 8 months ago and we ended up just doing a Robocopy. It was a SQL2000 Cluster. Source was 2003 32 Ent with VCS and Destination was a 2003 32 Ent with no VCS.
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Support
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP