Date: Thu, 28 Mar 2024 12:17:48 +0000 (UTC) Message-ID: <2059039533.1.1711628268308@7cfb4a8ae7df> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_0_1707485633.1711628268295" ------=_Part_0_1707485633.1711628268295 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
In order to help you design your own strategy for backing up all= of your Lotus servers while they are online, we are providing the followin= g sample backup strategy. Please remember that your specific needs may not = match this particular scenario, therefore you should carefully design your = strategy to fit your situation.
For the purposes of this strategy, we are going to classify the data on = our system as either
In this example we have decided that we will backup the Lotus server dat= a and the other user data daily. The system data only needs to be backed up= weekly or monthly, depending on how often it is being changed (ie. by appl= ying PTFs).
Backing up Lotus server data
In order to backup all Lotus Notes databases while they are online with zer=
o synchronization time, use the STRBKUBRM
com=
mand to backup the QLTSSVR control group that was created by BRMS.
STRBKUBRM CTLGRP(QLTSSVR) =
SBMJOB(*NO)
If you have multiple tape drives, you can use the individual control gro= ups, ie...QLTSDOMxx, and send them down in batch to get concurrent use from= your tape library.
You can also create your own control group(s) to tailor these backups ac= cording to your own particular needs..
In addition, you might wish to consider using an incremental online back= up strategy if:
Go to the BRMS incrementa= l online Lotus server backup to u= nderstand this process.
Backing up other user data
You can backup the rest of the non-Lotus user data using Save While Active(=
SWA). This data can all be saved while your Lotus servers are online. You w=
ill need to create a BRMS/400 control group similar to the following contro=
l group:
Group . . . . . . . . . . : SYSWODOM Default activity . . . . : FFFFFFF Text . . . . . . . . . . : Backs up all user data except notes
Weekly =09Retain =09Save =09SWA Backup List Activity =09Object =09While =09Message Seq Items Type SMTWTFS =09Detail =09Active =09Queue 10 *EXIT *DFTACT =09 =09 =09=20 20 *SAVSECDTA *DFTACT =09*NO =09 =09=20 30 *SAVCFG *DFTACT =09*NO =09 =09=20 40 *ALLUSR *DFTACT =09*ERR =09*YES =09*LIB 50 *ALLDLO *DFTACT =09*NO =09*YES =09=20 60 QLTSEXCL *LNK *DFTACT =09*YES =09*YES =09*LIB 70 *EXIT *DFTACT
The QLTSEXCL link list (sequence 60 above) which is automatically create= d by BRMS/400, will backup all link data not being backed up by the QLTSSVR= control group above
Backing up system data
You will need to backup the system data once a week or month, based on the =
activity within this area (ie...applying ptfs,etc) Your Lotus servers will =
need to be offline during this operation, as the system must be in restrict=
ed state.
You can start by copying the *SYSGRP control group and include the QIBML= INK link list. An example is shown below:
Group . . . . . . . . . . : RESTRICTED Default activity . . . . . *BKUPCY Text . . . . . . . . . . . Backs up all system data Type information, press Enter.
Weekly Retain Save SWA Backup List Activity Object While Message Seq Items Type SMTWTFS Detail Active Queue 10 *EXIT *DFTACT =09 =09 =09=20 20 *SAVSYS *DFTACT =09 =09 =09=20 30 *IBM *DFTACT *NO *NO =09=20 40 QIBMLINK *LNK *DFTACT *NO *NO =09=20 50 *EXIT *DFTACT
Conclusion
This strategy is not for every Notes/400 customer, but it does provide info=
rmation that will help provide your Notes/400 users more access to their ma=
il, with less down time. There are quite a few ways to alter this strategy =
in order to fine tune it for your specific configuration. (ie...moving the =
*ALLDLO to the once a week/month control group.)