shcart
ADSM.ORG Member
- Joined
- Jan 6, 2003
- Messages
- 91
- Reaction score
- 1
- Points
- 0
- Location
- Monroe, NC
- Website
- www.geocities.com
A little useful advice.
We are using SP (for VE) on a large Blueprint server. Essentially we have one asnode per vcenter (1800-2000 guests).
If you are going to replicate a server built like this DO NOT start backing up to the primary until you have the Replication target set up and ready to go. Protect storage pool works fine though it runs for a long time. However the Replicate node receiving process appears to pin the DB2 log when it starts on the asnode and then takes a only few hours to consume the all of the permitted 256GB of log space (on a 300GB volume). At which point the SP instance tanks (leaving DB2 Active. hmmmm curiouser and curiouser). Will update when we get more information.
We are using SP (for VE) on a large Blueprint server. Essentially we have one asnode per vcenter (1800-2000 guests).
If you are going to replicate a server built like this DO NOT start backing up to the primary until you have the Replication target set up and ready to go. Protect storage pool works fine though it runs for a long time. However the Replicate node receiving process appears to pin the DB2 log when it starts on the asnode and then takes a only few hours to consume the all of the permitted 256GB of log space (on a 300GB volume). At which point the SP instance tanks (leaving DB2 Active. hmmmm curiouser and curiouser). Will update when we get more information.