April 24, 2006 at 12:26 pm
I'm seeing strange results when I query backupmediafamily for some of my databases. I ran a script to generate the "restore database" commands for all databases and noticed this script fails for some databases. For those failures it generates a physical disk path that does not exist. sysdevices has the correct path so I'm not sure where backupmediaset gets its data. It's possible this path existed in the past, but it isn't there anymore. The puzzling thing is these backup files are from new backups.
select max (backup_start_date), physical_device_name
from msdb..backupmediafamily a
join msdb..backupset b
on a.media_set_id = b.media_set_id
where physical_device_name like '%imsql1%'
group by physical_device_name
order by physical_device_name
Any ideas?
Dave
April 24, 2006 at 9:25 pm
Here is an update. I found that if I do not specify a backup device or if I create a new backup device with a different name, backupmediafamily contains the correct information. However, if I delete the backup device and create it with the same name, backupmediafamily contains the wrong path. For example, the path it contains is G:\MSSQL\Backup\Server1\Accounting.bak when the actual path is G:\MSSQL\Backup\Accounting.bak. I don't understand what's happening.
SQL Server 2000 with sp3a running on Windows 2000 SE.
Dave
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply