[Search for users]
[Overall Top Noters]
[List of all Conferences]
[Download this site]
Title: | DEChub/HUBwatch/PROBEwatch CONFERENCE |
Notice: | Firmware -2, Doc -3, Power -4, HW kits -5, firm load -6&7 |
Moderator: | NETCAD::COLELLA DT |
|
Created: | Wed Nov 13 1991 |
Last Modified: | Fri Jun 06 1997 |
Last Successful Update: | Fri Jun 06 1997 |
Number of topics: | 4455 |
Total number of notes: | 16761 |
3432.0. "Recovery Mgr config. examples" by NETCAD::GILLIS () Tue Apr 09 1996 13:40
This is taken from the clearVISN Recovery Manager Version V1.1 Release Notes
11 Scheduling Recovery Manager Batch Jobs on Windows NT
11.1 Running Recovery Manager in Batch Mode
Recovery Manager has a non-gui interface for executing command
files from a DOS window. Once a command file is created in the
GUI, it can be executed either within Recovery Manager using the
Command File button in the Main window, or it can be executed in
a DOS window with the following syntax:
Recovery Manager Batch mode syntax (spacing is important):
(installed_path)\recov.exe -j command_file
The logfile that you specified in each backup and restore job when
you created the command file will be appended with the new sta-
tus information. The Recovery Manager logfile, recov.log, will
record a history of the user action.
11.2 Using Windows NT to Schedule Batch Jobs
Setup of Schedule service
Go to Main->Control Panel->Services, select the Schedule service,
and change the Startup Type to be automatic (if not already) us-
ing the Startup button. [The same information can be found through
Recovery Manager's main window Help icon, following the link "Prod-
uct Overview->Product Features-> click Here for Batch mode .."
to "Executing a Command File in Windows NT in Batch Mode".]
Usage of the "AT" command
Once the Scheduler service is started, the AT command runs a batch
file at a specified time. The default is to run jobs on the lo-
cal computer; the \\computername switch allows you to schedule
a job to run on a remote computer.
Type AT ? in the dos window for more info. Each scheduled job has
its own id spawned. You can list all scheduled jobs by typing "AT"
with no arguments, and you can delete a job from the list by spec-
ifying its id with the /DELETE switch.
Other switches such as /EVERY:date[,...] and /NEXT:date[,...] al-
low you to define a repeat sequence to the job. Specify the full
name of the day(s) of the week and/or the number of the day in
a month in a comma-separated list after the colon.
Important
Jobs using the /EVERY switch live forever unless deleted
by their process id. All other jobs are removed by the
system once they have been executed, unless the user
deletes them. Rebooting or restarting the computer has
no effect on the jobs in the scheduler.
Job Create Syntax:
WIN AT [\\computername] time [/every:date[,...]] [/next:date[,...]]
command
Job Destroy Syntax:
WIN AT [\\computername] id /delete OR /delete /yes
AT command Scheduling Examples
o Example 1: Run batch.bat at 2:30 pm today
AT 14:30 c:\recov\batch.bat
o Example 2: Delete first job
AT 1 /delete
o Example 3: Run "batch.bat" at 9:00am every Thursday and Fri-
day
AT 9:00 /EVERY:th,f c:\recov\batch.bat
o Example 4: Run "batch.bat" at 9:00am next Wednesday only
AT 9:00 /NEXT:w c:\recov\batch.bat
o Example 5: Run "batch.bat" at 3:45 pm on the 1st and 15 day of
each month, and on every Friday
AT 3:45 /every:1,15,f c:\recov\batch.bat
12 Automatic Network Configuration with Recovery Manager -
Examples
Once a Backup operation of a network has been saved, Recovery Man-
ager can be used to restore that configuration. Running Recov-
ery Manager in batch mode with the "AT" command allows the user
to restore configurations automatically on a time schedule of the
user's choosing.
A few examples are given below, and how each would be implemented
follows the problem description. Each assumes that Recovery Man-
ager was installed in directory path c:\recov for simplicity, and
that Windows NT's Schedule service has been started and is con-
figured properly.
12.1 Example 1 - Saving a Baseline Configuration
o Task Description
A network manager wishes to automatically save the current con-
figuration of her hub once a week.
o Solution
o Steps Within Recovery Manager
Using Recovery Manager, the network manager opens a Backup
window via the GUI for the hub, specifies "Select All" to
select all supported devices and parameter subsets, and checks
the "Save to Command File" box so that the entire operation
is saved to a command file. She chooses the logfile name "base-
line.log", the saveddata file name "baseline.sdf", and the
command file name "baseline.cmd".
o Steps Outside Recovery Manager
She creates a batch file, "baseline.bat", with the follow-
ing contents:
C:\recov\recov.exe -j C:\recov\baseline.cmd
She then issues the following command in a DOS window at the
prompt to schedule "baseline.bat" to run at the proper time:
C:\> win at 20:00 /EVERY:f C:\recov\baseline.bat
This will run "baseline.bat" every Friday at 8:00pm, which
will save the current configuration of the hub to "baseline.sdf",
append the status information for the operation to "base-
line.log", and append event history information to "recov.log".
To keep separate copies of the saved configuration from week
to week, she manually copies "baseline.sdf" to a filename
of the form "<today's_date>.sdf" when she arrives at work
on Monday morning of the next week. To see if the saved con-
figuration data has changed from week to week, she can in-
voke an external facility such as "WinDiff" on .sdf files
from successive weeks.
12.2 Example 2 - Restoring Daily and Nightly Configurations
o Task Description
A network manager wishes to configure his network at differ-
ent times based on user demand. He knows that the network has
two distinct utilization trends (daily and nightly operation),
and wishes to automatically configure each hub in the network
for these two different modes of operation. The daily config-
uration will define parameters that will maximize bandwidth dur-
ing the weekday or peak hours, and the nightly configuration
will define lower-cost parameters for the off-peak nightly hours.
For simplicity, it is assumed that his network is composed of
two DEChub900 hubs.
o Solution
o Steps within MultiChassis Manager/Recovery Manager
The network manager has to configure each hub for daily op-
eration using MultiChassis Manager. Once a configuration is
applied for each hub/agent, he can invoke Recovery Manager
from within MultiChassis Manager using the Applications pull-
down, and Backup the daily configuration information for each
hub to a separate saveddata file. This has to be repeated
for the nightly configuration, where separate and unique saved-
data files for each hub are chosen.
A Restore window is then opened for each hub, specifying the
saveddata file of each hub's daily configuration from the
previous backup operation. A common command file name is se-
lected to contain the commands that restore daily config-
urations for both hubs. This is repeated for the nightly op-
eration, where separate Restore windows for each hub are opened
that reference their respective nightly saveddata parame-
ter files. A common command file name (different from thecom-
mand file used for the daily configuration) is selected to
contain the commands that restore nightly configurations for
both hubs.
The desired result of these steps is the creation of com-
mand files that will restore the daily and nightly param-
eters for each hub. This eliminates the need to go back through
the "Restore" window to restore a particular configuration;
one need only run the command file through Recovery Manager's
GUI Command File icon, or run it in batch mode from a DOS
window.
o Steps Outside Recovery Manager
For this example, assume that the network manager saved the
command files for restoring the daily and nightly config-
urations within Recovery Manager as c:\recov\daily_r.cmd and
c:\recov\night_r.cmd, respectively. These will be referenced
in batch files that are run with the "AT" command for job
scheduling, as will follow.
For restoring the daily configuration, he would create a batch
file, "daily.bat", with the following contents:
c:\recov\recov.exe -j c:\recov\daily_r.cmd
To schedule the daily configuration to be applied every day,
he would type at the DOS prompt:
c:\> win at 6:00 /every:m,t,w,th,f,s,su c:\recov\daily.bat
This would restore the daily configuration at 6:00am every
morning.
For restoring the nightly configuration, he would create a
batch file, "nightly.bat", with the following contents:
c:\recov\recov.exe -j c:\recov\night_r.cmd
To schedule the night configuration to be applied every night,
he would type at the DOS prompt:
c:\>win 20:00 /every:m,t,w,th,f,s,su c:\recov\nightly.bat
This would restore the night configuration at 8:00pm every
night.
T.R | Title | User | Personal Name | Date | Lines |
---|
3432.1 | Recovery Manager Configuration Examples - now in online help | NETCAD::GILLIS | | Thu Jul 25 1996 11:48 | 9 |
| The online help has this information now.
Follow the links from Recovery Manager's Main tool bar help icon [?]:
Release Info->General Recovery Manager Issues
->Automatic Network Configuration with Recovery Manager
John Gillis
clearVISN Apps - Recovery Manager
|