search for: source_host

Hello, Any help on the following issue will be appreciated. How do I delete files or directories in my first level of directory that is specified as host. Here is an example : rsync -avz --delete ${SOURCE_HOST}:/mlinkfam/extract/sccs/pa/* /mlinkfam/extract/sccs/pa Giving above command I find redundant files or directory not getting deleted from the first level of target directory /mlinkfam/extract/sccs/pa. However, files or directories do get deleted from subdirectories /mlinkfam/extract/sccs/pa/qa or...

I want to manage remote libvirt , have run libvirtd in the dest host : [root@dest_host ~]# ps aux | grep libvirtd root 3293 0.0 0.1 923796 5856 ? Sl 12:59 0:00 libvirtd --daemon then I use the command in source host : 1. [root@source_host ~]# ssh -l root 211.87.***.97 ## login the dest host 2. [root@dest_host ~]# virsh -c qemu+ssh://127.0.0.1/system list --all # query vm status output: Id Name State ---------------------------------------------------- - ubuntu...

...using SGI's Data Migration Facility (DMF). A typical command we use is the following (but I have shortened the paths and addresses). rsync --password-file=not_for_your_eyes --numeric-ids -a --stats --one-file-system --max-size=8.0GB --warn --whole-file --link-dest=previous --delete root at source_host::backups/source_dir current --password-file=not_for_your_eyes . for the daemon --numeric-ids . since the userids on the source are not always available on the destination -a . archive mode --stats . statistics --one-file-system . stops the backup of everything when backing up /...

This is a minor release of Shorewall. WARNING: This release introduces incompatibilities with prior releases. See http://www.shorewall.net/upgrade_issues.htm. Changes are: a) There is now a new NONE policy specifiable in /etc/shorewall/policy. This policy will cause Shorewall to assume that there will never be any traffic between the source and destination zones. b) Shorewall no longer

...st --delete -ave ssh myuser@source_server:/var/attachments/ /backups/var/varattachments/var/attachments/ | mail -s "`hostname`: rsync of /var/attachments/ from source_server done for `date '+ %m/%d/%Y'`" backups Here is the cron message that is sent out... Read from remote host source_host: Connection reset by peer rsync: connection unexpectedly closed (1879176 bytes received so far) [receiver] rsync error: error in rsync protocol data stream (code 12) at io.c(359) rsync: writefd_unbuffered failed to write 4 bytes: phase "unknown" [generator]: Broken pipe (32) rsync err...

...age and hence when you migrate these guests , it results in different unit names on the destination hosts. Thus the migrated guest gets mapped to the wrong LUNs and is given the wrong disks. The problem is that the LUN numbers on the destination host and source host do not agree. Example, LUN 0 on source_host, for example, may be LUN 5 on destination_host. When the guest is given the wrong disk, it suffers a fatal I/O error. (This is manifested as fatal I/O errors since the guest has no idea that its disks just changed out under it.)The migration does not take into account that the unit numbers do match...

I am getting the following message when Shorewall stops can anybody shed any light on this message and where I should be looking? Thanks root@bobshost:~# shorewall stop Loading /usr/share/shorewall/functions... Processing /etc/shorewall/params ... Processing /etc/shorewall/shorewall.conf... Loading Modules... Stopping Shorewall...Processing /etc/shorewall/stop ... IP Forwarding Enabled