Date: Thu, 28 Mar 2024 22:50:09 +0000 (UTC) Message-ID: <1472122627.53.1711666209655@4f7825c124e0> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_52_1060298555.1711666209654" ------=_Part_52_1060298555.1711666209654 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
Learn about how BRMS can work with IBM Cloud Storage So= lutions for i to save backups to a cloud location
While the IBM Cloud Storage Solutions for i using BRMS may be convenient= , it may not be ideal for users or organizations that transfer large amount= s of data from a backup. This solution is intended for small enviro= nments saving less than 2TB of data per day. Cloud connectivity wa= s not developed as a replacement alternative for physical or Virtual Tape L= ibrary (VTL) devices.
It is important to be aware that backup and restore operations to the cl= oud involve two stages. BRMS manages one stage of the operation and the oth= er stage is controlled by the IBM Cloud Storage Solutions for i product.
The first stage of a cloud backup is a BRMS backup to internal tape or v= irtual optical images. These require resources on the backup system that ca= n be intensive and does consume space. The second stage is the transfer of = the virtual images to the cloud.
The first stage of the restore is a transfer of the virtual images from = the cloud. The cloud transferred images are a whole file. The entire virtua= l image transfers back to the backup system from the cloud. The transfer of= the virtual images back to the backup system can be resource intensive and= consumes space on the backup system. The second stage is the BRMS restore = operation from the virtual image.
Changing the system name while it has active virtual images in the cloud= will cause the automatic transfer and restore process to fail. Reference <= a href=3D"/wiki/spaces/IWT/pages/1740046341" data-linked-resource-id=3D"174= 0046341" data-linked-resource-version=3D"4" data-linked-resource-type=3D"pa= ge">Renaming a BRMS/ICC cloud solution system for more details.
The transfer operations to the cloud are not owned by the BRMS component= . The cloud connection, transfer operations, and transfer performance is ma= naged by the IBM Cloud Storage Solutions for i product. Additionally, any j= ournal receiver maintenance needed for the IBM Cloud Storage Solutions for = i product has to be handled separately since this journaling is not part of= a BRMS owned process.
Large backup virtual images can cause lengthy transfer times when the im= ages are moved and may degrade network performance.
Because BRMS performs the backup to local media or media images, the bac= kup system requires at least as much storage space as the size of the backu= p. When using virtual optical images to store a backup, significantly more = storage space may be required.
When using cloud turnkey control groups as your primary backup strategy = for multiple systems, BRMS recommends setting unique volume prefixes. Refer= ence BRMS= Networking with IBM Cloud Storage Solutions for i for more details.
Follow these links for information about implementing and managing backu= p and restore operations with BRMS and the cloud: