BO4 - Deleting report not removing report from underlying Filestore

[former_member272336]

Hi,

server team who do backups have advised about 600,000 files in filestore and this causing backups to take a while.

we have nowhere near that number of reports (primarily wid files) and assume this relates to the network of sub-folders business objects uses to store .wid files.

Is this the case?

Also, when we remove a report from test system would expect the underlying .wid file and network of sub-folders which stores it to diasppear from the filesystem but doesn;t look to be the case here.

Why is this?

Many Thanks

[former_member185603 · Accepted solution]

Regarding your 1st question - Instances will be stored in FRS. Report templates will be in Input FRS and schedules will be stored in Output FRS.

if you remove ,it should be removed from FRS. Before removing , note down the path of the report in FRS, and verify after it is deleted from system.

[former_member272336 · Accepted solution]

Hi,

Checked the properties of the .wid in the frs and can still see the file on filesystem of frs after deleting

Our instances limit se to 2 to keep output one as small as possible.

[former_member185603 · Accepted solution]

Can you check if Hotbackup is turned on in CMC? . That might be the reason, report was not deleted from FRS, eventhough you deleted.

Check the kb# 1983780

[DellSC · Accepted solution]

The file should be removed, but the folders aren't.  I recommend to my clients to "prune" the filestores about every 6 months.  To do this, you will require a down-time of about 30 minutes on your BO system.

Here are the steps:

1.  Stop the Job Server so that no schedules run while you're doing this.

2.  Stop the Input File Repository server and edit its properties.  Add " -prune" to the end of the command line.

3.  Start the Input File Repository server.  It will probably hang in the "initializing" state for several minutes while it clears out unneeded folders.

4.  Stop the Input File Repository server and edit its properties to take " -prune" off of the command line.

5.  Start the Input File Repository Server again.

6.  Repeat steps 2 through 5 for the Output File Repository Server.  Since you have instance limits, this might take longer to run.

7.  Restart the job server.

-Dell

[former_member185603 · Accepted solution]

Prune is not supported in 4.1. You can use Reposcan to delete empty folders and if there is any inconsistencies between CMS and FRS

[DellSC · Accepted solution]

That really sucks.  You shouldn't run Reposcan with repair on a production system because of the possibility for unintended consequences.  It's also more difficult to run, especially on large systems where it won't get to all of the objects because of resource limitations.  I once had to try to run it on a 4.0 system that had over 600 K objects - @25,000 objects at a time because it would die when it ran out of memory.

-Dell

[former_member136842 · Accepted solution]

Hi,

as already mentioned, probably due to the activated Hot Backup. After the configured Time period the document should disappear from the FRS.

Check also SAP Note 1901595.

Regards

-Seb.

[former_member272336 · Accepted solution]

Hi All,

Thanks for replies.

Yes - was down to hot backup being enabled.

Using 4.0 -prune looks useful

Why is it not supported in 4.1?

Thanks