> 3.1 isn't supported at all anymore,
Actually support ends January 31st, 2001
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of
Scott McCambly
Sent: Tuesday, November 28, 2000 2:22 PM
To: [EMAIL PROTECTED]
Subject: Re: How to archive daily
inal Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of
Michel Engels
Sent: Tuesday, November 28, 2000 7:56 AM
To: [EMAIL PROTECTED]
Subject: Re: How to archive daily/monthly/weekly
I did receive almost the same request of our users and started some tests,
thinking th
Hello,
The two solutions suggested so far will both work, but I wanted to point
out some issues with each.
First - with Backup Sets, the obvious problem is that they are not
supported at your ADSM Level of 3.1. 3.1 isn't supported at all anymore,
so I would imagine you will be upgrading soon. T
I did receive almost the same request of our users and started some tests,
thinking that a daily backup and a yearly archive were the only possibilities.
But then I started thinking of using backupsets. Our users wanted to go a little
further and have a daily copy, a weekly copy, a monthly copy an
Hi I would think you'd want:
-1 default backup with verexits set to 10 ( if you want to ensure a file changed
everyday could be restored to a specific version for a day for 10 days)
- 1 default archive group set to 1 year retention run each month
- 1 additional archive group set to 7 year reten
Hello ADSM admins,
A customer has a request for a bacup/archive and I'm not really sure how to
implement this
so that both these requirements are met and the ADSM server has the least
data to keep.
The customer has a directory on a server (NT) where he wants something
like:
1) daily backups re
