MSDE 2000 backups and restores

Hi All
I am new to MSDE (from access)
I have chosen simple recovery mode for MSDE Database and do a full backup
each day then subsequent backups within the same day using differential
backups
The problem is I don't really understand how the differential backup should
work
1. Do you use a different file name for the Full and Differential backups?
e.g
BACKUP DATABASE TRAMCARS TO DISK = N'C:\Backup\Tramcars.bak' WITH INIT,
NOUNLOAD, NOSKIP, STATS = 10, NOFORMAT, NAME = 'Tramcars Diff Backup'
GO
BACKUP DATABASE TRAMCARS TO DISK = N'C:\Backup\Tramcarsdiff.bak' WITH INIT,
differential,
NOUNLOAD, NOSKIP, STATS = 10, NOFORMAT,
NAME = 'Tramcars Diff Backup'
GO
2 Do you use different file names for each differential backups during the
day or append each diff backup to the previous?
Because the literature shows TSQL code for Restoring includes reference to a
File = 1 (or 2 etc)
Regards
Steve
hi Steve,
> The problem is I don't really understand how the differential backup
> should work
> 1. Do you use a different file name for the Full and Differential
> backups? e.g
> BACKUP DATABASE TRAMCARS TO DISK = N'C:\Backup\Tramcars.bak' WITH
> INIT, NOUNLOAD, NOSKIP, STATS = 10, NOFORMAT, NAME = 'Tramcars Diff
> Backup'
> GO
> BACKUP DATABASE TRAMCARS TO DISK = N'C:\Backup\Tramcarsdiff.bak'
> WITH INIT, differential,
> NOUNLOAD, NOSKIP, STATS = 10, NOFORMAT,
> NAME = 'Tramcars Diff Backup'
> GO
correct... use 2 different files OR "init" the backup set with the full
backup and append to it the successive differential..
if you choos to have only 1 backup file, when restoring you have to specify
the
RESTORE DATABASE [xxx] FROM DISK = N'C:\xxxx.bak'
WITH FILE = n ,
......
where n is 1 for the very first (complete full backup) and then apply the
differential
WITH FILE = n , -- where n=2

> 2 Do you use different file names for each differential backups
> during the day or append each diff backup to the previous?
> Because the literature shows TSQL code for Restoring includes
> reference to a File = 1 (or 2 etc)
this is up to you... on how you "store" backup sets, how long you have to
store them, your internal policies, the actual media hosting the backups...
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.15.0 - DbaMgr ver 0.60.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Andrea
Again thanks for your reliable input
Steve
Regards
Steve
"Andrea Montanari" wrote:

> hi Steve,
> correct... use 2 different files OR "init" the backup set with the full
> backup and append to it the successive differential..
> if you choos to have only 1 backup file, when restoring you have to specify
> the
> RESTORE DATABASE [xxx] FROM DISK = N'C:\xxxx.bak'
> WITH FILE = n ,
> ......
> where n is 1 for the very first (complete full backup) and then apply the
> differential
> WITH FILE = n , -- where n=2
>
> this is up to you... on how you "store" backup sets, how long you have to
> store them, your internal policies, the actual media hosting the backups...
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.15.0 - DbaMgr ver 0.60.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
>
sql

msdb trascation logging mode

Hi,
I have a production SQL 2000 database with transaction logging turned on
('Full' recovery mode). I backup the transaction log every 15 minutes. In
order to use the point-in-time recovery option, do I also need to have the
'Full' recovery model set on the msdb? I ask this because I assume the msdb
holds information about the transaction log backup taken on the production
database. Without this information, I suspect point-in-time recover will not
be possible. Is my assumption correct?
Regards,
James G.Hi
MSDB is not needed to do point in time recovery. MSDB is just used to keep
the backup information so that Enterprise Manager UI can show you what
backups are available. It is a nice to have.
Point in time recovery needs the database dump and all the transaction log
dumps after that to the time you want to restore to.
Regards
--
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"James Goodwill" wrote:

