Sponsored Content
Operating Systems AIX moving data from FS from one storage to FS in another storage Post 302470416 by filosophizer on Wednesday 10th of November 2010 04:55:57 AM
Old 11-10-2010
Quote:
Originally Posted by bakunin
This will work as expected, but will be slower than the mirrorlv/mirrorvg procedure. The reason is that migratepv only works serially, while mirrorlv has (can have) several processes in parallel.

If O/P has a SVC s/he could use flash copy, which will probably be the fastest method but this requires stopping/starting of the application and a remount of the filesystems involved.

I hope this helps.

bakunin
I once tried flashcopy on DS4700 but flash copy only creates a readonly copy. You cannot write on it. May be the higher versions of DS like DS5020 or above, have the function to copy in read/write mode from SAN Storage to SAN Storage.

SVC = Storage Volume Controller is a very good option, but very few companies buy. It is usually used to consolidate/connect different SAN Storages through one box.
 
SYSTEMD-MACHINE-ID-COMMIT.SERVICE(8)			 systemd-machine-id-commit.service		      SYSTEMD-MACHINE-ID-COMMIT.SERVICE(8)

NAME
systemd-machine-id-commit.service - Commit a transient machine ID to disk SYNOPSIS
systemd-machine-id-commit.service DESCRIPTION
systemd-machine-id-commit.service is an early boot service responsible for committing transient /etc/machine-id files to a writable disk file system. See machine-id(5) for more information about machine IDs. This service is started after local-fs.target in case /etc/machine-id is a mount point of its own (usually from a memory file system such as "tmpfs") and /etc is writable. The service will invoke systemd-machine-id-setup --commit, which writes the current transient machine ID to disk and unmount the /etc/machine-id file in a race-free manner to ensure that file is always valid and accessible for other processes. See systemd-machine-id-setup(1) for details. The main use case of this service are systems where /etc/machine-id is read-only and initially not initialized. In this case, the system manager will generate a transient machine ID file on a memory file system, and mount it over /etc/machine-id, during the early boot phase. This service is then invoked in a later boot phase, as soon as /etc has been remounted writable and the ID may thus be committed to disk to make it permanent. SEE ALSO
systemd(1), systemd-machine-id-setup(1), machine-id(5), systemd-firstboot(1) systemd 237 SYSTEMD-MACHINE-ID-COMMIT.SERVICE(8)
All times are GMT -4. The time now is 05:55 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy