Forum Discussion

snawaz3's avatar
snawaz3
Level 6
12 years ago
Solved

TIR with move detection

My backup policies contained TIR with move detection selected. I read that TIR does not allow file level restore. It allows only folder level restore. I unchecked TIR with move detection and ran a full backup. The backups do not contain all the folders. Why did this happen and how can I get my backup to backup all folders.

 

 

  • That is possible and known as incremental forever, but when it was first introduced there was a lot of talk about it and eventually the "advice" was to run a real one once a month to ensure you had a verified stable copy of the backup - the fear was that corruption could creep in I have some customers who only do a real one once a year but it is your choice how and if you do a real one Your real issue is that a job that takes 7 to 8 days is just unacceptable and really your place needs to invest in acheiving a better result than that - either by using multiple streams as we talked about in your other thread or by investing in de-dupe, or being able to use a snapshot technology on this data - even the Enterprise client to do flashbackup backups
  • For Synthetic you must use TIR with move detection I would generally only do Synthetic to disk and ensuring i had enough disk space to hold everything needed - generally enough for three full copies of a backup - that being the last full, all the incrementals and the next full you are about to create De-Dupe using accelerator would be a better option if you had the licensing or funds to do it - would be way faster for you.
  • do not have de dupe. i am sure i have enough disk storage. so my regular full with TIR selected should complete by wednesday. if i do a differntial on wednesday evening and a cummulative increment with synthetic selected on thursday, would that be enough to do a full backup with synthetic selected on friday?
  • As long as you have a real Full and a real incremental then you will be able to do a Synthetic Full afterwards It is worth having schedules for each - so maybe a real full once a month, incrementals daily and sysnthetic fulls weekly Hope this helps
  • from what i read i got the impression that i would have to do a normal full just once. then the differentials and the cummulative incremental, after that the synthetic full. the cummaltive incremental would consolidate all the differentials and the normal full. after that the synthetic full would become the base line for the cummalative incremental. i would not have to do another normal full. the problem is with the normal full. that is the one that runs for 7 to 8 days. i was hoping to get 1 normal full done and out of the way.
  • That is possible and known as incremental forever, but when it was first introduced there was a lot of talk about it and eventually the "advice" was to run a real one once a month to ensure you had a verified stable copy of the backup - the fear was that corruption could creep in I have some customers who only do a real one once a year but it is your choice how and if you do a real one Your real issue is that a job that takes 7 to 8 days is just unacceptable and really your place needs to invest in acheiving a better result than that - either by using multiple streams as we talked about in your other thread or by investing in de-dupe, or being able to use a snapshot technology on this data - even the Enterprise client to do flashbackup backups
  • Thanks mark_solutions. I am trying to stepup snapshot and am getting an error message. i am creating a new thread for this.