correct way to backup?

hi,
to backup my sql server 2000 databases, I right click on the database name
(from enterprise mgr),select the backup database option, choose 'database
complete' , and then add a filename as the destination. I backup to a files
on the harddisk and then backs up those files to a tape.
Is this a good backup process? I mean, the way I am doing it, will it backup
the complete database, the users on that database, etc? And will I have
problems while restoring? By restoring, I mean I will create a new database
(empty) by the same name in a different machine and then restore it from the
backup file.Will the users in that database also get restored?
Your suggestions are very much appreciated.
thanks!!HOW TO: Move Databases Between Computers That Are Running SQL Server
http://support.microsoft.com/defaul...kb;en-us;314546
AMB
"rtn" wrote:

> hi,
> to backup my sql server 2000 databases, I right click on the database name
> (from enterprise mgr),select the backup database option, choose 'database
> complete' , and then add a filename as the destination. I backup to a file
s
> on the harddisk and then backs up those files to a tape.
> Is this a good backup process? I mean, the way I am doing it, will it back
up
> the complete database, the users on that database, etc? And will I have
> problems while restoring? By restoring, I mean I will create a new databas
e
> (empty) by the same name in a different machine and then restore it from t
he
> backup file.Will the users in that database also get restored?
> Your suggestions are very much appreciated.
> thanks!!|||This is a good start. You need to automate the process somehow. The
database maintenance wizard offers some help or you can write scripts and
use the SQL agent to schedule them. The most important thing is to test
your recovery process. Restore the databases somewhere. See what you get.
Document the process and any extra recovery steps you figure out. You don't
want to be figuring this out under the time crunch of a down system.
Geoff N. Hiten
Microsoft SQL Server MVP
"rtn" <rtn@.discussions.microsoft.com> wrote in message
news:DF6C6D32-9A0C-4866-9918-79EAFF6DEEB1@.microsoft.com...
> hi,
> to backup my sql server 2000 databases, I right click on the database name
> (from enterprise mgr),select the backup database option, choose 'database
> complete' , and then add a filename as the destination. I backup to a
> files
> on the harddisk and then backs up those files to a tape.
> Is this a good backup process? I mean, the way I am doing it, will it
> backup
> the complete database, the users on that database, etc? And will I have
> problems while restoring? By restoring, I mean I will create a new
> database
> (empty) by the same name in a different machine and then restore it from
> the
> backup file.Will the users in that database also get restored?
> Your suggestions are very much appreciated.
> thanks!!|||thanks for your reply.
I tried a test recovery. All goes well, expect the fact that users that are
present in the original database does not get restored. I think everything
except the users get restored.
any suggestions on this would be greatly appreciated.
thanks!
"Geoff N. Hiten" wrote:

> This is a good start. You need to automate the process somehow. The
> database maintenance wizard offers some help or you can write scripts and
> use the SQL agent to schedule them. The most important thing is to test
> your recovery process. Restore the databases somewhere. See what you get
.
> Document the process and any extra recovery steps you figure out. You don
't
> want to be figuring this out under the time crunch of a down system.
> Geoff N. Hiten
> Microsoft SQL Server MVP
> "rtn" <rtn@.discussions.microsoft.com> wrote in message
> news:DF6C6D32-9A0C-4866-9918-79EAFF6DEEB1@.microsoft.com...
>
>|||Look up sp_change_users_login in BOL to relink users and logins. The users
still exist, it is just the logins they link to are not on the restore
server. That is part of what I meant by documenting the entire recovery
process. What changes do you need to make to the server and the environment
to replace a failed server? That is what you have to document. Restoring a
database is a very small part of the entire recovery process.
Geoff N. Hiten
Microsoft SQL Server MVP
"rtn" <rtn@.discussions.microsoft.com> wrote in message
news:AEE9F493-416C-46FD-A410-6E8473C0C10A@.microsoft.com...[vbcol=seagreen]
> thanks for your reply.
> I tried a test recovery. All goes well, expect the fact that users that
> are
> present in the original database does not get restored. I think everything
> except the users get restored.
> any suggestions on this would be greatly appreciated.
> thanks!
> "Geoff N. Hiten" wrote:
>|||thanks for the help again. As you said, sp_change_users_login did the job of
linking the SQL users and the logins. I documented the procedure.
two more quick questions.
1. this stored procedure doesn't work with windows users. In addition to sql
users, my databases also have a few windows users. How can I go about
restoring these windows users and their permissions?
2. also, this stored procedure doesn't work for dbo etc. So what can i do
about restoring dbo, etc
thanks again, you have been a major help.
"Geoff N. Hiten" wrote:

> Look up sp_change_users_login in BOL to relink users and logins. The user
s
> still exist, it is just the logins they link to are not on the restore
> server. That is part of what I meant by documenting the entire recovery
> process. What changes do you need to make to the server and the environme
nt
> to replace a failed server? That is what you have to document. Restoring
a
> database is a very small part of the entire recovery process.
> Geoff N. Hiten
> Microsoft SQL Server MVP
>
> "rtn" <rtn@.discussions.microsoft.com> wrote in message
> news:AEE9F493-416C-46FD-A410-6E8473C0C10A@.microsoft.com...
>
>