Re: TDP SQL sessions wants to write to same tape...
if its same node with collocation turned on it might be max mount points value that should be increased (im not sure if this is aplicable for SQL TDP) goran. - Original Message - From: Niklas Lundstrom [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Friday, February 13, 2004 10:04 AM Subject: TDP SQL sessions wants to write to same tape... Hello I've been running a backup of a SQL server db but I took too long so I increased the stripe-parameter to 2 so it would utilize 2 sessions and 2 tape drives for the backup. However when the backup starts both sessions wants to write to the same volume, leaving one of the session in a media-wait state for the whole backup and the backup fails after 12h. 12,064 BPX-T- RecvW0 S 20.5 K 62.6 G Node TDP MSS- ROBUR22_SQL cp/Ip QL 12,066 BPX-T- MediaW 13.0 H 5.2 K 2.5 M Node TDP MSS- ROBUR22_SQL cp/Ip QL What can I do to fix this??? Regards Niklas Lundstrvm Swedbank
Re: TDP SQL sessions wants to write to same tape...
Niklas, Goran is correct. You need to make sure that MAXNUMMP for the NODENAME you are using for your SQL backups is set to at least to the number of stripes you are using. Also, turning on collocation by filespace will ensure that data for different stripes remains on different tapes so that the restores will also be able to read from separate tapes at the same time. From Chapter 3 of the User's Guide: - The maxnummp parameter for register or update node must be at least the maximum number of stripes to be used for backup or restore when removable media such as tapes are used or if migration occurs during the backup or restore operation. The default value is 1. This value is the maximum number of mount points a node can have at one time. If other backups or restores may occur at the same time, the value of this parameter must be large enough to allow for all of the needed mount points. - The collocate parameter for define stgpool should be set to filespace to ensure that individual data stripes stay on separate removable volumes. The default value is no. Not doing so may require move operations to make the data for each stripe of a restore simultaneously accessible. There is also a nice IBM KB article (1145253) describing more details. Go here: www.ibm.com Search for this (include the double quotes in the search window): DP for SQL : Data Striping Del ADSM: Dist Stor Manager [EMAIL PROTECTED] wrote on 02/13/2004 04:04:00 AM: Hello I've been running a backup of a SQL server db but I took too long so I increased the stripe-parameter to 2 so it would utilize 2 sessions and 2 tape drives for the backup. However when the backup starts both sessions wants to write to the same volume, leaving one of the session in a media-wait state for the whole backup and the backup fails after 12h. 12,064 BPX-T- RecvW0 S 20.5 K 62.6 G Node TDP MSS- ROBUR22_SQL cp/Ip QL 12,066 BPX-T- MediaW 13.0 H 5.2 K 2.5 M Node TDP MSS- ROBUR22_SQL cp/Ip QL What can I do to fix this??? Regards Niklas Lundström Swedbank
Re: TDP SQL sessions wants to write to same tape...
thank you - Original Message - From: Del Hoobler [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Friday, February 13, 2004 1:00 PM Subject: Re: TDP SQL sessions wants to write to same tape... Niklas, Goran is correct. You need to make sure that MAXNUMMP for the NODENAME you are using for your SQL backups is set to at least to the number of stripes you are using. Also, turning on collocation by filespace will ensure that data for different stripes remains on different tapes so that the restores will also be able to read from separate tapes at the same time. From Chapter 3 of the User's Guide: - The maxnummp parameter for register or update node must be at least the maximum number of stripes to be used for backup or restore when removable media such as tapes are used or if migration occurs during the backup or restore operation. The default value is 1. This value is the maximum number of mount points a node can have at one time. If other backups or restores may occur at the same time, the value of this parameter must be large enough to allow for all of the needed mount points. - The collocate parameter for define stgpool should be set to filespace to ensure that individual data stripes stay on separate removable volumes. The default value is no. Not doing so may require move operations to make the data for each stripe of a restore simultaneously accessible. There is also a nice IBM KB article (1145253) describing more details. Go here: www.ibm.com Search for this (include the double quotes in the search window): DP for SQL : Data Striping Del ADSM: Dist Stor Manager [EMAIL PROTECTED] wrote on 02/13/2004 04:04:00 AM: Hello I've been running a backup of a SQL server db but I took too long so I increased the stripe-parameter to 2 so it would utilize 2 sessions and 2 tape drives for the backup. However when the backup starts both sessions wants to write to the same volume, leaving one of the session in a media-wait state for the whole backup and the backup fails after 12h. 12,064 BPX-T- RecvW0 S 20.5 K 62.6 G Node TDP MSS- ROBUR22_SQL cp/Ip QL 12,066 BPX-T- MediaW 13.0 H 5.2 K 2.5 M Node TDP MSS- ROBUR22_SQL cp/Ip QL What can I do to fix this??? Regards Niklas Lundstrvm Swedbank
