info Xen Orchestra cli cmd

olivierlambert

So the use case is making a copy of the CR VM? (so you have a backup of the backup?)

Gheppy

Yes but in an automatic way not by hand

olivierlambert

Why not replicating twice to 2 different SR directly in the backup job?

Gheppy

I don't think we're on the same page.

The scenario is like this:
The real VM is in another site and has two disks (system and database).
I have a copy of it, with the help of CR, on my site.
From the copy on my site I want to use only one disk (database).
The idea I started from is to make a copy on the whole VM and then use only disk 2.
Only for this copy I need 20 hours + and CR is done every 2 hours.
All I want now is to disable CR job when I make the copy to not break the CR.
And after I finish the copy to enable the CR job.

For now, as I said, I'm taking the following steps:

I disable the CR job
start copying
enable the CR job
Everything manual and CR job does not break.

All i want is to find a way through xo-cli to be able to temporarily disable this CR job.

olivierlambert

What do you mean with:

From the copy on my site I want to use only one disk (database).

What do you mean by "use only one disk"? What "use"? Make another copy but just of this DB disk?

The term "use" is very unclear to me, what do you want to do with it?

Gheppy

I hope this is more clear.
I use ssh copy because is more faster that VM copy over XOCE.
Over ssh copy I get 200 Mbps and over XOCE I get max 65 Mbps.
All VM discks are VHD over EXT SR.

Gheppy

So there is no way to send a deactivation or activation request to xo-cli?

fohdeesha

@Gheppy I'm not sure if xo-cli supports job interactions, @olivierlambert may have to inquire with the xo-cli dev @julien-f . For your niche use case, you could solve it in the meantime by running your XO instance from your house (or wherever this CR destination and DB test server are). Then, you can set the CR job to replicate to two remotes, your main CR destination, and then your test pool you've been manually copying to. Since these are now both local to XOA, it won't use up extra internet bandwidth, XOA will still only be pulling one stream from the production server out on the internet, then once it's inside your network on XO, it duplicates and writes to both local CR destinations

julien-f

@Gheppy

use backupNg.getAllJobs to list the all the jobs and find the id of the job you want to manage
use schedule.getAll to list all schedules and find the ones which reference your job via the jobId property
schedule.set id=<schedule id> enabled=json:false
schedule.set id=<schedule id> enabled=json:true

Gheppy

Thanks for the guidance, that's all I need.
It's all working now.

Thank you