Media Set Problems
RudiM
Posts: 11
Hi
I am having some problems with my Log restore.
I have Server A (SQL 2005 Ent)(SQL Backup 5) which does transactional log back up every 10 min. The log is copied to server B (SQL 2005 Ent)(SQL Backup 5) to a shared directory.
When The logs are being restored I get the following error.
"The media set for database 'DBNAME' has 1 family members but only 2 are provided. All members must be provided."
If I restart the restore job again the log gets restored. In some cases I have to run the restore Query from SQL Query using the full log name to get the log restored.
Any Idea what can be causing this?
Thansk
Rudi
I am having some problems with my Log restore.
I have Server A (SQL 2005 Ent)(SQL Backup 5) which does transactional log back up every 10 min. The log is copied to server B (SQL 2005 Ent)(SQL Backup 5) to a shared directory.
When The logs are being restored I get the following error.
"The media set for database 'DBNAME' has 1 family members but only 2 are provided. All members must be provided."
If I restart the restore job again the log gets restored. In some cases I have to run the restore Query from SQL Query using the full log name to get the log restored.
Any Idea what can be causing this?
Thansk
Rudi
Rudi
Comments
SQL Backup Consultant Developer
Associate, Yohz Software
Beyond compression - SQL Backup goodies under the hood, updated for version 8
No from the primary server there is no error's raised, the backup was succesfull.
Yes there is.
Warning 300: BackUp Failed. Retry attempt: 1
VDI error 1010: Failed to get configuration from server
SQL Error 3013 and SQL error 3201
Thx
Rudi
SQL Backup Consultant Developer
Associate, Yohz Software
Beyond compression - SQL Backup goodies under the hood, updated for version 8
C:\>SQLBackupC -SQL "RESTORE SQBHEADERONLY FROM DISK = 'F:\Cellularlogs\LOG__Cel
lular_20081004_023000.sqb' "
'SQLBackupC' is not recognized as an internal or external command,
operable program or batch file.
Sorry I am not that clued up when it comes to SQL....
Here is the out put
C:\Program Files\Red Gate\SQL Backup\(LOCAL)>SQLBackupC -SQL "RESTORE SQBHEADERO
NLY FROM DISK = 'F:\Cellularlogs\LOG__Cellular_20081004_023000.sqb' "
Red Gate SQL Backup 5.2.0.2825, (c) Red Gate Software Ltd 2004 - 2007
Serial number: 010-001-073940-7652
Reading SQB file header of "F:\Cellularlogs\LOG__Cellular_20081004_023000.sqb"
Backup group ID : 0
File number : 0 of 0
Backup type : 2 (Transaction log)
Native backup size : 33.250 MB
Backup start : 04 October 2008 02:30:48
Backup end : 04 October 2008 02:30:49
Server name : CAPS
Database name : Cellular
First LSN :
Last LSN :
Checkpoint LSN :
Database backup LSN :
C:\Program Files\Red Gate\SQL Backup\(LOCAL)>SQLBackupC -SQL "RESTORE SQBHEADERO
NLY FROM DISK = 'F:\CellularLogs\LOG__Cellular_20081004_024000.sqb' "
Red Gate SQL Backup 5.2.0.2825, (c) Red Gate Software Ltd 2004 - 2007
Serial number: 010-001-073940-7652
Reading SQB file header of "F:\CellularLogs\LOG__Cellular_20081004_024000.sqb"
Backup group ID : 0
File number : 0 of 0
Backup type : 2 (Transaction log)
Native backup size : 31.000 MB
Backup start : 04 October 2008 02:40:43
Backup end : 04 October 2008 02:40:44
Server name : CAPS
Database name : Cellular
First LSN :
Last LSN :
Checkpoint LSN :
Database backup LSN :
It looks like the backup process failed to write the header details when the backup was reattempted. If the backup process did not record any warnings re this, but only that the backup failed on the first attempt, then it's most likely a bug in 5.2, and probably fixed in 5.3.
SQL Backup Consultant Developer
Associate, Yohz Software
Beyond compression - SQL Backup goodies under the hood, updated for version 8
Good time to upgrade then. Thanks foe all the help
regards
Rudi