HPE GreenLake Administration
- Community Home
- >
- Storage
- >
- Midrange and Enterprise Storage
- >
- HPE EVA Storage
- >
- Continuous Access log size
HPE EVA Storage
1829736
Members
1646
Online
109992
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
06-29-2010 06:54 AM
06-29-2010 06:54 AM
Continuous Access log size
Trying to understand the world of CA Logs size.
CA replication will be set at Enhanced Asynchronous, what are the default and maximum DR Log files sizes?
Looking over SPOCK it looks to states the Default DR group log file as 100GB for Sync and Async, what is the max?
And it also reads that in Enhanced Async mode minimum log size is 1624MB, is this correct?
CA replication will be set at Enhanced Asynchronous, what are the default and maximum DR Log files sizes?
Looking over SPOCK it looks to states the Default DR group log file as 100GB for Sync and Async, what is the max?
And it also reads that in Enhanced Async mode minimum log size is 1624MB, is this correct?
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-29-2010 01:56 PM
06-29-2010 01:56 PM
Re: Continuous Access log size
Default =
- Sum of all the vdisks on the DR group for XCS 4.xxx to 6.1xx
- 100 GB for firmwares 6.2xxx and 09xxxxxx
Minimum =
- 136 MB for XCS < 6.1xx
- 1,624 MB for XCS 6.1xx or 6.2xx
- 5 GB for XCS 09xxxxxx
- Sum of all the vdisks on the DR group for XCS 4.xxx to 6.1xx
- 100 GB for firmwares 6.2xxx and 09xxxxxx
Minimum =
- 136 MB for XCS < 6.1xx
- 1,624 MB for XCS 6.1xx or 6.2xx
- 5 GB for XCS 09xxxxxx
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-30-2010 05:17 AM
06-30-2010 05:17 AM
Re: Continuous Access log size
Functionally, the maximum you would want to set it to would be the sum total of all disk drives in the group, keeping in mind the log space will be taken (as it is not already reserved) out of your available space on the disk array at the time of need (when replication would be broken). This space is also RAID1 space as well.
If you do not have a lot of free space avaiable, you need to determine which disk groups will be allowed to grow their logs to what size, before the entire disk group would go into full copy mode upon resumption of replication. This can be a balancing act as some disks (database logs, for instance) may be more important to keep from full-copy mode than others, especially those (database files) that may create a log of log space relative to the actual data changed.
Lastly, you want to make sure that you have at least "single" protection set to provide enough space on the source array to recover upon disk failure if your logs might grow to use up the free space.
If you do not have a lot of free space avaiable, you need to determine which disk groups will be allowed to grow their logs to what size, before the entire disk group would go into full copy mode upon resumption of replication. This can be a balancing act as some disks (database logs, for instance) may be more important to keep from full-copy mode than others, especially those (database files) that may create a log of log space relative to the actual data changed.
Lastly, you want to make sure that you have at least "single" protection set to provide enough space on the source array to recover upon disk failure if your logs might grow to use up the free space.
check out evamgt.wetpaint.com and evamgt google group
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