![]() ![]() I found my process does work if I use a utility to restore the MBR. There are bound to be tools about to help you recover from a deleted partition, so you MAY be able to get this to work - it depends on how important it is to reduce downtime for converting your SFW volume to a partition This is quite convoluted, but it you could get point 3 to work, then this would quicker then copying the data for very large filesystems like the 1TB filesystem in your case. Create partition on the disk as in step 2.Delete the volume on your new disk that was created when breaking the mirror.When mirror is synced, stop access to the volume (i.e stop apps and users writing to it) and then break mirror.Mirror volume in SFW to the now empty disk.Check converted volume is exactly the same size in sectors as the volume in SFW and if it isn't then grow original volume (not converted volume) so it is the same size in sectors. ![]() Add the disk to the diskgroup which converts partition to a volume.Create a partition on the disk the same size as volume in SFW,.Add a new disk to the system the same size (actually slightly larger) as SFW volume.If 1 is not true then you can get round this my mirroring volume onto contiguous space on a single disk in UNIX and WindowsĢ is possible in Solaris using tool mksdpart and is possible in Windows, in theory, if you: So I don't why the data region is been affected, but it maybe that Windows THINKS it is not formatted when it actually is - i.e maybe there is some flag in the private region/MBR that dictates if the data is formatted. So for instance in the simpler instance if you just delete a volume and then recreate (without formatting) then Windows Explorer says the volume is not formatted and the same is true of deleting and recreating a partition. The problem on Windows is that point 3 does not seem to be true which is surprising. The deletion and creation of Veritas volumes and native O/S partitions does not change the data - i.e when you delete the volume or partition, the data remains intact and you are just removing the information in the private region or MBR about where the volume resides on disk.You are able to create a native O/S partition in exactly the same position as the volume.The Veritas Volume is on contiguous space on a single disk.In UNIX this relies on the following 3 properties: Volume Manager can configure and monitor hardware RAID devices, and manage shared storage in supported clusteri.This is possible in UNIX, but it looks more complicated in Windows. Volume Manager provides easy-to-use, online storage management for enterprise computing and Storage Area Network (SAN) environments.The easy-to-use interface simplifies disk administration tasks, such as adding or moving storage resources or data. By creating virtual storage devices from physical disks and disk arrays, Volume Manager removes the physical limitations of disk storage so you can configure, share, and manage storage for optimal results. Traditional disk storage management is a labor-intensive process, often requiring machines to be taken offline for hours at a time-disabling user access to data and requiring tedious, manual intervention by system administrators. In distributed client/server environments, users demand that databases, mission-critical applications, and other resources be continuously available and safe from the damage caused by disk failures.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |