![](v3_space.gif) |
![](v3_space.gif) |
![](v3_space.gif) |
![](v3_space.gif) |
![](v3_space.gif) |
![](v3_space.gif) |
![](v3_space.gif) |
![](v3_space.gif) |
![](v3_space.gif) |
![](v3_space.gif) |
![](v3_space.gif) |
![](v3_space.gif) |
![](v3_space.gif) |
![](v3_space.gif) |
![](v3_space.gif) |
![](v3_space.gif) |
![](v3_space.gif) |
![](v3_space.gif) |
Ø |
Deleting
object creates a tombstone.
|
|
|
|
Ø |
Object
moved to a specific container
|
|
|
|
Ø |
Used
to replicate deletion process
|
|
|
|
Ø |
Object
still in the database
|
|
|
|
Ø |
Physically
deleted after tombstone lifetime expires
|
|
|
|
Ø |
Enterprise-wide
setting
|
|
|
CN=Directory
Service, CN=Windows NT, CN=Services,
|
|
and so
on.
|
|
|
|
Ø |
Remember:
Tombstone lifetime = backup lifetime
|
|
|
Ø |
How
does the database release space again?
|
|