January 27, 2011 at 5:13 pm
Problem with SQL Backup. I have a new Test SQL 2005 Active/Active Cluster, Databases and Log Drives on a SAN using iSCSI NIC's. C Drive on local hard drives. Databases work fine, quick and no issues apart from Backups. The backup regime is basically a copy of how we back up the current SQL2000 database and it works really well.
I have set up a full SQL backup for the database on a schedule to a backup device on the SAN followed by a transaction log backup to a log backup device (this is with "init"). The logs are backed up every 2 hours up to this point (using noinit) to the same log backup device but these are cleared once the DB is backup up. I do similar with master and msdb databases and do not have any problems.
I create the backup devices for the database and logs. The database backup job runs and takes approx 10 minutes to successfully backup a 50GB database to the backup device and then the log backups all work fine too. However when the db backup job runs the next time it seems to hang (disk access is sporadic whereas on the original backup it was high load all the time - using perfmon) and i get loads of SQL I/O error messages in the SQL logs. I can leave the job for a couple of hours and eventually it will fail. When i try to access the backup device i get a System Table 0 not found error and the backup device file size is 2K. The only way to re-run a backup is to delete and re-create the backup device.
This problem occurs on both of the Clustered SQL servers.
Any suggestions would be helpful. I have checked the backup account permissions on the SQL box, database and disk directories etc and all looks fine.
January 27, 2011 at 7:34 pm
Problem with SQL Backup.
When you say 'SQL Backup', do you mean the product by Red Gate Software, or SQL Server backups in general?
Thanks.
SQL BAK Explorer - read SQL Server backup file details without SQL Server.
Supports backup files created with SQL Server 2005 up to SQL Server 2017.
January 28, 2011 at 1:24 am
The backup jobs are all running using the built in SQL Backup software and running as SQLServerAgent jobs.
I checked this morning and a database backup job that took 7 minutes originally took 17 Hours to complete when i left it running - the database and log sizes had hardly changed!!
January 28, 2011 at 1:35 am
Could you please post the contents of the SQL Backup log for that backup process? The default folder where the logs are stored is C:\Documents and Settings\All Users\Application Data\Red Gate\SQL Backup\Log\<instance name> on Windows 2003 and older, and C:\ProgramData\Red Gate\SQL Backup\Log\<instance name> on Windows Vista and newer.
Could you also please post the backup command that was in use?
Thanks.
SQL BAK Explorer - read SQL Server backup file details without SQL Server.
Supports backup files created with SQL Server 2005 up to SQL Server 2017.
January 28, 2011 at 3:14 am
Log file extract:
2011-01-27 21:19:41.72 spid4s SQL Server has encountered 36 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [G:\Microsoft SQL Server\MSSQL.3\MSSQL\Data\DBBackup2_1_Data.ndf] in database [DBBackup2] (6). The OS file handle is 0x00000A88. The offset of the latest long I/O is: 0x000003f6b00000
2011-01-27 21:25:21.73 spid4s SQL Server has encountered 32 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [G:\Microsoft SQL Server\MSSQL.3\MSSQL\Data\DBBackup2_1_Data.ndf] in database [DBBackup2] (6). The OS file handle is 0x00000A88. The offset of the latest long I/O is: 0x00000406d00000
2011-01-27 21:28:22.57 Backup Database backed up. Database: DBBackup2, creation date(time): 2011/01/14(12:55:52), pages dumped: 2137867, first LSN: 497:106:37, last LSN: 497:122:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'DBBackupliveBACKDB'}). This is an informational message only. No user action is required.
2011-01-27 21:28:22.87 Backup Log was backed up. Database: DBBackup2, creation date(time): 2011/01/14(12:55:52), first LSN: 497:104:1, last LSN: 497:130:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'DBBackupliveBACKLOG'}). This is an informational message only. No user action is required.
2011-01-27 21:40:22.05 spid4s SQL Server has encountered 24 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [G:\Microsoft SQL Server\MSSQL.3\MSSQL\Data\DBBackup2_1_Data.ndf] in database [DBBackup2] (6). The OS file handle is 0x00000A88. The offset of the latest long I/O is: 0x00000000400000
2011-01-27 21:45:32.06 spid4s SQL Server has encountered 38 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [G:\Microsoft SQL Server\MSSQL.3\MSSQL\Data\DBBackup2_1_Data.ndf] in database [DBBackup2] (6). The OS file handle is 0x00000A88. The offset of the latest long I/O is: 0x00000010d00000
2011-01-27 21:50:32.06 spid4s SQL Server has encountered 21 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [G:\Microsoft SQL Server\MSSQL.3\MSSQL\Data\DBBackup2_1_Data.ndf] in database [DBBackup2] (6). The OS file handle is 0x00000A88. The offset of the latest long I/O is: 0x00000027c00000
2011-01-27 21:52:22.06 spid4s SQL Server has encountered 1 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [G:\Microsoft SQL Server\MSSQL.3\MSSQL\DATA\templog.ldf] in database [tempdb] (2). The OS file handle is 0x00000848. The offset of the latest long I/O is: 0x0000000002c800
2011-01-27 21:55:42.07 spid4s SQL Server has encountered 26 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [G:\Microsoft SQL Server\MSSQL.3\MSSQL\Data\DBBackup2_1_Data.ndf] in database [DBBackup2] (6). The OS file handle is 0x00000A88. The offset of the latest long I/O is: 0x0000003b800000
2011-01-27 22:01:22.07 spid4s SQL Server has encountered 34 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [G:\Microsoft SQL Server\MSSQL.3\MSSQL\Data\DBBackup2_1_Data.ndf] in database [DBBackup2] (6). The OS file handle is 0x00000A88. The offset of the latest long I/O is: 0x0000004e000000
2011-01-27 22:07:22.07 spid4s SQL Server has encountered 40 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [G:\Microsoft SQL Server\MSSQL.3\MSSQL\Data\DBBackup2_1_Data.ndf] in database [DBBackup2] (6). The OS file handle is 0x00000A88. The offset of the latest long I/O is: 0x0000005fe00000
2011-01-27 22:12:32.08 spid4s SQL Server has encountered 35 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [G:\Microsoft SQL Server\MSSQL.3\MSSQL\Data\DBBackup2_1_Data.ndf] in database [DBBackup2] (6). The OS file handle is 0x00000A88. The offset of the latest long I/O is: 0x00000075600000
2011-01-27 22:17:32.08 spid4s SQL Server has encountered 22 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [G:\Microsoft SQL Server\MSSQL.3\MSSQL\Data\DBBackup2_1_Data.ndf] in database [DBBackup2] (6). The OS file handle is 0x00000A88. The offset of the latest long I/O is: 0x00000084a00000
2011-01-27 22:22:52.09 spid4s SQL Server has encountered 35 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [G:\Microsoft SQL Server\MSSQL.3\MSSQL\Data\DBBackup2_1_Data.ndf] in database [DBBackup2] (6). The OS file handle is 0x00000A88. The offset of the latest long I/O is: 0x0000009c700000
2011-01-27 22:28:02.09 spid4s SQL Server has encountered 42 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [G:\Microsoft SQL Server\MSSQL.3\MSSQL\Data\DBBackup2_1_Data.ndf] in database [DBBackup2] (6). The OS file handle is 0x00000A88. The offset of the latest long I/O is: 0x000000ada00000
2011-01-27 22:33:02.09 spid4s SQL Server has encountered 25 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [G:\Microsoft SQL Server\MSSQL.3\MSSQL\Data\DBBackup2_1_Data.ndf] in database [DBBackup2] (6). The OS file handle is 0x00000A88. The offset of the latest long I/O is: 0x000000b6800000
2011-01-27 22:38:22.10 spid4s SQL Server has encountered 28 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [G:\Microsoft SQL Server\MSSQL.3\MSSQL\Data\DBBackup2_1_Data.ndf] in database [DBBackup2] (6). The OS file handle is 0x00000A88. The offset of the latest long I/O is: 0x000000d3a00000
2011-01-27 22:43:22.10 spid4s SQL Server has encountered 28 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [G:\Microsoft SQL Server\MSSQL.3\MSSQL\Data\DBBackup2_1_Data.ndf] in database [DBBackup2] (6). The OS file handle is 0x00000A88. The offset of the latest long I/O is: 0x000000ecc00000
2011-01-27 22:48:32.11 spid4s SQL Server has encountered 33 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [G:\Microsoft SQL Server\MSSQL.3\MSSQL\Data\DBBackup2_1_Data.ndf] in database [DBBackup2] (6). The OS file handle is 0x00000A88. The offset of the latest long I/O is: 0x00000103800000
2011-01-27 22:53:32.11 spid4s SQL Server has encountered 30 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [G:\Microsoft SQL Server\MSSQL.3\MSSQL\Data\DBBackup2_1_Data.ndf] in database [DBBackup2] (6). The OS file handle is 0x00000A88. The offset of the latest long I/O is: 0x00000119900000
2011-01-27 22:58:42.11 spid4s SQL Server has encountered 40 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [G:\Microsoft SQL Server\MSSQL.3\MSSQL\Data\DBBackup2_1_Data.ndf] in database [DBBackup2] (6). The OS file handle is 0x00000A88. The offset of the latest long I/O is: 0x00000131600000
2011-01-27 23:04:02.12 spid4s SQL Server has encountered 39 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [G:\Microsoft SQL Server\MSSQL.3\MSSQL\Data\DBBackup2_1_Data.ndf] in database [DBBackup2] (6). The OS file handle is 0x00000A88. The offset of the latest long I/O is: 0x00000142c00000
2011-01-27 23:09:12.12 spid4s SQL Server has encountered 41 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [G:\Microsoft SQL Server\MSSQL.3\MSSQL\Data\DBBackup2_1_Data.ndf] in database [DBBackup2] (6). The OS file handle is 0x00000A88. The offset of the latest long I/O is: 0x00000159600000
2011-01-27 23:14:52.13 spid4s SQL Server has encountered 36 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [G:\Microsoft SQL Server\MSSQL.3\MSSQL\Data\DBBackup2_1_Data.ndf] in database [DBBackup2] (6). The OS file handle is 0x00000A88. The offset of the latest long I/O is: 0x0000016dd00000
2011-01-27 23:20:02.13 spid4s SQL Server has encountered 26 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [G:\Microsoft SQL Server\MSSQL.3\MSSQL\Data\DBBackup2_1_Data.ndf] in database [DBBackup2] (6). The OS file handle is 0x00000A88. The offset of the latest long I/O is: 0x00000182900000
2011-01-27 23:22:22.13 spid4s SQL Server has encountered 2 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [G:\Microsoft SQL Server\MSSQL.3\MSSQL\DATA\templog.ldf] in database [tempdb] (2). The OS file handle is 0x00000848. The offset of the latest long I/O is: 0x000000000ab600
2011-01-27 23:25:22.13 spid4s SQL Server has encountered 35 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [G:\Microsoft SQL Server\MSSQL.3\MSSQL\Data\DBBackup2_1_Data.ndf] in database [DBBackup2] (6). The OS file handle is 0x00000A88. The offset of the latest long I/O is: 0x0000019ce00000
2011-01-27 23:31:02.14 spid4s SQL Server has encountered 33 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [G:\Microsoft SQL Server\MSSQL.3\MSSQL\Data\DBBackup2_1_Data.ndf] in database [DBBackup2] (6). The OS file handle is 0x00000A88. The offset of the latest long I/O is: 0x000001b4a00000
2011-01-27 23:36:12.14 spid4s SQL Server has encountered 32 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [G:\Microsoft SQL Server\MSSQL.3\MSSQL\Data\DBBackup2_1_Data.ndf] in database [DBBackup2] (6). The OS file handle is 0x00000A88. The offset of the latest long I/O is: 0x000001cd600000
2011-01-27 23:37:22.14 spid4s SQL Server has encountered 1 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [G:\Microsoft SQL Server\MSSQL.3\MSSQL\DATA\templog.ldf] in database [tempdb] (2). The OS file handle is 0x00000848. The offset of the latest long I/O is: 0x00000000002000
2011-01-27 23:41:22.15 spid4s SQL Server has encountered 32 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [G:\Microsoft SQL Server\MSSQL.3\MSSQL\Data\DBBackup2_1_Data.ndf] in database [DBBackup2] (6). The OS file handle is 0x00000A88. The offset of the latest long I/O is: 0x000001d9b00000
2011-01-27 23:46:32.15 spid4s SQL Server has encountered 29 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [G:\Microsoft SQL Server\MSSQL.3\MSSQL\Data\DBBackup2_1_Data.ndf] in database [DBBackup2] (6). The OS file handle is 0x00000A88. The offset of the latest long I/O is: 0x000001ecd00000
2011-01-27 23:52:12.15 spid4s SQL Server has encountered 36 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [G:\Microsoft SQL Server\MSSQL.3\MSSQL\Data\DBBackup2_1_Data.ndf] in database [DBBackup2] (6). The OS file handle is 0x00000A88. The offset of the latest long I/O is: 0x00000200600000
2011-01-27 23:57:32.16 spid4s SQL Server has encountered 38 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [G:\Microsoft SQL Server\MSSQL.3\MSSQL\Data\DBBackup2_1_Data.ndf] in database [DBBackup2] (6). The OS file handle is 0x00000A88. The offset of the latest long I/O is: 0x00000221d00000
2011-01-28 00:00:18.72 spid21s This instance of SQL Server has been using a process ID of 5540 since 25/01/2011 10:08:42 (local) 25/01/2011 10:08:42 (UTC). This is an informational message only; no user action is required.
2011-01-28 00:02:52.16 spid4s SQL Server has encountered 32 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [G:\Microsoft SQL Server\MSSQL.3\MSSQL\Data\DBBackup2_1_Data.ndf] in database [DBBackup2] (6). The OS file handle is 0x00000A88. The offset of the latest long I/O is: 0x0000023a800000
2011-01-28 00:08:32.17 spid4s SQL Server has encountered 32 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [G:\Microsoft SQL Server\MSSQL.3\MSSQL\Data\DBBackup2_1_Data.ndf] in database [DBBackup2] (6). The OS file handle is 0x00000A88. The offset of the latest long I/O is: 0x00000256200000
2011-01-28 00:13:42.17 spid4s SQL Server has encountered 44 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [G:\Microsoft SQL Server\MSSQL.3\MSSQL\Data\DBBackup2_1_Data.ndf] in database [DBBackup2] (6). The OS file handle is 0x00000A88. The offset of the latest long I/O is: 0x00000263700000
2011-01-28 00:19:02.18 spid4s SQL Server has encountered 35 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [G:\Microsoft SQL Server\MSSQL.3\MSSQL\Data\DBBackup2_1_Data.ndf] in database [DBBackup2] (6). The OS file handle is 0x00000A88. The offset of the latest long I/O is: 0x00000272100000
2011-01-28 00:24:42.18 spid4s SQL Server has encountered 29 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [G:\Microsoft SQL Server\MSSQL.3\MSSQL\Data\DBBackup2_1_Data.ndf] in database [DBBackup2] (6). The OS file handle is 0x00000A88. The offset of the latest long I/O is: 0x00000287900000
2011-01-28 00:29:52.18 spid4s SQL Server has encountered 32 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [G:\Microsoft SQL Server\MSSQL.3\MSSQL\Data\DBBackup2_1_Data.ndf] in database [DBBackup2] (6). The OS file handle is 0x00000A88. The offset of the latest long I/O is: 0x0000029ac00000
2011-01-28 00:34:52.19 spid4s SQL Server has encountered 28 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [G:\Microsoft SQL Server\MSSQL.3\MSSQL\Data\DBBackup2_1_Data.ndf] in database [DBBackup2] (6). The OS file handle is 0x00000A88. The offset of the latest long I/O is: 0x000002b4900000
2011-01-28 00:40:02.19 spid4s SQL Server has encountered 34 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [G:\Microsoft SQL Server\MSSQL.3\MSSQL\Data\DBBackup2_1_Data.ndf] in database [DBBackup2] (6). The OS file handle is 0x00000A88. The offset of the latest long I/O is: 0x000002c9800000
2011-01-28 00:43:43.74 Backup Error: 3041, Severity: 16, State: 1.
2011-01-28 00:43:43.74 Backup BACKUP failed to complete the command BACKUP DATABASE DBBackup2. Check the backup application log for detailed messages.
2011-01-28 01:01:46.09 Backup Database backed up. Database: DBBackup2, creation date(time): 2011/01/14(12:55:52), pages dumped: 2137867, first LSN: 497:153:71, last LSN: 497:183:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'DBBackupLIVEBACKDB'}). This is an informational message only. No user action is required.
2011-01-28 01:02:03.14 spid4s SQL Server has encountered 4 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [G:\Microsoft SQL Server\MSSQL.3\MSSQL\Data\DBBackup2_Data.mdf] in database [DBBackup2] (6). The OS file handle is 0x00000A0C. The offset of the latest long I/O is: 0x00000000700000
2011-01-28 01:03:13.14 spid4s SQL Server has encountered 28 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [G:\Microsoft SQL Server\MSSQL.3\MSSQL\Data\DBBackup2_1_Data.ndf] in database [DBBackup2] (6). The OS file handle is 0x00000A88. The offset of the latest long I/O is: 0x00000007a00000
2011-01-28 01:04:44.61 Backup Error: 3041, Severity: 16, State: 1.
2011-01-28 01:04:44.61 Backup BACKUP failed to complete the command BACKUP DATABASE DBBackup2. Check the backup application log for detailed messages.
2011-01-28 01:11:43.69 spid4s SQL Server has encountered 13 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [G:\Microsoft SQL Server\MSSQL.3\MSSQL\Data\DBBackup2_1_Data.ndf] in database [DBBackup2] (6). The OS file handle is 0x00000A88. The offset of the latest long I/O is: 0x00000262300000
2011-01-28 01:14:10.62 Backup Database backed up. Database: DBBackup2, creation date(time): 2011/01/14(12:55:52), pages dumped: 2137867, first LSN: 497:209:37, last LSN: 497:225:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'DBBackupliveBACKDB'}). This is an informational message only. No user action is required.
2011-01-28 01:15:13.99 spid4s SQL Server has encountered 6 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [G:\Microsoft SQL Server\MSSQL.3\MSSQL\Data\DBBackup2_Data.mdf] in database [DBBackup2] (6). The OS file handle is 0x00000A0C. The offset of the latest long I/O is: 0x00000000a00000
2011-01-28 01:15:33.99 spid4s SQL Server has encountered 1 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [G:\Microsoft SQL Server\MSSQL.3\MSSQL\DATA\tempdb.mdf] in database [tempdb] (2). The OS file handle is 0x00000854. The offset of the latest long I/O is: 0x00000000012000
2011-01-28 01:16:43.99 spid4s SQL Server has encountered 7 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [G:\Microsoft SQL Server\MSSQL.3\MSSQL\Data\DBBackup2_1_Data.ndf] in database [DBBackup2] (6). The OS file handle is 0x00000A88. The offset of the latest long I/O is: 0x00000002000000
2011-01-28 01:20:07.79 spid64 Error: 18204, Severity: 16, State: 1.
2011-01-28 01:20:07.79 spid64 BackupDiskFile::OpenMedia: Backup device 'G:\SQLBackup\DBBackupLIVEBACKDB.bak' failed to open. Operating system error 32(error not found).
2011-01-28 01:20:26.79 Backup Error: 3041, Severity: 16, State: 1.
2011-01-28 01:20:26.79 Backup BACKUP failed to complete the command BACKUP DATABASE DBBackup2. Check the backup application log for detailed messages.
2011-01-28 01:27:30.06 Backup Database backed up. Database: DBBackup2, creation date(time): 2011/01/14(12:55:52), pages dumped: 2137867, first LSN: 497:251:37, last LSN: 497:267:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'DBBackupliveBACKDB'}). This is an informational message only. No user action is required.
2011-01-28 05:15:24.49 spid4s SQL Server has encountered 1 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [G:\Microsoft SQL Server\MSSQL.3\MSSQL\DATA\templog.ldf] in database [tempdb] (2). The OS file handle is 0x00000848. The offset of the latest long I/O is: 0x0000000001ac00
2011-01-28 08:59:28.91 spid53 Configuration option 'Agent XPs' changed from 1 to 0. Run the RECONFIGURE statement to install.
Backup job runs using this command:
BACKUP DATABASE [DBBackup2] TO [DBBackupliveBACKDB] WITH NOFORMAT, INIT, NAME = N'DBBackuplive Full Database Backup', SKIP, NOREWIND, NOUNLOAD, STATS = 10
January 28, 2011 at 6:17 am
Ok, you're obviously not using SQL Backup[/url], but the native SQL Server BACKUP command.
It looks like there are multiple instances of the job all trying to back up the database concurrently, to the same file. If you were to run sp_who2, how many BACKUP processes do you see running?
SQL BAK Explorer - read SQL Server backup file details without SQL Server.
Supports backup files created with SQL Server 2005 up to SQL Server 2017.
January 28, 2011 at 10:39 am
Think have sorted the problem. I created the backup devices on the C drive of the server rather than on the SAN drives and now the backups run fine (<5 minutes for 50GB database). I dont undertand why but maybe it had something to do with the iSCSI connections to the SAN drives whcih causes an issue with large files.
January 30, 2011 at 8:22 am
are you using windows 2003 or windows 2008?
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply