shaba/lvm2
1
0
Fork 0
mirror of git://sourceware.org/git/lvm2.git synced 2024-12-22 17:35:59 +03:00
Code Releases Activity
b896caa19b
lvm2/tools/archive.h

55 lines
1.6 KiB
C
Raw Normal View History

o High level archiving and backup functions. I've split the old autobackup function into two seperate areas: 'archiving' is performed *before* a vg configuration is changed. This produces a numbered backup in /etc/lvm/archive. A 'backup' is performed *after* a vg change. So the directory /etc/lvm/backup will hold the a copy of the current configuration.
2002-01-03 18:46:48 +03:00
/*
* Copyright (C) 2001 Sistina Software (UK) Limited.
*
* This file is released under the GPL.
*/
#ifndef _LVM_TOOL_ARCHIVE_H
#define _LVM_TOOL_ARCHIVE_H
o sync tool changes for backup stuff.
2002-01-07 14:12:11 +03:00
#include "metadata.h"
o High level archiving and backup functions. I've split the old autobackup function into two seperate areas: 'archiving' is performed *before* a vg configuration is changed. This produces a numbered backup in /etc/lvm/archive. A 'backup' is performed *after* a vg change. So the directory /etc/lvm/backup will hold the a copy of the current configuration.
2002-01-03 18:46:48 +03:00
/*
o Added functions to display what's in the archive. o For now vgcfgrestore -l <vg> displays this list. A bit hacky, but it'll get better.
2002-02-11 14:43:17 +03:00
* FIXME: This file is going to merge with the archiving code in
* lib/format_text at some point.
*/
/*
* There are two operations that come under the general area of
* backups. 'Archiving' occurs just before a volume group
* configuration is changed. The user may configure when
* archived files are expired. Typically archives will be stored
* in /etc/lvm/archive.
o High level archiving and backup functions. I've split the old autobackup function into two seperate areas: 'archiving' is performed *before* a vg configuration is changed. This produces a numbered backup in /etc/lvm/archive. A 'backup' is performed *after* a vg change. So the directory /etc/lvm/backup will hold the a copy of the current configuration.
2002-01-03 18:46:48 +03:00
*
o Added functions to display what's in the archive. o For now vgcfgrestore -l <vg> displays this list. A bit hacky, but it'll get better.
2002-02-11 14:43:17 +03:00
* A 'backup' is a redundant copy of the *current* volume group
* configuration. As such it should be taken just after the
* volume group is changed. Only 1 backup file will exist.
* Typically backups will be stored in /etc/lvm/backups.
o High level archiving and backup functions. I've split the old autobackup function into two seperate areas: 'archiving' is performed *before* a vg configuration is changed. This produces a numbered backup in /etc/lvm/archive. A 'backup' is performed *after* a vg change. So the directory /etc/lvm/backup will hold the a copy of the current configuration.
2002-01-03 18:46:48 +03:00
*/
int archive_init(const char *dir,
unsigned int keep_days, unsigned int keep_min);
void archive_exit(void);
o sync laptop to test machine.
2002-01-07 12:05:31 +03:00
void archive_enable(int flag);
o High level archiving and backup functions. I've split the old autobackup function into two seperate areas: 'archiving' is performed *before* a vg configuration is changed. This produces a numbered backup in /etc/lvm/archive. A 'backup' is performed *after* a vg change. So the directory /etc/lvm/backup will hold the a copy of the current configuration.
2002-01-03 18:46:48 +03:00
int archive(struct volume_group *vg);
Preparation for an LVM2 liblvm - pass cmd_context into each tool and link some globals that the tools need into that structure.
2002-02-11 23:50:53 +03:00
int archive_display(struct cmd_context *cmd, const char *vg_name);
o High level archiving and backup functions. I've split the old autobackup function into two seperate areas: 'archiving' is performed *before* a vg configuration is changed. This produces a numbered backup in /etc/lvm/archive. A 'backup' is performed *after* a vg change. So the directory /etc/lvm/backup will hold the a copy of the current configuration.
2002-01-03 18:46:48 +03:00
int backup_init(const char *dir);
void backup_exit(void);
o sync tool changes for backup stuff.
2002-01-07 14:12:11 +03:00
void backup_enable(int flag);
o High level archiving and backup functions. I've split the old autobackup function into two seperate areas: 'archiving' is performed *before* a vg configuration is changed. This produces a numbered backup in /etc/lvm/archive. A 'backup' is performed *after* a vg change. So the directory /etc/lvm/backup will hold the a copy of the current configuration.
2002-01-03 18:46:48 +03:00
int backup(struct volume_group *vg);
o Rename many occurrences of 'backup' to 'archive' to reduce confusion. o Extract file creation/renaming code into a library and change backup code to use it too. o Support umask. o Bring lvm.conf man page up-to-date.
2002-01-09 22:16:48 +03:00
int backup_remove(const char *vg_name);
o High level archiving and backup functions. I've split the old autobackup function into two seperate areas: 'archiving' is performed *before* a vg configuration is changed. This produces a numbered backup in /etc/lvm/archive. A 'backup' is performed *after* a vg change. So the directory /etc/lvm/backup will hold the a copy of the current configuration.
2002-01-03 18:46:48 +03:00
Some new features.
2002-11-18 17:04:08 +03:00
struct volume_group *backup_read_vg(struct cmd_context *cmd,
const char *vg_name, const char *file);
int backup_restore_vg(struct cmd_context *cmd, struct volume_group *vg);
Run through indent - no (intentional) changes to any code.
2002-02-12 00:00:35 +03:00
int backup_restore_from_file(struct cmd_context *cmd, const char *vg_name,
const char *file);
Preparation for an LVM2 liblvm - pass cmd_context into each tool and link some globals that the tools need into that structure.
2002-02-11 23:50:53 +03:00
int backup_restore(struct cmd_context *cmd, const char *vg_name);
o vgcfgrestore.
2002-01-10 17:27:47 +03:00
Some new features.
2002-11-18 17:04:08 +03:00
int backup_to_file(const char *file, const char *desc, struct volume_group *vg);
o High level archiving and backup functions. I've split the old autobackup function into two seperate areas: 'archiving' is performed *before* a vg configuration is changed. This produces a numbered backup in /etc/lvm/archive. A 'backup' is performed *after* a vg change. So the directory /etc/lvm/backup will hold the a copy of the current configuration.
2002-01-03 18:46:48 +03:00
#endif
Copy Permalink