qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Ishani Chugh <chugh.ishani@research.iiit.ac.in>
To: qemu-devel@nongnu.org
Cc: stefanha@redhat.com, jsnow@redhat.com,
	Ishani Chugh <chugh.ishani@research.iiit.ac.in>
Subject: [Qemu-devel] [PATCH 1/3] Backup Tool: Manpage for Incremental Backup
Date: Thu, 31 Aug 2017 00:45:36 +0530	[thread overview]
Message-ID: <1504120538-9309-2-git-send-email-chugh.ishani@research.iiit.ac.in> (raw)
In-Reply-To: <1504120538-9309-1-git-send-email-chugh.ishani@research.iiit.ac.in>

Adds command description to perform incremental backup and
a full example for the same.

Signed-off-by: Ishani Chugh <chugh.ishani@research.iiit.ac.in>
---
 contrib/backup/qemu-backup.texi | 18 ++++++++++++++++++
 1 file changed, 18 insertions(+)

diff --git a/contrib/backup/qemu-backup.texi b/contrib/backup/qemu-backup.texi
index 7ad266c..8e5cb86 100644
--- a/contrib/backup/qemu-backup.texi
+++ b/contrib/backup/qemu-backup.texi
@@ -58,6 +58,7 @@ qemu-backup command [command options].
 @item qemu-backup restore --guest guestname
 @item qemu-backup guest remove --guest guestname
 @item qemu-backup drive remove --guest guestname --id driveid
+@item qemu-backup backup --inc --guest guestname
 @end itemize
 @node  Command Parameters
 @chapter  Command Parameters
@@ -67,6 +68,7 @@ qemu-backup command [command options].
 @item --id: id of guest or drive.
 @item --qmp: Path of qmp socket.
 @item --target: Destination path on which you want your backup to be made.
+@item --inc: incremental backup (Optional).
 @end itemize
 
 @node  Command Descriptions
@@ -119,6 +121,11 @@ This command helps remove a drive which is set for backup in configuration of gi
 
 example: drive remove --guest=fedora --id=root
 
+@item qemu-backup backup --inc --guest guestname
+This command is used for making incremental backup.
+
+example: qemu-backup backup --inc --guest fedora
+
 @item A full backup can be performed by following the given steps:
 
 Perform a full backup of 'vm001', which has one drive:
@@ -129,6 +136,17 @@ qemu-backup add --id drive0 --guest vm001 --target /backups/vm001-drive0.img
 
 qemu-backup backup --guest vm001
 
+@item An incremental backup can be performed by following the given steps:
+
+Perform an incremental backup of 'vm001', which has one drive:
+
+qemu-backup guest add --guest vm001 --qmp /path/to/vm001.sock
+
+qemu-backup add --id drive0 --guest vm001 --target /backups/vm001-drive0.img
+
+qemu-backup backup --inc --guest vm001
+
+qemu-backup backup --inc --guest vm001
 
 @end itemize
 
-- 
2.7.4

  reply	other threads:[~2017-08-30 19:16 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-30 19:15 [Qemu-devel] [PATCH 0/3] Backup Tool: Incremental backup Ishani Chugh
2017-08-30 19:15 ` Ishani Chugh [this message]
2017-08-31  1:57   ` [Qemu-devel] [PATCH 1/3] Backup Tool: Manpage for Incremental Backup Fam Zheng
2017-08-30 19:15 ` [Qemu-devel] [PATCH 2/3] Backup Tool: Support " Ishani Chugh
2017-08-31  1:56   ` Fam Zheng
2017-08-30 19:15 ` [Qemu-devel] [PATCH 3/3] Backup Tool: Test " Ishani Chugh
2017-08-31  2:02   ` Fam Zheng
2017-09-01 22:53     ` John Snow
2017-09-07  4:03       ` Ishani

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1504120538-9309-2-git-send-email-chugh.ishani@research.iiit.ac.in \
    --to=chugh.ishani@research.iiit.ac.in \
    --cc=jsnow@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).