- Community Home
- >
- Storage
- >
- Entry Storage Systems
- >
- Disk Enclosures
- >
- Re: Logical Arrangement of Virtual Disks, Host, Da...
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
Discussions
Discussions
Forums
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
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
тАО11-13-2007 04:09 AM
тАО11-13-2007 04:09 AM
Logical Arrangement of Virtual Disks, Host, Data Replication Folders
I was hoping to get some opinions, advise, and/or examples of how some of you logically setup your virtual disks, hosts, and data replication within Command View to determine if you have any better ideas than my own. Initially what I did was break up Virtual Disk folders by the type of file system the vDisk would be (e.g. NTFS, HPUX, VMFS, RDM). When we started playing with CA I found it might be more logical to create Virtual Disk folders based on the name of the system being replicated (e.g. EXCHANGE_SERVER_NAME) and put all the vDisks presented to the host within this subfolder.
Then we started playing around with virtualizing Exchange 2003 with VMware VI3 and now the replicated LUNs are a mix of VMFS volumes and RDM's (Raw Device Mappings).
Luckily we're in testing phase of this project so nothing is in production, but the my Virtual Disk, Host, and DR folders are becoming a huge mess! Any suggestions on how to keep a good house within CV? How do you all arrange your objects?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-13-2007 07:04 AM
тАО11-13-2007 07:04 AM
Re: Logical Arrangement of Virtual Disks, Host, Data Replication Folders
RDMs can be a bit hard to identify, so I use different LUN address ranges for VMFS and RDM disks. RDM disks can be collected in a per-VM subfolder. For example:
\\Virtual Disks\ESXCluster1\VMFS-1
\\Virtual Disks\ESXCluster1\VMFS-2
\\Virtual Disks\ESXCluster1\VM1-RDM\VM1-RDM-1
\\Virtual Disks\ESXCluster1\VM1-RDM\VM1-RDM-2
\\Virtual Disks\ESXCluster1\VM2-RDM\VM2-RDM-1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-13-2007 08:47 AM
тАО11-13-2007 08:47 AM
Re: Logical Arrangement of Virtual Disks, Host, Data Replication Folders
VHost1>>VGuest1_disk1_etc_etc
>>VGuest2_disk1_etc_etc
>>Vguest2_disk2_etc_etc
You could also create additional folders from there.
If you have a large mix of platforms then an upper level of platform then host would be prudent.
HPUX>>host1>>etc..
WDOZE>>host3>>etc..
LINUX>>host2>>etc..
I find the more fully qualified the names then the items become self explanatory reducing error and bad/old documentation.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-13-2007 10:18 AM
тАО11-13-2007 10:18 AM
Re: Logical Arrangement of Virtual Disks, Host, Data Replication Folders
Can you tell me on which disk is stored my database? How would you start searching?
Microsof
Dataware
hostname
BD
vdisk
vdisk
Logs
vdisk
vdisk
Groupware
hostname
BD
vdisk
vdisk
Logs
vdisk
vdisk
Linux
Monitoring
hostname
Aplication Server
hostname
vdisk
hostname
vdisk
Unix
Production
CluProd
applications
vdisk
vdisk
vdisk
database
datafiles
vdisk
vdisk
vdisk
logs
vdisk
vdisk
vdisk
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-13-2007 03:24 PM
тАО11-13-2007 03:24 PM
Re: Logical Arrangement of Virtual Disks, Host, Data Replication Folders
For both hosts and VDisks, our folder structure usually is
OS Platform > physical blade, cabinet or cluster name > hostname
With the Vdisks belonging to the host or cluster in the hostname folder. Some of those folders for shared disks in a cluster (or ESX environment) have names like NAS0102 or ESXFARM1, etc.
For Vdisk names, we usually will start with the hostname, followed by lun and GB of the disks, such as
ESXFARM01_011_0512
And for some Vdisks, we will place a filesystem name/mount point as a last field at the end of a vdisk name.
We've found this useful in catching errors or even just parsing the SSSU output in excel, although there are much better ways to do that.