Re: STGPOOL migration thresholds
I have enough disk cache to handle these large backups, but the problem I have is the log file filling up and not emptying fast enough to handle this deluge of data especially the amount of directory information coming in from Windows file servers. I have the log file allocated at 13 GB with 12 GB assign and the backup threshold set to 50 percent. I still had several times when the log file went to over 90 percent and the system start delaying transactions by 30 milliseconds. One time the system also ran over 15 different DB backups in the space of 2 hours before the utilization went back down. Many of these DB backups only pick up 1 or 2 MB of data. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Nick Laflamme Sent: Wednesday, May 14, 2008 9:05 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] STGPOOL migration thresholds What are people using for storage pool migration thresholds these days? Do the speed and capacity of modern secondary storage make it more practical to have a very low threshold? In particular, I'm expecting a large number of large backups as some WinNT file permissions get updated en masse. If I'm expecting continual floods of data, I figure we ought to migrate large amounts each time, but I'm wondering what I'm missing. Collocation, mount times, and seek times are all factors, but we're using VTLs that should reduce mount and seek times. So, what are you using, and with what technology? Thanks, Nick This e-mail (including any attachments) is confidential and may be legally privileged. If you are not an intended recipient or an authorized representative of an intended recipient, you are prohibited from using, copying or distributing the information in this e-mail or its attachments. If you have received this e-mail in error, please notify the sender immediately by return e-mail and delete all copies of this message and any attachments. Thank you.
STGPOOL migration thresholds
What are people using for storage pool migration thresholds these days? Do the speed and capacity of modern secondary storage make it more practical to have a very low threshold? In particular, I'm expecting a large number of large backups as some WinNT file permissions get updated en masse. If I'm expecting continual floods of data, I figure we ought to migrate large amounts each time, but I'm wondering what I'm missing. Collocation, mount times, and seek times are all factors, but we're using VTLs that should reduce mount and seek times. So, what are you using, and with what technology? Thanks, Nick
Re: STGPOOL migration thresholds
We changed from 80-40 to 80-60 when we installed the VTL. We have not had a reason to change since. Andy Huebner -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Nick Laflamme Sent: Wednesday, May 14, 2008 9:05 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] STGPOOL migration thresholds What are people using for storage pool migration thresholds these days? Do the speed and capacity of modern secondary storage make it more practical to have a very low threshold? In particular, I'm expecting a large number of large backups as some WinNT file permissions get updated en masse. If I'm expecting continual floods of data, I figure we ought to migrate large amounts each time, but I'm wondering what I'm missing. Collocation, mount times, and seek times are all factors, but we're using VTLs that should reduce mount and seek times. So, what are you using, and with what technology? Thanks, Nick This e-mail (including any attachments) is confidential and may be legally privileged. If you are not an intended recipient or an authorized representative of an intended recipient, you are prohibited from using, copying or distributing the information in this e-mail or its attachments. If you have received this e-mail in error, please notify the sender immediately by return e-mail and delete all copies of this message and any attachments. Thank you.