> Hi,
> I have a production SQL 2000 database with transaction logging turned on
> ('Full' recovery mode). I backup the transaction log every 15 minutes. In
> order to use the point-in-time recovery option, do I also need to have the
> 'Full' recovery model set on the msdb? I ask this because I assume the msd
b
> holds information about the transaction log backup taken on the production
> database. Without this information, I suspect point-in-time recover will n
ot
> be possible. Is my assumption correct?
> Regards,
> James G.
>
>|||Hi James
The MSDB doesn't have to be in full recovery mode. In fact the MSDB
has no role when you run the restore. If the MSDB would have any role
in the restore then it would be impossible to restore the database on a
different server. All the data that is needed for the point in time
restore is stored in the log backup it self.
Adi|||Hi,
'Full' recovery model set on the msdb?
Ans:- NO NEED
I suspect point-in-time recover will not be possible. Is my assumption
correct?
No. You can do it with out a MSDB tranasction log backup.
MSDB database holds the backup history information. FOR each backup SQL
Server logs an entry into BACKUPSET table in MSDB database.
This is just an information only and will be useful if you use Enterprise
manager to do point in time recovery. Even if you
do not have tis information you can do a recovery based on Transaction log
file date and time. For a time based recovery:-
1. Restore the Full database backup first with Norecovery
2. Restore the logbackup file in sequence based on date and time with
Norecovery till last file
3. Restore the last transaction log backup with RECOVERY and STOPAT option.
Note:-
I am taking the MSDB full database backup daily once only.
Thanks
Hari
SQL Server MVP
"James Goodwill" <james.goodwill@.uk.fujitsu.com> wrote in message
news:DmmHe.10993$SO4.8738@.newsfe4-win.ntli.net...
> Hi,
> I have a production SQL 2000 database with transaction logging turned on
> ('Full' recovery mode). I backup the transaction log every 15 minutes. In
> order to use the point-in-time recovery option, do I also need to have the
> 'Full' recovery model set on the msdb? I ask this because I assume the
> msdb
> holds information about the transaction log backup taken on the production
> database. Without this information, I suspect point-in-time recover will
> not
> be possible. Is my assumption correct?
> Regards,
> James G.
>
>

msdb trascation logging mode

Hi,
I have a production SQL 2000 database with transaction logging turned on
('Full' recovery mode). I backup the transaction log every 15 minutes. In
order to use the point-in-time recovery option, do I also need to have the
'Full' recovery model set on the msdb? I ask this because I assume the msdb
holds information about the transaction log backup taken on the production
database. Without this information, I suspect point-in-time recover will not
be possible. Is my assumption correct?
Regards,
James G.
Hi
MSDB is not needed to do point in time recovery. MSDB is just used to keep
the backup information so that Enterprise Manager UI can show you what
backups are available. It is a nice to have.
Point in time recovery needs the database dump and all the transaction log
dumps after that to the time you want to restore to.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"James Goodwill" wrote:

> Hi,
> I have a production SQL 2000 database with transaction logging turned on
> ('Full' recovery mode). I backup the transaction log every 15 minutes. In
> order to use the point-in-time recovery option, do I also need to have the
> 'Full' recovery model set on the msdb? I ask this because I assume the msdb
> holds information about the transaction log backup taken on the production
> database. Without this information, I suspect point-in-time recover will not
> be possible. Is my assumption correct?
> Regards,
> James G.
>
>
|||Hi James
The MSDB doesn't have to be in full recovery mode. In fact the MSDB
has no role when you run the restore. If the MSDB would have any role
in the restore then it would be impossible to restore the database on a
different server. All the data that is needed for the point in time
restore is stored in the log backup it self.
Adi
|||Hi,
'Full' recovery model set on the msdb?
Ans:- NO NEED
I suspect point-in-time recover will not be possible. Is my assumption
correct?
No. You can do it with out a MSDB tranasction log backup.
MSDB database holds the backup history information. FOR each backup SQL
Server logs an entry into BACKUPSET table in MSDB database.
This is just an information only and will be useful if you use Enterprise
manager to do point in time recovery. Even if you
do not have tis information you can do a recovery based on Transaction log
file date and time. For a time based recovery:-
1. Restore the Full database backup first with Norecovery
2. Restore the logbackup file in sequence based on date and time with
Norecovery till last file
3. Restore the last transaction log backup with RECOVERY and STOPAT option.
Note:-
I am taking the MSDB full database backup daily once only.
Thanks
Hari
SQL Server MVP
"James Goodwill" <james.goodwill@.uk.fujitsu.com> wrote in message
news:DmmHe.10993$SO4.8738@.newsfe4-win.ntli.net...
> Hi,
> I have a production SQL 2000 database with transaction logging turned on
> ('Full' recovery mode). I backup the transaction log every 15 minutes. In
> order to use the point-in-time recovery option, do I also need to have the
> 'Full' recovery model set on the msdb? I ask this because I assume the
> msdb
> holds information about the transaction log backup taken on the production
> database. Without this information, I suspect point-in-time recover will
> not
> be possible. Is my assumption correct?
> Regards,
> James G.
>
>

