Re: archive - inactive files?
With my idea, you would export dude2, so you won't lose the inactive files. Here's the order: 1. Rename dude1 to dude2 2. Register new dude1 3. Export dude2 Nick Cassimatis [EMAIL PROTECTED] He who laughs last has a good backup. Alexander Lazarevich <[EMAIL PROTECTED] To C.EDU>[EMAIL PROTECTED] Sent by: "ADSM:cc Dist Stor Manager" Subject <[EMAIL PROTECTED] Re: archive - inactive files? .EDU> 06/05/2004 11:30 AM Please respond to "ADSM: Dist Stor Manager" I still can't get confirmation from the manual: Does exporting a node preserve all the inactive (deleted) files? Secondarily, if I rename dude1 to dude2, won't I lose all the deleted files? I have to export dude1 to preserve the inactive files, assuming export preserves those, right? Thanks for the help, Alex On Fri, 4 Jun 2004, Nicholas Cassimatis wrote: > > > > > > Or rename node dude1 to dude2, and export dude2, register new dude1... > > Nick Cassimatis > [EMAIL PROTECTED] > > He who laughs last has a good backup. > > > > > "Stapleton, Mark" > <[EMAIL PROTECTED] > ERBEE.COM> To > Sent by: "ADSM: [EMAIL PROTECTED] > Dist Stor cc > Manager" > <[EMAIL PROTECTED] Subject > .EDU> Re: archive - inactive files? > > > 06/04/2004 07:49 > PM > > > Please respond to > "ADSM: Dist Stor > Manager" > > > > > > > From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of > Nicholas Cassimatis > >Unfortunately, that won't work to keep everything as it is now. The > >inactive files will expire per the rules established for them - after > your > >RetainExtra duration passes, you'll only have active files (except for > the > >Last Versions, retained per the RetainLast setting). > > > >You can setup a new management class with all settings at /no > limit, > >configure the client to use that for all files (new domain may work > best) > >run one last backup to rebind everything, then do the node rename. I > can't > >think of an easier way to do what Alex is trying to accomplish. > > I can: > > export node dude1 devc= > > The export will keep forever. dude1's data can be imported whenever it > is needed. > > Oh, and name the new node dude2. > > -- > Mark Stapleton > > <><><>
Re: archive - inactive files?
>I still can't get confirmation from the manual: > >Does exporting a node preserve all the inactive (deleted) files? The Admin Ref manual says of Export Node: "FILEData Specifies the type of files that should be exported for all nodes being exported to the server. This parameter is optional. The default value is NONE." If FILEData chooses backup data: "The server exports all backup versions of files..." >Secondarily, if I rename dude1 to dude2, won't I lose all the deleted >files? I have to export dude1 to preserve the inactive files, assuming >export preserves those, right? Review the TSM doc on how files expire... Policy retention by date will cause old versions (which are still represented in the TSM db) to age out over time. Policy retention by version causes old versions to shift out only upon the next backup of the same named file. And if you review the elements of the TSM db BACKUPS table, you will see that the timestamps involved are for when a file was backed up, and when it went inactive. So if you extend your policies, you can further delay expiration. In any case, your site should not be so concerned about Inactive files: they were supposed to go away by design anyway. Richard Sims
Re: archive - inactive files?
I still can't get confirmation from the manual: Does exporting a node preserve all the inactive (deleted) files? Secondarily, if I rename dude1 to dude2, won't I lose all the deleted files? I have to export dude1 to preserve the inactive files, assuming export preserves those, right? Thanks for the help, Alex On Fri, 4 Jun 2004, Nicholas Cassimatis wrote: > > > > > > Or rename node dude1 to dude2, and export dude2, register new dude1... > > Nick Cassimatis > [EMAIL PROTECTED] > > He who laughs last has a good backup. > > > > > "Stapleton, Mark" > <[EMAIL PROTECTED] > ERBEE.COM> To > Sent by: "ADSM: [EMAIL PROTECTED] > Dist Stor cc > Manager" > <[EMAIL PROTECTED] Subject > .EDU> Re: archive - inactive files? > > > 06/04/2004 07:49 > PM > > > Please respond to > "ADSM: Dist Stor > Manager" > > > > > > > From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of > Nicholas Cassimatis > >Unfortunately, that won't work to keep everything as it is now. The > >inactive files will expire per the rules established for them - after > your > >RetainExtra duration passes, you'll only have active files (except for > the > >Last Versions, retained per the RetainLast setting). > > > >You can setup a new management class with all settings at /no > limit, > >configure the client to use that for all files (new domain may work > best) > >run one last backup to rebind everything, then do the node rename. I > can't > >think of an easier way to do what Alex is trying to accomplish. > > I can: > > export node dude1 devc= > > The export will keep forever. dude1's data can be imported whenever it > is needed. > > Oh, and name the new node dude2. > > -- > Mark Stapleton > >
Re: archive - inactive files?
Or rename node dude1 to dude2, and export dude2, register new dude1... Nick Cassimatis [EMAIL PROTECTED] He who laughs last has a good backup. "Stapleton, Mark" <[EMAIL PROTECTED] ERBEE.COM> To Sent by: "ADSM: [EMAIL PROTECTED] Dist Stor cc Manager" <[EMAIL PROTECTED] Subject .EDU> Re: archive - inactive files? 06/04/2004 07:49 PM Please respond to "ADSM: Dist Stor Manager" From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Nicholas Cassimatis >Unfortunately, that won't work to keep everything as it is now. The >inactive files will expire per the rules established for them - after your >RetainExtra duration passes, you'll only have active files (except for the >Last Versions, retained per the RetainLast setting). > >You can setup a new management class with all settings at /no limit, >configure the client to use that for all files (new domain may work best) >run one last backup to rebind everything, then do the node rename. I can't >think of an easier way to do what Alex is trying to accomplish. I can: export node dude1 devc= The export will keep forever. dude1's data can be imported whenever it is needed. Oh, and name the new node dude2. -- Mark Stapleton <><><>
Re: archive - inactive files?
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Nicholas Cassimatis >Unfortunately, that won't work to keep everything as it is now. The >inactive files will expire per the rules established for them - after your >RetainExtra duration passes, you'll only have active files (except for the >Last Versions, retained per the RetainLast setting). > >You can setup a new management class with all settings at /no limit, >configure the client to use that for all files (new domain may work best) >run one last backup to rebind everything, then do the node rename. I can't >think of an easier way to do what Alex is trying to accomplish. I can: export node dude1 devc= The export will keep forever. dude1's data can be imported whenever it is needed. Oh, and name the new node dude2. -- Mark Stapleton
Re: archive - inactive files?
Unfortunately, that won't work to keep everything as it is now. The
inactive files will expire per the rules established for them - after your
RetainExtra duration passes, you'll only have active files (except for the
Last Versions, retained per the RetainLast setting).
You can setup a new management class with all settings at /no limit,
configure the client to use that for all files (new domain may work best)
run one last backup to rebind everything, then do the node rename. I can't
think of an easier way to do what Alex is trying to accomplish.
Nick Cassimatis
[EMAIL PROTECTED]
He who laughs last has a good backup.
"Rushforth, Tim"
<[EMAIL PROTECTED]
PEG.CA>To
Sent by: "ADSM: [EMAIL PROTECTED]
Dist Stor cc
Manager"
<[EMAIL PROTECTED] Subject
.EDU> Re: archive - inactive files?
06/04/2004 05:13
PM
Please respond to
"ADSM: Dist Stor
Manager"
You could rename dude1 to dude1_old.
Then register a new dude1.
Delete dude1_old when you no longer need the backups.
Or you could rename each filespace under dude1 and delete these renamed
filespaces when you no longer need them.
An archive will only archive files that exist on your node.
-Original Message-
From: Alexander Lazarevich [mailto:[EMAIL PROTECTED]
Sent: June 4, 2004 4:10 PM
To: [EMAIL PROTECTED]
Subject: archive - inactive files?
TSM 5.1.6.5 on 2K server.
- We are reinstalling our fileserver (linux).
- The new system must have the same exact hostname and IP.
- Lets call the current system dude1.
- Lets call the new system dude2.
- We want to keep the existing backup of dude1 on the TSM server,
including all active and inactive files.
- We want to start backing up the new dude2 system while dude1 still
exists on backups.
- dude1 is totally backed up, all active and inactive files. however,
dude1 no longer backs up, it is archived (but with inactive files).
- dude2 is backing up normally, active and inactive files, all the while
dude1 data is still on backups.
Is there any way to do this? I can think of 3 ways, but I'm not sure if
it's possible:
1) Archive dude1. Does archive keep inactive files? Or only active files?
We have to keep inactive files.
2) In the dsm.sys for dude2, change the nodename for dude2, so that it is
different from dude1. Then dude1 remains on backups, and dude2 looks
like a different client to the backup server. Then once the 30 day
retention expires on deleted files, rename dude2 to dude1 in the
dsm.sys file back to what it was originally. Does changing the nodename
delete inactive files, is it the same as performing a new full backup?
3) Change the nodename on all the files for dude1 that are ALREADY IN THE
DATABASE. Is this even possible?
Anyway, you can see my problem. We need to start backing up the new
system, and keep all the active and inactive files for the old system at
the same time.
Thanks in advance!
Alex
--- ---
Alex Lazarevich | Systems Administrator | Imaging Technology Group
Beckman Institute | University of Illinois | www.itg.uiuc.edu
--- ---
<><><>
Re: archive - inactive files?
Sorry, inactive files will expire based on your policy. So if you need to keep them then maybe rename the node, put it into a different policy domain with the policy that you require. (keeping inactive files for however long you want.) -Original Message- From: Alexander Lazarevich [mailto:[EMAIL PROTECTED] Sent: June 4, 2004 4:20 PM To: [EMAIL PROTECTED] Subject: Re: archive - inactive files? On Fri, 4 Jun 2004, Rushforth, Tim wrote: > You could rename dude1 to dude1_old. wont we lose all the inactive files for dude1? we have to keep inactive files. is there any way to go into the database and change the nodename on all entries owned by dude1? seems to me that wouldn't be possible, just to wierd... alex > Then register a new dude1. > > Delete dude1_old when you no longer need the backups. > > Or you could rename each filespace under dude1 and delete these renamed > filespaces when you no longer need them. > > An archive will only archive files that exist on your node. > > -Original Message- > From: Alexander Lazarevich [mailto:[EMAIL PROTECTED] > Sent: June 4, 2004 4:10 PM > To: [EMAIL PROTECTED] > Subject: archive - inactive files? > > TSM 5.1.6.5 on 2K server. > > - We are reinstalling our fileserver (linux). > - The new system must have the same exact hostname and IP. > - Lets call the current system dude1. > - Lets call the new system dude2. > - We want to keep the existing backup of dude1 on the TSM server, > including all active and inactive files. > - We want to start backing up the new dude2 system while dude1 still > exists on backups. > - dude1 is totally backed up, all active and inactive files. however, > dude1 no longer backs up, it is archived (but with inactive files). > - dude2 is backing up normally, active and inactive files, all the while > dude1 data is still on backups. > > Is there any way to do this? I can think of 3 ways, but I'm not sure if > it's possible: > > 1) Archive dude1. Does archive keep inactive files? Or only active files? >We have to keep inactive files. > > 2) In the dsm.sys for dude2, change the nodename for dude2, so that it is >different from dude1. Then dude1 remains on backups, and dude2 looks >like a different client to the backup server. Then once the 30 day >retention expires on deleted files, rename dude2 to dude1 in the >dsm.sys file back to what it was originally. Does changing the nodename >delete inactive files, is it the same as performing a new full backup? > > 3) Change the nodename on all the files for dude1 that are ALREADY IN THE >DATABASE. Is this even possible? > > Anyway, you can see my problem. We need to start backing up the new > system, and keep all the active and inactive files for the old system at > the same time. > > Thanks in advance! > > Alex > --- --- >Alex Lazarevich | Systems Administrator | Imaging Technology Group > Beckman Institute | University of Illinois | www.itg.uiuc.edu > --- --- >
Re: archive - inactive files?
On Fri, 4 Jun 2004, Rushforth, Tim wrote: > You could rename dude1 to dude1_old. wont we lose all the inactive files for dude1? we have to keep inactive files. is there any way to go into the database and change the nodename on all entries owned by dude1? seems to me that wouldn't be possible, just to wierd... alex > Then register a new dude1. > > Delete dude1_old when you no longer need the backups. > > Or you could rename each filespace under dude1 and delete these renamed > filespaces when you no longer need them. > > An archive will only archive files that exist on your node. > > -Original Message- > From: Alexander Lazarevich [mailto:[EMAIL PROTECTED] > Sent: June 4, 2004 4:10 PM > To: [EMAIL PROTECTED] > Subject: archive - inactive files? > > TSM 5.1.6.5 on 2K server. > > - We are reinstalling our fileserver (linux). > - The new system must have the same exact hostname and IP. > - Lets call the current system dude1. > - Lets call the new system dude2. > - We want to keep the existing backup of dude1 on the TSM server, > including all active and inactive files. > - We want to start backing up the new dude2 system while dude1 still > exists on backups. > - dude1 is totally backed up, all active and inactive files. however, > dude1 no longer backs up, it is archived (but with inactive files). > - dude2 is backing up normally, active and inactive files, all the while > dude1 data is still on backups. > > Is there any way to do this? I can think of 3 ways, but I'm not sure if > it's possible: > > 1) Archive dude1. Does archive keep inactive files? Or only active files? >We have to keep inactive files. > > 2) In the dsm.sys for dude2, change the nodename for dude2, so that it is >different from dude1. Then dude1 remains on backups, and dude2 looks >like a different client to the backup server. Then once the 30 day >retention expires on deleted files, rename dude2 to dude1 in the >dsm.sys file back to what it was originally. Does changing the nodename >delete inactive files, is it the same as performing a new full backup? > > 3) Change the nodename on all the files for dude1 that are ALREADY IN THE >DATABASE. Is this even possible? > > Anyway, you can see my problem. We need to start backing up the new > system, and keep all the active and inactive files for the old system at > the same time. > > Thanks in advance! > > Alex > --- --- >Alex Lazarevich | Systems Administrator | Imaging Technology Group > Beckman Institute | University of Illinois | www.itg.uiuc.edu > --- --- >
Re: archive - inactive files?
You could rename dude1 to dude1_old. Then register a new dude1. Delete dude1_old when you no longer need the backups. Or you could rename each filespace under dude1 and delete these renamed filespaces when you no longer need them. An archive will only archive files that exist on your node. -Original Message- From: Alexander Lazarevich [mailto:[EMAIL PROTECTED] Sent: June 4, 2004 4:10 PM To: [EMAIL PROTECTED] Subject: archive - inactive files? TSM 5.1.6.5 on 2K server. - We are reinstalling our fileserver (linux). - The new system must have the same exact hostname and IP. - Lets call the current system dude1. - Lets call the new system dude2. - We want to keep the existing backup of dude1 on the TSM server, including all active and inactive files. - We want to start backing up the new dude2 system while dude1 still exists on backups. - dude1 is totally backed up, all active and inactive files. however, dude1 no longer backs up, it is archived (but with inactive files). - dude2 is backing up normally, active and inactive files, all the while dude1 data is still on backups. Is there any way to do this? I can think of 3 ways, but I'm not sure if it's possible: 1) Archive dude1. Does archive keep inactive files? Or only active files? We have to keep inactive files. 2) In the dsm.sys for dude2, change the nodename for dude2, so that it is different from dude1. Then dude1 remains on backups, and dude2 looks like a different client to the backup server. Then once the 30 day retention expires on deleted files, rename dude2 to dude1 in the dsm.sys file back to what it was originally. Does changing the nodename delete inactive files, is it the same as performing a new full backup? 3) Change the nodename on all the files for dude1 that are ALREADY IN THE DATABASE. Is this even possible? Anyway, you can see my problem. We need to start backing up the new system, and keep all the active and inactive files for the old system at the same time. Thanks in advance! Alex --- --- Alex Lazarevich | Systems Administrator | Imaging Technology Group Beckman Institute | University of Illinois | www.itg.uiuc.edu --- ---
archive - inactive files?
TSM 5.1.6.5 on 2K server. - We are reinstalling our fileserver (linux). - The new system must have the same exact hostname and IP. - Lets call the current system dude1. - Lets call the new system dude2. - We want to keep the existing backup of dude1 on the TSM server, including all active and inactive files. - We want to start backing up the new dude2 system while dude1 still exists on backups. - dude1 is totally backed up, all active and inactive files. however, dude1 no longer backs up, it is archived (but with inactive files). - dude2 is backing up normally, active and inactive files, all the while dude1 data is still on backups. Is there any way to do this? I can think of 3 ways, but I'm not sure if it's possible: 1) Archive dude1. Does archive keep inactive files? Or only active files? We have to keep inactive files. 2) In the dsm.sys for dude2, change the nodename for dude2, so that it is different from dude1. Then dude1 remains on backups, and dude2 looks like a different client to the backup server. Then once the 30 day retention expires on deleted files, rename dude2 to dude1 in the dsm.sys file back to what it was originally. Does changing the nodename delete inactive files, is it the same as performing a new full backup? 3) Change the nodename on all the files for dude1 that are ALREADY IN THE DATABASE. Is this even possible? Anyway, you can see my problem. We need to start backing up the new system, and keep all the active and inactive files for the old system at the same time. Thanks in advance! Alex --- --- Alex Lazarevich | Systems Administrator | Imaging Technology Group Beckman Institute | University of Illinois | www.itg.uiuc.edu --- ---
