make_net_recovery and cron (distribution)

[Romalfox]

Team,

I'm setting up a local management server with my scripts and stuff.
I created a small script to take a make_net_recovery and wants to add this script to the crons of my client (servers).

However, I want to maintain this script locally, even so as all cron tasks.
So I was thinking:
1/ create make_net_recovery script locally
2/ add this script to my own crontab
3/ scp make_net_recovery-script to all clients
4/ scp my own crontab to all clients

however, then all clients will start their make_net_recovery exactly at the same time ...

any workarounds ?

brgds,

Raf

[Torsten.]

Well, all depends on the amount of free network resources, number of clients and how busy the server is.

I think you need to check how many clients the server can serve at a time ...

[Romalfox]

Well for the moment my archive server is just 2 mirrored internal disks of 146 GB, so I'm not expecting miracles of that.
Even so, if all 10 clients start at the same time, they all may take longer then when I start them one after the other ?
So what I want to accomplish is to have them all start with 1 hour difference.

[Ganesan R]

Hi,

I am not sure whether I understood your requirement correct or not. If you have a ignite server and wants to take clients backup in regular interval in different timings then
schedule the crontab entry with different timings in the clients like below.

on client1:
===========

00 01 15 * * /opt/ignite/bin/make_net_recovery -s

on client2:
===========
00 01 1 * * /opt/ignite/bin/make_net_recovery -s

on client 2

[Romalfox]

Hello,

yes that is exactly what I want, but I do not want to log on to each server, edit the contab en move to the next.

No I was thinking of creating one crontab, distribute it, and then apply some kind of trick I'm still looking for to make sure each server starts at a different time.

What you suggest is correct, but my question is, how to implement this with the least effort ?

[OldSchool · Accepted solution]

well, i guess you could make a script that contains the "make_net_recovery".

Within the script you could examine the hostname that it runs on and then fire off an "at" job at various times based on the hostname.

That would keep the script and the crontab the same, but buries the details of when the make_net_recovery actually is run.

This could cause issues around daylight saving time transitions, if they apply.

and it introduces a level of obfuscation that I don't like to see, but thats up to you.

[Romalfox]

All, I decided to edit the cron on the ignite server to
ssh HOSTNAME make_XXX_recovery

so it is the server who manages.

Thank you alle for the replies.


Raf

[Steven E. Protter]

Shalom Raf

make_net_recovery uses a lot of network band width.

It is a BAD idea to start them all the same time. You need to stagger them.

Have root start the job on each system and set the crontab to stagger the jobs.

SEP

[Romalfox]

SEP, All,

I was not totally clear ;-)

Ignite server (cron)
0 22 * * * ssh server1 make_net_recovery
0 23 * * * ssh server2 make_net_recovery
etc etc

thanks all,


Raf