msdb trascation logging mode

Hi,
I have a production SQL 2000 database with transaction logging turned on
('Full' recovery mode). I backup the transaction log every 15 minutes. In
order to use the point-in-time recovery option, do I also need to have the
'Full' recovery model set on the msdb? I ask this because I assume the msdb
holds information about the transaction log backup taken on the production
database. Without this information, I suspect point-in-time recover will not
be possible. Is my assumption correct?
Regards,
James G.Hi
MSDB is not needed to do point in time recovery. MSDB is just used to keep
the backup information so that Enterprise Manager UI can show you what
backups are available. It is a nice to have.
Point in time recovery needs the database dump and all the transaction log
dumps after that to the time you want to restore to.
Regards
--
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"James Goodwill" wrote:
> Hi,
> I have a production SQL 2000 database with transaction logging turned on
> ('Full' recovery mode). I backup the transaction log every 15 minutes. In
> order to use the point-in-time recovery option, do I also need to have the
> 'Full' recovery model set on the msdb? I ask this because I assume the msdb
> holds information about the transaction log backup taken on the production
> database. Without this information, I suspect point-in-time recover will not
> be possible. Is my assumption correct?
> Regards,
> James G.
>
>|||Hi James
The MSDB doesn't have to be in full recovery mode. In fact the MSDB
has no role when you run the restore. If the MSDB would have any role
in the restore then it would be impossible to restore the database on a
different server. All the data that is needed for the point in time
restore is stored in the log backup it self.
Adi|||Hi,
'Full' recovery model set on the msdb?
Ans:- NO NEED
I suspect point-in-time recover will not be possible. Is my assumption
correct?
No. You can do it with out a MSDB tranasction log backup.
--
MSDB database holds the backup history information. FOR each backup SQL
Server logs an entry into BACKUPSET table in MSDB database.
This is just an information only and will be useful if you use Enterprise
manager to do point in time recovery. Even if you
do not have tis information you can do a recovery based on Transaction log
file date and time. For a time based recovery:-
1. Restore the Full database backup first with Norecovery
2. Restore the logbackup file in sequence based on date and time with
Norecovery till last file
3. Restore the last transaction log backup with RECOVERY and STOPAT option.
Note:-
I am taking the MSDB full database backup daily once only.
Thanks
Hari
SQL Server MVP
"James Goodwill" <james.goodwill@.uk.fujitsu.com> wrote in message
news:DmmHe.10993$SO4.8738@.newsfe4-win.ntli.net...
> Hi,
> I have a production SQL 2000 database with transaction logging turned on
> ('Full' recovery mode). I backup the transaction log every 15 minutes. In
> order to use the point-in-time recovery option, do I also need to have the
> 'Full' recovery model set on the msdb? I ask this because I assume the
> msdb
> holds information about the transaction log backup taken on the production
> database. Without this information, I suspect point-in-time recover will
> not
> be possible. Is my assumption correct?
> Regards,
> James G.
>
>

msdb recovery on sql 2005

Hi

I have a backup of msdb on sql 2005 version 9.00.2047

I need to use this backup to restore msdb on the same machine.

But the version has been upgraded to 9.00.2153

All of my attempts end up with the same messages

"...cannot be restored because it was created by a different version of the server..."

Thanks.

You are going to have to find an install of version 9.00.2047, restore the msdb database, upgrade the instance to 9.00.2153, backup the msdb database again, and then use that backup to restore to the instance that you want.

There is a reason that every hotfix and service pack has an explicit warning message that you must backup system databases immediately after applying the service pack or hotfix. You can not restore a system database across hotfix or service pack versions.

|||Thanks it worked as you said.

MSDB Recovery Model Option

Hi,
On one of our servers, whenever there is a system reboot the recovery model
option on the MSDB database is reset to 'Simple'. This is causing the
Transaction Log to fail. At that point I have to go back and change it to
'Full' again. Is there any setting/configuration that I can change so the
recovery model is not changed and is always 'Full' like I setup. Any kind of
input on this is very much appreciated.
Thank you
This is by design. Leave the MSDB database in simple recovery and do more
frequent full backups. SQL does not like full recovery for system
databases.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"helpplease" <helpplease@.discussions.microsoft.com> wrote in message
news:C862E63E-B996-43A8-8936-7C691D15C0F0@.microsoft.com...
> Hi,
> On one of our servers, whenever there is a system reboot the recovery
> model
> option on the MSDB database is reset to 'Simple'. This is causing the
> Transaction Log to fail. At that point I have to go back and change it to
> 'Full' again. Is there any setting/configuration that I can change so the
> recovery model is not changed and is always 'Full' like I setup. Any kind
> of
> input on this is very much appreciated.
> Thank you
>
|||Thank you very very much Geoff.
"Geoff N. Hiten" wrote:

