02-04-2004
Oh man, now someone voted.. apparently the number 7 is more popular than the number 15.
I closed the poll - feel free to reopen it, raguramtgr, if there's actually a point to it!
6 More Discussions You Might Find Interesting
1. AIX
When I use tsm command: archive -subdir=yes /dir1/
to backup file system: /dir1
After I delete the contents under /dir1 and recovery it from TSM backup,
retrieve /dir1/
I found the link breaked. Such as:
Before:
ls -l
lrwxrwxrwx 1 abc develop 8 Apr 28 16:04 bin... (1 Reply)
Discussion started by: rainbow_bean
1 Replies
2. Linux
Hey guys, I hope this is the right place to post. As i'm not too sure where this question would go.
The question is: How is backup and recovery carried out in major corporations. Even if you are not in a major corporation an answer would be great.
I'm doing some research as to how it's carried... (2 Replies)
Discussion started by: LibRid
2 Replies
3. Shell Programming and Scripting
Hi,
Do we have any options in rsync to recover files from the backup?
Please share your thoughts.
Thanks in advance. (0 Replies)
Discussion started by: MVEERA
0 Replies
4. Shell Programming and Scripting
Hi Everyone,
we are running rsync with --backup mode, Are there any rsync options to remove backup folders on successful deployment?
Thanks in adv. (0 Replies)
Discussion started by: MVEERA
0 Replies
5. Red Hat
Can you please let me know a clear step by step procedure link/doc for an effective full backup and recovery procedure for a Redhat server with 2.6.34.9-69.fc13.x86_64 ?
Thanks in advance.
I also have the same question for Ubuntu Enterprise 12.04 if you would ...
thanks again (0 Replies)
Discussion started by: cmontr
0 Replies
6. Ubuntu
Is it possible to take incremental backup in Linux using tar command?
Please guide me.
Suppose I have a directory /data.
And want incremental backup.
What will be the incremental "tar" command syntax? (6 Replies)
Discussion started by: engineer2002
6 Replies
cpio(4) Kernel Interfaces Manual cpio(4)
NAME
cpio - Format of cpio archive
DESCRIPTION
The header structure, when the -c option of cpio(1) is not used, is: struct {
short h_magic,
h_dev;
ushort h_ino,
h_mode,
h_uid,
h_gid;
short h_nlink,
h_rdev
h_mtime[2],
h_namesize,
h_filesize[2]'
char h_name[h_namesize rounded to word]; } Hdr; When the -c option is used, the header information is described by:
sscanf(Chdr,"%6o%6o%6o%6o%6o%6o%6o%6o%11lo%6o%11lo%s",
&Hdr.h_magic, &Hdr.h_dev, &Hdr.h_ino, &Hdr.h_mode,
&Hdr.h_uid, &Hdr.h_gid, &Hdr.h_nlink, &Hdr.h_rdev,
&Longtime, &Hdr.h_namesize,&Longfile,Hdr.h_name); The Longtime and Longfile are equivalent to Hdr.h_mtime and Hdr.h_filesize, respec-
tively. The contents of each file are recorded in an element of the array of varying length structures, archive, together with other items
describing the file. Every instance of h_magic contains the constant 070707 (octal). The items h_dev through h_mtime have meanings
explained in stat(2). The length of the null-terminated path name h_name, including the null byte, is given by h_namesize.
The last record of the archive always contains the name TRAILER!!! Special files, directories, and the trailer are recorded with h_file-
size equal to zero.
RELATED INFORMATION
cpio(1), find(1), stat(2) delim off
cpio(4)