- Community Home
- >
- Servers and Operating Systems
- >
- Legacy
- >
- Operating System - Tru64 Unix
- >
- problem with volclonedg on large volume
Operating System - Tru64 Unix
1753797
Members
6981
Online
108799
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
Discussions
Discussions
Forums
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
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
тАО10-23-2006 12:48 AM
тАО10-23-2006 12:48 AM
problem with volclonedg on large volume
Greetings all,
Hope that someone can help me to find out a solution to following problem:
Customer has Tru64 v5.1b Cluster and XP12000 Storage. We are using volclonedg to create a copy of an LSM disk group whose underlying disks have been cloned via XP12000. We clone 4 different dg's and we encounter a problem only on the largest dg who contains more then 60 striped disks. The other dg's contains between 3 to 10 striped disks.
The volclonedg is very slow (runs about 30mins), but it ends successfully and all volumes (including the large datadg) are online, started and accessible on the target system. But if we reboot the target system the disks in the datadg are "online aliased". The strange thing is that the hostid in disks shows the source host and not the target host. The other cloned dg's have the correct target hostid. The volclonedg is executed via rsh from the source host to the target host with following string. A volsave is executed on the source host before the volclonedg is executed:
rsh $REMOTEHOST /usr/sbin/volclonedg -d $LSMCONFDIR/LSM.*."$LOCALHOST" -c $i -l $DISKS >/dev/null 2>&1
Does anyone knows about such kind of problems with volclonedg? Is there a possibility to better troubleshoot it?
Any help would be very appreciated.
cheers
Mario Grande
HP Switzerland
Hope that someone can help me to find out a solution to following problem:
Customer has Tru64 v5.1b Cluster and XP12000 Storage. We are using volclonedg to create a copy of an LSM disk group whose underlying disks have been cloned via XP12000. We clone 4 different dg's and we encounter a problem only on the largest dg who contains more then 60 striped disks. The other dg's contains between 3 to 10 striped disks.
The volclonedg is very slow (runs about 30mins), but it ends successfully and all volumes (including the large datadg) are online, started and accessible on the target system. But if we reboot the target system the disks in the datadg are "online aliased". The strange thing is that the hostid in disks shows the source host and not the target host. The other cloned dg's have the correct target hostid. The volclonedg is executed via rsh from the source host to the target host with following string. A volsave is executed on the source host before the volclonedg is executed:
rsh $REMOTEHOST /usr/sbin/volclonedg -d $LSMCONFDIR/LSM.*."$LOCALHOST" -c $i -l $DISKS >/dev/null 2>&1
Does anyone knows about such kind of problems with volclonedg? Is there a possibility to better troubleshoot it?
Any help would be very appreciated.
cheers
Mario Grande
HP Switzerland
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-23-2006 02:10 AM
тАО10-23-2006 02:10 AM
Re: problem with volclonedg on large volume
Sorry if I don't help, I don't know very much about LSM, but I just want to ask you if:
You run the freezefs before taking the hardware snapshot?
You run the hwmgr after the hardware disk cloning?
You run the freezefs before taking the hardware snapshot?
You run the hwmgr after the hardware disk cloning?
Por que hacerlo dificil si es posible hacerlo facil? - Why do it the hard way, when you can do it the easy way?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-23-2006 02:54 AM
тАО10-23-2006 02:54 AM
Re: problem with volclonedg on large volume
Hi Ivan,
We do not a freezefs because we do a pairresync and a pairsplit on XP12000 with unactive advFS domains.
The hole procedure is made by a script. These are roughly the steps:
1. Stop application on source and target host
2. Gather fdmns information on targethost
3. umount all relevant mountpoints on source and target host
4. Save LSM config with volsave on sourcehost
5. Deport dg's on targethost
6. pairresync and pairsplit on XP12000
7. Mount all filesets on sourcehost
8. Restore /etc/fdmns entries on targethost
9. Dg import with volclonedg on targethost
10. Mount all filesets on targethost
11. Start application
This procedure is in use and works fine since many months. But we used it without LSM. Now since we have introduced LSM stripe sets to reach better performance we encouter a problem that the dg are available immediately after the volclonedg, but if we reboot the targethost the largest dg isn't any more available because the disks are in the "online aliased" state. That means that they have the wrong hostid in the private region. We can fix it manually but we suppose that something goes wrong with the volclonedg.
cheers
Mario Grande
We do not a freezefs because we do a pairresync and a pairsplit on XP12000 with unactive advFS domains.
The hole procedure is made by a script. These are roughly the steps:
1. Stop application on source and target host
2. Gather fdmns information on targethost
3. umount all relevant mountpoints on source and target host
4. Save LSM config with volsave on sourcehost
5. Deport dg's on targethost
6. pairresync and pairsplit on XP12000
7. Mount all filesets on sourcehost
8. Restore /etc/fdmns entries on targethost
9. Dg import with volclonedg on targethost
10. Mount all filesets on targethost
11. Start application
This procedure is in use and works fine since many months. But we used it without LSM. Now since we have introduced LSM stripe sets to reach better performance we encouter a problem that the dg are available immediately after the volclonedg, but if we reboot the targethost the largest dg isn't any more available because the disks are in the "online aliased" state. That means that they have the wrong hostid in the private region. We can fix it manually but we suppose that something goes wrong with the volclonedg.
cheers
Mario Grande
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.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP