Author: "Hyde, Don (CC-LAN Services)" <DON.HYDE AT CONAGRA DOT COM>
Date: Thu, 2 Nov 2000 09:57:21 -0600
Hi, Sorry for the seeming simplicity of this question. We have been getting good incremental backups through the command line scheduler. We have been running these backups in parallel with existing p
Author: "Joshua S. Bassi" <jbassi AT GLORYWORKS DOT COM>
Date: Thu, 2 Nov 2000 08:31:31 -0800
You can: 1) delete the existing filespaces off the *SM server, but that would leave you in jeopardy in the event you lose a disk on the NetWare box and hadn't yet backed up the client, 2) have your *
Author: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU]On Behalf Of
Date: Sun, 04 Oct 2015 17:26:31 -0500
Hi, Sorry for the seeming simplicity of this question. We have been getting good incremental backups through the command line scheduler. We have been running these backups in parallel with existing p
Or use Rename Filespace to keep the old one for a while. Alternately, if you can rename the volume whose contents you are sending, or use a variant node name, that would do it. You should be able to
Author: "Prather, Wanda" <Wanda.Prather AT JHUAPL DOT EDU>
Date: Thu, 2 Nov 2000 15:30:48 -0500
When we want to "start from scratch", we rename the client's filespaces on the ADSM server. (to something like filespacename-OLD) The next time the client backs up, it will back up everything again.