MDSP

Newcomer
Joined
Mar 25, 2024
Messages
3
Reaction score
0
Points
0
Hello!
i want to back up certain files from the NIM-PROD LPAR to tape and that tape will be moved permanently offsite, what would be the best way to go about doing that? I have the BA Client installed on NIM-PROD.
would really appreciate any advice!

Thank you!
 
If you want to go directly to tape, then configure a tape storage pool, define a management class with unlimited retention and once you complete a backup, update volume(s) and set them to offsite. Or if you want to store to disk as primary stg, you can use retention sets with unlimited retention time and use move retmedia to move the tape media to vault/offsite.
 
MDSP,

Just my USD 0.02 .

"...configure a tape storage pool, define a management class with unlimited retention and once you complete a backup, update volume(s) and set them to offsite."

If you plan to utilize the backup copy group, and a management class with the unlimited retention.

To bind files to a specific management class, in the dsm.opt for Windows and dsm.sys for Unix, for files that are not explicitly included, include the following statement at the top of your include list:
include /.../* mgmt_class_name
or if you want a file to be bound to a specific management class.
include /path/to/the/name_of_file.* mgmt_class_name

Any changes to the dsm.opt (Windows) or the dsm.sys (Unix) file, the schedule service/daemon need to be stop and restarted so that the new updates will be read into memory.

If the retention is set to unlimited and there are other nodes within the same policy domain (not the same as a Windows Domain), then ALL the data for ALL the nodes within the policy domain will be retained. No data will expire, there will be an increase in tape usage. Space reclamation will not occur for the tapes.
If and when we do the restore, and if the file changes a lot, there are going to be a LOT of versions of the file.

FYI: Policy domain is set or group of nodes is called as policy domain. Policy domain contains policy set and in each policy domain we can define N no. of policy sets but at a time only policy set can be activated.

However, if the node in question is within its own policy domain, only the data from that specific node will be kept for an unlimited period. No rebinding would be encounter since we would only have just the default managementclass.

When we have one or more managementclass in addition to the default managementclass.
During the backup process, we may encounter something called rebinding. Also, If the node in question is moved to another policy domain, the data will be rebound to the default management class. This means that a certain number of files will be kept for a certain amount of days rather than unlimited quantity and time.


"...you can use retention sets with unlimited retention time and use move retmedia to move the tape media to vault/offsite."

Not sure what version of TSM/SP Server that we are running.

8.1.7 retention set introduce
8.1.10 option to copy retention set to tape or vtl
8.1.13 retention set to cloud

The TSM/SP Server need to be at 8.1.10 or higher to copy the retention set to tape or vtl.

When it comes to sending the primary tape off site and needing to perform a restore, it is necessary for the tape to be returned back on site. However, if the tape reaches the reclamation threshold, it must be brought back on site for reclamation purposes.

In cases where time is of the essence and waiting for the primary tape to be returned from the offsite location is not feasible, a copy pool can be created. This copy pool will serve as a backup for the primary pool. The tapes that belong to the copy pool are the ones that need to be sent off site.

If there is a need to retain certain files for a long period of time and store them on tape to be sent off site, setting up an archive copy group with the desired retention is recommended. By default, the retention for the archive is set at 365 days. However, you have the flexibility to specify any integer value between 0 and 30000, representing the number of days for retention.

Unlike backup, archiving data does not encounter rebinding.
Unless the node is moved into another policy domain with a different archive retention.

To provide an additional layer of protection, it is advisable to backup the archive primary storage pool to the archive copy pool. The tapes that belong to the archive copy pool should then be sent to the offsite location. If there is a problem with the archive primary tape, the data can be recreated via the archive copy pool.

Offsite location, I do not mean the drawer in your desk nor the next building.
Not to scare you.
Just a reminder - September 11, 2001, Twin Towers, NYC
Company was in Tower 1, their off site location was in the basement of Tower 2.
Tower 1 and 2 gone. All data are lost, now company no longer exist.

Also, about once a year attempt a test retrieve to be sure that we can get the file back.

If using an archive primary storage pool and an archive copy storage pool are too complex.
Would use retention sets, need to be at 8.1.10 or higher since we want the data on tape.
IBM Spectrum Protect 8.1.10 - Copy Retention Sets to Tape - Demo


Not sure how long the application will be around.
Keep a copy of the os, TSM/SP Server and Client.
Along with the code, download a copy of the Server and Client manual.
Document the restore steps, in detail, for your self in the future.

Good Luck,
Sias
 
Back
Top