Convenient operation method for backup storage replacement of database server without any influence

[root@eebdb ~]# df -h

Filesystem Size Used Avail Use% Mounted on

/dev/mapper/VolGroup-lv_root 50G 14G 33G 30% /

tmpfs 127G 19M 127G 1% /dev/shm

/dev/sda1 485M 39M 421M 9% /boot

192.16.10.10:/volume1/eebbak 80T 33T 47T 42% /ebbbak

192.16.9.9:/volume1/eebbak 104T 171G 104T 1% /ebbbaknew

Premise: Oracle databases are backed up in/ebbbak directory, 192.16.10.10:/volume1/eebbak storage expires, to replace the new storage 192.16.9.9:/volume1/eebbak, how to do?

1. Mount the new storage 192.16.9.9:/volume1/eebbak to the/ebbbaknew directory, and backup all new database backups to the/ebbbaknew directory.

2. Create a new directory 192.16.9.9:/volume1/eebbak_old on the new storage side, copy all files of 192.16.10.10:/volume1/eebbak_old on the storage side to 192.16.9.9:/volume1/eebbak_old.

3、umount /ebbbak

4、mount 192.16.10.9:/volume1/eebbak_old /ebbbak

The above ensures that the backups are all stored on the new storage 192.16.9.9. The directories mounted on the server are/ebbbak and/ebbbaknew, which correspond to the storage 192.16.9.9:/volume1/eebbak_old and 192.16.9.9:/volume1/eebbak_old, respectively. The historical backups are stored in 192.16.9.9:/volume1/eebbak stores the new backups, and the paths and files in the mounted/ebbbak directory are the same as those in the old storage 192.16.10.10, and the paths of the backup files recorded in the control files remain unchanged.