> This is by design. Leave the MSDB database in simple recovery and do more
> frequent full backups. SQL does not like full recovery for system
> databases.
> --
> Geoff N. Hiten
> Senior Database Administrator
> Microsoft SQL Server MVP
>
> "helpplease" <helpplease@.discussions.microsoft.com> wrote in message
> news:C862E63E-B996-43A8-8936-7C691D15C0F0@.microsoft.com...
>
>

MSDB Recovery Model Option

Hi,
On one of our servers, whenever there is a system reboot the recovery model
option on the MSDB database is reset to 'Simple'. This is causing the
Transaction Log to fail. At that point I have to go back and change it to
'Full' again. Is there any setting/configuration that I can change so the
recovery model is not changed and is always 'Full' like I setup. Any kind of
input on this is very much appreciated.
Thank youThis is by design. Leave the MSDB database in simple recovery and do more
frequent full backups. SQL does not like full recovery for system
databases.
--
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"helpplease" <helpplease@.discussions.microsoft.com> wrote in message
news:C862E63E-B996-43A8-8936-7C691D15C0F0@.microsoft.com...
> Hi,
> On one of our servers, whenever there is a system reboot the recovery
> model
> option on the MSDB database is reset to 'Simple'. This is causing the
> Transaction Log to fail. At that point I have to go back and change it to
> 'Full' again. Is there any setting/configuration that I can change so the
> recovery model is not changed and is always 'Full' like I setup. Any kind
> of
> input on this is very much appreciated.
> Thank you
>|||Thank you very very much Geoff.
"Geoff N. Hiten" wrote:
> This is by design. Leave the MSDB database in simple recovery and do more
> frequent full backups. SQL does not like full recovery for system
> databases.
> --
> Geoff N. Hiten
> Senior Database Administrator
> Microsoft SQL Server MVP
>
> "helpplease" <helpplease@.discussions.microsoft.com> wrote in message
> news:C862E63E-B996-43A8-8936-7C691D15C0F0@.microsoft.com...
> > Hi,
> >
> > On one of our servers, whenever there is a system reboot the recovery
> > model
> > option on the MSDB database is reset to 'Simple'. This is causing the
> > Transaction Log to fail. At that point I have to go back and change it to
> > 'Full' again. Is there any setting/configuration that I can change so the
> > recovery model is not changed and is always 'Full' like I setup. Any kind
> > of
> > input on this is very much appreciated.
> >
> > Thank you
> >
>
>

MSDB Recovery Model Option

Hi,
On one of our servers, whenever there is a system reboot the recovery model
option on the MSDB database is reset to 'Simple'. This is causing the
Transaction Log to fail. At that point I have to go back and change it to
'Full' again. Is there any setting/configuration that I can change so the
recovery model is not changed and is always 'Full' like I setup. Any kind o
f
input on this is very much appreciated.
Thank youThis is by design. Leave the MSDB database in simple recovery and do more
frequent full backups. SQL does not like full recovery for system
databases.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"helpplease" <helpplease@.discussions.microsoft.com> wrote in message
news:C862E63E-B996-43A8-8936-7C691D15C0F0@.microsoft.com...
> Hi,
> On one of our servers, whenever there is a system reboot the recovery
> model
> option on the MSDB database is reset to 'Simple'. This is causing the
> Transaction Log to fail. At that point I have to go back and change it to
> 'Full' again. Is there any setting/configuration that I can change so the
> recovery model is not changed and is always 'Full' like I setup. Any kind
> of
> input on this is very much appreciated.
> Thank you
>|||Thank you very very much Geoff.
"Geoff N. Hiten" wrote:

> This is by design. Leave the MSDB database in simple recovery and do more
> frequent full backups. SQL does not like full recovery for system
> databases.
> --
> Geoff N. Hiten
> Senior Database Administrator
> Microsoft SQL Server MVP
>
> "helpplease" <helpplease@.discussions.microsoft.com> wrote in message
> news:C862E63E-B996-43A8-8936-7C691D15C0F0@.microsoft.com...
>
>