GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- VXVM dirty region logs
Operating System - HP-UX
1846839
Members
7192
Online
110256
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
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
Go to solution
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
09-09-2004 08:16 PM
09-09-2004 08:16 PM
Hi guys
I have am interesting issue, it is that i have just built a new server to replicate a current production server.
the server is mainly a sybase Database server and has approx 130 raw disk volumes.
i have now been asked by stake holder (having himself just read veritas professional document)to turn on DIRTY REGION LOGS.
can this be done on already set up volumes and if so how( hopefully easily)
regards
andrew
I have am interesting issue, it is that i have just built a new server to replicate a current production server.
the server is mainly a sybase Database server and has approx 130 raw disk volumes.
i have now been asked by stake holder (having himself just read veritas professional document)to turn on DIRTY REGION LOGS.
can this be done on already set up volumes and if so how( hopefully easily)
regards
andrew
Solved! Go to Solution.
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-09-2004 11:18 PM
09-09-2004 11:18 PM
Solution
Hi,
This can be done on an excisting volume (vxfs).
link to the URL
http://ftp.support.veritas.com/pub/support/products/VolumeManager_UNIX/vm32_admin_240253.pdf
Adding DRL Logging to a Mirrored Volume
To put dirty region logging (DRL) into effect for a mirrored volume, a log subdisk must be
added to that volume. Only one log subdisk can exist per plex.
To add DRL logs to an existing volume, use the following command:
# vxassist addlog volume logtype=drl [nlog= n]
The nlog attribute can be used to specify the number of log plexes to add. By default, one
log plex is added. For example, to add a single log plex for the volume vol03, use the
following command:
# vxassist addlog vol03 logtype=drl
When the vxassist command is used to add a log subdisk to a volume, by default a log
plex is also created to contain the log subdisk unless you include the keyword nolog in
the layout specification.
For a volume that will be written to sequentially, such as a database log volume, include
the logtype=drlseq attribute to specify that sequential DRL is to be used:
# vxassist addlog volume logtype=drlseq [nlog= n]
Once created, the plex containing a log subdisk can be treated as a regular plex. Data
subdisks can be added to the log plex. The log plex and log subdisk can be removed using
the same procedures as are used to remove ordinary plexes and subdisks.
Regards,
Robert-Jan
This can be done on an excisting volume (vxfs).
link to the URL
http://ftp.support.veritas.com/pub/support/products/VolumeManager_UNIX/vm32_admin_240253.pdf
Adding DRL Logging to a Mirrored Volume
To put dirty region logging (DRL) into effect for a mirrored volume, a log subdisk must be
added to that volume. Only one log subdisk can exist per plex.
To add DRL logs to an existing volume, use the following command:
# vxassist addlog volume logtype=drl [nlog= n]
The nlog attribute can be used to specify the number of log plexes to add. By default, one
log plex is added. For example, to add a single log plex for the volume vol03, use the
following command:
# vxassist addlog vol03 logtype=drl
When the vxassist command is used to add a log subdisk to a volume, by default a log
plex is also created to contain the log subdisk unless you include the keyword nolog in
the layout specification.
For a volume that will be written to sequentially, such as a database log volume, include
the logtype=drlseq attribute to specify that sequential DRL is to be used:
# vxassist addlog volume logtype=drlseq [nlog= n]
Once created, the plex containing a log subdisk can be treated as a regular plex. Data
subdisks can be added to the log plex. The log plex and log subdisk can be removed using
the same procedures as are used to remove ordinary plexes and subdisks.
Regards,
Robert-Jan
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 2026 Hewlett Packard Enterprise Development LP