Creating and configuring jobs
Jobs can still be newly created or jobs can be updated via the command line.
The following command must be entered:
C:Program Files (x86)vdogClientVDogAutoCheckIn.exe" /RD:d:vdClientArchive /at:c /JobConfig /CFile:d:AutoCheckIn.ini /Password:******** /Account:versiondog
In addition to parameters for AutoCheckIn, the /JobConfig parameter must also be specified for job creation.
| Paramete | Descriptio |
|---|---|
| /JobConfi | Indicates that a job should be created!!! note Only required if only the job configuration is to be changed and no component is to be created, no versioning and no check-in is to be performed. |
Configuration file
In addition to the entries described AutoCheckIn, the INI file for the job configuration contains the section [Jobconfig]. The section keys can be used to enter values for job configuration settings that are also available in the Job configuration area in the AdminClient. For the settings for which no values are specified in the INI file, default values are set.
Key Description
JobId ID of the job whose configuration is to be changed.
TemplateJobId ID of the job whose configuration (excluding the ID) should be taken over.
JobName
Name of the job
Note
If the name is empty, an existing job must be found through the JobId or TemplateJobId keys.
The default value is an empty string.
UploadType
Name of the upload type
Note
If the name is empty, an existing job must be found through the JobId or TemplateJobId keys.
The default value is an empty string.
ComponentId
ID of the component
Note
If the name is empty, an existing job must be found through the JobId or TemplateJobId keys.
The default value is an empty string.
UploadAgentId
ID of the upload agent
The default value is an empty string.
Note
To determine the IDs of the upload agents configured in your system, you have two options:
- In the AgentStations.ini file (
vdServerArchiveVD$AConfiguration), you will find the ID of the agent after the prefix U_. - Select the desired job in the AdminClient in the Jobs module, select Copy job parameters to clipboard in the Help tab, in the ribbon, and then paste the contents of the clipboard into an editor. The ID of the upload agent is displayed as the value of the 4959 key.
ComparePolicy
Indicates the comparison strategy. Possible values:
0: No comparison takes place.
1: Previous Backup <-> Backup
2: Server version <-> Backup
3: Server version <-> Backup, Previous Backup <-> Backup
The default value is 3.
Execute
Indicates when the job should be executed. Possible values:
0: Execution is not carried out according to a schedule.
1: Execution is carried out according to a schedule.
2: The BackupClient is used for the execution
The default is 0.
RollOver
Number of remaining backups (Rollover)
A minimum of 1 and a maximum of 999 backups will be kept.
The default value is 5.
RepetitionOnError
Indicates whether and when the job should be executed again in case of an error. The string consists of the 3 following values, separated by commas:
- Indication whether the job will be executed again (0 or 1)
- Waiting time (in minutes) until the job is executed again
- Maximum number of repetitions
Example: 1,30,2 means that the job will be executed again, 30 minutes will be waited between the attempts, and a maximum of 2 attempts will be made.
StartTime
If the key Execute has the value 1, use this key to determine when the job should be executed.
The value of the key is a string containing following values, separated by commas:
- Starting time: Time at which the job will be executed
- Interval at which the job should be executed (3: hourly, 2: daily, 1: weekly, 0: monthly)
- Additional values depend on which interval was selected
Hourly
- Additional hours
- Additional minutes
Example: 16:00,3,2,45: This means that after 16:00 the job will be executed at 2 hour and 45 minute intervals.
Daily:
- No additional values.
Example: 16:00.2: The job will be executed each day at 16.
Weekly:
- Number of weeks between executions
- Week day (1: Sunday, 2: Monday, 4: Tuesday, 8: Wednesday, 16: Thursday, 32: Friday, 64: Saturday)
- If the job should be executed on multiple week days, the numbers will be aggregated. For example, Monday and Saturday: 2+64=66
Example:
16:00,1,4,4: The job will be executed every forth week on Tuesday at 16.
16:00,1,2,24: The job will be executed every second week on Wednesday and Thursday at 16.
Monthly:
- Execution rhythm in the month when the job is executed (0: on every n. day, where n indicates the date, 1: on a certain day of the week).
- If 0 is selected as the first value, the second value indicates on which day of the month the job will be executed.
- If 1 is selected as the first value, the second value specifies the week of the month and the third value specifies the day of the week when the job will be executed (0: Sunday, 1: Monday, 2: Tuesday, 3: Wednesday, 4: Thursday, 5: Friday, 6: Saturday).
- The job can only be executed on a specific day of the month. You cannot specify multiple week days.
- Month in which the job was executed (1: January, 2: February, 4: March, 8: April, 16: May, 32: June, 64: July, 128: August, 256: September, 512: October, 1024: November, 2048: December)
- If the job is to be executed on several months, the respective numbers are added. For example, March, July and October: 4+64+512=580
Example:
16:00,0,0,5,32: The job will be executed on 5th June at 16:00.
16:00,0,1,2,3,512: The job will be executed in the second week of October, on Tuesday at 16:00.
The default value is an empty string.
EmailRecipients
List of users or group ID’s who are informed by email. These are separated by commas.
The default value is an empty string.
<ParameterId as digit>
Indicates the parameter ID
The default value is an empty string.
If a job is created, the ID of the created job will be given in the section [Result] in the key JobId.