Are they essentially the same thing? Do they or can they backup the same thing in terms of SharePoint? It looks as though NTBackup can only be used to backup the DB and STSADMIN is used to backup EVERYTHING related to a SharePoint site including the DB. Is this true?
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations derfloh on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
NTBackup or STSADIM?
- Thread starter jdnorris
- Start date
Thomas2000
Technical User
Hello,
the stsadm does not do a database backup per say, but it does backup everything in your sites (and since everything i sharepoint is stored in a database, it gets the data from there). I am running both stsadm for site backup and then using maintenance jobs in SQL to do actual database backups of the SQL databases.
the NTbackup will not be able to restore/move/migrate a sharepoint site in the same way as the stsadm does.
So I would recommend you to use stsadm for your sharepoint backups, if you do not have a 3rd party SharePoint specific backup software.
Cheers,
Thomas
the stsadm does not do a database backup per say, but it does backup everything in your sites (and since everything i sharepoint is stored in a database, it gets the data from there). I am running both stsadm for site backup and then using maintenance jobs in SQL to do actual database backups of the SQL databases.
the NTbackup will not be able to restore/move/migrate a sharepoint site in the same way as the stsadm does.
So I would recommend you to use stsadm for your sharepoint backups, if you do not have a 3rd party SharePoint specific backup software.
Cheers,
Thomas
Burninator
IS-IT--Management
- Jul 8, 2003
- 40
As Thomas said STSADM will make a complete backup of your WSS site or site group into a file you specify then you can back that file up to tape. However if you are using SQL for your backend databases, you can also use the SQL backup to backup the Config and Content databases there. I don't suggest re-usig the config DB, if moving or restoring the sites to them same or a new server.
Also note neither of these backup methods will take into account customizations to your Sharepoint Sites, by that I mean Web Parts, CSS, basically anything that is not a part of the SQL database. If you want to backup those customizations I suggest with NTbackup, backing up the c:/program files/common files/microsoft shared/web server extensions/60/ directory.
If you are using WMSDE, I highly suggest if you can to install the SQL Client tools to administer the WMSDE databases the OSQL command line can be a bit intimidating to use. If you don't have a full blown version of SQL 2000, download the EVAL version from the Micrsoft site to install them.
Later
Jay
Also note neither of these backup methods will take into account customizations to your Sharepoint Sites, by that I mean Web Parts, CSS, basically anything that is not a part of the SQL database. If you want to backup those customizations I suggest with NTbackup, backing up the c:/program files/common files/microsoft shared/web server extensions/60/ directory.
If you are using WMSDE, I highly suggest if you can to install the SQL Client tools to administer the WMSDE databases the OSQL command line can be a bit intimidating to use. If you don't have a full blown version of SQL 2000, download the EVAL version from the Micrsoft site to install them.
Later
Jay
- Status
Similar threads
- Locked
- Question
- Locked
- Question