Archieve Backup

winprod

ADSM.ORG Member
Joined
Sep 7, 2011
Messages
17
Reaction score
0
Points
0
PREDATAR Control23

We use archiving for long term storage (5 years)
I have a script for a full backup and a script for a incremental backup.
Is there anyway to do a archive backup in of my exchange mailboxes.
 
PREDATAR Control23

Is there anyway to do a archive backup in of my exchange mailboxes.

How are we backing up the Exchange mailboxes?
Are we backing up the Exchange mailboxes via the TSM Backup/Archive Client?
Or are we using the Tivoli Data Protection aka ITSM for Mail now known as IBM Spectrum Protect for Mail ?

Good Luck,
Sias
 
PREDATAR Control23

How are we backing up the Exchange mailboxes?
Are we backing up the Exchange mailboxes via the TSM Backup/Archive Client?
Or are we using the Tivoli Data Protection aka ITSM for Mail now known as IBM Spectrum Protect for Mail ?

Good Luck,
Sias
Hi we are using Tivoli Data Protection
 
PREDATAR Control23

Since the Exchange database is being backed up via the TDP.
Bad news. Can not perform archive for long term storage.
Nor can you convert a backup to archive or visa versa.

Solution:
- Dump the data into a flat file and use the TSM B/A Client to archive the data.

Good Kuck,
Sias
 
PREDATAR Control23

Got this from support.

Using a different nodename to keep the Exchange database backups for long term retention

Server configuration:

1.Define a node on the TSM server which will be used exclusively for keeping the long term backups.
e.g. register node TDPEXCHKEEP<pwd> domain=<domain name>

2.Under the domain the 'tdpexchkeep' node belongs to, create a management class which will be used for extended retentions
e.g. define mgmtclass <domain name> <policy set> TDPEXCHKEEPCLASS

3. Under this class, create a BACKUP copy group with the desired retentions. For example, if you plan on running a backup for long term retention once a month and want to retain it for 1 year:
e.g. define copygroup <domain name> <policy set> TDPEXCHKEEPCLASS type=backup destination=<pool name> vere=nolimit verd=nolimit rete=365 reto=365

NOTE: The use of NoLimit ensures that all copies for this node will stay in storage based on the two retention values. At a minimum, it would need to be set to 12 to ensure a full year stays in storage for this example.

4.After creating the copy group you must activate the policy set to see the changes
e.g. activate policyset <domain name> <policy set>

Data Protection configuration:

1. Once the server steps are completed you can begin to use the DP GUI/Cmdline to do perform the backups and keep these for long term retention. To accomplish this, the nodename configured for keeping the backups must be used. Create a copy of your current TDP options file, and modify the nodename to use the 'tdpexchkeep' nodename

2.After modifying your options file to use the 'tdpexchkeep' node, either start your TDP GUI or Cmdline with this option file
e.g. tdpexc /tsmoptfile=<x:/full path to file/tdpkeep.opt>
tdpexcc /tsmoptfile=<x:/full path to file/tdpkeep.opt>

3. Authenticate with the server, and verify that the correct nodename is being used. If this is true, then you have successfully configured the TDP client to connect as the 'tdpexchkeep' node. Log off and proceed to the next step

4. After authentication, you need to configure the optfile to point the data to the correct class. Edit your TDP tdpkeep.opt options file and add an include parameter to point to the class your defined above ( you may need to use vsspolicy instead of includes)
e.g. include "SERVER1\Storage Group 1\...\*" TDPEXCHKEEPCLASS or vsspolicy

NOTE: Use the TDP for Exchange manual to see different syntax examples for include/exclude and vsspolicy processing..

To invoke a backup that is to kept for long term retention, you will be running a backup of the database. Since this is being sent to a management with extended retentions it will mimic an 'archive' in that the data will be saved on the TSM Server for a longer period of time. To run this you must login using the 'tdpexchkeep' nodename as you did above. After running a backup using the 'tdpexchkeep' nodename, use the following select statement on the server to verify the data is bound to the correct management class. If the class name is incorrect, review the include syntax for errors. The select statement needs to be run by the TSM Administrator via the TSM

Administrative commandline (dsmadmc):
e.g. select filespace_name,hl_name,ll_name,backup_date,class_name from backups where node_name='TDPEXCHKEEP
 
PREDATAR Control23

Thank you for the update.
Learn something new every day with TSM.

Since there are going to be two nodes.
One for daily backup and one for long term data retention.
Need to make a note somewhere about this. So in the future when you need to restore the data from the long term backup, need to know what node name was used.

Good Luck,
Sias
 
PREDATAR Control23

Actually there is a way to use the same node.

In TDP for Exchange, in the VSS Policy bingding configuration, you can specify a management class for:
  • * (all)
  • Full
  • Incremental
  • Differential
  • and copy
Taken from TDP for Exchange user guide:
Copy Backup (VSS)
A copy backup is similar to a full backup except that transaction log files
are not deleted after the backup. A copy backup is used to make a full
backup of the Exchange Server database without disrupting any backup
procedures that use an incremental or differential backup.

So the COPY backup is the one you will need to set to your monthly management class like MC_MONTHLY.
Full and incremental should be set to your daily backup management class like STANDARD or MC_DAILY, that's up to you.

So in you tdpexc.cfg you would have something like this:
VSSPOLICY * * FULL * STANDARD
VSSPOLICY * * INCREMENTAL * STANDARD
VSSPOLICY * * COPY * MC_MONTHLY


Then create a script exccopy.cmd that will run tdpexcc like this:
tdpexcc backup * copy /tsmoptfile=dsm.opt /skipintegritycheck /logfile=excsch.log >> exccopy.log

Create a schedule for this backup, define the association and you're all set.
The same principle applies to TDP for SQL by the way.
 
PREDATAR Control23

Copy Backup (VSS)
A copy backup is similar to a full backup except that transaction log files
are not deleted after the backup. A copy backup is used to make a full
backup of the Exchange Server database without disrupting any backup
procedures that use an incremental or differential backup.

I seem to have over looked the above in the manual.
I would suspect that the steps that you have would be a supported process.


Thank You!
Sias
 
Top