Solved

Backup Jobs failing using the Integrated backup utility in 2003 Server

Posted on 2004-09-01
4
165 Views
Last Modified: 2010-04-19
The backup jobs are failing on my servers.  I remote in to each server and start the job and if I log off before the backup is done it fails to complete itself.  I have about 15 servers and this becomes a pain.  I got to the point where I'll Login thru remote desktop and start the jobs and instead off logging off I just close out the remote desktop leaving myself logged on.  This works but only for a couple of days until the session times out.  Does anyone know how I could go about Backing my servers without being logged on using the Intergrated Backup Utility in Server 2003.
0
Comment
Question by:john-coleman
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
4 Comments
 
LVL 11

Accepted Solution

by:
infotrader earned 250 total points
ID: 11955846
The problem with Remote Desktop or Terminal Services is that when you start a program or something, you are only starting the program for that session.  Once you log out, the session disconnects and terminates, closing any applications you are running on that particular session.

You should try to log in directly from the console and start the backup job, or setup jobs directly through the console instead.

If you want remote access capability that do not terminate, you should try something like VNC or PCAnywhere.  I use tightVNC to do this.  It basically takes control of the server/workstation instead of just starting a session, so for example, when you move the mouse, you can see on the server that the mouse actually moves.  That way, you KNOW you are running the services/apps using the primary console, NOT the session.

- Info
0
 
LVL 16

Assisted Solution

by:JamesDS
JamesDS earned 250 total points
ID: 11959214
john-coleman

To logon to the console remote with terminal services:

MSTSC /v:servername /CONSOLE

This should stay logged in regardless of whether you are connected, but only works on Windows 2003 servers as 2000 does not support console login with TS

Cheers

JamesDS
0

Featured Post

NEW Veeam Agent for Microsoft Windows

Backup and recover physical and cloud-based servers and workstations, as well as endpoint devices that belong to remote users. Avoid downtime and data loss quickly and easily for Windows-based physical or public cloud-based workloads!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

Recently, I had the need to build a standalone system to run a point-of-sale system. I’m running this on a low-voltage Atom processor, so I wanted a light-weight operating system, but still needed Windows. I chose to use Microsoft Windows Server 200…
Scenerio: You have a server running Server 2003 and have applied a retail pack of Terminal Server Licenses.  You want to change servers or your server has crashed and you need to reapply the Terminal Server Licenses. When you enter the 16-digit lic…
Attackers love to prey on accounts that have privileges. Reducing privileged accounts and protecting privileged accounts therefore is paramount. Users, groups, and service accounts need to be protected to help protect the entire Active Directory …

740 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question