Browse Community
Help
Log In
Responses(4)
Solutions(0)
bingo.1
2.4K Posts
1
August 17th, 2016 19:00
In the 'old' times, the functionality was different:
nsrclone was used to copy save sets
nsrstage was the utility to migrate them
With the option 'nsrclone -m' staging could also be done with 'nsrclone'.
So EMC decided to stop development of 'nsrstage' and proceed with nsrclone, in general.
ledugarte
96 Posts
August 18th, 2016 10:00
Hello.
Why you decided to kept your indexes backed up until your backup retention time expiration?. Why don't save index separatelly with a group with less retention policy? If you need to browse a non browsable backup, you can rebuild this index solely.
pp4eto
2 Posts
0
August 20th, 2016 14:00
Project team has wanted this. And it will take time to change it , because of approvals and etc
August 21st, 2016 00:00
Just keep in mind that the connection to the CFI location will be fast enough - if not it will limit backup/recover throughput.
Dell Support Resources
View All
Top
bingo.1
2.4K Posts
1
August 17th, 2016 19:00
In the 'old' times, the functionality was different:
nsrclone was used to copy save sets
nsrstage was the utility to migrate them
With the option 'nsrclone -m' staging could also be done with 'nsrclone'.
So EMC decided to stop development of 'nsrstage' and proceed with nsrclone, in general.
ledugarte
96 Posts
1
August 18th, 2016 10:00
Hello.
Why you decided to kept your indexes backed up until your backup retention time expiration?. Why don't save index separatelly with a group with less retention policy? If you need to browse a non browsable backup, you can rebuild this index solely.
pp4eto
2 Posts
0
August 20th, 2016 14:00
Project team has wanted this. And it will take time to change it , because of approvals and etc
bingo.1
2.4K Posts
0
August 21st, 2016 00:00
Just keep in mind that the connection to the CFI location will be fast enough - if not it will limit backup/recover throughput.