Search String: Display: Description: Sort:

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*Backup\s+Versioning\s+\/\s+Retention\s+Policy\s+Survey\s*$/: 3 ]

Total 3 documents matching your query.

1. Backup Versioning / Retention Policy Survey (score: 1)
Author: "Merryman, John A." <JMERRYMAN AT PARTNERS DOT ORG>
Date: Mon, 3 Nov 2003 09:17:23 -0500
Hi TSMers, It's our understanding that industry standard TSM backup versioning policies (if there is such a thing) are the following: TSM Policy Setting Industry Standard Versions Data Exist 7 / 14**
/usr/local/webapp/mharc-adsm.org/html/ADSM-L/2003-11/msg00022.html (10,976 bytes)

2. Re: Backup Versioning / Retention Policy Survey (score: 1)
Author: John Naylor <john.naylor AT SCOTTISH-SOUTHERN.CO DOT UK>
Date: Mon, 3 Nov 2003 14:39:11 +0000
I expect you will get many replies, so here goes my small offering. 1) There is no such thing as an industry standard for backup 2) You need to find out/understand you r bisiness requirements for res
/usr/local/webapp/mharc-adsm.org/html/ADSM-L/2003-11/msg00024.html (12,469 bytes)

3. Re: Backup Versioning / Retention Policy Survey (score: 1)
Author: "French, Michael" <Michael.French AT SAVVIS DOT NET>
Date: Mon, 3 Nov 2003 14:03:26 -0600
John's right, there is no industry standard, everyone has to make their own based on the needs of their environment. My current settings are: Versions Data Exists: 8 Versions Data Deleted: 4 Retain E
/usr/local/webapp/mharc-adsm.org/html/ADSM-L/2003-11/msg00039.html (13,440 bytes)


This search system is powered by Namazu