5...4...3...2...1...fly!
Fly! Do flyyyyy!
A patient
has broken both legs, three ribs and bruised the right wrist when trying to fly.
Shall we go flying? Far from it, we will rather create a logon script.
The backup is prepared, how to
set it up?
In the last step we prepared a script which
will enable us to back up data on a workstation. How to run it now? It is the Administrator
again, who will help us, specifically [the second]
button.
Step 1: Create a new logon
script...
We have two possibilities to
select. We can create a logon/netlogon/login script. It is a script in the
.bat or .cmd format, by means of which you can run the backup by clicking
the script or run it when logging in the domain. The second possibility is to
create a registry file by means of which you can facilitate the setup on individual stations
in the peer-to-peer network. Upon clicking the logon script will be inserted
in the register, in the key HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Run.
We will select the first option and go on.
Step 2: Which backup
script do you want to run?
It is advisable to say whence
the backup will actually be launched. So in the first field ("NetBackup.lite runtime....") we will enter:
Step 3: On which days do you want to enable the script to be launched?
It is unlikely, that
you will want to run the backup every day. For example every Wednesday is sufficient.
Just one click and that's it:
Step 4: Advanced setting...
Here you can
set two
items. The first one, "Size of the block being copied", is the size of
the data
which are being copied in one step. 8192 B is the default setting, i.e.
if the backuped file has 16384 B, it will be copied in two parts. This
setting affects memory resources needed by the application. This number
may not be lower than 1024 B (the default setting is 8192 B) and must
be a multiple of 1024.
Another setting is "Delay before the backup starts". This option enables setting of time in seconds (0-1000) for which NetBackup.lite will wait before the backup starts.
Windows 95
If you have
Windows 95 in a network
with the NT server (or the Windows 2000 server) and launch the backup
from the logon script
(as we do), it can happen, that it starts backing up, although the
Windows 95
system has not finished initialization routines yet and complete
interface (explorer.exe) has not start. In case of slower PCs the
system is not able to provide
enough resources to the NetBackup application and the application fails
with the error
"the program has performed an invalid operation" or behaves strangely.
The delay option
is a solution to this problem. You can set for example 15 seconds of
delay. The applications waits, Windows will start correctly and the
backup will be performed without any problems.
There is probably no use to explain the third one, "Switch off the computer after the backup is finished":) Here we will not set anything in our case.
The next item is "Yes, I want to enable weekly data cycling during the whole backup". NetBackup enables differentiation of days in a week and backing up always in the folder with the name of the day, on which the backup runs. On Monday the backup is placed in the folder "Monday", the backup of Tuesday in the folder "Tuesday" etc. The application is evident: on Monday you carry out a backup, the next day you change something and carry out a backup again. On Wednesday you will find out, that the correct result was in the document of Monday and it is too late, because you have backed up in one place. This function prevents this, you can always return to the backups which are one week old. We will not use it here and continue through the button "Next".
Step 5: Saving logon script...
Well. The last step.
We call the script "All.bat" and place it directly in the folder
"NetLogon".
Done!
Everything is prepared. Now we need to set our system to run this script during network logon and that's all.
Upon the next network logon - if on Wednesday - the backup is launched and the whole content of folders is backed up on the server. The first backup will, of course, last longer, next time only changed files will be transferred.
Windows 2000
Server
This example
shows, how to apply NetBackup.lite on Windows 2000 server. It is quite
similar in Novell NetWare or Windows NT networks, for detailed
information see manual of your network. You may of course use
"Sheduler" to schedule running backups or run them using "Script
Runner", it depends on you.
Windows 95
You can
encounter problems running NetBackup on some workstations with Windows
95. If you get "Runtime error 21x" after backup and the application
will fail, you may have too long name of runtime application. In
Windows 95, the name of runtime cannot be longer than 8 characters, for
example "Backup.exe".
Script Runner.....well, well,
I do not know this one either.
"Script Runner" ("ScriptRunner.exe") is a little tool for users to
be able to easily run backup. Its setting can be found in the security setting help,
here we will show you, how it looks like:
You may send its shortcut to users, which can run the backup using this shortcut.
Setting of other features of the application can be found at the beginning, in security setting help. Well, do we take a [cake] now and [let's get down to it]?