srp
ADSM.ORG Member
Hi,
I hope I am in the right forum, else please tell me otherwise!
1. Being a newbie I was wondering if I could accomplish the following without "DRM".
- Back up our Disk(Primary) storage pool every night.
- Perform a full backup of the database every night and run incremental backups Mon - Fri and copy data to tape - can I use copypool or ltopool?.
- Run Archive backups every weekend and month by backing up my primary storage pool(diskpool) to my Copypool(tapepool) and storing offsite and retaining that data for 1 month for weekly's tapes and 1 year for the monthly tape backups.
- Ship the database and copy storage pool volumes to an offsite location every day and be able to RESTORE them for up to a year?
2. From the link below I have been reading up on offsite storage and TSM:
http://www.redbooks.ibm.com/redbooks/pdfs/sg245416.pdf
The steps that you need to perform to send data offsite are:
1. Back up your vital data to the copy storage pools.
2. List all volumes that must be sent to offsite.
3. Check out volumes from the library.
4. Update the volume location to offsite.
Backup your vital data
Use the backup stgpool command to create copies of files that reside in a primary
storage pool, and store them in a copy storage pool. This is shown in
Example 13-35. File versions are only copied if they do not already exist in the
copy storage pool — if a file is already present in the specified copy storage pool,
then it is not recopied. However, if a copy of a physical file already exists in the
copy storage pool, but the copy is marked damaged, a new copy will be created,
provided that the primary physical file is not also marked damaged. The following
command backs up onsite data from the DISKDATA and DISKDIRS storage pool
to the OFFDATA and OFFDIRS storage pools respectively. (This task can also
be automated using a server script...
Offsite tape management to onsite
In this section we show how to move offsite volumes to the onsite location. These
offsite volumes either have no active data on them (status of EMPTY) or are
being returned to recreate damaged data in a primary storage pool.
Offsite tapes can be seen as your second good copy of critical data. As you
perform backup and archive operations, all data is saved in storage pools, which
are the basic unit for onsite operations. When you perform a backup stgpool
command, IBM Tivoli Storage Manager verifies which data has not previously
been sent to offsite yet and then performs the copy operation of any new data.
This means the operation is incremental and hence minimizes the amount of
time required to execute it.
As backup and archive data age and expire, the offsite tapes contain less and
less active data. Offsite tape reclamation consolidates these tape volumes,
replacing the partially filled tapes with full and empty tapes. The newly emptied
tapes remain in a pending state until after the reuse delay period has expired. At
this time the status of the tape changes to EMPTY. Empty tapes can be brought
back onsite and returned to the scratch pool.
3. And do I understand this correctly about Copypool's from above ?
Yesterday, I could NOT restore data from an "offiste Copypool tape because a volume was deemed "Empty" and either because the REUSE DELAY=0 or ?
I was unaware my Copypool tapes were expiring (expire inventory? process?)
So then, I set the access=readonly and it WAS deleted!!
What can I do about this if we don't run DRM and I want to use Copypool?
Should I just use Ltopool(tapepool)? Perhaps migrate from diskpool to the ltopool(tapepool)?
Or could I use the command: "backup stg diskpool ltopool"?
Would that preserve my data if my setting are correct?
I am unsure what parmaters to set to keep my data onsite(available) & offsite(available for restores up to a yr?) and not have TSM delete it periodically.
sory for the load of information here, hope somone can decipher and give some feedback.
Thanks for any help on the subject of "offsite storage".
srp
I hope I am in the right forum, else please tell me otherwise!
1. Being a newbie I was wondering if I could accomplish the following without "DRM".
- Back up our Disk(Primary) storage pool every night.
- Perform a full backup of the database every night and run incremental backups Mon - Fri and copy data to tape - can I use copypool or ltopool?.
- Run Archive backups every weekend and month by backing up my primary storage pool(diskpool) to my Copypool(tapepool) and storing offsite and retaining that data for 1 month for weekly's tapes and 1 year for the monthly tape backups.
- Ship the database and copy storage pool volumes to an offsite location every day and be able to RESTORE them for up to a year?
2. From the link below I have been reading up on offsite storage and TSM:
http://www.redbooks.ibm.com/redbooks/pdfs/sg245416.pdf
The steps that you need to perform to send data offsite are:
1. Back up your vital data to the copy storage pools.
2. List all volumes that must be sent to offsite.
3. Check out volumes from the library.
4. Update the volume location to offsite.
Backup your vital data
Use the backup stgpool command to create copies of files that reside in a primary
storage pool, and store them in a copy storage pool. This is shown in
Example 13-35. File versions are only copied if they do not already exist in the
copy storage pool — if a file is already present in the specified copy storage pool,
then it is not recopied. However, if a copy of a physical file already exists in the
copy storage pool, but the copy is marked damaged, a new copy will be created,
provided that the primary physical file is not also marked damaged. The following
command backs up onsite data from the DISKDATA and DISKDIRS storage pool
to the OFFDATA and OFFDIRS storage pools respectively. (This task can also
be automated using a server script...
Offsite tape management to onsite
In this section we show how to move offsite volumes to the onsite location. These
offsite volumes either have no active data on them (status of EMPTY) or are
being returned to recreate damaged data in a primary storage pool.
Offsite tapes can be seen as your second good copy of critical data. As you
perform backup and archive operations, all data is saved in storage pools, which
are the basic unit for onsite operations. When you perform a backup stgpool
command, IBM Tivoli Storage Manager verifies which data has not previously
been sent to offsite yet and then performs the copy operation of any new data.
This means the operation is incremental and hence minimizes the amount of
time required to execute it.
As backup and archive data age and expire, the offsite tapes contain less and
less active data. Offsite tape reclamation consolidates these tape volumes,
replacing the partially filled tapes with full and empty tapes. The newly emptied
tapes remain in a pending state until after the reuse delay period has expired. At
this time the status of the tape changes to EMPTY. Empty tapes can be brought
back onsite and returned to the scratch pool.
3. And do I understand this correctly about Copypool's from above ?
Yesterday, I could NOT restore data from an "offiste Copypool tape because a volume was deemed "Empty" and either because the REUSE DELAY=0 or ?
I was unaware my Copypool tapes were expiring (expire inventory? process?)
So then, I set the access=readonly and it WAS deleted!!
What can I do about this if we don't run DRM and I want to use Copypool?
Should I just use Ltopool(tapepool)? Perhaps migrate from diskpool to the ltopool(tapepool)?
Or could I use the command: "backup stg diskpool ltopool"?
Would that preserve my data if my setting are correct?
I am unsure what parmaters to set to keep my data onsite(available) & offsite(available for restores up to a yr?) and not have TSM delete it periodically.
sory for the load of information here, hope somone can decipher and give some feedback.
Thanks for any help on the subject of "offsite storage".
srp