HPE GreenLake Administration
- Community Home
- >
- Storage
- >
- Entry Storage Systems
- >
- Disk Enclosures
- >
- business copy variable
Disk Enclosures
1832891
Members
2808
Online
110048
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
08-25-2004 01:41 AM
08-25-2004 01:41 AM
business copy variable
Hi,
Can anyone tell me how the {partition} variable in BC jobs relates to the OS it will be mounted on.
For instance the snapunit.mount template.
It snap(clones) a vdisk and mounts its to the target server.
when editing the MOUNT line in the job, the BCV component has the {partition} variable.
When left defualt, the job fails --> log tells you an unspecified variable exists.
Now i filled in the number 4 as the variable and the job runs.
Now i wonder how this related to the OS and in particualr to other OS'es (partion and disk numbers ?)
Does anyone have BC experience on this ?
thanks,
rmk
Can anyone tell me how the {partition} variable in BC jobs relates to the OS it will be mounted on.
For instance the snapunit.mount template.
It snap(clones) a vdisk and mounts its to the target server.
when editing the MOUNT line in the job, the BCV component has the {partition} variable.
When left defualt, the job fails --> log tells you an unspecified variable exists.
Now i filled in the number 4 as the variable and the job runs.
Now i wonder how this related to the OS and in particualr to other OS'es (partion and disk numbers ?)
Does anyone have BC experience on this ?
thanks,
rmk
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-30-2004 08:41 AM
08-30-2004 08:41 AM
Re: business copy variable
I believe it is just the current Drive Letter.
I always have trouble with that particular variable.
Steven
I always have trouble with that particular variable.
Steven
Steven Clementi
HP Master ASE, Storage, Servers, and Clustering
MCSE (NT 4.0, W2K, W2K3)
VCP (ESX2, Vi3, vSphere4, vSphere5, vSphere 6.x)
RHCE
NPP3 (Nutanix Platform Professional)
HP Master ASE, Storage, Servers, and Clustering
MCSE (NT 4.0, W2K, W2K3)
VCP (ESX2, Vi3, vSphere4, vSphere5, vSphere 6.x)
RHCE
NPP3 (Nutanix Platform Professional)
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
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP