Do not try to make PC1 or PC2 to point directly to the job database file on another computer. This will only lead to problems. Here is a solution for your situation:
1. On PC2, which is always on, run 24x7 in the master scheduler mode (e.g. server mode enable) with a local job database file.
2. On PC1, which is tuned on sometimes, also use a local job database file
3. On PC1 setup remote agent profile for the master scheduler (Tools/Remote Agents menu)
4. On PC1 setup a job to periodically replicates the job database (or a job that is run manually and has [no schedule] for the schedule. When asked for the destination use profile name specified in step #3. Tip: For #4 use available jobs replication template (Tools/New/Job From Template menu)
When PC1 is on, it will periodically or on demand update jobs to PC1. : Hi, : Sorry for my bad english, i'm french.
: Here is what I want to make :
: http://img309.imageshack.us/my.php?image=local2ll.jpg : PC2 is switched on, all the time
: PC1 is sometimes switched on, not always (so impossible to apply remote
: agents)
: PC1 sometimes modify the data base of pc2 (job.dat) : When i try to do it, the software on pc1 said me : "Unable to write to
: job database. File may be opened by another instance...."
: Because the first pc whitch is started is pc2 and It takes the rights of
: writing on the file job.DAT.
: So after pc1 can't modify the base by the local area network of Windows. : A solution ? (Pc2 is always started the first one) : Thanks for your help.
|
