

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
Hi There,
I've got the virtual environment integration working fine. however after creating a backup specification and configure a schedule, the backups won't start automatically. The scheduler works fine for regular file backups.
I've checked location: C:\ProgramData\OmniBack\Config\Server\Schedules
A schedule file for the regular file backup is present but there's no file created of the vmware backup specification.
Any ideas? Could this be a bug maybe? I didn't have this issue with dp 6.11 version.
Accepted Solutions

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
Could you please confirm, Your Cell manager and the VM esx or VC have the same time set ?
Ranjith


- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
All the schedules for backups other than filesystem backups are in a different tree.
Here is where my 'Virtual Environment' schedules are located:
C:\ProgramData\OmniBack\Config\Server\Barschedules\VEAgent

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
Could you please confirm, Your Cell manager and the VM esx or VC have the same time set ?
Ranjith


- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
Hi There,
I confirm hereby a schedule in this location:
C:\ProgramData\OmniBack\Config\Server\Barschedules\VEAgent
Sorry I overlooked it.
The time's in sync.
Still nothing in my internal database..


- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
This is crazy.. Nothing's shown in the internal database because the backup is running!
I overlooked something I guess.. Nevermind, issue solved!