backup files from another server with sbs backup
I have an sbs 2003 premium, with sbs backup confugured.
Next to that server we have a TSserver running.
Is it possible to backup some folders from that TSserver with the sbs backup?
Or is it only possible to backup the local stuff?
It's a really small firm, so it isn't possible to buy expensive solutions like Arcserve or backup exec.
If it's not possible to backup from other servers, what would be another cheap / good solution?
Next to that server we have a TSserver running.
Is it possible to backup some folders from that TSserver with the sbs backup?
Or is it only possible to backup the local stuff?
It's a really small firm, so it isn't possible to buy expensive solutions like Arcserve or backup exec.
If it's not possible to backup from other servers, what would be another cheap / good solution?
Saineolai
Configure NT Backup on the Terminal Server to back up files to a directory shared out on the SBS server would be one option.
ASKER
Saineolai,
I thought about that, but i would like to centralise the backup on the sbs server, if possible ...
I thought about that, but i would like to centralise the backup on the sbs server, if possible ...
The standard backup does not offer to backup shared network folders, but it is also possible to schedule a second NT backup job including those folders. Or if you like to experiment directly editing "Small Business Backup Script.bks". But I went for Saineolai's solution initiating them on the second server through ntbackup.
suppsaws
i'd get some external storage for each server and attach via 1gigabit ethernet or USB 2.0. then i'd run a ntbackup on each of them. here is why i'd do it that way.
(1) by moving your backup files onto another external disk, you won't lose your backup data if the computer's HD fails.
(2) instead of it backing up your SBS server and then your TSserver, you could back them up simulantiously making for faster backups.
i know it doesnt really answer your question, just some friendly advice.
michael
myfootsmells
i'd get some external storage for each server and attach via 1gigabit ethernet or USB 2.0. then i'd run a ntbackup on each of them. here is why i'd do it that way.
(1) by moving your backup files onto another external disk, you won't lose your backup data if the computer's HD fails.
(2) instead of it backing up your SBS server and then your TSserver, you could back them up simulantiously making for faster backups.
i know it doesnt really answer your question, just some friendly advice.
michael
myfootsmells
What are you wanting to back up on the Terminal Server? If it's data, you should keep that on your SBS and then you won't have to worry about backing up a separate server (other than perhaps imaging the server to be able to reinstall it in case of major disaster).
If there is too much data to put on your SBS, you might consider a Windows Storage Server configuration: http://www.microsoft.com/windowsserversystem/wss2003/techinfo/plandeploy/wss_sbs.mspx
Jeff
TechSoEasy
If there is too much data to put on your SBS, you might consider a Windows Storage Server configuration: http://www.microsoft.com/windowsserversystem/wss2003/techinfo/plandeploy/wss_sbs.mspx
Jeff
TechSoEasy
ASKER
It's just data indeed.
The data is now on the SBS server.
Although now all data is on the sbs server, what can I use the space on the tsserver for?
Won't the sbs server get too much load?
Isn't it better to place the data from the TS applications on the TS server itself?
The data is now on the SBS server.
Although now all data is on the sbs server, what can I use the space on the tsserver for?
Won't the sbs server get too much load?
Isn't it better to place the data from the TS applications on the TS server itself?
suppsaws
i would place data that's needed on the TS server to conserve network bandwidth, but that's just me.
michael
myfootsmells
i would place data that's needed on the TS server to conserve network bandwidth, but that's just me.
michael
myfootsmells
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.