I'm trying to keep backups of my home directory (i.e. back it up every day or so) using rsync with link-dest.
This is how I do it,
The problem is when I do this it seems to just copy my entire home directory again (as in every time I do a backup it copies everything again, rather I only want the changes to be copied and the others linked). It appears that I'm not creating hardlinks. What am I doing wrong?
Thanks
can you use options "-zavrR" instead?
also, try to see what's going on using '--verbose' option as well.
I have been experimenting with rsync as a scriptable backup option, reading various example and tips pages, including Time Machine for every Unix out there - IMHO
That page seems to describe the exact behavior I want: The ability to make a "full backup" snapshot regularly, but with rsync... (0 Replies)
I have 2 different id's for an ftp destination. Each id handles files differently on the destinations end. Is it possible to have one destination machine and assign an alias name for each id. The .netrc file doesn't allow this. (2 Replies)
Hi,
in makefile, if the sourc and dest in different directory, no matter the source file changed or not, it seems the dest always been build, how do you resolve this?
Thanks.
peter (1 Reply)
Hello All,
I've encountered a strange behaviour from g++ that doesn't make sense to me. Maybe you can shed some light on it:
I have a bunch of source files and want to compile them and link them with a static library liba.a located in /usr/local/lib64 into an executable
Approach 1 works... (0 Replies)
Hi everybody,
I read about treads realted to this issue but they did not resovle issue given below.
Please help me resolve issue given below
I have html file under /srv/www/htdocs/actual_folder
ls actual_folder/
test.html
and following link works... (0 Replies)
Ok, I'm trying to figure out how to reference a remote file using the rsync --link-dest parameter.
Here is the code I have so far:
#
# FILESERVER INCREMENTAL BACKUP SCRIPT
#
# Remove previous log file
rm /usr/local/bin/rsync-incremental.log
# Set daily variables
DAY0=`date -I`... (6 Replies)
Hi All
I am facing an issue with our new solaris machine.
in /var/adm/messages
root@Prod-App1:/var/tmp#
root@Prod-App1:/var/tmp#
root@Prod-App1:/var/tmp# cat /var/adm//messages
Apr 20 03:10:01 Prod-App1 syslogd: line 25: WARNING: loghost could not be resolved
Apr 20 08:24:18 Prod-App1... (0 Replies)
Hi All
I am facing an issue with our new solaris machine.
in /var/adm/messages
Apr 22 16:43:05 Prod-App1 in.routed: interface net0 to 172.16.101.1 turned off
Apr 22 16:43:33 Prod-App1 mac: NOTICE: nxge0 link up, 1000 Mbps, full duplex
Apr 22 16:43:34 Prod-App1 mac: NOTICE: nxge0 link... (2 Replies)
I wish to copy all the files & folder under /web/Transfer_Files/data/ on mymac1 (Linux) to remote server mybank.intra.com (Solaris 10) /tmp/ location
I am using Ansible tool synchronize module which triggers the unix rsync command as below:rsync --delay-updates -F --compress --archive --rsh=ssh... (2 Replies)
Discussion started by: mohtashims
2 Replies
LEARN ABOUT OPENSOLARIS
patchmedia
patchmedia(1M) System Administration Commands patchmedia(1M)NAME
patchmedia - modify Solaris media with patches and packages
SYNOPSIS
/usr/bin/patchmedia -d media-root [-v] [-o iso] [-l label]
pkg_or_patch [pkg_or_patch ...]
DESCRIPTION
The patchmedia utility takes a list of patches and packages as input and updates the install miniroot in media-root (the root directory of
an on-disk image of a Solaris installation media) to include the specified patches and packages. These patches and packages are also placed
in a subdirectory called DU under the Solaris install image. For example:
media-root/Solaris_10/DU
When booting a system from the updated media, the patches and packages will be part of the booted Solaris image. They will also be applied
to the target system being installed at the end of the installation process.
If -o is specified, a bootable ISO image is created in the file media.iso that contains the Solaris install media. The ISO image can then
be burned onto a CD/DVD with utilities such as cdrw(1) or cdrecord(1). (The latter is not a SunOS man page.)
OPTIONS
The following options are supported:
-d media-root
Top-level directory of on-disk image of Solaris installation media. This is option must be specified.
-o iso
Create a Solaris ISO image of media-root.
-l label
Label/volume name of the ISO image (if -o option is specified). If -o is not specified, the name of Solaris directory under media-root,
for example, Solaris_10, will be used.
-v
Verbose. Multiple -v options increase verbosity.
OPERANDS
The following operands are supported:
pkg_or_patch [pkg_or_patch ...]
One or more patches or packages (you can have both patches and packages in a single command) with which the Solaris installation media
media-root will be updated.
EXAMPLES
Example 1 Updating a Solaris Install Image with Patch and Package
The following command updates the Solaris install image in s10u1 by adding patch 123456-07 and package SUNWfoo.
# /usr/bin/patchmedia -d s10u1 SUNWfoo 123456-07
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWcsu |
+-----------------------------+-----------------------------+
|Interface Stability |Committed |
+-----------------------------+-----------------------------+
SEE ALSO cdrw(1), mkcd(1M), attributes(5)mkisofs(8), (/usr/share/man/man8/mkisofs.8), in the SUNWfsman package (not a SunOS man page)
SunOS 5.11 29 Jul 2008 patchmedia(1M)